fsck at boot

AlexWilMac

AlexWilMac

Moderator
I've googled a lot to find a way to force fsck on main hdd/ssd but I'm not sure over the solution suggested because you have no sign of anything.
Someone says you have to create an empty file named forcefsck in root.
Is it right?
And, if so, which devices will it check for?
After boot the main device (the one which stores records) is /dev/sda1 but how can I pass this parameter to fsck command the way it is described above?
It seems better to launch a specific script but how exactly?
 
Hi

I am in the same situation although using VTI Image on a Solo 2. The scripts in /etc/init.d seem not to honor a /forcefsk file.

I think the best is currently to use shutdown with -F to force a fsck on reboot, for example inside a telnet or ssh session to the box:
shutdown -F -r now

This will restart the box and hopefully do a fsck. You do not need to provide /dev/sda1 or so, as this is recorded in fstab to be mounted as the main hdd.

There are also some settings in /etc/defaults/rcS, but the
ENABLE_ROOTFS_FSCK=yes
and
FSCKFIX=yes
seem also not be evaluated by the /etc/init.d/ scripts (checkroot.sh and mountall.sh).

I will appreciate any help on these.

~Josef
 
I managed to let the box do a fsck at boot but now it is stuck somewhere in fsck with no network access. I am unable to connect to the box and need to disconnect the hdd or so...

The scripts say something about that network should be started regardless of a fsck, but that does not work too. Seems the scripts are all broken in regards of what they should do.

For the box the hdd is independend of the nand boot image and it should start network and then the fsck without issue.

Will see what is next...
 
You must log in or register to reply here.
Back
Top