tmonkeys
asked on
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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