JustinAiken Posted November 23, 2011 Posted November 23, 2011 Last night I decided to add the new EARX drive I'd finished preclearing to my array, so I stopped it. I stupidly forgot to stop sabnzbd/couchpotato/sickbeard first, not sure that has anything to do with this. When I stopped it, drive8 redballed on me. I saved the syslog: Decided to rebuild drive 8 on the new drive I was planning on adding for expansion, so placed it in the drive slot, let it rebuild overnight. This morning the rebuild was finished, but it's showing that I have 50 errors from the last parity check that finished at 4am; I never ran a parity check, just the rebuild; the only parity checking was the one that ran for a few minutes when I rebooted my server for a couple of minutes before the rebuild (had to reboot due to plugin non-responsiveness...) I'm just wondering what I should do next... -Let it be and RMA the drive that died -if the syslog indicates the drive is actually probably ok, and I should just preclear it and add it back -If I should be in panic mode, facing data loss after the drive8 rebuild
JustinAiken Posted November 23, 2011 Author Posted November 23, 2011 Apparently the forum won't let me post if I include the link to the pastbin... add the e to the link. Weirdness. http://pastbin.com/uJ9ywDbB
dgaschk Posted November 25, 2011 Posted November 25, 2011 Please attach the entire syslog as a text file. Zip if needed.
dgaschk Posted November 26, 2011 Posted November 26, 2011 Only a partial syslog is attached. See http://lime-technology.com/forum/index.php?topic=9880.0
Recommended Posts
Archived
This topic is now archived and is closed to further replies.