On Oct 21, 2012, at 2:19 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote: > Without further details from Chris I'm assuming megaraid_sas is loading > but not working. Is this the case Chris? If so I'm thinking the Intel > board simply isn't supported by the 3.2 megaraid_sas driver. Yes, this is precisely the case and my guess as well. Just for shates and gagles I've also loaded mptsas and mpt2sas - to no effect. I also noticed a dmesg error, I'm not sure if this is caused by no driver being available or some other failure. "FW in FAULT state": > [ 6.396235] megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011 > [ 6.396726] megasas: 0x1000:0x005b:0x8086:0x3513: bus 1:slot 0:func 0 > [ 6.397232] megaraid_sas 0000:01:00.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26 > [ 6.397677] megaraid_sas 0000:01:00.0: setting latency timer to 64 > [ 6.397721] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > [ 6.397798] megasas: Waiting for FW to come to ready state > [ 6.397800] megasas: FW in FAULT state!! > [ 6.397822] megaraid_sas 0000:01:00.0: PCI INT A disabled But the raid controller seems to be configured fine. I have tried both JBoD (which I'm not totally sure is supported by the controller) and RAID 0. Thanks, Chris
Attachment:
smime.p7s
Description: S/MIME cryptographic signature