mpt2sas_cm0: failure at drivers

[Izzy9999]

I have an LSI 9240-8I flashed to 9211-8i P20 IT mode using Forward breakout cables. Unraid sees the card but not the disks attached to it. There seems to be a problem loading the drivers. I'm running it off of a trial key so none of my drives are attached. Only the 9240 with 2 drives attached to it. Any ideas would be appreciated. Thanks

 

Feb  7 14:38:55 Tower kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x2f impl SATA mode
Feb  7 14:38:55 Tower kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst 
Feb  7 14:38:55 Tower kernel: mpt3sas version 26.100.00.00 loaded
Feb  7 14:38:55 Tower kernel: mpt3sas 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (16383784 kB)
Feb  7 14:38:55 Tower kernel: cryptd: max_cpu_qlen set to 1000
Feb  7 14:38:55 Tower kernel: usbcore: registered new interface driver btusb
Feb  7 14:38:55 Tower kernel: scsi host3: ahci
Feb  7 14:38:55 Tower kernel: usb 1-1.5: Direct firmware load for ar3k/AthrBT_0x01020200.dfu failed with error -2
Feb  7 14:38:55 Tower kernel: scsi host4: ahci
Feb  7 14:38:55 Tower kernel: Bluetooth: Patch file not found ar3k/AthrBT_0x01020200.dfu
Feb  7 14:38:55 Tower kernel: scsi host5: ahci
Feb  7 14:38:55 Tower kernel: Bluetooth: Loading patch file failed
Feb  7 14:38:55 Tower kernel: ath3k: probe of 1-1.5:1.0 failed with error -2
Feb  7 14:38:55 Tower kernel: usbcore: registered new interface driver ath3k
Feb  7 14:38:55 Tower kernel: AVX version of gcm_enc/dec engaged.
Feb  7 14:38:55 Tower kernel: scsi host6: ahci
Feb  7 14:38:55 Tower kernel: AES CTR mode by8 optimization enabled
Feb  7 14:38:55 Tower kernel: scsi host7: ahci
Feb  7 14:38:55 Tower kernel: scsi host8: ahci
Feb  7 14:38:55 Tower kernel: ata1: SATA max UDMA/133 abar m2048@0xf7e16000 port 0xf7e16100 irq 28
Feb  7 14:38:55 Tower kernel: ata2: SATA max UDMA/133 abar m2048@0xf7e16000 port 0xf7e16180 irq 28
Feb  7 14:38:55 Tower kernel: ata3: SATA max UDMA/133 abar m2048@0xf7e16000 port 0xf7e16200 irq 28
Feb  7 14:38:55 Tower kernel: ata4: SATA max UDMA/133 abar m2048@0xf7e16000 port 0xf7e16280 irq 28
Feb  7 14:38:55 Tower kernel: ata5: DUMMY
Feb  7 14:38:55 Tower kernel: ata6: SATA max UDMA/133 abar m2048@0xf7e16000 port 0xf7e16380 irq 28
Feb  7 14:38:55 Tower kernel: ata3: SATA link down (SStatus 0 SControl 300)
Feb  7 14:38:55 Tower kernel: ata1: SATA link down (SStatus 0 SControl 300)
Feb  7 14:38:55 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300)
Feb  7 14:38:55 Tower kernel: ata2: SATA link down (SStatus 0 SControl 300)
Feb  7 14:38:55 Tower kernel: ata4: SATA link down (SStatus 0 SControl 300)
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: sending diag reset !!
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: diag reset: SUCCESS
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: _base_spin_on_doorbell_int: failed due to timeout count(10000), int_status(c0000000)!
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: doorbell handshake int failed (line=5212)
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: _base_get_ioc_facts: handshake failed (r=-14)
Feb  7 14:38:55 Tower kernel: mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10684/_scsih_probe()!

syslog.txt

[JorgeB]

This suggests a problem with that particular controller, try re-flashing it if not yet done.

[Izzy9999]

41 minutes ago, JorgeB said:

This suggests a problem with that particular controller, try re-flashing it if not yest done.

I'll give it a shot. Thanks

[ItHurtsMyHart]

On 2/8/2021 at 3:55 AM, Izzy9999 said:

I'll give it a shot. Thanks

Did re-flashing the firmware end up working for you?