I was doing a every other month parity check and drive 6 (sde) started showing that it was being emulated. I stopped the paityy check, shut down and pulled all of the SATA cables out and reinstalled them. When I restarted, the drive was no longer being emulated so I take that as the issue was resolved due to a bad connection.

I restarted the parity check and when it reached 12gb the parity drive started showing UDMA CRC errors and froze the check.

I installed a new parity drive due to the old one having sync errors being reported and now during the parity rebuild, it has been extremely slow and is now at 0.3% and has not changed in at least 10 hours.

Here is a screen grab of the Array Devices

And here is the Array Operation

While typing this up, the array is now showing read errors on drive 4 so I have attached the diagnostics from just before I started typing this post and another one from just now after the read error was reported.

I do still have the old parity drive that I have not touched and I have a spare 4TB drive in the unassigned disks if I need to connect either one of those for testing.

The only thing I use the server for is as a video server (Jellyfin & Emby) and a few backup documents. My end goal is to get things back to normal and then offload the videos to a stack of bluray discs incase this happens again.

And shrink the array to maybe only 12 - 16tb saving the other discs as emergency replacements.

tower-diagnostics-20260714-1917.zip tower-diagnostics-20260714-1956.zip

6 hours ago, Erik M said:

When I restarted, the drive was no longer being emulated so I take that as the issue was resolved due to a bad connection.

That is not possible; something is missing, once a disk is emulated, only a rebuild (or new config) will fix it.

Diags show you are using a controller with SATA port multipliers; those were never recommended, but they are basically unusable with the latest Unraid releases due to a kernel change/regression. My recommendation would be to replace it; otherwise, downgrade to 7.2.4. Another option that may help with 7.2.5+/7.3.x is to disable NCQ with a kernel parameter by adding this to the kernel options:

libata.force=noncq

Then reboot

I did do a new config, keeping all the same and chose valid pairity before I replaced the pairity drive. That is when the emulation ended.

I was thinking it may be the controler. The motherboard does not have enough SATA connections so I used a controler.

I will try to downgrade to 7.2.4 and see if that changed things before I replace the controler.

Thank you for the infomation!

I did the downgrade this morning before work and it appears to be rebuilding much better. 4½ hours in and it has rebuilt 5.7%. Much better than 53 hours at 0.3%!

Thank You!!!!

I will mark this answered once things finish and return to normal.

Wonderful!
Downgrading solved the issue.

I will have to look around for a motherboard that has more SATA ports before I upgrade to a newer version of Unraid.