This card was supported fine and worked find in V 5.0.6

 

I tried V6.0-beta14b and the driver for LSI SATA controller 9211-8i I don't think is included (LSISAS2008 driver seems to not be included in the kernel).

 

Not working syslog info from V6.0 beta build:

Apr  1 17:27:13 Tower kernel: mpt2sas0: sending diag reset !!

Apr  1 17:27:16 Tower kernel: mpt2sas0: diag reset: FAILED

Apr  1 17:27:16 Tower kernel: mpt2sas0: _base_get_ioc_facts: failed getting to correct state

Apr  1 17:27:16 Tower kernel: mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8253/_scsih_probe()!

 

Working syslog info from V 5.0.6 build:

Apr  1 18:56:09 Tower kernel: mpt2sas0: diag reset: SUCCESS

Apr  1 18:56:09 Tower kernel: mpt2sas0: Allocated physical memory: size(3379 kB)

Apr  1 18:56:09 Tower kernel: mpt2sas0: Current Controller Queue Depth(1483), Max Controller Queue Depth(1720)

Apr  1 18:56:09 Tower kernel: mpt2sas0: Scatter Gather Elements per IO(128)

Apr  1 18:56:09 Tower logger: /etc/rc.d/rc.inet1:  Polling for DHCP server on interface eth0:

Apr  1 18:56:09 Tower kernel: mpt2sas0: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00)

Apr  1 18:56:09 Tower kernel: mpt2sas0: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)

Apr  1 18:56:09 Tower kernel: mpt2sas0: sending port enable !!

Apr  1 18:56:09 Tower  kernel: mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b001bdd296), phys(

Apr  1 18:56:09 Tower kernel: mpt2sas0: port enable: SUCCESS

Apr  1 18:56:09 Tower kernel: scsi 1:0:0:0: Direct-Access    ATA      ST31000528AS    CC37 PQ: 0 ANSI: 6

Apr  1 18:56:09 Tower kernel: scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221107000000), phy(7), device_name(0x5000c50019b1cac2)

Apr  1 18:56:09 Tower kernel: scsi 1:0:0:0: SATA: enclosure_logical_id(0x500605b001bdd296), slot(4)

Apr  1 18:56:09 Tower kernel: scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)

Apr  1 18:56:09 Tower kernel: scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)

Apr  1 18:56:09 Tower kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0

Apr  1 18:56:09 Tower kernel: scsi8 : Fusion MPT SAS Host

Apr  1 18:56:09 Tower kernel: ACPI: PCI Interrupt Link [LNEB] enabled at IRQ 18

Apr  1 18:56:09 Tower kernel: mpt2sas1: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8310320 kB)

Apr  1 18:56:09 Tower kernel: mpt2sas 0000:07:00.0: irq 47 for MSI/MSI-X

Apr  1 18:56:09 Tower kernel: mpt2sas1-msix0: PCI-MSI-X enabled: IRQ 47

Apr  1 18:56:09 Tower kernel: mpt2sas1: iomem(0x00000000febfc000), mapped(0xf8538000), size(16384)

Apr  1 18:56:09 Tower kernel: mpt2sas1: ioport(0x000000000000e000), size(256)

Apr  1 18:56:09 Tower  kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)

Apr  1 18:56:09 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off

Apr  1 18:56:09 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08

Apr  1 18:56:09 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA

Apr  1 18:56:09 Tower kernel:  sdb: sdb1

Apr  1 18:56:09 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk

Apr  1 18:56:09 Tower kernel: mpt2sas1: sending diag reset !!

Apr  1 18:56:09 Tower kernel: mpt2sas1: diag reset: SUCCESS

Apr  1 18:56:09 Tower  kernel: mpt2sas1: Allocated physical memory: size(3379 kB)

Apr  1 18:56:09 Tower kernel: mpt2sas1: Current Controller Queue Depth(1483), Max Controller Queue Depth(1720)

Apr  1 18:56:09 Tower kernel: mpt2sas1: Scatter Gather Elements per IO(128)

Apr  1 18:56:09 Tower kernel: mpt2sas1: LSISAS2008: FWVersion(18.00.00.00), ChipRevision(0x03), BiosVersion(07.37.00.00)

Apr  1 18:56:09 Tower  kernel: mpt2sas1: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)

