sidezero

Everything looks great after the rebuild. Thanks again.

Rebuild is running. Thank you again for all the help.

Ran a repair on the emulated disk and re-started the array in normal mode to confirm there doesn't appear to be a lost+found directory created on the emulated Disk 8. At this point am I good to re-add the new drive in the disk8 slot and start the array/rebuild?

Drive set to xfs and updated diags attached. orbit-diagnostics-20250827-0336.zip

Process followed and updated diagnostics attached. Thank you. orbit-diagnostics-20250826-1253.zip

The failures seem pretty consistent with Disk 8 despite it being in three different slots now. With the current issues is there any process where I can re-install the original Disk 13 and then attempt to rebuild Disk 8 instead with the existing parity data?

Yep, a different vertical and horizontal row.

There are no power splitters in place. When I performed a rebuild I had to purposely purchase an overkill PSU in order to get enough connections for the backplane. I moved Disk 8 to another slot as requested and I saw the same thing upon boot. Disk 8 and Disk 13 are unable to be mounted and the parity operation kicked off. Disk 8 is currently accumulating millions of errors. Updated diagnostic attached. orbit-diagnostics-20250826-0847.zip

I use an old Norco 4220 case. Since the cables are shared to a backplane I swapped slots on the backplane with another drive before it became unmountable.

Updated diagnostics are attached. I haven't stopped the array to re-add Disk 13 yet at this point from the initial slot swap and boot up/auto start. orbit-diagnostics-20250825-1546.zip

I mistakenly removed Disk 13 from the Unraid GUI and had auto start enabled without realizing. Upon boot up Disk 8 is showing additional read errors and unmountable. Disk 13 is also showing the same but that is expected due to my previous manual removal. I still have the original Disk 13 available.

Thank you. Rebuild cancelled and will report back.

Looks like this accidentally got marked as solved early morning when submitted. That’s been corrected. Apologies for the mixup.

Diagnostics attached. Since the failure I've disabled the docker and vm services to limit writes to the array. Disk 13, sdt is the drive originally replaced for the upgrade. Disk 8, sdm is the drive that started throwing errors during the rebuild of sdt. Thank you orbit-diagnostics-20250825-0911.zip

I replaced one of my 6TB drives yesterday to upgrade and during the rebuild overnight a second drive started reporting over 800,000 read errors which have stopped while the rebuild still continues. What should my next steps be? I have the original 6TB drive I replaced still, but data has still been written to the array while the rebuild was in progress overnight.