Hello all,

    I'm new to the scene and just purchased a bunch of hardware to use for my unRAID setup, I just built the server but after booting to the latest beta version 6.2beta21 it seems that my ssd drives that are attached directly to the sata ports on my motherboard are showing fine but none of the disks I have connected to my HBA card are being recognized by unRAID as they do not show up in the drive array drop downs. I believe the HBA Chipset is Marvell 9215. I currently had two drives in the chassie when I pulled the diags. any help would greatly be appreciated.

 

Thanks,

Diag.txt

tower-diagnostics-20160406-2202.zip

I also notice this in the logs...

 

Apr  7 08:22:45 Tower kernel: ata1: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata3: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata2: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata4: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata9: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata8: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata10: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata5: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata7: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata13: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata12: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata14: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata16: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata17: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata18: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata19: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata22: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata21: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata20: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata26: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata24: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata25: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata23: SATA link down (SStatus 0 SControl 300)

Apr  7 08:22:45 Tower kernel: ata11: link is slow to respond, please be patient (ready=0)

Apr  7 08:22:45 Tower kernel: ata15: link is slow to respond, please be patient (ready=0)

Apr  7 08:22:45 Tower kernel: ata11: softreset failed (device not ready)

Apr  7 08:22:45 Tower kernel: ata15: softreset failed (device not ready)

Apr  7 08:22:45 Tower kernel: ata11: softreset failed (1st FIS failed)

Apr  7 08:22:45 Tower kernel: ata15: softreset failed (1st FIS failed)

Apr  7 08:22:45 Tower kernel: ata11: softreset failed (1st FIS failed)

Apr  7 08:22:45 Tower kernel: ata11: limiting SATA link speed to 3.0 Gbps

Apr  7 08:22:45 Tower kernel: ata15: softreset failed (1st FIS failed)

Apr  7 08:22:45 Tower kernel: ata15: limiting SATA link speed to 3.0 Gbps

Apr  7 08:22:45 Tower kernel: ata11: softreset failed (1st FIS failed)

Apr  7 08:22:45 Tower kernel: ata11: reset failed, giving up

Apr  7 08:22:45 Tower kernel: ata15: softreset failed (1st FIS failed)

Apr  7 08:22:45 Tower kernel: ata15: reset failed, giving up

Please see this, but further responses, if any, should be continued here.