Ver 6.12.8 - Unable to add new drive to array

[illmatik]

I'm trying to add a new 14TB drive to my array. I'm taking the array off-line, adding the new drive to an empty slot and bringing the array back online. 

 

At this point I'm expecting the Disk Clear to begin. It seems to start for a split second and then it switches to a paused Parity Check. 

 

I've tried pre-clearing using Unknown Devices as well, but when the clearing process starts, I'm no longer able to see the drive in UD or see the status of the pre-clear. 

 

I've also tried another 14TB drive I have but I'm observing the same issues. 

optimus-diagnostics-20240805-1257.zip

[itimpi]

I can see in the syslog in the diagnostics that the clear starts, but then almost immediately you fet

Aug  5 12:44:51 optimus kernel: sd 1:0:16:0: Power-on or device reset occurred
Aug  5 12:44:51 optimus kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 8 TIMES] ###
Aug  5 12:44:52 optimus kernel: sd 1:0:16:0: Power-on or device reset occurred
Aug  5 12:44:52 optimus kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 7 TIMES] ###
Aug  5 12:44:53 optimus kernel: sd 1:0:16:0: Power-on or device reset occurred
Aug  5 12:44:54 optimus kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 7 TIMES] ###
Aug  5 12:44:54 optimus kernel: sd 1:0:16:0: [sdr] tag#674 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=6s
Aug  5 12:44:54 optimus kernel: sd 1:0:16:0: [sdr] tag#674 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 08 40 00 00 04 00 00 00
Aug  5 12:44:54 optimus kernel: I/O error, dev sdr, sector 2112 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2048
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2056
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2064
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2072
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2080
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2088
Aug  5 12:44:54 optimus kernel: md: disk16 write error, sector=2096

and then ongoing errors of a similar sort.  Quite why this is happening I am not sure.   Have you carefully checked the cabling (in particular power) to the new drive?

 

 

[illmatik]

I'm using a 20bay chassis which has 5x backplanes. I had to use some splitter adapters to get enough molex power connectors - 2 for each of the 5 backplanes. Perhaps the output on the power supply cannot handle this amount of connections with the splitters? 

 

This is backplane number 5 out of 5 so all of the other ones are each powering 4 drives. 

[illmatik]

I disconnected and re-connected all the molex power connectors going into the backplane and that seemed to have done something as the Disk Clear is performing as expected now.

 

Thank you!