Apr  1 18:56:09 Tower kernel: mpt2sas1: sending port enable !!

Apr  1 18:56:09 Tower kernel: mpt2sas1: host_add: handle(0x0001), sas_addr(0x500605b0013c8880), phys(

Apr  1 18:56:09 Tower kernel: mpt2sas1: port enable: SUCCESS

UnraidV6syslog.zip

UnraidV5syslog.zip

My Dell H310 cross flashed to a LSI 9211-8i IT mode works fine for me in 6b14b on my HP N40L.  I've got another of those and some M1015s all cross flashed to LSI 9211-8i in pass through in ESXi 5.0 to unRAID VMs at least one VM is 6b14b.

 

Since it is working on 5.0.6 I've got to assume it is in IT mode but I still have to ask is it?

 

At work now but could get my log entries when i get home if you think it would help.

If the 9211-8i driver wasn't included, we would have heard lots of complaints before now.

 

I'm using the Supermicro AOC-USAS2 card, flashed to 9211-8i and it is working perfectly well.

The module 'mpt2sas' is your driver, and it's loading correctly, and seeing 2 cards, but neither are cooperating.  I'm not an expert, but it looks like the mem and IO resources for both cards are assigned, although with a little juggling of the mem buffers needed.  But neither of the cards appears to respond, and I don't know why.  The only thing I can suggest is make sure they both are fully updated, correct firmware and settings and modes.

OK.. So I flashed the latest firmware into the LSI 9211-8i cards (both of them).

 

I upgraded to the latest from the LSI web site as of today.

BIOS update: V.7.38.01.00 - 2014.07.06

Firmware update: HBA_9211_8i_IT  (P19)

 

Still the same result.

 

I have searched the web and found this link that might seem relevant to the failure I am getting in the syslog:

 

http://www.spinics.net/lists/linux-pci/msg38416.html

 

It mentions that

 

"In 3.19 rc6, the LSISAS2008 card is found but mpt2sas fails to load correctly. If pci=realloc=off is added to the startup command line, mpt2sas is correctly loaded."

 

I'm not that familiar with Linux.. How could I try this?

 

 

I would imagine you would add it to the syslinux line that loads the unraid you are using.  But someone that knows linux should answer the question not me.

 

Based on what I've seen on the web that command (pci=realloc=off) is dealing with resource allocations and virtualization.  So you might also be able to change bios settings to make it work.  I have 2 M1015s on a Tyan S5512 MB passed through in ESXi 5.0 to an unRAID VM currently they are working.  But I am using virtualization and that might be with an older kernel as well.  So an alternative for you is to turn ON or OFF all the virtualization options your MB has and see if that makes a difference.  Just make note of what you change so you can change it back if it doesn't help.

I'd like to try.. however I'm not sure where the bootloader config file is to add this config parameter to the syslinux line in unraid.

 

There also seems to be zero ability in my MB bios to change any PCI option and map settings.  Along with no ability to change virtualization settings.

 

Reposted due to copy/paste edit being required...

 

I'd like to try.. however I'm not sure where the bootloader config file is to add this config parameter to the syslinux line in unraid.

 

The file is located here: /boot/syslinux/syslinux.cfg

 

The first label listed is the default boot.

 

I'm not certain, but you could try the following:

 

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pci=realloc=off initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

 

Here is what mine looks like (using Intel PState fix):

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append intel_pstate=disable initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

 

For what it's worth to @LimeTech , here's the last post [2015-02-26] in the chain of bug troubleshooting... http://www.spinics.net/lists/linux-pci/msg39002.html

 

Hopefully they'll have this change into the latest Kernel soon.

Thanks Guys,

 

While I was waiting for a response I did actually figure it out how to modify the syslinux.cfg file to add the pci=realloc=off parameter.

 

And... Guess what.. Eureka.. It worked!  I can see all of my drives again with unraid 6.

 

Moral of this story is that it looks like the LSI 9211-8i firmware doesn't like to have the PCI maps reallocated.

Nice work everyone!  That does look like the correct patch that's needed, but you have a good workaround for now.

I just wanted to tell that I had this exact issue when I upgraded from 5.0.4 to 6.0.1

 

Is it so that this is still the correct way to solve the issue? I'm asking because from RobJ's answer I felt that this could be solved in release since the issue was in some beta version.

 

Anyway I did try it and it seemed to work for me. So thanks for that!