[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] recover LVM system



Hi Heinz!

thanks for your reply.

On Tue, 28 Jan 2003, Heinz J . Mauelshagen wrote:

> you've got no LVM prblem but rather a filesystem one unless
> direct access to the LV fails
> (i.e. "dd if=/dev/system/data of=/dev/null bs=1k count=1024").

zeus:/home/bailong # dd if=/dev/system/data of=/dev/null bs=1k
count=1024
1024+0 records in
1024+0 records out
zeus:/home/bailong #

This doesn't sound good :-(. I tried to add a volume with yast2,
rebooted the computer and he couldn't mount it anymore. I was panicing
and tried to create a new LVM, but didn't create any new FS (is yast2 doing
it automatically?)

> What do mount and fsck display ?

zeus:/home/bailong # mount /dev/system/data /data
mount: you must specify the filesystem type

zeus:/home/bailong # mount -t ext3 /dev/system/data /data
mount: wrong fs type, bad option, bad superblock on /dev/system/data,
       or too many mounted file systems

zeus:/home/bailong # fsck /dev/hda5
fsck 1.26 (3-Feb-2002)
e2fsck 1.26 (3-Feb-2002)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open
/dev/hda5

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>

fsck.ext2 /dev/hda5 failed (status 0x8). Run manually!

zeus:/home/bailong # fsck /dev/hdb5
fsck 1.26 (3-Feb-2002)
e2fsck 1.26 (3-Feb-2002)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open
/dev/hdb5

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>

fsck.ext2 /dev/hdb5 failed (status 0x8). Run manually!

Seems no recovery possible....

Cheers
Sven



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]