Bug 474482
Summary: | Harddisk attached to onboard Marvell SAS controller on Asus P6T Deluxe not detected under Fedora 10 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | mind.faq | ||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | 10 | CC: | kernel-maint, mm+rhbz, quintela | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2009-04-15 21:40:09 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
mind.faq
2008-12-04 00:19:50 UTC
Created attachment 325612 [details]
output of lspci
controller is listed correctly by lspci
Created attachment 325614 [details]
output of lsscsi
only devices connected to SATA ports of Intel ICH10R southbridge are listed
Created attachment 325615 [details]
relevant part of dmesg output
*** Bug 474483 has been marked as a duplicate of this bug. *** I have a nearly identical system which does recognize a single sas drive on the built in Marvell controller. My drive is a Seagate ST373455SS (73 G 15k SAS). I'm also using an i7 920 on a Asus P6T-Deluxe with a couple of SATA drives as well. There are some problems using the sas drive however because rc.sysinit and/or the init script in the initrd try to use it before the mvsas driver has finished making the device appear. This means that partitions on it may fail to fsck or logical volumes fail to appear during rc.sysinit, depending on the timing. To fix this, what I needed to do was add a delay loop into rc.sysinit. In my case I just hacked a loop waiting for /dev/sdc to appear just before rc.sysinit does the "lvm vgchange -a y" to set up the logical volumes. This works fine. To make the sas drive usable as the root file system we need a similar delay for the device to appear before init tries to mount it as the new root, otherwise the mount fails and the system will not boot. mkinitrd already has a list of drivers for which it turns on a "wait_for_scsi" loop in init, but mvsas isn't on the list. I added mvsas to the list, created a new initrd and now / is fine on the sas drive. I have not tried /boot on the sas drive yet. This is all with the stock Fedora 10 kernel from the release DVD. No new kernel or modprobing required. This may not be same as the originators problem however, since on my system the drive does show up. lsscsi shows it as: [0:0:0:0] cd/dvd HL-DT-ST DVD-RAM GH22NS30 1.01 - [1:0:0:0] disk ATA ST3500320AS SD15 - [2:0:0:0] disk ATA ST3500320AS SD15 - [6:0:0:0] disk SEAGATE ST373455SS 0002 - The one line patch to mkinitrd is attached below. The hack to rc.sysinit is not since I've just hardcoded it to wait for /dev/sdc rather than find a general solution. Created attachment 326026 [details]
patch to mkinitrd
one line patch to mkinitrd to add mvsas to the list of modules to turn on "wait_for_scsi"
The kernel bug is fixed in 2.6.27.19 and later kernels. And mkinitrd doesn't have a list of modules any more, so it should not need any changes. |