liquidkaos Posted October 18, 2011 Share Posted October 18, 2011 Scenario: This morning during the mover script, the parity drive returned 541 errors (and remained green): Oct 18 03:46:05 Tower kernel: md: disk0 read error Oct 18 03:46:05 Tower kernel: handle_stripe read error: 747275568/0, count: 1 The really awesome part of this story is that 4 days ago disk 4 returned 300 errors (and remained green) of exactly the same type. I sent another drive in for RMA that I had sitting on the desk (it was a DOA drive during shipping) and was waiting for it to come back to replace disk 4 in case it had some missing data. The question now is, when the replacement drive comes in, do I slot it in drive 0 or drive 4? LOL! Fug. Quote Link to comment
liquidkaos Posted October 18, 2011 Author Share Posted October 18, 2011 Wow. I just went to stop the array and I heard the machine do a little drive dance and then I lost tower on port 8080, port 80, telnet, ftp, etc. I can still ping it, but otherwise it is just chillin. Quote Link to comment
dgaschk Posted October 18, 2011 Share Posted October 18, 2011 You disks might be ok. It sounds like there may be another problem. Please post the system specs and a syslog. Quote Link to comment
liquidkaos Posted October 18, 2011 Author Share Posted October 18, 2011 I had to power down the machine. Everything came back up, it started parity checking, I stopped it for now until I figure this out. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.