From owner-freebsd-bugs@freebsd.org Wed Oct 14 13:44:26 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6B8EA13911 for ; Wed, 14 Oct 2015 13:44:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 890341DAB for ; Wed, 14 Oct 2015 13:44:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9EDiQ2v001437 for ; Wed, 14 Oct 2015 13:44:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 191348] [mps] LSI2308 with WD3000FYYZ drives disappears after hotswapping Date: Wed, 14 Oct 2015 13:44:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: patch-ready X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: Karli.Sjoberg@slu.se X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 13:44:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191348 --- Comment #34 from Karli.Sjoberg@slu.se --- I did it! I don=C2=B4t think I can provide you with much better data than t= his! Today we installed a new SC837E26-RJBOD1 around 13:20 in the log and insert= ed and pulled the external SAS cable a couple of times for good measure. Then = at around 13:34 we tried inserting the first disk (WD40EZRX) to test out the internal cabling, and then it happened: mpssas_get_sata_identify: error reading SATA PASSTHRU; iocstatus =3D 0x804b mps3: Sleeping 5 seconds after SATA ID error to wait for spinup Just kept repeating over and over again. Tried reinserting it in bay 1 didn= =C2=B4t help. So we tried pulling it out from bay 1 and insert it into bay 2 but wi= th the same result. So we pulled it out and inserted a Seagate ST2000DM001 into bay 1. It didn= =C2=B4t show up, bay "blocked". Reinserted it into bay 2 made it appear at 13:45. A= lso tried putting it in bay 3, also worked. Pulled that one out and inserted a Samsung HD103SI first in bay 1, didn=C2= =B4t work, "blocked". Then tried in bay 2 and 3 made it appear. Then we tried another WD40EZRX in bay 1, didn=C2=B4t work. Bay 2 and 3 work= ed however. We went back to the first "bad" WD40EZRX and tried bay 1, 2 and 3, still didn=C2=B4t work. There=C2=B4s also trace here of me pulling out a WD RE SAS WD4001FYYG from = another SC837E26-RJBOD1 to test with in the "blocked" bay 1 at 14:09. Here I hypothesized that this first bad WD40EZRX permanently taints every b= ay it=C2=B4s inserted in so we tried reinserting a drive that previously showe= d up, at least in bay 2 and 3, the ST2000DM001. Inserting it in bay 1 did nothing, as before. But now I would have thought that it actually wouldn=C2=B4t show up= in bay 2 or 3 either since we had tried inserting the "bad" drive in there. But the ST2000DM001 actually did show up there, in bay 2 and 3, that is. Bay 1 is however "blocked" for any of the SATA drives. As a last test we took the WD RE SAS WD4001FYYG drive and inserted it into = both bay 1 and 2 which worked, as expected, at 13:13. Full log uploaded named "kernel-critical log" Best Regards Karli Sj=C3=B6berg --=20 You are receiving this mail because: You are the assignee for the bug.=