SuperBlock（超级块）损坏导致系统无法正常启动

SuperBlock（超级块）损坏导致系统无法正常启动
问题现象：
开机后，硬件检测完毕，加载系统文件，提示如下错误：
Couldn’t find ext2 superblock, trying magic number in superblock while trying to open /dev/sdi 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
Is a directory while trying to open/ [FAILED]
***An error occurred during the file system check.\
***Dropping you to a shell; the system will reboot
***When you leave the shell
Give root password for maintenance( or type Control-D to continue):

---

解决方案1：
最简单的修复步骤——修改fstab文件

但修复模式是无法对fstab进行直接编辑的，需先执行mount -o remount, rw /命令，即——以可读写方式重新挂载根文件系统，执行完毕后，再对fstab进行编辑

---

解决方案2：
还有一种修复步骤是采用修复超级块的方式，比较麻烦，详细修复步骤见下方

解决步骤：输入root密码登入修复模式
1、登入后执行命令mke2fs -n /dev/sdi提示时按y确定 查看分区信息最后一行的数字就是超级块所在，随便用一个

2、然后输入命令fsck -b查到的数字/dev/sdi修复，返回下面的结果时修复成功
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/sdi was not cleanly unmounted, 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
/dev/sdi: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdi: 11/26104 files (9.1% non-contiguous), 8966/104388 blocks

3、重新格式化，慎用，如上述操作还是没有返回第二步的执行成功显示，则请输入mkfs.ext3 /dev/sdi提示时按y确定，这两条命令执行完后重启服务器
如果mount命令发现有的分区变成了ro
可以试试先umount后再mount