Raspberry Pi打破了SD卡？无法格式化

Question

所以,我有一个来自CnMemory的8GB SDHC.我用它来做我的Raspberry Pi.它到目前为止工作.但后来我的覆盆子冻结了(无法通过ssh连接,apache也没有回应).所以我把力量拉了出来.我重新启动了覆盆子.这次是我的显示器.FS似乎腐败了.我做了fsck并解决了问题.重新启动shutdown -r.现在它根本不会开始.好的,所以我想我需要为它添加一个空白的新图像.

我不能.GParted告诉我,该卡只有1GB而不是8GB.

# fsck /dev/mmcblk0 
fsck from util-linux 2.20.1
e2fsck 1.42.8 (20-Jun-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

fdisk和fdisk/dev/mmcblk0导致以下结果

# fdisk
[...]
Disk /dev/mmcblk0: 1073 MB, 1073741824 bytes
4 heads, 16 sectors/track, 32768 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mmcblk0 doesn't contain a valid partition table

# fdisk /dev/mmcblk0 
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xccf88a5e.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): w
The partition table has been altered!

它冻结了.它说它已被改变但它并没有被卡在那里.

Windowssystem无法将SDCard格式化为获得I/O错误.

这是第二个出现此问题的SD卡!

我希望你知道如何解决这个问题.谢谢!

---

编辑:

当我尝试擦除分区表时,dd也会冻结.

# dd if=/dev/zero of=/dev/mmcblk0 bs=512 count=1

---

EDIT2:

dmesg节目 invalid allocation unit size

如果我尝试使用mkfs编写,则会出现一些错误.

# mkfs /dev/mmcblk0 --type=ext4
mke2fs 1.42.8 (20-Jun-2013)
Warning: could not erase sector 2: Attempt to write block to filesystem resulted in short write
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376

Allocating group tables: done                            
Warning: could not read block 0: Attempt to read block from filesystem resulted in  short read
Warning: could not erase sector 0: Attempt to write block to filesystem resulted in short write
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/8
Warning, had trouble writing out superblocks.

# dmesg
mmc0: SD Status: Invalid Allocation Unit Size
[...]

几个小时后我完全打破了吗？