Hello,

I tried to shutdown improperly on several servers to see what happen, and they all self fixed fine.

On this one server when I shutdown improperly, it has this during boot up "Unexpected Inconsistency: Run fsch manually".

I reinstalled RH 7.1 and improperly shutdown (turn off the power switch) several times. Each time, it gives me this.."Unexpected Inconsistency: Run fsch manually".

Advise?

Most of the time on a improper shutdown a server on boot up can put the pieces of the filesystem back together when it runs fsck at bootup, but depnding on what was running when the system was improperly shutdown and what file systems got corrupted, it may be necc. to perform a manual fsck, you can do this by simply putting in the root password and typing at the # sign, fsck /whateverpartitionis messed up..

so if its says /home has a problem you would type:

fsck /home

then you basically answer yes to all the questions it asks

Thanks for your answer.

The weird thing is I never had this problem on the other servers.
On the other servers, I turn it on shut it down improperly several times. No problem at all.

On this sever, it boots up with ".."Unexpected Inconsistency: Run fsch manually" message every time I shutdown improperly. Fixing it is not a problem, but having this message for every improper shutdown doesn't look right.

Originally posted by Asia

On this sever, it boots up with ".."Unexpected Inconsistency: Run fsch manually" message every time I shutdown improperly. Fixing it is not a problem, but having this message for every improper shutdown doesn't look right.

Your partitions might be overlapped with each other. Try 'fdisk', and see if it complains.

There is no warning when I run fdisk.


I don't know why suddenly it works smoothly.
I purposely power off/on several times, and I don't get that message anymore.

That's weird. I think I have to play with this server several times.

:cool:

Originally posted by Asia
There is no warning when I run fdisk.


I don't know why suddenly it works smoothly.
I purposely power off/on several times, and I don't get that message anymore.

That's weird. I think I have to play with this server several times.

:cool:


:) That's weird, maybe it is hardware related. Or maybe a DMA problem. Try running the system for days and if the problem arise again, disable DMA from BIOS and see if it solves the problem.

We kept getting that on that server that I posted about in another thread, the problem is on early kernels, this loves to pop up anytime you shutdown improperly

It was driving me nuts, we were ready to have Amax pick up the server (they happen to be in the same city as our datacenter) but at the last second, I had our datacenter re-boot, run fsck manually, then we upgraded to 2.4.17 kernel and it has been working fine ever since.

The kernels that we were running when that error kept occuring was 2.4.2-2 and 2.4.9-12

you can also do a shutdown -f 0 and it will run fsck on reboot

Hi!
If you are sure that the filesystem is clean then you can disable this feature of checking at boot time.

Here's how....

The first is that if the file /etc/fastboot exists, no checks are made. The second is that the ext2 filesystem has a special marker in its superblock that tells whether the filesystem was unmounted properly after the previous mount. This allows e2fsck (the version of fsck for the ext2 filesystem) to avoid checking the filesystem if the flag indicates that the unmount was done (the assumption being that a proper unmount indicates no problems). Whether the /etc/fastboot trick works on your system depends on your startup scripts, but the ext2 trick works every time you use e2fsck. It has to be explicitly bypassed with an option to e2fsck to be avoided.

I have copied the above from this site.
http://www.linuxhq.com/guides/SAG/x1038.html#AEN1289
It is a good link and worth reading.
However, I would suggest enabling check at boot time unless it is a real pain... :)

Have a great day :)

regards
amar