GooseDeer

Hello, So I bought a H310 to replace my H710. I have switched everything over and I have started the parity-check again. Switching over to the H310 provides me with a lot more information and not understand why the raid controller was not recommended. As stated, before I have 6 disks with are 12 TB with one being the parity. 2 of the drives were bought new, and the other 4 were bought refurbished a year ago. I didn't test these drives when I bought them, but they seem to have been working up until now. However, I cannot say that for sure as a lot of the information I am seeing was hidden being the H710 raid controller. I can see the following drives have errors: Disk 1: Reallocated sector count: 27720 Reported uncorrect: 2743 Disk 3: Reallocated sector count: 7200 Reported uncorrect: 2380 The status of the party-check is: Total size: 12 TB Elapsed time: 22 hours, 25 minutes Current position: 11.8 TB (98.2 %) Estimated speed: 987.0 KB/sec Estimated finish: 2 days, 12 hours, 33 minutes Sync errors corrected: 60 Once it gets to around 97% is drops to like 1-2MB/sec, and I have seen it drop to low B/sec when it gets to ~99.7% I have attached a new set of diagnostic logs. I have a couple questions: With the errors, does this mean that the party check is pointless as it ends up taking too long? Are these large error numbers for Disk 1 and Disk 3? I don't really have a reference point. Should I replace these drives? Would it be possible to get a refund from amazon for these drives as I bought them a year ago this month? If there any next steps I can do to improve my situation without have to buy new drives? linux-node-00-diagnostics-20250818-1953.zip

I didn't know that raid controller would cause issues. I currently use a Dell T320 as my server and it has a PERC H710 controller. I have just purchased a H310 in IT mode to replace this with. In the meantime, I will run the array in maintenance mode, and start the data-rebuild again and provide new diag files if it grinds to a holt again.

I’m running Unraid 7.1.2 with 5 data drives and 1 parity drive. A few days ago, during a parity sync, my server unexpectedly restarted. When it came back online, Disk 2 showed a warning: "Disabled – contents emulated." Following advice from the forums, I: Removed the disk from the array. Started the array without it. Stopped the array again. Re-added the drive to the array. When I started the array, the disabled warning was gone, and the system began rebuilding the drive. Initial rebuild behavior: Speed: ~200–300 MB/s Progress: smooth until ~98% At 98%: speed dropped to ~1–2 MB/s At 99%: dropped to just a few B/s, with an ETA of >1000 days. Someone on the forums suggested the slowdown might be due to the drive being written to during rebuild. They recommended running the rebuild in Maintenance Mode. What I tried next: Stopped the array. Started it again in Maintenance Mode. Restarted the rebuild. Current problem: Now the rebuild is only running at 1–3 MB/s from the very start. Additional notes: Drives are ~2 years old. Low usage overall. No obvious SMART errors so far (but I can post a report if needed). Has anyone experienced something similar, or have ideas on how to restore normal rebuild speed? Could this be a hardware issue, or something with Unraid after the restart? Thanks in advance! linux-node-00-diagnostics-20250813-0737.zip