Red Hat Bugzilla – Bug 216147
Installer crashed with error block.dmraid.GroupingError on system which had preexisting md raid
Last modified: 2009-10-07 09:39:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20061011 Fedora/22.214.171.124-7.fc6 Firefox/126.96.36.199
Description of problem:
Just after the media check the system starts to load the graphical installer, but then crashes with the error:
see http://homepages.gac.edu/~sommere/rhel5b2installcrash.JPG for a screencap of the stack trace
the system had previously had several raid 1 and 6 arrays. The raid 6 arrays had lvm on top of them.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up system with raid devices (both raid 6 and 1) and lvm
2. try to install over that system
3. the installer will crash before you can do anythign about it
see stack trace
I should have been able to install over the system
Moving to RHEL 5.5 so it doesn't get mistakenly closed by the bot
Very strange behavior. And, ofcourse, I can't reproduce :). I think its directly linked to the setup you have on the box.
Can you please run the following script on tty2. As soon as you get tty2.
rss = block.getRaidSet()
run it as like this `python scriptName`. You can also execute it in a python console. Pls post the output.
Does the system in question actually have BIOS RAID? Or is the raid you mention it has all software raid (mdraid) or full hardware RAID ?
I filed this bug in 2006...
I am almost positive it was mdraid (as the subject of the bug states)
If I remember correctly, I used dd to wipe out the drives and was then able to install.
I _assume_ this has been fixed in the almost 3 years that have past...
Obviously I can't run a script on the system. I'm not even sure we still HAVE that system, but it has probably been reinstalled a few times since then in any case.
Hmm, you are right, we did leave this one lingering very long, sorry about that.
Ok, closing this as insufficient info then.