March 14, 201412 yr Hi everyone, I had a disk die on me, and am currently rebuilding it. I happen to glance at the syslog to see how things were going, when I noticed a whack of these types of error messages: Mar 14 04:33:20 Tower kernel: md: disk0 read error, sector=641936912 (Errors) Mar 14 04:33:20 Tower kernel: md: multiple disk errors, sector=641936912 (Errors) Mar 14 04:33:20 Tower kernel: md: disk0 read error, sector=641936920 (Errors) Mar 14 04:33:20 Tower kernel: md: multiple disk errors, sector=641936920 (Errors) Disk0 is my parity drive. My conclusion is that the parity drive is suffering from read errors in restoring my data. Indeed if I look closer at the main screen, it says right there: 46 read errors. Questions: How badly should I worry about the integrity of my (restored) data? What actions should I take to mitigate the errors from the drive? Should I assume the worst and immediately replace the drive? Thanks so much in advance!
March 14, 201412 yr Not a good spot for you...a failed disk AND a failed/failing parity drive. After the failed disk is restored by parity (realizing that parity itself may be broken) write NOTHING to the array until you post a full syslog and get some advice on what to do... http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog
March 15, 201412 yr Author Thanks DaleWilliams, I have attached a syslog. And Smart Status report. syslog-2014-03-15.txt SMART-Drive_0.txt
Archived
This topic is now archived and is closed to further replies.