On 11/08/2016 12:47 PM, Benjammin2068 wrote: > Hey all, > > I'm still trying to work through this.. > > I've replaced the cables on the new AOC-SAS2LP-MV8 and the card itself (supermicro sent replacements) > > > but I still occasionally have the mismatch_cnt error.. (like a week will go by and a weekend raid-check will happen with nothing.) > > So -- my question now (as recommended by someone else) is how to see if it's a drive issue somehow. (not that it's a "real" drive issue, but a card firmware issue that's aggravated by a drive's firmware somehow.) > > I've looked through the logs -- but how do I trace down a mismatch_cnt? I don't see anything in dmesg or messages.... > > There are a couple 3Gb/s drives attached to this card.. maybe that's it? Who knows? But I don't have debug info to help me chase it down now that I'm trying to work it out with Supermicro tech support. > > Where do I look for more info about source or the event of the mismatch? > > Now that I think about it -- and have been talking out loud to myself (I don't think I'm crazy)... A parallel to all this is: I don't think the mismatch_cnt started showing up until I moved from RAID5 to RAID6. :O How painful is it to switch back to RAID5 to test that theory? -Ben -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
