Look in the syslog for the corrupt file(s) list, then delete them, or restore from a backup, and run another scrub to confirm 0 errors.

1 hour ago, JorgeB said:

Look in the syslog for the corrupt file(s) list, then delete them, or restore from a backup, and run another scrub to confirm 0 errors.

Okay I have the logs and can see the files. Since they are files waiting to be moved I should need to worry about where there final storage would  be on the main array correct?  Because they were not moved. Oh while waiting  I have done smart tests Long self tests and the first two passed. I don't kbow if it matters but I added screen shots of their attributes. 

All passed here are the other two. I am not sure if they even matter but I'd rather give too much info than not enough.

3 hours ago, JorgeB said:

Look in the syslog for the corrupt file(s) list, then delete them, or restore from a backup, and run another scrub to confirm 0 errors.

Okay I deleted the files and ran a scrub (which just shows 240gb scanned out of 1TB) but shows no errors. The stats command and it shows 2 errors. See the attached for both. 

Sorry a total of 6

Okay so I went back and use the cmd prompts given previously cleared it again and for good measure re-ran  the scrub and it all seems clear. For my own sanity will you look over the system logs and tell me if everything looks ok?

syslog.txt

When you get time.  

Thanks again for all your help

Looks OK for now, you can use the script to monitor the pool, so you are warned if new errors come up.

10 hours ago, JorgeB said:

Looks OK for now, you can use the script to monitor the pool, so you are warned if new errors come up.

It seems great. It defiantly had me stressed. I think I spent a week trying to figure it out myself. I am going to mark the memory as what solved the issue although it defiantly led to many more problems. Also I want to say thanks for all the help. Your are appreciated. I will give a donation  not this Friday but the next.