As the title of the post suggests. Had a faulty drive on Disk 11. Got a new Hard Drive and after running preclear on it I assigned it to Disk 11.

 

However Unraid still says there is not proper disk there and is running on emulated version.

 

 

unraid-tower-diagnostics-20250314-2010.zip

9 minutes ago, bm83 said:

Got a new Hard Drive and after running preclear on it I assigned it to Disk 11.

Looks like you rebooted after that. syslog only has about 1.5 minutes in it. Can't tell what happened before boot.

 

My guess is that it disabled the new disk as it was rebuilding.

 

Looks like it should be OK to rebuild if you fix whatever disabled it. Probably bad connection.

 

Do you still have the original disk?

2 minutes ago, trurl said:

Looks like you rebooted after that. syslog only has about 1.5 minutes in it. Can't tell what happened before boot.

 

My guess is that it disabled the new disk as it was rebuilding.

 

Looks like it should be OK to rebuild if you fix whatever disabled it. Probably bad connection.

 

Do you still have the original disk?

 

 

I do have the original disk. But it's the one that does not register at all on the system. 

 

Did check all the cables etc. and these are all good. 

 

 

Try rebuild again and don't reboot before getting diagnostics if there are problems.

You can use this procedure:

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

8 minutes ago, trurl said:

You can use this procedure:

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

 

 

Thanks I did that but now I have errors showing up on Disk 11 -  Error 1024.

 

The Unraid server is stuck at "Read Check 0.0% * Paused".

 

 

 

unraid-tower-diagnostics-20250314-2053.zip

Mar 14 20:51:25 unRAID-Tower kernel: md: recovery thread: recon D11 ...
Mar 14 20:51:26 unRAID-Tower kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
### [PREVIOUS LINE REPEATED 9 TIMES] ###
Mar 14 20:51:26 unRAID-Tower kernel: mpt2sas_cm0: log_info(0x31110101): originator(PL), code(0x11), sub_code(0x0101)
### [PREVIOUS LINE REPEATED 49 TIMES] ###
Mar 14 20:51:26 unRAID-Tower kernel: sd 1:0:12:0: [sdn] tag#5636 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 14 20:51:26 unRAID-Tower kernel: sd 1:0:12:0: [sdn] tag#5636 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 48 40 00 00 00 08 00 00
Mar 14 20:51:26 unRAID-Tower kernel: I/O error, dev sdn, sector 18496 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Mar 14 20:51:26 unRAID-Tower kernel: md: disk11 write error, sector=18432
Mar 14 20:51:26 unRAID-Tower kernel: sd 1:0:12:0: [sdn] tag#5635 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 14 20:51:26 unRAID-Tower kernel: sd 1:0:12:0: [sdn] tag#5635 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 44 40 00 00 04 00 00 00
Mar 14 20:51:26 unRAID-Tower kernel: I/O error, dev sdn, sector 17472 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0
Mar 14 20:51:26 unRAID-Tower kernel: md: disk11 write error, sector=17408
Mar 14 20:51:26 unRAID-Tower kernel: md: disk11 write error, sector=17416
Mar 14 20:51:26 unRAID-Tower kernel: md: disk11 write error, sector=17424
Mar 14 20:51:26 unRAID-Tower kernel: md: disk11 write error, sector=17432

and so forth.

 

Looks like you were rebuilding in maintenance mode, since no disks were mounted when rebuild started. Makes it harder to know if all disks were mountable or not but earlier in syslog I could see them mounting OK.

 

SMART for new disk looks fine, but it disconnected and is now unassigned device sdae.

 

You have a lot of disks, so I suspect power. Any splitters? Ideally, no more than 4 disks per PSU cable.

Alright switched the drive placement and started the process again. 

 

Seems to be working right now as far as I can tell. 

 

Good to go from this point onwards?

Scratch that. Error on another drive right now - Disk 18. 

 

Also error is back on Disk 11. 

 

So the array rebuild is stuck at 0.3%.

 

 

unraid-tower-diagnostics-20250314-2138.zip

I've moved that faulty drive to another location. 

 

Going to try running rebuild again.  

Error once again. 

 

Time to take the server apart and figure out what going on. 

 

I was analyzing the diagnostics and preparing this response when you posted again.

15 minutes ago, bm83 said:

Error on another drive right now - Disk 18. 

You have single parity and 1 disabled disk, so it can't disable another. I think most would consider having dual parity with so many disks.

 

Disk18 disconnected and reconnected as unassigned sdae

 

Looks like disk11 and disk18 are on different controllers, so power is still the main suspect.

 

35 minutes ago, trurl said:

I was analyzing the diagnostics and preparing this response when you posted again.

You have single parity and 1 disabled disk, so it can't disable another. I think most would consider having dual parity with so many disks.

 

Disk18 disconnected and reconnected as unassigned sdae

 

Looks like disk11 and disk18 are on different controllers, so power is still the main suspect.

 

 

 

Yes they are on different controllers.

 

Going to take everything apart and see tomorrow. 

 

I will also get another drive to add additional parity. 

 

Thanks for all your help... I'm sure I'll be reaching out tomorrow!

Also recommend upgrading to 6.12.15 as soon as possible, ideally before attempting more rebuilds, there's a bug that can disable an extra disk.

Thanks. Ordered a new psu (with support for 12 sata drives without any extenders). 

 

Going to give that a try and see what happens. Also, will keep that in mind about the upgrade.

 

Cheers