tyrindor Posted July 13, 2012 Share Posted July 13, 2012 Just got SAS MV8 driver errors on B14. During a data rebuild... Going to go back down to B12a.. and now my parity probably has sync errors. Link to comment
whiteatom Posted July 19, 2012 Share Posted July 19, 2012 Did the error stop you from using the array? I thought I had seen that error on b14, but there are no problems afterwards. I can't confirm this, but I believe rolling back only stops the problem with the array going down, not the source error. Link to comment
mbryanr Posted July 19, 2012 Share Posted July 19, 2012 Why haven't you tried rc6? Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Link to comment
sidezero Posted July 19, 2012 Share Posted July 19, 2012 Been running the rc6 test for about 3 1/2 days now. No issues thus far with it and I've ran a parity check and the mover script as well without any issues. Had tons of issues with all releases after B11 previously. Link to comment
tyrindor Posted July 19, 2012 Share Posted July 19, 2012 I got this today on RC6 during a parity rebuild, I believe it's the new form of BLK_EH_NOT_HANDLED. It took 3 days of heavy load, then a parity sync to finally make it happen. I did extended SMART test on the drive, and smart shows no errors whatsoever. Stopped array, removed drive, re-assigned drive, and the drive is going fine again like there was absolutely no problems. I'm sure it's just a matter of time though. More info posted on the RC6 thread: http://lime-technology.com/forum/index.php?topic=21377.msg191317#msg191317 syslog.txt Link to comment
whiteatom Posted October 13, 2012 Share Posted October 13, 2012 Upgrade to rc8a a d this goes away. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.