Denis Blazevic

The scrub finished without any issues. There were a lot of data errors, which I guess has happened because of previous errors that happened during syncs. All got fixed with snapraid fix -e, execpt one unrecoverable error. I guess I will leave it running with one stick for now, and see if it occurs again. If it doesn't then I know for sure the stick is faulty. I have attached the file.

My setup with the new drive is like following: Two 4TB data drives (the bad drive has been removed and replaced with a new one) One 10TB parity drive. The new data drive has been rsynced with the old bad one, so all the data that could be saved has been saved. (was like 99% saved). So in this case I would just need to do snapraid scrub -p full twice (one with each module). If the scrub fails, I just go and test the other memory? (makes sense I guess) And If the other memory stick doesnt fail, then...

My setup with the new drive is like following: Two 4TB data drives (the bad drive has been removed and replaced with a new one) One 10TB parity drive. The new data drive has been rsynced with the old bad one, so all the data that could be saved has been saved. (was like 99% saved). So in this case I would just need to do snapraid scrub -p full twice (one with each module). If the scrub fails, I just go and test the other memory? (makes sense I guess) And If the other memory stick doesnt fail, then...

My setup with the new drive is like following: Two 4TB data drives (the bad drive has been removed and replaced with a new one) One 10TB parity drive. The new data drive has been rsynced with the old bad one, so all the data that could be saved has been saved. (was like 99% saved). So in this case I would just need to do snapraid scrub -p full twice (one with each module). If the scrub fails, I just go and test the other memory? (makes sense I guess) And If the other memory stick doesnt fail, then...

My setup with the new drive is like following: Two 4TB data drives (the bad drive has been removed and replaced with a new one) One 10TB parity drive. The new data drive has been rsynced with the old bad one, so all the data that could be saved has been saved. (was like 99% saved). So in this case I would just need to do snapraid scrub -p full twice (one with each module). If the scrub fails, I just go and test the other memory? (makes sense I guess) And If the other memory stick doesnt fail, then...

My setup with the new drive is like following: Two 4TB data drives (the bad drive has been removed and replaced with a new one) One 10TB parity drive. The new data drive has been rsynced with the old bad one, so all the data that could be saved has been saved. (was like 99% saved). So in this case I would just need to do snapraid scrub -p full twice (one with each module). EDIT: Also heres the cmp files. cmp_B_15530.1548861290: 431710891 102 73 431710892 3 32 431710893 35 27 431710900 56 65 431710901...

My setup with the new drive is like following: Two 4TB data drives (the bad drive has been removed and replaced with a new one) One 10TB parity drive. The new data drive has been rsynced with the old bad one, so all the data that could be saved has been saved. (was like 99% saved). So in this case I would just need to do snapraid scrub -p full twice (one with each module).

EDIT: Double post...