Very Computer

From the shell, ran e2fsck -f on all Linux partitions.
The root partition had a couple of problems which fsck
supposedly fixed. (No critical files were affected, it
seems.  Interestingly, the affected files were ones I
had copied over from a DOS partition using automatic
CRLF-LF conversion.)  Rebooted, but got the same error
as before.  Reran e2fsck -f on all Linux partitions
again, all were reported as OK.  I only checked the
ext2 partitions, although there are a few non-Linux
partitions (FAT, HPFS, etc.); I assume fsck ignores
those, so even if they had a problem (I don't think
they do) that wouldn't seem to be an issue.

What is going on here?  I assume it is e2fsck that is
detecting the problem and returning an error code during
boot, so why doesn't it identify a problem when I run it
from the shell?  More urgently, how can I repair the
problem so I can boot Linux again?

(Yes, in case anyone is wondering, I ALWAYS do a normal
shutdown.  I am well aware how disastrous it can be to
power off the machine without shutting down first.)

Any help on this will be GREATLY appreciated, since a
reformat/reinstall does not especially appeal to me...

Regards,
Marty

Quote:>With the file system check during boot, get a report:
>   *** An error occurred during the file system check
>   ***   (blah, blah...)

>From the shell, ran e2fsck -f on all Linux partitions.
>The root partition had a couple of problems which fsck
>supposedly fixed. (No critical files were affected, it
>seems.  Interestingly, the affected files were ones I
>had copied over from a DOS partition using automatic
>CRLF-LF conversion.)  Rebooted, but got the same error
>as before.  Reran e2fsck -f on all Linux partitions
>again, all were reported as OK.  I only checked the
>ext2 partitions, although there are a few non-Linux
>partitions (FAT, HPFS, etc.); I assume fsck ignores
>those, so even if they had a problem (I don't think
>they do) that wouldn't seem to be an issue.

>What is going on here?  I assume it is e2fsck that is
>detecting the problem and returning an error code during
>boot, so why doesn't it identify a problem when I run it
>from the shell?  More urgently, how can I repair the
>problem so I can boot Linux again?

But if your root partition is mounted rw, then fsck will be UNABLE to
properly fix any problems. RTFM about root partitions, try and boot off
a recovery disk and run fsck from there, etc etc.

On SCO, you ran fsck with the -b option, which unmounted it, fixed it,
and forced a reboot. When I tried to fix a crashed Slackware system I
had some fun. Just remember, you MUST NOT run fsck over a filesystem
mounted rw, and you should be able to sort things out after a couple of
tries.
--
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
Trousers with a single hole in their waistband are topologically equivalent
to a doughnut. These sugarcoated trousers have yet to catch on at fast-food
outlets! (SuperStrings by F. David Peat)

If replying by e-mail please mail wol. Anything else may get missed amongst
the spam.