The "no such file or directory" sound more like the LV cannot be found.
What does "lvdisplay" say?
Regards,
Dennis
On 01/30/2012 06:56 PM, Jason T. Slack-Moehrle wrote:
> Hi All,
>
> One of my servers upon a restart today comes up with an error
>
> checking filesystems:
>
> fsck.ext3: no such file or directory while trying to open /dev/VolGroup-1/Logvol00.
>
> /dev/VolGroup-1/LogVol00. 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<device>
>
> I dropped into the shell and tried mounting:
>
> mount -t ext3 /dev/VolGroup-1/LogVol00
>
> I tried booting to media and do 'linux rescue' but it could not mount file filesystems either and nothing at all ends up in /mnt/sysimage.
>
> I think this was caused by installing quotas and changing /etc/fstab to add ,usrquota,grpquota.
>
> There are 2 x 1tb drives, software raid, mirrored.
>
> Can anyone provide advice on how to solve? I would think if I could get /etc/fstab edited back to normal I would be all set.
>
> -Jason
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
