How to check file system for errors?

MasterC · 08-29-2003, 08:57 PM

Quote:

Originally posted by subzero0
Sorry for this error. The reiserfsck program is on the cd and loads from the command line in rescue boot.

I tried single and ro as boot time options but recieved the same reiserfsck error i always do: "This partition is loaded with write permissions. Cannot continue" or something to that effect. So no progress was made there.

I tried the "shutdown -r -F now" command but did not yield any information about my fstab but instead, "surprise surprise", shutdown my computer.

That's what it's supposed to do

It shuts down and forces an FSCK upon reboot

Cool

subzero0 · 08-30-2003, 05:29 PM

Fstab looks good:

/dev/hdb1 / reiserfs notail 1 1
none /dev/pts devpts mode=0620 0 0
/dev/hdb6 /home reiserfs notail 1 2
none /mnt/cdrom supermount dev=/dev/hdc,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0
none /mnt/cdrom2 supermount
........

I suppose the which ever boot script is used to check the fs for errors is not smart enought to use reiserfsck when the partition is of type reiserfs.

Does anyone know where to change this value?

quatsch · 08-30-2003, 05:57 PM

try this. As root
mount -o remount -o ro /
This should remount the / file system read only. Then try run reiserfsck.

subzero0 · 09-02-2003, 05:02 PM

Quote:

Originally posted by quatsch
try this. As root
mount -o remount -o ro /
This should remount the / file system read only. Then try run reiserfsck.

Using this i was finally able to check the fs for errors. One was found and to fix it reiserfsck told me to rerun the program with --fix-fixable to repair this inconsistency. After trying this the program exited with an error citing, "mounted w/ write permissions cannot check partition." Is there a way to mount this partition so that "reiserfsck --fix-fixable" can make the necessary changes to the partition?

quatsch · 09-02-2003, 07:52 PM

Quote:

"mounted w/ write permissions cannot check partition."

this seems to be saying that the file system is mounted read-wrte. To run the check, it has to be mounted read-only again. But I guess if you do that, you can't fix the file system. You could get Knoppix or some other linux that can run from a CD and run the file system check. Or if you have 500MB or so to spare, you could do a very minimal install of mandrake there (basically no X windows and anything that needs X, no servers, etc) and run the fsck from there.