March 23, 201115 yr Hey Guys, Running 5 beta 5b. Just put in a 500Gb drive, has been running in another computer with no issues. It attached itself to the array without any issues. I ran parity check after this and didn't experience any issues. Used it as a TimeMachine backup drive for a few weeks, just ran another Parity check and it came up with a top of errors. Syslog is 2Gb. Here's a screenshot, and slice of the issues below: Mar 23 11:57:17 Media kernel: md: disk0 read error Mar 23 11:57:17 Media kernel: handle_stripe read error: 308000192/0, count: 1 Mar 23 11:57:17 Media kernel: md: disk5 read error Mar 23 11:57:17 Media kernel: handle_stripe read error: 308000192/5, count: 1 Mar 23 11:57:17 Media kernel: md: disk0 read error Mar 23 11:57:17 Media kernel: handle_stripe read error: 308000200/0, count: 1 Mar 23 11:57:17 Media kernel: md: disk5 read error Mar 23 11:57:17 Media kernel: handle_stripe read error: 308000200/5, count: 1 Mar 23 11:57:17 Media kernel: md: disk0 read error
March 23, 201115 yr It seems your parity has gone offline. I would check the cables on both and pull SMART reports on both. The parity red-ball will not fix itself. You will have to get that drive back on-line or a new one in there and then re-build parity. You can start the array with that one unassigned and then it will be considered new when you assign it again. Peter
March 23, 201115 yr Author Yeah just checking it from work, restarted and it showed the setup below. Basically said I've plugged in a new parity drive. Size and serial look the same, and Beta 5 doesn't have the slots issues beta 6 has? First thing to check cables as you said, then I'll figure out what to do from SMART reports. Cheers for the quick reply
March 23, 201115 yr Author One of the cables was very slightly tweaked. Smart utils showed passed, but highlighted that my Seagate Terras still need a firmware update. Better get onto that - sigh.. Both the drives were on the bridge on the controller, so potentially the motherboard might be going. I'll have to keep an eye on it... Cheers for the help
March 23, 201115 yr Those errors usually relate to cabling or the drive itself starting to go. Get smart reports from your drives and find out if any have a higher reallocated sector count or a higher pending sectors count.
March 23, 201115 yr Yup, appears any connection to the parity drive was lost completely and then it came back. I'd replace the cables and then rebuild the parity if the SMART reports look OK. Peter
March 23, 201115 yr Author Here are my smart reports. I couldn't see anything out of the ordinary... I'll replace the cables tonight. Went to do a parity sync, and 30 minutes into it the server locked up!! sdf is parity sdg is seagate No good...! smartsdf.txt smartsdg.txt
March 26, 201115 yr Author Sweet - appears it was a SATA cable issue. Before I was getting abysmal performance, now I'm getting 32MB/s without cache drive. I wonder if a bad cable for however many months would have caused data corruption?
March 27, 201115 yr It shouldn't but you never know. There is error checking (I believe it's CRC) on the SATA link so "bad bits" shouldn't make it through. Peter
Archived
This topic is now archived and is closed to further replies.