Maikel Verheijen
2014-Oct-14 08:47 UTC
nvd disk on nvme controller not detected at boot-time
Hi list! We recently purchased a HP DL380e G8 server to serve as our backup server with an Intel P3600 that uses the nvme interface. We added load_nvme="YES" and load_nvd="YES" to our loader.conf, and they both get loaded, however the ssd disk device is not detected at boot. When we unload and reload the nvd module the disk does get detected. Is there a way to see if the load-order is correct? We added verbose_loading="YES" to the loader.conf, but dmesg doesn't show me the actual loading. One thing I did see related to the nvme in the dmesg (full dmesg attached) output is this: nvme0: <Generic NVMe Device> mem 0xfbdf0000-0xfbdf3fff irq 16 at device 0.0 on pci3 ? nvme0: SET FEATURES (09) sqid:0 cid:9 nsid:0 cdw10:00000080 cdw11:00000000 nvme0: INTERNAL DEVICE ERROR (00/06) sqid:0 cid:9 cdw0:0 After unloading and reloading the nvd module the disk does get detected: nvd0: <INTEL SSDPEDME400G4> NVMe namespace nvd0: 381554MB (781422768 512 byte sectors) Is there anyone that might give me some pointers on how to get the nvd0 device loaded consistently at boot time? Thanks in advance, Kind regards, Maikel Verheijen -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dmesg_output.txt URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20141014/0d59155e/attachment.txt>
On Tue, Oct 14, 2014 at 1:47 AM, Maikel Verheijen < Maikel.Verheijen at redwood.com> wrote:> Hi list! > > We recently purchased a HP DL380e G8 server to serve as our backup server > with an Intel P3600 that uses the nvme interface. We added load_nvme="YES" > and load_nvd="YES" to our loader.conf, and they both get loaded, however > the ssd disk device is not detected at boot. When we unload and reload the > nvd module the disk does get detected. Is there a way to see if the > load-order is correct? We added verbose_loading="YES" to the loader.conf, > but dmesg doesn't show me the actual loading. > > One thing I did see related to the nvme in the dmesg (full dmesg attached) > output is this: > >Hi Maikel, Which version of FreeBSD are you using? I believe both of these issues have been fixed on HEAD and merged to stable/9 and stable/10. 9.3 and 10.1-RC would have these fixes. 9.2 and 10.0 would not.> nvme0: <Generic NVMe Device> mem 0xfbdf0000-0xfbdf3fff irq 16 at device > 0.0 on pci3 > ? > nvme0: SET FEATURES (09) sqid:0 cid:9 nsid:0 cdw10:00000080 cdw11:00000000 > nvme0: INTERNAL DEVICE ERROR (00/06) sqid:0 cid:9 cdw0: >This was fixed in r263277. Incidentally, the error message here is harmless and not associated with the primary issue you have described above.> > After unloading and reloading the nvd module the disk does get detected: > > nvd0: <INTEL SSDPEDME400G4> NVMe namespace > nvd0: 381554MB (781422768 512 byte sectors) >The load on boot issue was fixed in r263310. Best regards, -Jim> > Is there anyone that might give me some pointers on how to get the nvd0 > device loaded consistently at boot time? >Thanks in advance,> Kind regards, > Maikel Verheijen > > > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >