我的筆記型電腦上安裝了 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 的即時版本。我試過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 測試顯示磁碟正常，沒有壞磁區。