Hi, I'm a Red Hat Linux beginner.

How should I exit from the system when reaching the point where you type your ID and password when entering. I restart my PC, but I suppose that is wrong because every time I enter Red Hat, the system begins checking because of "Incorrect unmount".

And now I have another problem. Now the system is no longer able to finish the ckecking described in the previous paragraph, reporting the following:

checking root filesystem
/dev /hdc 6 contains a file system with errors, check forced
/dev /hdc 6:
Unattached inode 313338

/dev /hdc 6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
(i.e., without -a or -p options)
FAILED
*** An error ocurred during the file system check
*** Dropping you to a shell; the system will reboot
*** when you leave the shell

Give root password for maintenance
(or type Control-D for normal startup):

Thank you very much

To shutdown your system you should type:
To fix your current problem:
1) Give the root password at the prompt. This should bring you into single user mode.
2) type fsck /dev/hdc6
3) Reboot

If you are still having problems let us know.

How, then, can you run fsck on a mounted AND busy partition?

Good catch bjc, I must have been in a hurry when I typed that. Step 1.5 would be to make sure that the filesystem is not mounted. If it it is not possible to unmount the partition (say /sbin or / is on the bad partition) then you would need to boot with a floppy. If you need any more info let us know.

I have a similar problem upon bootup. Only sometimes do I have the option to enter root password for maintenance though. The rest of the time, I get a series of errors that preclude "Code: 84 3b...", a kernel panic message, and a sync problem. When I do enter the root password it crashes also. Any recommendations?

ph

More On Forced Checks
 

I have a similar problem to that posted above with a Mandrake KDE installation. e2fsck detects errors on boot, reports at length, claims to have fixed the problems with blocks and inodes, but the "fix" doesn't stick. I have compounded my issue by running this install as an img file rather than on an actual partition and haven't quite figured out what to throw on a boot disk. . . I've also looked at debugfs which appears to have better manual tools than e2fsck but. . . has its own complexities.

Thanks for your thoughts!