Bug 504429
Summary: | Dmraid results for nforce4 fakeraid | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rehan Khan <rehan.khan> | ||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | rawhide | CC: | anaconda-maint-list, hdegoede, rmaximo, vanmeeuwen+fedora | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i386 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2009-06-07 07:25:34 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
Rehan Khan
2009-06-06 22:27:15 UTC
Created attachment 346765 [details]
anaconda.log
Created attachment 346766 [details]
Storage.log
Created attachment 346767 [details]
Dmraid output
I should mention this motherboard has a newer Nvidia mediashield firmware than the last one released for this motherboard by Nvidia. It was a community bios build to update the Mediashield and SIL 3112 firmware to allow the use of more up to date drivers. The firmware was taken (I guess) from firmware released with later Nvidia motherboards. It works fine with Windows XP and Windows Server 2003. Hi, Indeed fake (motherboard raid) 5 is not yet supported in the upstream kernel, and thus not yet supported in Fedora. This is causing the crash you are seeing (sad but true). Given that we're too close to F-11 to fix this, and we expect to have dmraid45 in the kernel which will be in F-12, I'm going to close this as wontfix (wontfix for F-11 that is, for F-12 the problem should go away once we have kernel support). Thanks for the info. It's a shame that anaconda(?) crashes instead of just ignoring the problem drives. Makes for a bad user experience. Would it not be better for anaconda to to just go ahead and see if it can find a drive it can work with and if not report this to the user? For example in this case there is a standard sata drive (non raid) in the machine with free space on it that can be used. Just for informational purposes, when the backtrace is displayed to the user the user gets the option of sending it to bugzilla. With the fields filled in (un, pw etc) clicking send hangs the installer. Before the installer hangs the 'detecting storage' dialog re-appears. I know that the code is new for this release (and it's probably too late to put things into this release) but for later releases it might be worth briefly looking at these two issues for a better user experience. cheers Rehan |