我的笔记本电脑上安装了 Linux Mint 12。昨天我像往常一样关闭了它，今天早上当我启动它时，我看到了一个错误屏幕。
（翻译自瑞典语）
检查 /home 磁盘单元时发现致命错误
我可以选择忽略、跳过手动恢复。我首先尝试忽略，这只是将范围缩小到跳过和手动恢复。
在手动恢复模式（以root身份提示）我尝试过fsck.ext4 -p /dev/sda3。
fsck.ext4: Device or resource busy while trying to open /dev/sda3
Filesystem mounted or opened exclusively by another program?
所以我启动了 Linux Mint 12 的实时版本。该分区没有像其他分区那样出现在 nautilus 中。我试过fsck.ext4 -p /dev/sda3
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda3
The superblock could not be read or does not describe a correct ext4
filesystem. If the device is valid and it really contains an ext4
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>
我读了一篇关于该问题的教程并输入mke2fs -n /dev/sda3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
4218880 inodes, 16852736 blocks
842636 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
515 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
我在该列表中选择了一个随机数 294912，然后输入e2fsck -b 294912 /dev/sda3
e2fsck 1.41.14 (22-Dec-2010)
One or more block group descriptor checksums are invalid. Fix<y>? yes
Group descriptor 0 checksum is invalid. FIXED.
...
Group descriptor 512 checksum is invalid. FIXED.
/dev/sda3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #1 (31743, counted=24413).
Fix<y>? yes
(then there's about 100 more of that but different groups)
Free blocks count wrong for group #465 (32768, counted=30402).
Fix<y>? yes
Free blocks count wrong (16541927, counted=13884226).
Fix<y>? yes
Free inodes count wrong for group #208 (8192, counted=8183).
Fix<y>? yes
(10 more of these)
Free inodes count wrong (4218869, counted=4214769).
Fix<y>? yes
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 4111/4218880 files (2.1% non-contiguous), 2968510/16852736 blocks
然后我安装/dev/sda3到/mnt.这些文件使用 ecryptfs 进行加密。我用ecryptfs-recover-private它给了我 /tmp 中的文件。它们看起来没有损坏。
为什么我的超级块在启动时会“重新损坏”自身？快速 SMART 测试显示磁盘正常，没有坏扇区。