August 4, 20214 yr Hi after changing a cable so I could use all my slut in LSI 9201-16e Will my unraid not see any HDD . No matter the cable and what off the sas plate I connected it too . Also the sas plate work out any problem in a other controller. So fell I have try what I can think off .. can see in syslog it give a error But not sure what it mean Try too add the partSorry it look wird hope the syslog help more but it spicel the mpt2sas thing I was wondering what will say it the driver as I understand ? Edit the time code on the syslog and the post info is different update the post today Tower kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 4 23:03:53 Tower kernel: sdc: sdc1 Aug 4 23:03:53 Tower kernel: sd 4:0:0:0: [sdc] Attached SCSI disk Aug 4 23:03:53 Tower kernel: ata5: SATA link down (SStatus 0 SControl 330) Aug 4 23:03:53 Tower kernel: ata6: SATA link down (SStatus 0 SControl 330) Aug 4 23:03:53 Tower kernel: ata7: SATA link down (SStatus 0 SControl 330) Aug 4 23:03:53 Tower kernel: ata8: failed to resume link (SControl 0) Aug 4 23:03:53 Tower kernel: ata8: SATA link down (SStatus 0 SControl 0) Aug 4 23:03:53 Tower kernel: BTRFS: device fsid 3a0fe81f-ee26-4611-91b0-f8133532d249 devid 1 transid 152680 /dev/sdb1 scanned by udevd (1756) Aug 4 23:03:53 Tower kernel: mpt2sas_cm0: sending diag reset !! Aug 4 23:03:53 Tower kernel: random: crng init done Aug 4 23:03:53 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting Aug 4 23:03:53 Tower kernel: mpt2sas_cm0: diag reset: SUCCESS Aug 4 23:03:53 Tower kernel: mpt2sas_cm0: _base_spin_on_doorbell_int: failed due to timeout count(10000), int_status(c0000000)! Aug 4 23:03:53 Tower kernel: mpt2sas_cm0: doorbell handshake int failed (line=5934) Aug 4 23:03:53 Tower kernel: mpt2sas_cm0: _base_get_ioc_facts: handshake failed (r=-14) Aug 4 23:03:53 Tower kernel: mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:11045/_scsih_probe()! Aug 4 23:03:54 Tower kernel: EDAC amd64: F17h detected (node 0). Aug 4 23:03:54 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Aug 4 23:03:54 Tower kernel: EDAC amd64: tower-syslog-20210804-2300.zip
August 5, 20214 yr You should post your diagnostics file instead of the syslog. Does the controller see the drives within it's BIOS?
August 7, 20214 yr Author On 8/5/2021 at 1:55 PM, Squid said: You should post your diagnostics file instead of the syslog. Does the controller see the drives within it's BIOS? Hi sorry for that . And the bios also can't one will think it was the cables then but wird if all don't work the same time tower-diagnostics-20210807-1549.zip
August 17, 20214 yr I had a similar thing happen to me about 10 years ago and after spending hours on it, someone on this board said "re-seat the card." I unplugged the card from the pci slot, re-inserted it, and the mb detected it again, thus unraid saw the drives, and fixed my problem. Hopefully you got it figured out already though.
August 17, 20214 yr Author 1 hour ago, nate1749 said: I had a similar thing happen to me about 10 years ago and after spending hours on it, someone on this board said "re-seat the card." I unplugged the card from the pci slot, re-inserted it, and the mb detected it again, thus unraid saw the drives, and fixed my problem. Hopefully you got it figured out already though. Thx have try unplug and change location. I have end up order a expander card too use instead with my other controller
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.