Red Hat Bugzilla – Bug 71908
Installer does not see LVM on raid devices except /dev/md0
Last modified: 2005-10-31 17:00:50 EST
Description of Problem: Low priority, as beta->beta upgrades are not supported, but it might be relevant for future versions, so I figured I'd file the bug report. System (limbo2, basically no updates) set up with two raid sets, one RAID0, one RAID1. Two LVM volume groups, one on the RAID1 set called "Mirror", the other called "Stripe". Many (many) partitions off of each volume. Root is "/dev/Mirror/slash" Tried to upgrade to Null via "upgrade". Anaconda claims "fstab contains entries that can not be mounted. Please fix and try again." At the top, anaconda claims that it found root at /dev/dev/Mirror/slash. The fstab is fine. I noticed that the installer did not have a /dev/Stripe directory, so I commented out all the strip-set partitions and tried again. Same result. Version-Release number of selected component (if applicable): null's installer. How Reproducible: Dunno. This is a pretty wacked setup. Steps to Reproduce: 1. Created above messed-up schema with Limbo. 2. Try and upgrade to null 3. Actual Results: "fstab contains entries that can not be mounted. Please fix and try again" Expected Results: successful upgrade. Additional Information:
Does rescue mode successfully mount the filesystems?
I didn't try a flat "rescue mode". I'll try that tonight. Using the shell on console 2 did not work. mount /dev/Mirror/slash /mnt/sysimage produced an unexpected error message along the lines of "no such filename", even if /mny/sysimage already existed as a directory.
Rescue mode also did not work (failed to mount anythin). Doing a new install of NULL, null did not see the "Stripe" LVM volume group at all, and that volume group had to be recreated, but it did see the already existing Mirror volume-group and Mirror's volumes.
This is a problem where we are not creating entries in /dev for raid devices other than /dev/md0, so when we run vgscan it doesnt see LVM on raid devices other than /dev/md0
*** Bug 74142 has been marked as a duplicate of this bug. ***
Fixed in CVS
Time tracking values updated
Fix confirmed with re0127.nightly.