chrismex

I thought as much, i will leave the configuration of dockers until tomorrow when the parity will hopefully have built ok, thank you for all of your help today.

I have managed to move all of the data from the drive to another without any issues so looks like the read error is in an area that wasnt being used yet thankfully. While the parity is building for this array is it ok to set up my docker apps and have them start writing data back to the array or is it best to wait until the initial parity check has completed?

Would it cause issues if i stop the parity check then move the data from that drive to a new empty one in the array from media/disk2 to media/disk7 ? Then i could run checks on the drive and maybe a preclear to see if there are fixable errors on the drive or rather than running checks should i just replace that drive?

Hi All, I am new to Unraid and have built a system, tranfered all of my data across added some extra drives and a cache then added a parity drive. I left the system to do the initial parity check over night and have come back to one of the drives having read errors and the parity sync dropping from around 100-150MB/s to 8-9MB/s. I have attached the diagnostics and can see that one of the drives has read errors but want to know what is my best option to resolve this. I understand the drive will likely need to be replaced but is it possible to get a parity build with all of the readable data on that drive so i can rebuilt and not lose everything on it. odin-diagnostics-20220405-1019.zip