1 Reply Latest reply: Jan 20, 2011 10:46 AM by Sean22 RSS

RS2WC080 setup

Sean22 Community Member
Currently Being Moderated

Hi All,

 

I'm attempting to build what will be a home server and am having trouble with the RS2WC080 Intel RAID Controller card.  The card is slotted in an ASUS P8P67 mobo in a Norco RPC 4220 chassis.  I have 7 1TB Samsung Spinpoint F3 drives slotted in the 2 of the Norco case backplanes and connected each backplane to the controller card with SFF 8087 cables.  I've installed Debian squeeze amd64 on a Crucial C300 SSD (seems like the mpt2sas kernel module should work in 2.6.31+), but can't seem to get the controller card to initialize even while booting. 

 

I'm trying to use the SSD for the OS and the RAID controller to establish a RAID 5 (or RAID 6 software RAID via mdadm, if possible) file system that the OS can access.  There a few things worth noting that I thought might be useful for anyone that might be able to help:

 

I can't get into the controller BIOS console.  When I hit ctrl+g, it tells me that it will start the BIOS console after the POST completes, but then immediately goes on to grub to load the kernel.  I can, however, get into a preboot CLI with ctrl+y.  When the card is initializing, it does display the 7 samsung drives and when I use -PDList -a0 all 7 drives are described.

 

Also worth noting is that the ASUS mobo uses EFI BIOS.  This is my first time dealing with EFI and there seem to be some specific procedures around it that I'm not sure I'm doing right.

 

-AdpBIOS -dsply -a0 returns:

 

BIOS on Adapter 0 is Enabled.

     BIOS will Stop on error.

Exit Code = 0x0

 

Some of the output from -AdpAllInfo -a0:

 

FW Package Build: 20.1.1-0047

BIOS Version: 4.12.00

Preboot CLI Version: 03.00-009:#%00008

WebBIOS Version: 4.0-14-e_6-Rel

NVDATA Version: 3.03.0039

FW Version: 2.0.04-0767

Boot Block Version: 2.01.00.00-0019

 

Physical Devices: 8

  Disks: 7

  Critical Disks: 0

  Failed Disks: 0

 

Allowed Device Type: SAS/SATA Mix

Allow Mix in Enclosure: Yes

Allow HDD SAS/SATA Mix in VD: Yes

Allow SSD SAS/SATA Mix in VD: No

All HDD/SSD Mix in VD: No

 

