Red Hat Bugzilla – Bug 505446
Anaconda traceback trying to re-purpose ex-member of unsupported RAID
Last modified: 2009-09-02 08:06:11 EDT
Description of problem:
I wanted to re-use a drive which had once been a member of a RAID which made use of a proprietary driver. I installed the disk in the computer, and ran the Fedora installer. Anaconda bombed out with a Python traceback every time after choosing Keyboard Type, complaining of an error in getRaidSets (I do not have the actual traceback--sorry).
I was able to work around the error by deleting the RAID metadata using dmraid, but Anaconda should probably be more forgiving and offer to do this itself.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert single drive which was once a member of proprietary RocketRAID into computer
2. Run Fedora 11 Installer
3. After choosing keyboard layout, traceback appears. Alas, no place to save traceback since it wouldn't use the disk, and I'm not clever enough to figure out how else to save it.
However, upon clicking the "Exit Installer" button, I could copy down the console error message, which seemed informative:
ERROR - RAID Type 8 not supported
ERROR adding /dev/sda to RAID set hpt45x-deaaabiga
ERROR No raid set found.
A message saying something like -- Hey, this drive is a member of a RAID. Continuing will erase this disk, and probably destroy the RAID it's a member of. Are you sure you want to continue? Yes/No
In order to get past the traceback, one can boot into Rescue mode and type:
dmraid -r -v -E /dev/sda
...to delete the RAID metadata, at which point Anaconda is delighted to use the disk.
Created attachment 356594 [details]
Traceback when trying to install F11 to a hard drive that has been (software) raid5 member
Same problem here. 'dmraid -r -v -E /dev/sda' did the trick!
Can you pls test with rawhide.
*** Bug 518891 has been marked as a duplicate of this bug. ***
does rawhide present the same behavior?
I regret to inform you I consumed my ex-proprietary-RAID drives using the workaround in the description.
We could close the bug as worksforme, but that seems a little premature in the cosmic scheme of things.