Bug 178256

Summary: dmraid exception after betanag screen
Product: [Fedora] Fedora Reporter: David Cantrell <dcantrell>
Component: anacondaAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-01-31 20:57:19 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:
Attachments:
Description Flags
Traceback none

Description David Cantrell 2006-01-18 21:02:05 UTC
dmraid exception after betanag screen.  I suppose I could take off my headphones
and go talk to Peter, but I'm listening to The Prodigy right now.

Comment 1 David Cantrell 2006-01-18 21:02:05 UTC
Created attachment 123401 [details]
Traceback

Comment 2 Andy Burns 2006-01-22 12:46:22 UTC
Pretty much the same as I was going to log ...

my config for this test intel D945GTPLR mobo with 2xSATA in freshly created
RAID0 array, zero'ed and created empty partitions on both disks before creating
array.



Comment 3 David Cantrell 2006-01-30 21:33:28 UTC
Some updates.  If I drop to the debugger when the exception happens, the error
message I get when I try to run startRaidDev(), the error displayed is for RAID5
and its state of non-implementation.

I wrapped startRaidDev() in try/except in startAllRaid (dmraid.py) and instead
of an exception, I get an error dialog about opening /dev/mapper/sil_afajddcfadaj.

This is on EM64T for me.

Comment 4 Jeremy Katz 2006-01-31 20:57:19 UTC
Fixed