You might try # dumpe2fs /dev/<your device> | grep superblock Then from this output - if you can get any - use one of the backup superblocks with #e2fsck -b <number from above output> /dev/VolGroup00/<logical volume> > -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Jason T. Slack-Moehrle > Sent: 31 January 2012 02:38 > To: CentOS mailing list > Subject: Re: [CentOS] One of my servers wont boot today > > > > > It says: > > > > > > > > /dev/VolGroup00/. 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> > > > > > > > > So I tried e2fsck -b 8193 /dev/VolGroup00 > > > > > > > > and it seems I get the same error coming up over and over > > > > > > > > I tried: > > > > > > > > fsck -y b=8193 /dev/VolGroup00 as well > > > > > > > > Any thoughts? > > > > > > You need to fsck each logical volume, not the whole volume group, > e.g. > > > > > > e2fsck -b 8193 /dev/VolGroup00/LogVol01 > > sure, I thought of that too. > > > > under /dev/VolGroup00 is LogVol00, LogVol01, LogVol02. > > > > I do e2fsck -b 8193 /dev/VolGroup00/LogVol00 and I get the same super > block error above. > > > > Same with LogVol01 and 02. > Forgot: > > e2fsck: Bad magic number in super-block while trying to open 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> > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos