Red Hat Bugzilla – Bug 13544
Installer Fails to Upgrade When Software RAID Drive Present
Last modified: 2008-05-01 11:37:56 EDT
Description pretty much says it all.
The installer fails to upgrade because it can't mount /dev/md0 where
/dev/md0 is a raid5 array set up with the detect-superblock on.
This defect is considered MUST-FIX for Winston Beta-5
*** Bug 12034 has been marked as a duplicate of this bug. ***
*** Bug 13191 has been marked as a duplicate of this bug. ***
Fixed (finally!) for beta 5.
The installer correctly identifies and upgrades with the RAID resent, but didn't
add the raid kernel modules to the initrd. The system installed fine, but did
This defect is considered MUST-FIX for Winston Release-Candidate #1
Have you seen this with beta 5? We fixed bugs in here, and it both works fine in
our labs and we've gotten confirmations from beta testers that this is fixed.
If you're still seeing this, please send a copy of your fstab.
Looks fixed. Thanks.
I did do an upgrade from beta-3 to (what I thought was) beta-5 and had problems,
but now I can't recreate, so I'm marking as WORKSFORME.
verified fix in post-pinstripe internal build ... thanks for the report!
Sorry I had to re-open. I just duplicated again with RC1.
I did an upgrade of beta4 -> rc1 over FTP. It installed and upgraded fine, but
when booting in for the first time it can't find /dev/md0. Apparently the raid
software drivers didn't get into the initrd, though the scsi drivers did, so it
failed in the fsck check when it couldn't fsck /dev/md0
I fixed the problem by building a new initrd and re-running lilo.
on a side note, mkinitrd should give better error messages if it can't find it's
components ... I had forgotten to mount /usr and running mkinitrd just produced
a bunch of shell errors. It would be best to add a little sanity at the top to
check for the stuff it needs.
Are you able to duplicate this error using a 6.2 -> RC1 upgrade path ...?
Beta->Beta upgrade path bugs aren't as crucial as previous release -> beta
upgrades, so please let us know if you have this problem using a non-beta
release such as 6.2 ...
I did not have this problem with an upgrade from a minimum 6.2 install ->
Winston RC-1 in test ...
Please reopen this issue if you are having trouble with 6.2 (or any other
previous non-beta release)