papnikol

Well, it will mean less bandwidth and heat. I also tried pausing parity check every few hours (just a hail mary) and it did not help. One thing I wanna try is rerun memtest (I ran it less than a year ago but you never know) but I have no monitor currently available and i have not found a way to run it headless.

The interesting (and perplexing for me) part is that parity check works ok while 2 parity drives and 11 data drives are being read. It usually freezes after passing the 8TB mark, meaning that 7 of the data drives do not have to be read anymore and spin down.

Thank you both for taking the time. But my CPU is not Ryzen. It is indeed AMD but pre-Ryzen - Athlon X4 840, released in the ancient times of 2014 Also, would it start being problematic after so many years (regarding this aspect)? I am aware of that warning but it was not a problem for me for many years (apart from a few parity errors). As I said before, Why would it suddenly start being problematic now?

Thanks (and I am attaching them here). towers-diagnostics-20260225-0027.zip

During the last few months, parity check has be leading to my server completely freezing (not ever reachable by ssh). The only way to regain access is a hard reset. Some details: The server will rub for days or weeks and only hang during a parity check. Transferring lots of big files is not a problem. I was running unraid 6.12.15 but updated to 7.2.3. That did not fix the problem. The parity check will run for at least the first 8 TBs and but freeze some time after that (my server is 14TBs, a parity drive is 18TBs - although I do not think this could be relevant) I have not changed any hardware VMs and docker are disabled. I had enabled Mirror syslog to flash so I am attaching it but I cannot see anything that would cause the problem When I did a parity swap some months ago, I had to try multiple times (maybe 5 or 6) unit I succeeded (this was quiet anxiety inducing) Any help would be welcome. I am expecting a new HDD any day now and I cannot replace my parity while this problem is going on. syslog-previous-2026.02.24

Thanks again, I really appreciated your (and @itimpi's) willingness to help

Thanks a lot for the help and patience. Rebuild seems to be going fine. I learned some new stuff I had not encountered before. I was wondering, what in the diagnostics file lead you to the conclusion that I should check the disk 3 filesystem?

Here you are:

Here is the msg i get:

Oh, sorry, I took diagnostics before the last step for me to look and I send those by mistake. Sorry for wasting you time. I have attached the correct ones with Array started in normal mode, disk 3 removed. towerp-diagnostics-20241118-1907.zip

Thanks for all your help. I am attaching new diags. I have performed New Config previously to restore a single redballed drive but not for such a case. I am guessing that I can now: - start the array again with disk3 - stop it - assign the new disk3 - start the array again & allow for the rebuild (why did I not think of that?) towerp-diagnostics-20241118-1853.zip

Yes, I had to reboot after the accident I mentioned. I was rebuilding disk 3. disk 1 seems fine

There you go, they are attached. towerp-diagnostics-20241118-1459.zip

Thanks for your response. The disk is disabled but it is fine (a cable was moved but nothing was being written to it, I tested it and it is actually fine) My whole plan is to first find a way to reenable the redballed disk and then start parity rebuild for the actually faulty one that has been replaced with a new disk...

Hi everyone, One data disk in my array needs replacement so I replaced it with a new one and initiated parity rebuild. Unfortunately, during that time my nephew (whom I have now disowned ) pushed my server by mistake and caused another data disk to redball. (I checked it and it is perfectly fine). Ideally, i want to reverse the "redballing", and restart the rebuild for the original faulty disk. Normally (if there was just a redballed disk), i would do that by creating a new configuration and accepting that parity is valid but now I cannot since the new disk was not rebuilt yet. Any suggestions are very welcome