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 asboot non lvm
spoke the following words to the mbuttes incomp.os.linux.misc...: It is very easy, actually. The key is...
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 parbreastion on the disk or something from the vendor.
(root) was mountet on VolGroup00, exceptboot
Printouts fra lvm (bootet fra RHEL4 rescue cd)
Output from lvscan and vgscan:
Couldn't find device with uid m51fn4 .... oWH4t1 repeat a couple of times Volume group "VolGroup00" not found
Couldn't find device with uid m51fn4 .... oWH4t1 PVdev-sda2 VG VolGroup00 lvm2 33,81 GB 128MB free PVdev-sdb1 VG VolGroup00 lvm2 33,91 GB 0 free PV unknown device VG VolGroup00 lvm2 0 0 free
If only the lvm is corrupt, and the parbreastions 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
Linux groups from Newsgroups