Hi compdict,
Welcome to TSG!
First, fsck requires that when run against a disk's filesystem, that the disk be unmounted - was your disk unmounted?
There is a field in the super block that sets the number of reboots without an fsck to about 30, then on the 31st reboot, fsck will run during bootup.
Do not attempt to run fsck separately against / or /home as fsck is intended to be run against an entire file system.
If you have a Linux Live CD, and you can boot from it - i.e. BIOS boot order specifies CD before hard drive, you can determine if your disk(s) are unmounted (by running the mount command with no parameters), unmount the disk (if necessary) with the umount /dev/xxxx command (where xxxx is the devices' name of the disk which the mount command will tell you), and run fsck with the command (from root account):
# script -c fsck fsck.out
where the script command will capture the output of the fsck command in the file fsck.out
If you manage to do this, post the output in this thread. When fsck is successfully run against a disk, the superblock count for the number of reboots without an fsck will be reset to 0, and again be able to be counted up to the limit.
-- Tom
__________________ The independence created by philosophical insight is - in my opinion - the mark of distinction
between a mere artisan or specialist and a real seeker after truth. - Einstein 1944
Imagination is more important than knowledge. - Einstein
Last edited by lotuseclat79 : 30-Jun-2008 10:25 AM.
|