fonzie Posted September 7, 2011 Posted September 7, 2011 I just ran a parity check on my unRAID about two days ago. It says parity is valid and came back with 0 errors. My concern is that my Disk1 shows 276 errors on my main page (//tower). I'm running unRAID 4.7 CASE: NZXT WHISPER WHI - 001BK Black Aluminum / Steel ATX http://www.newegg.com/Product/Product.aspx?Item=N82E16811146051 PSU: CORSAIR Enthusiast Series CMPSU-650TX 650W ATX12V http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005 MOBO: ASUS M4A785-M AM3/AM2+/AM2 AMD 785G HDMI Micro ATX http://www.newegg.com/Product/Product.aspx?Item=N82E16813131595 CPU: AMD Sempron 145 Sargas 2.8GHz 1MB L2 Cache Socket AM3 45W Single-Core http://www.newegg.com/Product/Product.aspx?Item=N82E16819103888 I skimmed through the syslog and it appears to be read errors, which to my understanding is not a serious issue. I would really like some reassurance just to put my mind at ease. I attached a full syslog as well as a SMART report I pulled from putty on Disk1 thanks smart.txt Syslog.zip
SSD Posted September 7, 2011 Posted September 7, 2011 Make sure to review the stickies at the top of the forum, including this one: http://lime-technology.com/forum/index.php?topic=9880.0 You should also attach a smart report from the disk showing errors.
fonzie Posted September 8, 2011 Author Posted September 8, 2011 UPDATE: I accidentally started another Parity check today but stopped it before it was completed (it was too hot of a day to have all drives spinning for hours) and now my Disk1 shows 0 errors. I still would like some reassurance that it was simply read errors or was it something more?
SSD Posted September 8, 2011 Posted September 8, 2011 UPDATE: I accidentally started another Parity check today but stopped it before it was completed (it was too hot of a day to have all drives spinning for hours) and now my Disk1 shows 0 errors. I still would like some reassurance that it was simply read errors or was it something more? Your smart report looks clean. The errors in your syslog may be caused by different things, but the most common reason is some sore of a cabling problem (either sata or PSU). Sometimes just unplugging and replugging the cables can fix intermittent problems like this one. That's where I would start.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.