“/lib/init/rw/rootdev contains a file system with errors, check forced”

本文记录了一次因系统更新过程中物理重启导致的Ubuntu启动故障，并详细描述了使用fsck命令检查和修复文件系统的全过程，最终成功解决了问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

故障起源于我手賤：看到系统提示有更新就点了安装，结果安装进行到一半时系统突然停止响应，于是物理重启。结果导致在开机画面（进度条）进行到约三分之一处，系统跳到命令行并提示：

/lib/init/rw/rootdev contains a file system with errors, check forced

...

并提示需要手动fsck检查。

输入命令root@ubuntu~/# fsck结果如下：

root@ubuntu:/# fsck fsck 1.41.3 (12-Oct-2008) e2fsck 1.41.3 (12-Oct-2008) /host/ubuntu/disks/root.disk is mounted. WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)? yes /host/ubuntu/disks/root.disk: recovering journal /host/ubuntu/disks/root.disk contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Entry '%gconf.xml' in /home/ysong/.gconf/apps/gnome-screensaver (456214) has deleted/unused inode 456869. Clear<y>? yes Entry 'opera6.ini' in /home/ysong/.opera (513440) has deleted/unused inode 514425. Clear<y>? yes Entry 'index.ini' in /home/ysong/.opera/mail (513996) has deleted/unused inode 514509. Clear<y>? yes Entry 'http%3A%2F%2Favatar.profile.youkuaiyun.com%2FF%2F4%2F1%2Fwendyjin2000.ico' in /home/ysong/.opera/images (514005) has deleted/unused inode 514962. Clear<y>? yes Entry 'dcache4.url' in /home/ysong/.opera/opcache (514017) has deleted/unused inode 514959. Clear<y>? yes Entry 'opr002BW' in /home/ysong/.opera/opcache (514017) has deleted/unused inode 514534. Clear<y>? yes Entry 'opr002BX' in /home/ysong/.opera/opcache (514017) has deleted/unused inode 514537. Clear<y>? yes Entry 'opr002BZ' in /home/ysong/.opera/opcache (514017) has deleted/unused inode 514683. Clear<y>? yes Entry 'opr002CF' in /home/ysong/.opera/opcache (514017) has deleted/unused inode 514937. Clear<y>? yes Entry 'opr002CY' in /home/ysong/.opera/opcache (514017) has deleted/unused inode 514978. Clear<y>? yes .... Pass 3: Checking directory connectivity Pass 4: Checking reference counts Unattached zero-length inode 8169. Clear<y>? yes Unattached zero-length inode 8174. Clear<y>? yes Unattached zero-length inode 73430. Clear<y>? yes Unattached inode 81730 Connect to /lost+found<y>? yes Inode 81730 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81738 Connect to /lost+found<y>? yes Inode 81738 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81739 Connect to /lost+found<y>? yes Inode 81739 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81741 Connect to /lost+found<y>? yes Inode 81741 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81759 Connect to /lost+found<y>? yes Inode 81759 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81760 Connect to /lost+found<y>? yes Inode 81760 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81761 Connect to /lost+found<y>? yes Inode 81761 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81763 Connect to /lost+found<y>? yes Inode 81763 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81764 Connect to /lost+found<y>? yes Inode 81764 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81765 Connect to /lost+found<y>? yes Inode 81765 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81766 Connect to /lost+found<y>? yes Inode 81766 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81768 Connect to /lost+found<y>? yes Inode 81768 ref count is 2, should be 1. Fix<y>? yes Unattached inode 81769 Connect to /lost+found<y>? ... Free blocks count wrong for group #31 (9175, counted=9142). Fix<y>? yes Free blocks count wrong for group #38 (230, counted=71). Fix<y>? yes Free blocks count wrong for group #39 (5713, counted=5461). Fix<y>? yes Free blocks count wrong (1026047, counted=1028105). Fix<y>? yes Inode bitmap differences: -68780 +81730 +(81738--81739) +81741 +(81759--81761) +(81763--81766) +(81768--81772) +81774 +(81776--81780) +81782 +81784 +81787 +(81789--81790) +81792 +(81795--81800) +(81802--81803) +81805 +238756 +(255585--255610) +(306209--306270) +(306272--306273) +(306277--306278) -(320318--320320) +456624 -456869 +458933 -514067 -514388 -514425 -514468 -514509 -514534 -514537 -514664 -514683 -514698 -514703 -514708 -514755 -514768 -514868 -514870 -514889 -514932 -(514935--514941) -514944 -(514958--514959) -(514961--514962) -(514972--514991) -(514993--514996) -(514998--515004) -(515006--515016) -(515018--515021) -(515023--515027) -(515029--515035)y -(521936--521943) Fix<y>? yes Free inodes count wrong for group #8 (4148, counted=4149). Fix<y>? yes Free inodes count wrong for group #10 (6595, counted=6558). Fix<y>? yes Free inodes count wrong for group #31 (5090, counted=5064). Fix<y>? yes Free inodes count wrong for group #37 (3278, counted=3212). Fix<y>? yes Free inodes count wrong for group #39 (3086, counted=3089). Fix<y>? yes Free inodes count wrong (554853, counted=554728). Fix<y>? yes /host/ubuntu/disks/root.disk: ***** FILE SYSTEM WAS MODIFIED ***** /host/ubuntu/disks/root.disk: ***** REBOOT LINUX ***** /host/ubuntu/disks/root.disk: 300392/855120 files (1.4% non-contiguous), 2389863/3417968 blocks

一路按"Y“后重启，结果发现错误依旧。

参考Wubi的网站说明［2］，进行如下操作：

#fdisk -l

则系统会列出硬盘的区：

/dev/sda1

/dev/sda2

/dev/sda3

...

我的Wubi是装在F盘的，为/dev/sda5

所以就敲命令：

root@ubuntu:~/# mkdir /win

结果提示为Read-only filesystem