From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjammin2068 Subject: Re: WARNING: mismatch_cnt is not 0 on Date: Tue, 8 Nov 2016 13:52:09 -0600 Message-ID: <201d1b91-a08e-480f-fd58-6b44461e65e8@gmail.com> References: <26b91420-97c9-f405-aa71-16cd5cda3a67@gmail.com> <409d9f5f-6f72-a399-93ab-2b10323f4122@fnarfbargle.com> <74e5712f-e89e-97af-8aa4-ae2948c02e94@turmel.org> <27577b8a-1b63-8f1a-9b68-b056622a5268@fnarfbargle.com> <41c176d2-0235-6ff0-996c-b32dc95d487d@gmail.com> <57EAA214.8030603@youngman.org.uk> <5427ce35-f222-8a2c-486e-441c4c6ec9a6@gmail.com> <0f6bd6f6-20ee-1720-23fc-27d206063bfc@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0f6bd6f6-20ee-1720-23fc-27d206063bfc@gmail.com> Sender: linux-raid-owner@vger.kernel.org To: Linux-RAID List-Id: linux-raid.ids 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? Thanks, -Ben