I use Red hat Linux. One day I had to restart my system due to hang up. after that when ever I boot in Linux following text appers:

checking root file system
/dev/hda5 contains a file system error, check forced
/dev/hda5:
unattached inode 5628

/dev/hda5: unexpected inconsistency; Run fsck Manually
( i.e., without -a or -p options)

[Failed]
*** An error occured 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):

On typing Control-D above thing repeat again but on giving the root password, following line appears. I do not no what to do thereafter.Please help.

(Repair filesystem) 1 #

hi
when such messages appear, u wait until the system gives u a shell to work on. enter the root password and type fsck /dev/hda5 or what ever ur filesystem name is. then press enter. the system will try repairing the file system. follow onscreen instructions. after successful completion of the fsck, press ctrl+D and the system reboots into normal modes.

further problems plz contact me

I just got the same problem uttamsaxena have this afternoon. I am also a newbie and almost opted to just reinstall Linux. I kept trying to run fsck /dev/hda2 because of the examples that I saw in the man pages. But after reading this thread and then looking closely at my screen, it was actually pointing to "/" instead of "/dev/hda2". Anyhow, I run fsck / and all is well now. Thanks!

Why does this happen? My previous shutdown was fine so I don't understand why.

Hello: I wanted to post a new thread for this problem, but the forum suggested that I add to this one instead because the problem is similar. Hope I can get some guidance with this situation on my Caldera edesktop 2.4 original unmodified distro. It installs just fine on my old Cyrix P-166+ system with 64MB of RAM (in the minimum package selection, desktop and recommended freeze up during install). Then after a shutdown and restart the file system check fails. I get a message in the upper left hand corner that says "Login as root to perform maintenance or press Ctrl-D for normal startup". If I provide my root password, nothing happens and no "shell" appears. If I type Ctrl-D, I get the level 6 kill all signal and then nothing. Will my emergency boot disk made during the installation process work to fix this problem, and if so, how? If I could get a shell, I could try the fsck dev/hda6 or "/" repair suggested elsewhere in this thread. Thanks so much for the assist. james91911

boot your machine using a boot CD and go into rescue mode. Edit the /etc/inittab file and check what is the default runlevel set to. It should not be 6 or 0. set it to either 3 or 5 and thinggs will work fine

Thank you very much for the reply subhasis_ray. One question: I have three floppy disks for my Caldera edesktop 2.4. One is a Lizard Boot Disk, one is a Lisa Boot Disk and the other is the emergency boot disk I made during the install. Which would you suggest I use to edit the file holding the run levels? Thanks so much.
james91911

Hi,

You boot from the disk which you used for installing the system. Once the intial boot screen comes, you will find the option of going into rescue mode. Use that.

Thanks, that clears that point up. I will add to this post if I have any more problems with this file system error. Have a great day. james91911.

Hi,
I was going to post a new thread when it was suggested I use this thread.

I have a Redhat 9 AS 3.0 system, dual boot with win2k. It has been working fine.

Recently, I installed pcsc-lite & ccid drivers for smart card. While running ./configure for both, I gave --prefix=/usr. After make, make install, I rebooted. The system wont boot properly.

The grub loads, and I can boot successfully with the Win2k. When I choose linux, the initial startup goes on, till it reaches the Init stage. There I get the following messages ( they are not verbatim, and I am only posting some, the rest are other tasks which also [ FAIL ])

-----------------------quote-----------------------------
"
Activating swap partitions [ FAIL]
initlog: error loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directory
initlog: error loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directory
Host: Athena [FAIL]
initlog: error loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directoryinitlog: error loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directory
Checking Root File system [ WORK]
Mounting local filesystem [ FAIL]

*** An error occurred during file system check. Dropping you to a shell;
*** the system will reboot when you leave the shell
"
-----------------------unquote-----------------------------
It gives me an option to type in root password or press Ctrl-D to continue.
When I give the root password, I get to a shell, Repair Filesystem.

I read other posts on this and other forums, and did a few steps.

/etc/fstab is as follows
-----------quote ----------------------
LABEL=/ / ext3 defaults 11
LABEL=/boot /boot ext3 defaults 12
none /dev/pts
....
....
...
and so on
------------------------------unquote---------------
All seem to be fine.

