fsck 计划重新启动-被忽略?

fsck 计划重新启动-被忽略?

最近我的服务器发生电源故障,这显然导致硬盘损坏:

sudo fsck -n
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
Warnung!  /dev/mapper/pdc_gahfdjcb2 ist mounted.
Warnung: Überspringe Journal-Wiederherstellung, da das Dateisystem im Nur-Lesen-Modus ist.
/dev/mapper/pdc_gahfdjcb2: sauber, 1716458/91226112 Dateien, 270400467/364881664 Blöcke
fsck.fat 3.0.26 (2014-03-07)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
 Automatically removing dirty bit.
Leaving filesystem unchanged.
[...]

作为参考,我的fstab样子是这样的:

/dev/mapper/pdc_gahfdjcb2 /          ext4  errors=remount-ro,usrquota,grpquota,acl 0       1
/dev/mapper/pdc_gahfdjcb1 /boot/efi  vfat  defaults        0       1
/dev/mapper/pdc_gahfdjcb3 none       swap  sw              0       0

由于我无法轻松地在服务器上运行实时磁盘,因此我想安排fsck在重启时执行:

sudo touch /forcefsck
sudo init 6

重启后,/forcefsck消失了,但驱动器没有修复 - 输出sudo fsck -n相同。我怀疑它fsck尚未启动,因为启动时间太短了。

知道为什么fsck可能无法运行吗?

相关内容