Tag Info

New answers tagged

3

For our ec2 ubuntu instance, the above answers did not work completely. On Ubuntu, by default, the check is not enabled in the rcS file. So Edit rcS file sudo vi /etc/default/rcS below the line #FSCKFIX=no Add FSCKFIX=yes Then do as suggested above. sudo touch /forcefsck Reboot from ec2 console. Delete the line FSCKFIX=yes to get back rcS ...


0

Simply edit the file /etc/default/rcS Uncomment and set FSCKFIX=yes /etc/default/rcS # automatically repair filesystems with inconsistencies during boot FSCKFIX=yes and reboot! Do remember to put it back afterwards.


0

I have run fsck -V -y twice on my 2TB RAID1 ext4 USB-mounted LaCie disks. In each case, the process ran 24 hours with visible progress but without completing. In each case, I killed the process and ran fsck -V -C -y which finished in minutes. Parameter -C is just supposed to provide a progress bar, but it seems to cancel some huge timewaster as well.


0

Firstly, in aborting a file system shrinking half-way through you have probably unrecoverably roached the file system; that is, you won't get it back as it was. Secondly, the fsck seems to have reconnected a bunch of valid-but-disconnected inodes under /home/lost+found, and you're going to go through this directory hoping to find important files. The ...


0

For md3 it reports "Creation Time : Wed Mar 4 01:03:28 2015", that seems rather recent to be the true creation date. Perhaps a recreate was done? In any case where this is RAID1 you should be able to run testdisk against one of the partitions and let it search for a filesystem. Try... testdisk /dev/sda3 Note in data recovery situations it is a mistake ...


0

Having the RCU Scheduler issue a warning/info is not a problem which would cause a reboot. Double check your log files and see if those messages are WARN/INFO or ERR/PANIC. per the documentation here: https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt These should be info messages. If you are manually rebooting the machine because of these ...


0

shutdown has -F for Force fsck on reboot. # shutdown -rF now It will create file /forcefsck and restart. You could also force fsck on next reboot by creating a file /forcefsck manually. # touch /forcefsck # reboot This is useful if the errors in the filesystem prevents you from using shutdown command.



Top 50 recent answers are included