I recently set up a new HBA which was pre-flashed and connects to the backplate for SilverStone RM43-320-RS

 

From what I can tell it seems the HBA is initializing correctly and it's reporting 4 drives, but one of the 4 drives is reporting it's disabled

 

I've attached diagnostics tower-diagnostics-20241029-1826.zip

 

Any help is greatly appreciated.

Start the array and post new diags to see if the emulated disk is mounting.

Here is the diagnostic after starting the array, I should also mention I found this 

 and ran the commands on all 4 drives to disable EPC and low current spinup but the same result, device is disabled

rocinante-diagnostics-20241029-2011.zip

Emulated disk is mounting, assuming contents looks correct, you can rebuild on top:

 

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

 

If it happens again save the diags before rebooting.

I have 2 drives now showing smart errors. I've tried to reformat them and assign them, but the kernel has panicked during the rebuild.

I will try to get something to bypass the rake backplate and connect it directly to the HBA to see if that's what is causing the issue. I might also see if there is SATA x4 host to sff-8643 target? I'm not sure if this is a thing. I can only find the host sff-8643 but I want to connect my mobo directly to the backplate to see if the HBA is the issue.

I have this diagnostic when I tried to reformat and it didn't seem to do so successfully.

I will try to keep debugging it once I get more physical stuff to do so.

 

rocinante-diagnostics-20241102-2230.zip

Nov  2 03:52:57 Rocinante kernel: sd 7:0:4:0: Power-on or device reset occurred
Nov  2 03:52:57 Rocinante kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov  2 03:52:57 Rocinante kernel: sd 7:0:4:0: Power-on or device reset occurred
Nov  2 03:52:57 Rocinante kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov  2 03:52:58 Rocinante kernel: sd 7:0:4:0: Power-on or device reset occurred
Nov  2 03:52:58 Rocinante kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
Nov  2 03:52:58 Rocinante kernel: sd 7:0:4:0: Power-on or device reset occurred
Nov  2 03:52:58 Rocinante kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
Nov  2 03:52:58 Rocinante kernel: sd 7:0:4:0: Power-on or device reset occurred
Nov  2 03:52:58 Rocinante kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)

 

This type of errors usually means a power/connection issue.

Hmm, I'll see what I can do about that, I currently have 1 molex cable per backplate (like between the psu and backplate and not sharing the same cable between multiple), I believe there is 2 plugs but the docs say they are for redundant power.

I really appreciate the help  

Ok, I ended up splitting the drives up into 2 backplates and it's looking better, I am now rebuilding the data and hopefully, it'll be normal this time

rocinante-diagnostics-20241103-1617.zip

rocinante-diagnostics-20241103-1732.zip

It seems like one of the drives is really dead? 

Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#564 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 d2 80 00 00 02 e8 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450482816 op 0x1:(WRITE) flags 0x0 phys_seg 93 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#566 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 ce 80 00 00 04 00 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450481792 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#567 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 bf e8 00 00 01 28 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450478056 op 0x1:(WRITE) flags 0x0 phys_seg 37 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#568 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c8 b0 00 00 01 d0 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450480304 op 0x1:(WRITE) flags 0x0 phys_seg 58 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#570 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c1 10 00 00 01 70 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450478352 op 0x1:(WRITE) flags 0x0 phys_seg 46 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#571 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c6 48 00 00 01 50 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450479688 op 0x1:(WRITE) flags 0x0 phys_seg 42 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#572 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c7 98 00 00 01 18 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450480024 op 0x1:(WRITE) flags 0x0 phys_seg 35 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#574 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 ca 80 00 00 04 00 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450480768 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#575 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 c2 80 00 00 03 c8 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450478720 op 0x1:(WRITE) flags 0x0 phys_seg 121 prio class 2
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 Sense Key : 0x2 [current] 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 ASC=0x4 ASCQ=0x0 
Nov  2 22:35:28 Rocinante kernel: sd 7:0:2:0: [sdd] tag#512 CDB: opcode=0x8a 8a 00 00 00 00 00 1a d9 d5 68 00 00 04 00 00 00
Nov  2 22:35:28 Rocinante kernel: I/O error, dev sdd, sector 450483560 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2
Nov  2 22:35:58 Rocinante kernel: sd 7:0:2:0: [sdd] tag#565 CDB: opcode=0x12 12 00 00 00 24 00
Nov  2 23:30:55 Rocinante emhttpd: spinning down /dev/sdd
Nov  2 23:31:39 Rocinante emhttpd: read SMART /dev/sdd

 

If that's the case I'll just need to run without it

Still looks more like a power/connection issue, swap cables with a different disk and retry, that should confirm, where the issue is.

I am using a Corsair AX 1000 I've tried both molex cables it comes with. I'll see if I can get a SATA to molex adapter to test with.

I don't think I am anywhere near the max watts for the PSU itself It is powering an AMD Ryzen 9 5900X and Nvidia 3080. there should still be lots of headroom for the PSU.

I power if it's overheating since the SilverStone RM43-320-RS does get a little toasty and the PSU is facing towards the CPU since the case didn't have holes on the other side

After much messing around, it seems like there might be an issue with the backplate, when I bypass it and correct it directly to the mobo or HBA, it seems to pick up all 4 drives right away.

Imma contact Silverstone to see if I am doing something wrong or if there's an issue with the backplates

 

Thanks again