我很好奇这是怎么发生的？我周末回来，不得不重启两个无关服务器，显示相同的类似消息：
fsck from util-linux 2.26.2
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck
Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
我必须fsck手动运行这两台服务器，而且两台服务器都很容易修复。问题是，一台是数据库服务器（生产），另一台是 Web 开发（非生产）服务器。这是怎么回事？我上班时两台服务器都在运行……两台服务器在重启时都失败了。顺便说一下，这些是虚拟驱动器……使用 VMWare ESXI Hypervisor。
我以为可能是“不干净”关机（断电），但机器正在运行，并且只是在fsck完成之前不会重新启动。
更新 我刚刚fsck在同一个 Hypervisor 应用程序中的另一台非生产服务器上运行 - 这就构成了 3 台服务器：
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
Warning! /dev/mapper/ywpData--vg-root is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/mapper/ywpData--vg-root: clean, 384516/6266880 files, 16531831/25039872 blocks
e2fsck 1.42.13 (17-May-2015)
Warning! /dev/sda1 is mounted.
/dev/sda1 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
Free blocks count wrong (100531, counted=295192).
Fix? no
Free inodes count wrong (124599, counted=124616).
Fix? no
/dev/sda1: 329/124928 files (16.1% non-contiguous), 398157/498688 blocks