Thanks Steve, I did as you suggested. fsck -N -V /dev/hda5 indicated the correct EXT2 filesystem fsck -V /dev/hda5 worked OK. No errors detected. running fsck again showed /dev/hda5 to be clean. However the ERROR ! cannot fsck because root is not read only message still appears during the boot A few lines later there is the message /dev/hda5 is rw Restore device permissions Do I simply, as root, use konquerer to set the permissions of /dev/hda5 to user R, group R where user is root and group is disk ? At present user is R and W and grout is R and W. -- John steve wrote:
On Sunday 30 June 2002 05:09, John Sved wrote:
During the boot sequence I see the following message on screen.
ERROR ! cannot fsck because root is not read only.
This started afer using mkinit or mk_init following the removal of a NIC module. That was fixed but since then the ERROR message occurs.
How should I restore the normal fsck after 20 boots.
/dev/hda5 is the root
What is the correct command to make root read only at boot time and restore the normal operation?
-- John
Boot up into single user by adding single to the boot line. I.e. 'linux single'. Then you'll get to a root login prompt. Login and run your fsck on /dev/hda5. Remember that your fsck should match the type of filesystem you use. I don't do it often enough to remember if it does that automatically. Though I think it would exit with a code if you use it on a wrong type.