July 13, 201213 yr 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.
July 19, 201213 yr 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.
July 19, 201213 yr 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.
July 19, 201213 yr 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
Archived
This topic is now archived and is closed to further replies.