February 7, 201313 yr Well, brand new test build with 2 TB greens is not going so well. The sane thing happened with my original build too. Not sure if its the parity drive or not, it shows about 128 errors in the web interface while running a parity check at about the 35% complete mark... from the syslog they seem to be read errors: Feb 7 15:31:11 UNRAID kernel: handle_stripe read error: 976520072/0, count: 1 Feb 7 15:31:11 UNRAID kernel: md: disk0 read error etc, Parity drive was new out of the package... pre-cleared successfully with 3 passes. Running unraid 5.0rc8 smart-paritydrive.txt
February 7, 201313 yr Author The syslog appears to be incomplete. Please attach the entire syslog. I'm using "cp /var/log/syslog /boot/syslog.txt" is that correct? Its still running the parity check for what its worth I didn't stop it just to see what happens. syslog2.txt
February 12, 201313 yr Author Re-ran a parity check twice and no errors on the parity drive or sync errors on the array in any of 3 checks. Were the original errors in the error log a real read error on the parity drive? I'm having trouble trusting this whole thing.
February 12, 201313 yr The log shows read errors on the parity drive. Post a SMART report for the parity drive.
February 12, 201313 yr Author The log shows read errors on the parity drive. Post a SMART report for the parity drive. its attached to my first post
Archived
This topic is now archived and is closed to further replies.