Bug 906952
| Summary: | Not all mvsas drives detected | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Larkin Lowrey <llowrey> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-03 19:39:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 691810 [details]
Boot up of 3.6.10-2.fc17.x86_64 via serial port
Created attachment 691811 [details]
Boot up of 3.6.11-1.fc17.x86_64 via serial port
Created attachment 691812 [details]
Boot up of 3.6.9-2.fc17.x86_64 via serial port
Are you still seeing this with the 3.9.4 kernel in updates-testing? I've been running 3.8.12-100.fc17.x86_64 for a few weeks and have not seen this issue since. This ticket can be closed. Thanks. Thanks for letting us know. |
Created attachment 691809 [details] Boot up of 3.7.3-101.fc17.x86_64 via serial port Description of problem: When booting with 3.7.3-101.fc17.x86_64, only 1 of 4 devices attached to an mvsas controller are detected. Earlier kernels worked, although the most recent two I used did not do so 100% reliably. The three missing drives are never detected. The prior kernel I used (3.6.11-1.fc17.x86_64) would intermittently fail to detect one or two at boot, and thus cause havoc for mdraid, but would eventually detect them and I could hot "--re-add" them via mdadm. Version-Release number of selected component (if applicable): Kernel 3.6.9-2.fc17.x86_64 How reproducible: Every time with 3.6.9-2.fc17.x86_64. I would intermittently have problems with 3.6.11-1.fc17.x86_64. I have rolled back to 3.6.9-2.fc17.x86_64 and have not had problems since. Steps to Reproduce: 1. Hook up multiple SATA drives to a Marvell SAS controller 2. Boot 3.7.3-101.fc17.x86_64 3. Actual results: Missing drives, and in my case failed or degraded mdadm arrays. Expected results: All drives detected and usable by mdadm during boot. Additional info: The controller is a Highpoint RocketRAID 2740 with dual Marvell 9485 controllers on board. 06:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller (rev 11) 07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller (rev 11) The drives are a mixture of Hitachi and Samsung 2TB SATA drives. I have a total of 14 drives. There are 6 connected via on motherboard SATA. There are 4 connected via two dual port Marvell AHCI cards. So, 10 are connected by AHCI native SATA and 4 are SATA drives connected via mvsas.