fsck.ext3: No such file or directory while trying to open

I got a error message when it's booting.

fsck.ext3: No such file or directory while trying to open /dev/VolGroup01/LogVol0

Here is my server information.
OS: Oracle Enterprise Linux Server release 5.4
kernel: 2.6.18-164.el5xen
fstab: /dev/VolGroup01/LogVol0 /oradate ext3 default 1 1

1) I tried fsck -f /dev/VolGroup01/LogVol0

fsck.ext3: No such file or directory while trying to open /dev/VolGroup01/LogVol0

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193


2) I tried e2fsck -b 8193 /dev/sda

e2fsck: Device or resource busy while trying to open /dev/sda Filesystem mounted or opened exclusively by another program?


3) I tried lvm lvs

Locking type -1 initialization failed


Please help me to boot up my server. Thank you.
tmonkeysAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
ls -li /sbin/fsck*

if you are missing it, create a hard link to an existing as all fsck.* should have the same inode

ln /sbin/fsck.ext2 /sbin/fsck.ext3
0
MazdajaiCommented:
Sounds like /var is readonly. Try booting from a live or rescue CD and run the same commands.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
arnoldCommented:
Misread/misinterpreted the error.
Look whether you can run fsck on /dev/mapper/VolGroup01-LogVol0

pvdisplay
vgdisplay
Lvdisplay
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Distributions

From novice to tech pro — start learning today.