Thread: LVM crash
View Single Post

  #1 (permalink)  
Old 02-18-2006
Jon Martin Solaas
 
Posts: n/a
Default LVM crash

During installation of a new scsi disk in a ProLiant 370 server with
RHEL4, LVM manager crashed (hung) and the configuration was corrupted.
The machine cannot boot, and gets kernel panic.

Configuration:

/dev/sda1: mounted as /boot non lvm

/dev/sda2: included in VolGroup00 (ext3),

/dev/sdb1: included in VolGroup00 (ext3)

/dev/sdc1: should have been included in VolGroup00 (the new disk)
/dev/sdc3: util partition on the disk or something from the vendor.

/ (root) was mountet on VolGroup00, except /boot

Printouts fra lvm (bootet fra RHEL4 rescue cd)

Output from lvscan and vgscan:

lvm>lvscan
lvm>vgscan

Couldn't find device with uid m51fn4 .... oWH4t1
[repeat a couple of times]
Volume group "VolGroup00" not found

lvm>pvscan

Couldn't find device with uid m51fn4 .... oWH4t1
PV /dev/sda2 VG VolGroup00 lvm2 [33,81 GB / 128MB free]
PV /dev/sdb1 VG VolGroup00 lvm2 [33,91 GB / 0 free]
PV unknown device VG VolGroup00 lvm2 [0 / 0 free]

lvm>

If only the lvm is corrupt, and the partitions and data are ok, I
suppose it's possible to recover from this. But how? I do not want to
experiment with this server, and I'm not very fluent in lvm configuration...

--
jon martin solaas
Reply With Quote