June 3, 201115 yr After roughly a year of no issues, I have my first sync error after the June 1 (NOCORRECT) monthly scan. Array Status STARTED, 3 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 1 times to address sync errors. I've attached the relevant scan logs and smart tests. I haven't run a RAM test because my Server is headless only. Server is a SS4200e with 3 1TB drives. From the forum research I don't think it's RAM though since after 3 NOCORRECT Parity scans it's the same block that keeps coming up. unRAID kernel: md: parity incorrect: 1283201440 I'm not sure how to read the Smart logs, but nothing sticks out and all 3 say PASSED. At this point should I just run Parity and let it correct? Thanks. syslog-20110601-224000.zip parity.txt disk1.txt disk2.txt
June 3, 201115 yr I would just let it correct. In the future, you can use the "md5 - Deep Checksums" package available in unMenu to calculate hashes over your data disks. If this happens again you can check the hashes to make sure none of you data is corrupt and the error is truly on the parity disk.
Archived
This topic is now archived and is closed to further replies.