Date: Tue, 13 Oct 2015 09:41:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 191348] [mps] LSI2308 with WD3000FYYZ drives disappears after hotswapping Message-ID: <bug-191348-8-FDGyoa1Lwo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-191348-8@https.bugs.freebsd.org/bugzilla/> References: <bug-191348-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191348 --- Comment #29 from Karli.Sjoberg@slu.se --- Look, if you rather want me to open up a new bug report, I can do that, but= the end result is the same as in this report; a disk gets kicked for whatever reason, you reinsert a new drive, but it never shows up. OS timeout is: dev.mps.[0-9].spinup_wait_time=3D5 We experience this problem on very different hardware. There are a couple of different SuperMicro motherboards, X9SRH-F, X8SIL-F, X9DBU-F, an HP DL180 G= 6, and a Sun Fire X4140. Most have one or several SuperMicro SC837E26-RJBOD1 b= ut the HP just have the internal bays and the X4140 has two standard Sun JBOD'= s, can't remember their names right now. So very varying in nature, except for the HBA's, that are all of the same maker; LSI models 9200, 9201, 9211 and several SuperMicro AOC-USAS2-L8i (LSI2008). The hard drives have also been varying. It=C2=B4s happened with Samsung, We= stern Digital and Seagate. And yes, if you insert the "kicked out" drive somewhere else, it works. It shows up and reports no SMART errors. Why does the SAS drive show up while any other SATA drive doesn=C2=B4t, if = it=C2=B4s not firmware/driver related? Who do I blame?:) /K --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191348-8-FDGyoa1Lwo>