Red Hat Bugzilla – Bug 680474
Anaconda doesn't recognize my LVM on RAID1 setup
Last modified: 2011-04-05 17:39:08 EDT
Description of problem:
One of my PC's has two harddrives configured in a RAID 1 configuration (softraid). On of the RAID devices (md1) hosts an LVM physical volume. When I try to install F15 (pre-alpha), it doesn't recognize this setup.
It does recognize the RAID1 devices, but it fails to detect the LVM setup that it hosts. This means I can't install F15 next to my existing F14 in an separate LVM partition. Let me know what additional information you would need for this issue.
/tmp/anaconda.log, /tmp/storage.log, and /tmp/syslog from when you hit the problem would be handy. Thanks.
Created attachment 481044 [details]
Ok, here they come...
Created attachment 481045 [details]
Created attachment 481047 [details]
For completeness: /dev/md1 is the RAID1 partition holding the LVM PV, /dev/md7 is a separate /boot partition.
This should be the same issue as bug 676519, which was fixed in anaconda-15.21-1 on rawhide. Setting this bug to block F15Beta instead of that one since this one is against F15.
Fixes this for me when used with 15.20.1
(PS, adding /sbin to PATH? Doesn't affect install, only us bit twiddlers.)
Fixed for Fedora 15 in anaconda-15.22-1.
Discussed at 2011-03-11 blocker review meeting. This issue is fixed and available for testing in anaconda-15.22-1. The issue has been accepted as a beta blocker.
I'd love to verify this, but I'm currently blocked by Bug 688682.
I'm not seeing this using anaconda-15.24-1 (installation images available from http://download.fedoraproject.org/pub/fedora/linux/development/15/). The test blocker you mentioned is now resolved in the latest pygobject2 which should also be included.
I tested doing an install with LVM on top of RAID devices. After the install completed, I started the installer again, and it recognized the existing RAID and LVM devices. I'll move this to VERIFIED once we have confirmation from the reporter (email@example.com).
I tried again today with a boot.iso from yesterday evening, but I still can't go into custom partitioning. Got a backtrace that already was in bugzilla under bug 684283, but that bug is marked as a duplicate of bug 682543. James reports (just today that bug 682543 should be fixed now. I'm not sure where I should get a more recent boot.iso with this fix to test again.
(In reply to comment #12)
> I tried again today with a boot.iso from yesterday evening, but I still can't
> go into custom partitioning. Got a backtrace that already was in bugzilla under
> bug 684283, but that bug is marked as a duplicate of bug 682543. James reports
> (just today that bug 682543 should be fixed now. I'm not sure where I should
> get a more recent boot.iso with this fix to test again.
If its still there try:
I used http://jlaska.fedorapeople.org/boot.iso to test again and with this image my LVM RAID setup is detected properly. I can add an LVM partition just fine now, so as far as I'm concerned you can close this bug.
Thank your for fixing this.
anaconda-15.26-1.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-15.26-1.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-15.26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.