[linux-lvm] recover LVM system

[linux-lvm] recover LVM system

[Sven Falk]

Hi,

seems I can't mount my LVM anymore, here are the details:

I created a logical volume called data containing the partitions hda5
and hdb5 on Suse 8.0. Here is the output from:

zeus:/home/bailong # pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE   PV "/dev/hda5" of VG "system" [50.98 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/hdb5" of VG "system" [57.26 GB / 40 MB
free]
pvscan -- total: 2 [108.26 GB] / in use: 2 [108.26 GB] / in no VG: 0
[0]

zeus:/home/bailong # vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "system"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your
volume group

zeus:/home/bailong # lvscan
lvscan -- ACTIVE            "/dev/system/data" [108.20 GB]
lvscan -- 1 logical volumes with 108.20 GB total in 1 volume group
lvscan -- 1 active logical volumes

Actually I can't mount the /dev/system/data anymore :-(

Cheers
Sven

Re: [linux-lvm] recover LVM system

[Heinz J . Mauelshagen]

Sven,

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").

What do mount and fsck display ?

Regards,
Heinz    -- The LVM Guy --


On Mon, Jan 27, 2003 at 07:20:06PM +0100, Sven Falk wrote:
> Hi,
> 
> seems I can't mount my LVM anymore, here are the details:
> 
> I created a logical volume called data containing the partitions hda5
> and hdb5 on Suse 8.0. Here is the output from:
> 
> zeus:/home/bailong # pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/hda5" of VG "system" [50.98 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/hdb5" of VG "system" [57.26 GB / 40 MB
> free]
> pvscan -- total: 2 [108.26 GB] / in use: 2 [108.26 GB] / in no VG: 0
> [0]
> 
> zeus:/home/bailong # vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "system"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your
> volume group
> 
> zeus:/home/bailong # lvscan
> lvscan -- ACTIVE            "/dev/system/data" [108.20 GB]
> lvscan -- 1 logical volumes with 108.20 GB total in 1 volume group
> lvscan -- 1 active logical volumes
> 
> Actually I can't mount the /dev/system/data anymore :-(
> 
> Cheers
> Sven
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] recover LVM system

[Sven Falk]

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

Re: [linux-lvm] recover LVM system

[Sven Falk]

Hi Heinz!

On Tue, 28 Jan 2003, Sven Falk wrote:

> 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 #

Got it. Finally I was able to fix the problem, I didn't understand
that I have to use /dev/system/data for the fsck, after running e2fsck
on the LVM he recovered all data. I'm happy ;-)))

Thanks for your help Heinz

Cheers
Sven