https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #30 from Stephen McConnell <s...@freebsd.org> --- > --- Comment #29 from karli.sjob...@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. I don't care if you open another bug or not. I'm just saying that this appears to be a different issue and it's best for both of us to be on the same page I think. > > OS timeout is: > dev.mps.[0-9].spinup_wait_time=5 This is a driver variable. It's not actually an OS timeout. This is a wait time between checking if a drive is finished spinning up. This was necessary in order to work around the problem where disks took a long time to spin up (the actual original issue here). By the time they spun up, the driver had given up waiting. This is exactly what I mean by saying that we should try to focus on the correct problem, and not mix it in with this original problem, which seems quite different to me. It confuses things. > > 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 G6, and a Sun Fire X4140. Most have one or several SuperMicro > SC837E26-RJBOD1 but 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´s happened with Samsung, > Western 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´t, if it´s > not firmware/driver related? Who do I blame?:) I'm not sure why the SAS drive shows up or who to blame yet. But, from what I've seen in the logs, it doesn't look like it's the driver, although I'm not completely sure yet. (In fact, if it was the driver I don't think a SAS drive would show up either.) I hope you can get from my previous explanation why I don't think it's the driver. The driver can only react to the firmware events that it receives. If the driver does not get a proper event to add a disk, it can't do it. It looks like the driver is not getting the events that it needs. It's possible that it's a Firmware problem, but I think we would have seen a lot more complaints from customers if that were true. If you can give me some exact, simple reproduction steps I can try to recreate it here. The less number of drives and smaller topology, the better for me since I don't have a lot of equipment at hand. > > /K -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
