Bug 151653
| Summary: | anaconda fails to bring up raid device whose members have moved | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
| Component: | anaconda | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | arequipeno, cje, cra, cweyl, gilboad, jarod, jburgess777, k.georgiou, mattdm, tmraz, wtogami |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-05-27 20:05:18 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: | 150226 | ||
|
Description
Alexandre Oliva
2005-03-21 14:38:55 UTC
The idea doesn't sound awful. If you're volunteering to do it, go right ahead ;) This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks. Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest this issue on a current release or on the latest development / test version, we would appreciate that. Otherwise, this bug will be marked as CANTFIX one month from now. Thanks for your help and for your patience. This sounds very much like what I am seeing when I try to install Fedora 7
test 3 on my home system. I have a number of software RAID devices spread
across 4 IDE drives. From Fedora Core 6 to Fedora 7 test 2, these drives
have been renamed as follows:
hde --> sda
hdg --> sdb
hdi --> sdc
hdk --> sdd
As a result, anaconda is unable to see any of my software RAID devices, and
I have bee unable to install any Fedora 7 test release. This is going to
bite anyone with software RAID devices on IDE drives very hard.
Seems like it is still an issue. *** Bug 238926 has been marked as a duplicate of this bug. *** Does it work when you manually start the MD device? - Gilboa I can start the devices with the --uuid= and --scan options. Trying to start them by specifying the partitions gives a "no devices found" error. This should be better now that we've switched to using mdadm for starting/stopping arrays (In reply to comment #9) > This should be better now that we've switched to using mdadm for > starting/stopping arrays Is there installation media that can be used to test this? I just tried installing today's Rawhide. Some progress has been made, but this is still not completely fixed. What works: * anaconda is able to use mdadm to start the software RAID devices. * All of the software RAID devices are listed in Disk Druid, and their sizes are shown correctly. * Software RAID devices that are LVM PVs are correctly identified as such, and the correct VG is listed in the "Mount Point/RAID/Volume" column. What doesn't work: * RAID members are not listed. * Software RAID devices with an ext3 filesystem on them are not correctly identified as such. Instead they are listed as "software RAID" in the "Type" column. Disk Druid will not allow me to assign a mount point to one of these devices unless I also choose to format it. Since my RAID-1 /boot device is shared between multiple installations, a reformat is obviously unacceptable. Net result, I'm still unable to install on this system. I disagree with closing this bug. Should be fixed in anaconda-11.2.0.62-1 . Sorry, .64-1 . *** Bug 240952 has been marked as a duplicate of this bug. *** bug 240952 was regarding an error placed in /etc/mdadm.conf by anaconda during a fresh install of F7T4, not an upgrade. so not 100% certain it really is a dup. can someone confirm? - i'm a bit lost in the comments on this bug and bug 238926! Hal-ee-loo-yah! This appears to be truly fixed in the RC. Disk Druid correctly detected ext3 filesystems on pre-existing software RAID devices and allows me to use them without a reformat. The component partitions are still not shown for software RAID devices, but that's certainly not a blocker. (In reply to comment #15) > bug 240952 was regarding an error placed in /etc/mdadm.conf by anaconda > during a fresh install of F7T4, not an upgrade. so not 100% certain it > really is a dup. Creating mdadm.conf files incorrectly is a different problem than this. If we're still creating mdadm.conf files incorrectly then bug 240952 should be reopened, but this particular bug is fixed. |