Running df gives
---------------quote ----------------------
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda6 2016488 270772 1643280 15% /
/dev/hda2 2016488 270772 1643280 15% /boot
none 2016488 270772 1643280 15% /dev/pts
none 2016488 270772 1643280 15% /dev/shm
/dev/hda5 2016488 270772 1643280 15% /home
/dev/hdb5 2016488 270772 1643280 15% /mnt/drv01
/dev/hdb6 2016488 270772 1643280 15% /mnt/drv02
/dev/hda8 2016488 270772 1643280 15% /tmp
/dev/hda3 2016488 270772 1643280 15% /usr
/dev/hda9 2016488 270772 1643280 15% /var
----------------unquote-------------------------------------

Running e2fsck on the individual partitions gives no errors
-----------quote----------------
/boot: clean, 39/26529 files, 1377/105840 blocks
...
...
and so on
----------unquote--------------------------

When I exit out of the shell, system says,
----------quote--------------------------
rm: cannot remove '/halt': Read only file system
/etc/rc/d/rc/sysint: line 595 : /var/run/utmpx: No such file or directory
----------unquote--------------------------


I booted using the Redhat CDRom , in the linux rescue mode. I am able to start with networking, and was able to view all the partitions, access any file under various users, etc.

I am not sure what other information any expert would need to fix my problem. I am guessing(hoping) that it is not serious, since I did not explicitly delete any files, only installed some smartcard drivers(pcsc-lite and ccid under /usr ( "[pcsc-lite-@athena] ./configure --prefix=/usr"] ).

Can someone please help me fix any problems, so I can have a normal booting Graphical Linux system like before.

Thanks in advance.

Hi,

I really am new to this so it might sound trivial. I have tried booting my system running mandrake and it does not go beyond the point that it asks that I enter a run level after displaying these messages:

INIT: No inittab file found
hda: dma_intr: error=0x40{uncorrectable error}, LBAsect=6570092, sector=6570087
hda:dma_intr:sattus=0x51{DriveReady Seekcomplete error}

Is that to say my hard disk has crashed?

Hello daloengy. Your hard drive would appear to be just fine. You did not say what version of Mandrake you are using, but my problems were always with older versions of Mandrake, Caldera etc. using the ext2 file system. If you would look at the post by subhasis_ray (#7) above, you will see that he recommended that I use the rescue mode of my boot disk to fix the problem. In that it was an ongoing problem that seems to crop up with ext2, I have graduated to newer versions that use ext3 or reiserfs. Good luck. james91911.

When trying to boot my system I get dropped into a shell with
the Repair filesystem prompt.

So I run e2fsck -pf /dev/hdb6

I get a message that says:

ERROR: Couldn't open /dev/null (Read-only file system)
/var: 8056/66264 files (2.7% non-contiguous), 134989/265041 blocks

I get the above error message on all the partitions...

What is wrong with /dev/null?

What do I need to fix?



Many thanks.

John,
When you get dropped to the prompt, and it gives you this error, try:
mount -o remount,rw /

This will remount the / filesystem as read/write.

I did a: mount -o remount,rw /


I get back:
mount: could not open /proc/partitions, so UUID and LABEL conversion cannot be done.

mount: no such partition found



If I type: mount
I get back a list of partitions...all show up as: (rw)

But if I try a unmount any one of them via: umount /whatever
I get a message:
umount: /dev/hdb6: not mounted

(hdb6 changes for each /whatever...)

I'm still lost...

What else should I try?

Many thanks!

So my problem is that when I run e2fsck I get an error telling me that /dev/null could
not be opened.

When I try an mount / to fix /dev/null I get a messages that:
mount: could not open /proc/partitions, so UUID and LABEL conversion cannot be done.
mount: no such partition found

I can to a ls-alt /dev/null I get:
-rw-r--r-- 1 root root 39 Oct 2 04:02 /dev/null

Which does not match another Linux system I have access to.

when I do a rm -fr /dev/null I get
rm: cannot unlink '/dev/null': Read only file system

So I seem to be stuck...can't mount the file system for RW, can't run 2efsck,
can't fix /dev/null

Am I missing anything?
What else could I try?

Many thanks!