Red Hat Bugzilla – Bug 238926
MD assembly failed due to sdX device renumbering
Last modified: 2007-11-30 17:12:03 EST
Description of problem:
While upgrading an FC6 system with F7t4 anaconda failed to locate all the
devices for the existing MD array and so could not upgrade the existing install.
This looks very much like a duplicate of:
237456: Existing LVM, Software Raid, and SATA disks not detected
I thought it made sense to open a new one to keep all my logs files and info
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. FC6 system with 4 SATA disks on AHCI controller as sda,sdb,sdc,sdd
2. /dev/md0 = RAID1 of sda1, sdb1, sdc1, sdd1
3. /dev/md1 = RAID5 of sda2, sdb2, sdc2, sdd2
4. Plug in USB Had disk containing f7t4-DVD.iso on filesystem
5. Plug in USB "all-in-one" card reader (which appears as 4 individual USB SCSI
6. Boot f7t4 install (from grub entry on existing install)
7. Anaconda loads usb-storage, assigns sda = USB hard disk
8. Also sd[bcde] are taken by all-in-one USB card reader
9. In anaconda, select HD install with /dev/sda1 as source. Starts OK
10. AHCI module loaded
11. The 4 installed hard disks for the MD array get assigned to sd[fghi]
12. Anaconda tries to start the MD array, finds sdf1 but fails to open or find
any of the other disks of md0
13. Ditto for md1 - finds sdf2 but no other array members.
14. MD array startup fails, anaconda finds no existing install
No working upgrade path :-(
I will attach the full syslog.txt which covers the MD messages etc for the
Should be able to start the array even though the sdX devices have changed.
I can make things a little better by removing the all-in-one USB device. In this
case the external USB disk gets sda, the 4 normal disks sd[bcde]. In this
scenario the array finds 3 of the 4 disk (sd[bcd] only) so manages to start up
in degraded mode allowing the install to proceed. Unfortunately there is no
indication of this in the GUI, slows down the install and takes a while to
rebuild the array afterwards.
Created attachment 154076 [details]
Created attachment 154078 [details]
Appears to be a dupe of bug 151653.
*** This bug has been marked as a duplicate of 151653 ***