Alexandro Posted January 6, 2016 Share Posted January 6, 2016 Hi folks, I had disk disabled due to a read error 3 days ago. As drive cages are part of the system I have checked all the connections for a loose cable, re-seated the drive and followed the procedure for rebuilding it. The rebuild process went fine and the drive came back online. The parity has been checked as the system "advised me" to do so. The parity check was with a "write corrections" option enabled when i started it. When the procedure was completed by nearly 90% the disk was disabled again and the log file was full of errors. I've checked everything again and even attached the disk to the other controller and different cage. This led me to the same situation. Smart test has been executed showing no errors. Please check my syslog and please advise what to do. Do I need a new disk to rebuild onto? TIA. syslog-2016-01-06.txt.zip Quote Link to comment
trurl Posted January 6, 2016 Share Posted January 6, 2016 Post the SMART attributes for that drive. Are you really running 6.0 as it says in your sig? Quote Link to comment
Alexandro Posted January 7, 2016 Author Share Posted January 7, 2016 Hi trurl, Thank you for your answer. I am running the latest 6.1.6 version. Please find attached the requested smart report for the drive. It looks absolutely fine to my understanding. unraid-smart-20160107-0630.zip Quote Link to comment
Alexandro Posted January 7, 2016 Author Share Posted January 7, 2016 I ran a non-correcting parity check. This time the process finished with errors but at least the drive was not kicked out of the array. No smart errors have been reported. Does this means that my parity is not correct? And what do I need to do in order to make it right? I am uploading my diagnostic files and a screenshot showing the errors reported during the parity check. According to the screenshot bellow there are some problems with the drive (critical medium error) but the smart report is clear. unraid-diagnostics-20160107-2117.zip Quote Link to comment
ufopinball Posted January 8, 2016 Share Posted January 8, 2016 Dunno if you have the option, but there's a known problem with the SAS2LP controllers. You show a SASLP card, and I don't know if the problem exists there as well ... but if you can move the drives off that particular controller, it's worth a test. It's a long thread, but you can skip to the last few pages as it covers a lot of what we found: http://lime-technology.com/forum/index.php?topic=42629.0 Good luck! Quote Link to comment
Alexandro Posted January 8, 2016 Author Share Posted January 8, 2016 Hello and thanks for the input. I can completely remove the SASLP controler and use only the H310's for the test. I am not sure this is a controler issue having in mind the long hassle-free history I had with the same configuration till now. 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.