Bug 234719
| Summary: | anaconda failed to detect SiI 3112 RAID1 after installing LVM and then trying to reinstall | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Wiktowy <michael.wiktowy> | ||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | triage | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | bzcl34nup | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-07 01:23:22 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 150225, 224205 | ||||||
| Attachments: |
|
||||||
|
Description
Michael Wiktowy
2007-03-31 20:30:22 UTC
Created attachment 151364 [details]
Anaconda unhandled exception
I blew away the linux partition using parted and the install was able to proceed as normal again. I reinstalled the default LVM layout again but this time I made sure that the selection was made to install grub on the RAID set ... it didn't and the existing one was still being used. I will open another bug to cover this issue (Bugzilla Bug 234724) The exact LVM error that occurs when the LiveCD is booted after the install is: "Setting up Logical Volume Management: Found duplicate PV {big long ID}: using /dev/sdb3 not /dev/sda3 2 logical volumes(s) in volume group "VolGroup00" now active" Is LVM not RAID-aware? If not then anaconda should not be using a LVM layout for RAID devices. Also, the LiveCD shouldn't be detecting and messing with existing LVMs on the harddisk. If I activate the RAID set manually using 'dmraid -ay', anaconda will detect the set properly again after language selection. So somehow the presence of an LVM filesystem on an existing system is blocking the activation of a dmraid set when starting anaconda on the LiveCD. On initial installation on a blank disk or when there is just a non-LVM partition layout on the disks, the activation of the dmraid set is not blocked. Hrmmm... this has worked for me previously. I need to beat my dmraid box into working again this afternoon to get to the bottom of this To be clear, anaconda run from the LiveCD *does* detect the dmraid RAID 1 set to install to provided that there are no LVM partitions on it. There is that error on LiveCD boot in Comment #2 that isn't present when there are no LVM partitions. That may indicate that LVM detection knows naught of dmraided drives and somehow messes up the activation of that set by anaconda. On the first installation, if I don't accept the default LVM partitions and rather put the old school boot-root-swap on normal partitions, anaconda redetects and activates the dmraid just fine as many times as I try subsequent installations. Of course, grub doesn't boot it either but that feedback is left for my other bugs re: booting dmraid with grub. This is still present in LiveCD 7 test 4. Work-around of dmraid -ay still works. I can't reproduce this on my dmraid box (which is ichraid, but should be the same as far as how the low-level bits work). Sinc eyou have a workaround and it hasn't been otherwise reported, dropping to target I can reproduce this on a Dell PE 650 with Promise SATA RAID controller and two SATA drives. I let the FC 7 (final) Live CD install the default LVM partition on a hardware mirrored array (RAID 1). Upon boot it detected the array from the Live CD. During the formatting, an LVM error occurred, and anaconda hung. Upon restart, the RAID controller wasn't detected (no /dev/mapper entries). I finally needed to run lvm, and remove all lvms, pvs, and vgs' to get the RAID to be detected. I did the live install, and on boot, the system panics, unable to see the root=LABEL=/1 partition. Doesn't look like the initrd is detecting the array. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp |