August 1, 201213 yr Hi, I have a couple of quick questions for anyone who might be able to help me. I have been running Pro 4.7 without major issues for a while now (and I'd like to keep it that way)... About 2 weeks ago one of my original Hitahchi 203 2tb drives redballed and I replaced it with a Seagate 2tb that was a warm spare. Parity rebuilt with no probs (zero errors) and I was back in business. Everything seems to be running well, even now. Last night at midnight a monthly parity check started and this morning I see 3 parity errors. (I seem to remember reading awhile back that this sometimes happens in the "housekeeping area" of the disk after it is rebuilt in 4.7, and then won't happen again???) So that is question 1... Are there any data errors or should I just ignore it, unless it happens again? I checked a syslog and a see a ton of these ATA13 drive seek errors.... Does that mean the impending demise of disk 13? Should I do anything about it? Or wait untill it redballs? Or am I way off base on this? I just got back in the mail from warranty repair, the hitachi disk (now seagate) as a certified repaired disk. I was just going to preclear it and put it back in the system. Does anyone have any experience with these recertified disks and their longevity? Thanks so much for an awesome forum, -Richard syslog-2012-08-01.zip
August 2, 201213 yr SMART reporting is disabled for a drive. ata13 does not equal disk13. ata13 could be any disk. It is probably the rebuilt drive. Enable for sda: smartctl -s on /dev/sda Replace sda with the correct designation. This will enable SMART for all drives: smartctl -s on /dev/sd?
August 2, 201213 yr Author I installed the smarthistory.php feature and found a drive that was in my server case as a warm spare (not precleared yet and a fairly recently added Samsung 2TB drive), gave back the notice as "Failed SMART Health test." I am running the preclear scipt on it now... it's been going for about 5 hours so far and 75% into the preread phase... with not much going on in syslog since the preclear started... I guess I'll just wait until the preclear finishes... Any ideas on my other questions? I've attached an updated syslog. Thanks, -Richard syslog-2012-08-02.txt
Archived
This topic is now archived and is closed to further replies.