Any advice would be greatly appreciated.  Please let me know if there is any other info that could prove useful to finding a solution.

  • 1. Re: RS2WC080 setup
    Sean22 Community Member
    Currently Being Moderated

    As is typically the case, as soon as I posted the question I thought to disconnect the SSD and try the card BIOS again.  Wa-la!  I could get into the BIOS and configured a RAID 5 logical volume across the 7 SATA drives.  However, once the volume was built and I reconnected the SSD to load up the OS, the card still fails to initialize.  Here are what I thought were relevant entries in dmesg:

     

    [    2.598914] ata5: failed to resume link (SControl 0)

    [    2.598919] ata1: failed to resume link (SControl 0)

    [    2.598922] ata3: failed to resume link (SControl 0)

    [    2.598926] ata6: failed to resume link (SControl 0)

    [    2.598940] ata1: SATA link down (SStatus 0 SControl 0)

    [    2.598951] ata3: SATA link down (SStatus 0 SControl 0)

    [    2.598958] ata6: SATA link down (SStatus 0 SControl 0)

    [    2.599239] ata5: SATA link down (SStatus 0 SControl 0)

    [    2.599413] ata2: failed to resume link (SControl 0)

    [    2.599497] ata2: SATA link down (SStatus 0 SControl 0)

    [    2.599507] ata4: failed to resume link (SControl 0)

    [    2.599592] ata4: SATA link down (SStatus 0 SControl 0)

     

    I see those errors before the logon screen ("failed to resume link"), but there's only 6 where there should be 7.  I think that may be a red herring, but wanted to include the errors just in case.

     

    These lines look like they may be the 7 drives and are at different ata points:

    [    1.589891] ata9: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121100 irq 45

    [    1.589894] ata10: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121180 irq 45

    [    1.589898] ata11: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121200 irq 45

    [    1.589901] ata12: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121280 irq 45

    [    1.589905] ata13: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121300 irq 45

    [    1.589908] ata14: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121380 irq 45

    [    1.589911] ata15: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121400 irq 45

    [    1.589915] ata16: SATA max UDMA/133 abar m2048@0xfa121000 port 0xfa121480 irq 45

    ...

    [  181.454334] scsi0 : LSI SAS based MegaRAID driver

    [  181.501284] md: linear personality registered for level -1

    [  181.502221] md: multipath personality registered for level -4

    [  181.503012] md: raid0 personality registered for level 0

    [  181.504382] md: raid1 personality registered for level 1

    [  181.505083] async_tx: api initialized (async)

    [  181.505315] xor: automatically using best checksumming function: generic_sse

    [  181.524022]    generic_sse: 15249.000 MB/sec

    [  181.524023] xor: using function: generic_sse (15249.000 MB/sec)

    [  181.591979] raid6: int64x1   3691 MB/s

    [  181.659942] raid6: int64x2   4012 MB/s

    [  181.727898] raid6: int64x4   3690 MB/s

    [  181.795847] raid6: int64x8   3189 MB/s

    [  181.863804] raid6: sse2x1    9205 MB/s

    [  181.931759] raid6: sse2x2   11300 MB/s

    [  181.999715] raid6: sse2x4   13069 MB/s

    [  181.999716] raid6: using algorithm sse2x4 (13069 MB/s)

    [  182.001758] md: raid6 personality registered for level 6

    [  182.001759] md: raid5 personality registered for level 5

    [  182.001760] md: raid4 personality registered for level 4

    [  182.004169] md: raid10 personality registered for level 10

    [  182.012272] PM: Starting manual resume from disk

    [  182.012274] PM: Resume from partition 8:3

    [  182.012275] PM: Checking hibernation image.

    [  182.012443] PM: Error -22 checking image file

    [  182.012446] PM: Resume from disk failed.

    ...

    [  370.810940] scsi 0:0:0:0: megasas: RESET -1 cmd=12 retries=0

    [  370.810943] megasas: [ 0]waiting for 1 commands to complete

    [  375.827630] megasas: [ 5]waiting for 1 commands to complete

    [  380.844371] megasas: [10]waiting for 1 commands to complete

    [  385.861091] megasas: [15]waiting for 1 commands to complete

    [  390.881842] megasas: [20]waiting for 1 commands to complete

    [  395.898572] megasas: [25]waiting for 1 commands to complete

    [  400.915297] megasas: [30]waiting for 1 commands to complete

    [  405.932029] megasas: [35]waiting for 1 commands to complete

    [  410.948754] megasas: [40]waiting for 1 commands to complete

    [  415.965486] megasas: [45]waiting for 1 commands to complete

    [  420.982210] megasas: [50]waiting for 1 commands to complete

    [  425.998945] megasas: [55]waiting for 1 commands to complete

    [  431.015674] megasas: [60]waiting for 1 commands to complete

    [  436.032389] megasas: [65]waiting for 1 commands to complete

    [  441.049133] megasas: [70]waiting for 1 commands to complete

    [  446.065864] megasas: [75]waiting for 1 commands to complete

     

    ...this explains why the boot hangs for a while before continuing...

     

    [  546.400440] megasas: [175]waiting for 1 commands to complete

    [  551.417178]

    [  551.417179] megasas[0]: Dumping Frame Phys Address of all pending cmds in FW

    [  551.417183] megasas[0]: Total OS Pending cmds : 1

    [  551.417184]

    [  551.417185] megasas[0]: 64 bit SGLs were sent to FW

    [  551.417187] megasas[0]: Pending OS cmds in FW :

    [  551.417189] megasas[0]: Frame addr :0x37843000 :

    [  551.417193] megasas[0]: frame count : 0x1, Cmd : 0x4, Tgt id : 0x0, lun : 0x0, cdb_len : 0x6, data xfer len : 0x24, sense_buf addr : 0x37842200,sge count : 0x1

    [  551.417197]

    [  551.417198]

    [  551.417199] megasas[0]: Pending Internal cmds in FW :

    [  551.417201] megasas[0]: Dumping Done.

    [  551.417201]

    [  551.417203] megasas: failed to do reset

    [  551.417208] scsi 0:0:0:0: megasas: RESET -1 cmd=12 retries=0

    [  551.417210] megasas: cannot recover from previous reset failures

    [  551.417212] scsi 0:0:0:0: megasas: RESET -1 cmd=12 retries=0

    [  551.417214] megasas: cannot recover from previous reset failures

    [  551.417216] scsi 0:0:0:0: Device offlined - not ready after error recovery

     

    Again, thanks for any suggestions.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points