On Thu, 11 Jan 2001, Fikret Can wrote:
> The following error is displayed on the console;
>
> EXT2-fs error (device ide0(3,2)): ext2-new block: free blocks count
> corrupted for block group 9
Whups. Bad karma!
> I know it is related to "fsck.ext2". My question arises, when fsck
> is run on an mounted fs, ext2.fsck /dev/hda1, it warns that severe
> damage may occur. What can i do after reboot to put Linux in maintanence
> mode and run fsck on an unmounted fs.
You don't even need to reboot.
mount -remount,ro /dev/hda1
then run fsck /dev/hda1
You might can then reverve it by doing
mount -remount,rw /dev/hda1
Alternately, when you reboot, hit TAB at the lilo: prompt and type
linux single
which will boot you to single user mode, and mount only your / filesystem
in read only mode to allow for fsck to be run properly.
Actually, the act of rebooting should do this for you - fsck is run on
startup in every distribution I know of, and if the inital brief scan
can't fix the problem, it'll drop to maintenance mode {I.E. single user
mode}, and you can do it from there.
DaZZa
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
