Hello,

I took a drive out of my array and can't get Partiy Check to complete. I used unbalanced to scatter my data across the rest of my drives. I then did a new config and set all of my array drives back to the correct configuration. I disabled Mover (by scheduling it for a month from the day before I made the change) set my Parity Drive back where it should be, and restarted the array. It got to .5% complete after several hours over night. I then removed the parity drive from the UI, not physically, and unassigned that drive to parity. Then started it up. Then stopped and put it back to force it again. Then my server began crashing. No UI, no SSH access. I updated to the latest version of Unraid, and tried again. This time I was able to get to 1.6% in about 15 minutes. Then it stopped again. The server is more stable and its not crashing, but it isn't progessing. It's just sitting at an estimate speed of 5.2 MB/s, and the ETA is climbing , now up to 35 days. If I look above, the parity drive does not show any rights, and the array drives don't show any reads. I tried to cancel parity, but that function is not working.

Attached are my diagnostic logs. Here are some other notes:
1. All my shares are back without issue
2. When a parity disk isn't assigned I can access those shares from my computers without issue. Initially, I had the shares mapped as shared drives on my Windows computers, and just by having them mapped, they were locking up 2 of my windows computer. The second I shutdown the server, my computers work perfectly again. No more Explorer hangs
3.I have 2 cache drives and both were assigned back correctly too
4. I have docker containers, but I turned off docker to allow the parity check to complete
5. I did the same with my VMs for the same reason.
6. This is the same parity drive that I have been using for quite some time.kong-diagnostics-20260120-0825.zip

Thanks for the help.

unRAID driver is crashing; this is typically a hardware problem, since you have multiple RAM sticks, try again with just one pair, if the same try with the other one, that will basically rule out bad RAM.

Thank you. Testing now. I'll report back when I know more.

Update:
I cheated and did a classic full RAM reseating instead of trying stick by stick. So far so good. 17% done with consistent speeds. Thanks again. I'll follow up once more if there's another failure and I will test RAM stick by stick. Promise.

Update 2: I'm at 91% and everything is still moving along nicely. Thank you again. I'm comfortable say it's solved even if that means jinxing it. Thanks again.

Edited January 21Jan 21 by Nomar1245
Update