Red Hat Bugzilla – Bug 136048
lvm went kablooie
Last modified: 2014-03-16 22:49:33 EDT
As an aside, we should probably work on ways to get these dumps
somewhere other than craptastic floppy drives.
Created attachment 105343 [details]
LVM. It's funtastic!
Created attachment 105344 [details]
This is what happened when I just tried to reboot anaconda on the same box
after it crashed. Worked around by nuking the disk, of course. :/
Preliminary guess is that it didn't like /dev/md14.
This is ... suspicious.
Volume group VolGroup00 metadata is inconsistent
Volume group for uuid not found:
Failed to activate new LV.
Creating volume group backup "/etc/lvm/backup/VolGroup00"
Volume group "VolGroup00" successfully created
l volumes for volume group VolGroup00.
format_text: _vg_read failed to read VG VolGroup00
Set up physical volume for "/dev/md0" with 163829376 available sectors
Physical volume "/dev/md0" successfully created
2.00.27 will help fix this - may need anaconda changes or further lvm2
I too have this issue when trying to attach existing Sata raid drives.
Does 2.00.29 fix this?
I don't have the filesystem in a state to reproduce this now. :/
I'll assume the md-recognition code in 2.00.29 probably fixed it and