Bug 227186
| Summary: | cannot see both SATA drives | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Florin Andrei <florin> |
| Component: | anaconda | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6 | CC: | triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-06 19:09:37 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: | |||
|
Description
Florin Andrei
2007-02-02 23:13:54 UTC
Ubuntu 6.06, Knoppix 5.1.1 and CentOS 4.4 - all of them see the drives correctly as /dev/sda and /dev/sdb Booting with 'linux nodmraid' should work around. 'linux nodmraid' makes no difference. It's like, whatever is supposed to be disabled by that option is not really disabled. Under the Advanced Storage Configuration button, the "disable dmraid device" option is grayed out. I did my initial tests with the 0202 BIOS version. I updated the BIOS to the latest 0801 version. Makes no difference. By the way - related to bug #227441 - it looks like the FC6 installer loads up the sata_nv module. It does not ask for additional modules (as opposed to FC7t1). Same experience with FC7 on Abit VT7 mobo. Using 2 Maxtor STM3160812AS drivers. Per Maxtor SATAII/300 installation manual, I am using the FORCE 150 jumper. I have installed SUSE 10.2 which sees both drives. The driver loaded is for the VT6420 controller whereas my RAID BIOS Utility indicates VT8237 controller. I prefer Fedora over all other distros, so would like resolution ASAP. Jeremy meant "linux nompath", I suspect. Try that, it should work... Works for me. Thanks! Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |