fsck repeat error in linux kernel 2.6

[chuikingman]

Hi,
When I boot the linux kernel 2.6 , I was kicked out and request to run fsck manually.
After running fsck -y /dev/vg00/lvol3 and /dev/vg00/lvol4 and reboot,
I still get the same error and request me to run fsck .
I attach the console output in here .
Please advice to fix it ....

[Rubberman]

Well, you obviously have some sort of serious problem with the file system. What are the error messages you get when you run fsck manually?

[proopnarine]

Were you able to drop to the shell and run fsck? And if so, do as Rubberman (Hi Rubberman! I haven't logged in for a long time!) suggested and post all the output. You should also, if possible, boot from non-hard drive medium, such as a bootable USB stick. From there, you can mount the offending drives, run fsck, and see what happens. I recently fixed a friend's computer (running Ubuntu) this way; he had the same error as you do, but I cannot say if the causes are related.

[jspring]

Try running Knoppix from a USB or CD drive. e2fsck or e2fsck -p are safer than fsck. The man page for both says it's unsafe to run fsck or e2fsck on mounted filesystems, so you should boot from another device listed in the BIOS. Good luck!

[praveen_parim]

There are 2 ways of doing this safely
1.Take down system to single user mode and unmount system.
2.Boot from cd into linux rescue mode.

If u r using step 1.
#init 1
#umount /
#fsck / or #e2fsck -y /
answer yes or just hold the enter key until it clears.

if u r using step 2
Put the cd say ubuntu or redhat
At the boot prompt type
linux rescue nomount
#fsck / or #e2fsck -y /dev/....whatever u wanna scan for..

That's it.Also have a watch on your fstab.Sometimes when u do rsync to sync servers some problems occur.anyways forget rsync now choose any one of the above steps .

bye
praveen

[chuikingman]

Well, you obviously have some sort of serious problem with the file system. What are the error messages you get when you run fsck manually?

I paste the screen output of the console .
I run fsk -y /dev/vg00/lvol4
Please advice ...

[chuikingman]

There are 2 ways of doing this safely
1.Take down system to single user mode and unmount system.
2.Boot from cd into linux rescue mode.

If u r using step 1.
#init 1
#umount /
#fsck / or #e2fsck -y /
answer yes or just hold the enter key until it clears.

if u r using step 2
Put the cd say ubuntu or redhat
At the boot prompt type
linux rescue nomount
#fsck / or #e2fsck -y /dev/....whatever u wanna scan for..

That's it.Also have a watch on your fstab.Sometimes when u do rsync to sync servers some problems occur.anyways forget rsync now choose any one of the above steps .

bye
praveen

Hi,
I use method 1 , I still get the same problem.
I have run
fsck -y /
fsck -y /dev/vg00/lvol4

I still get the same probelm after reboot ...
I copy the console output in here
Please advice as I have no redhat linux CD ..

[praveen_parim]

did you go to init 1 and then umount /dev/vg00/lvol4
Then run fsck.You can do it individually or
just do this then


#init 1
#mount -n -o remount /
#fsck /dev/vg00/lvol04
here answer yes, hope things come up.If it clears for lvol04 then u r on right track.Again error may come for other vol.Do the same.
#init 6


In the hindsight wanted to know what caused this prob.Some hard disk swapping or anything could have happened.If the cause is known it's very simple to fix.
praveen

[chuikingman]

did you go to init 1 and then umount /dev/vg00/lvol4
Then run fsck.You can do it individually or
just do this then


#init 1
#mount -n -o remount /
#fsck /dev/vg00/lvol04
here answer yes, hope things come up.If it clears for lvol04 then u r on right track.Again error may come for other vol.Do the same.
#init 6


In the hindsight wanted to know what caused this prob.Some hard disk swapping or anything could have happened.If the cause is known it's very simple to fix.
praveen

I still get the same error .
The JPG file fsck_err3a 3b is the screen I run fsck /dev/vg00/lvol4
The JPG fsck_err3c is the screen I run init 6 ..the same error is present ..

Please advice ...

[praveen_parim]

#debugfs -w /dev/vg00 -R "features ^resize_inode"

it will ask for the partition give the partition
#fsck.ext3 -f /dev/vg00

Hope it clears.