Hi all.

I tried to search for this but I'm not even sure what keywords to use. I replaced one of my data disks and started a data rebuild. I have had to pause it a couple of times due to increased temperatures when all disks are running but it seemed to chug along as expected until it got done with rebuilding the data on the replaced disk sometime tonight.

Currently it's mainly accessing the parity disk, at speeds I'm not sure is correct. It has also amassed 16+ billions of errors, and the number is increasing with ~400 000 per second.

There are two other disks that have ~272 million and ~815 million errors respectively but they aren't showing any read or write activity. The disks that are showing read activity besides the parity disk have speeds of ~8,5 MB/s.

If this is correct, what caused it and how can I fix it?

The GURUs are going to need to see your diagnostics file. Post it up in a new post in this thread. (Do NOT edit your original post to add it!!!!)

Thanks, I forgot to include it. To add; the docker service isn't running - despite it running yesterday - and I can't access any content on the file system.

nas-diagnostics-20260608-1703.zip

Syslog shows errors with multiple disks, are you using any kind of power splitters?

Yes. The power supply has enough power but not enough connectors.

Check/replace all connections; try to avoid splitters as much as possible, but make sure you are not splitting a SATA port into more than two. Molex can handle more than two, though still not recommended.

So stopping the data rebuild and shutting down the server would be ok at this point?

Considering the errors and multiplied risks, there is no point in continuing.

Thanks, I suspected as much but wanted to check.