I dusted out the server today and disk 1 disabled on array start. Stupidly shut down without grabbing logs/diagnostics and checked cables, as that was an issue for me in the past. Disk 1 SMART looked good on restart and decided to take the opportunity to put a larger drive in. Replaced Disk 1 with a larger drive, started the array to rebuild, and now Disk 7 is disabled. I have dual parity and didn't think I had much option but to hope 1 rebuilds successfully. After some time, the rebuild appears to not be progressing. Elapsed time is ticking up, but other stats are static.

Any help or suggestions on next steps would be appreciated. Thanks!

skynet-diagnostics-20260406-2257.zip

Disk7 has disconnected and is now Unassigned Device sdm. SMART for that disk looks OK.

Both emulated disks are mounted, disk7 is very full.

Shutdown, check connections, all disks, both ends, SATA and power, including splitters.

Since you have dual parity you can rebuild both at the same time.

4 minutes ago, trurl said:

Disk7 has disconnected and is now Unassigned Device sdm. SMART for that disk looks OK.

Both emulated disks are mounted, disk7 is very full.

Shutdown, check connections, all disks, both ends, SATA and power, including splitters.

Since you have dual parity you can rebuild both at the same time.

Thank you for the advice and quick reply! Is there a benefit to using maintenance mode to rebuild, if server downtime isn't a concern, or is that just unnecessary?

I never do. In maintenance mode you can't tell if your filesystems are mountable. But I mostly consider the server down anyway, file access will slow down rebuild, and rebuild will slow down file access.

1 minute ago, trurl said:

I never do. In maintenance mode you can't tell if your filesystems are mountable. But I mostly consider the server down anyway, file access will slow down rebuild, and rebuild will slow down file access.

Makes sense. Thanks, again!