Date: Mon, 24 Feb 2020 16:13:23 -0300 From: Mario Olofo <mario.olofo@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: John Kennedy <warlock@phouka.net>, freebsd-stable@freebsd.org Subject: Re: Running FreeBSD on M.2 SSD Message-ID: <CAP4Gn9Cy1w=ftw5QrdCFhWOQ_TaOOK=Wj2NGDC6R81fGPPAB6w@mail.gmail.com> In-Reply-To: <437a5eae-03c8-737d-48bf-39e2e9163d6d@nomadlogic.org> References: <CAP4Gn9DbdzSMbj=xn3E4TMRWzs-WY%2Bun2Rzd9Dt3PUeDL%2BYtpA@mail.gmail.com> <20200224144602.GA64065@phouka1.phouka.net> <CAP4Gn9DYui-x_wsDN3TUMd7cDPB%2BTSfRX3TL5DAa=8a1=eRGxQ@mail.gmail.com> <437a5eae-03c8-737d-48bf-39e2e9163d6d@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Pete, The nvmecontrol devlist don't found any devices. pciconf -lv nvme0 didn't found anything either. The camcontrol devlist output was as follows: root@~ # camcontrol devlist <ST10000LX015-1U7172 SDM3> at scbus0 target 0 lun 0 (ada0,pass0) <WDC WDS480G2G0B-00EPW0 UK450000> at scbus1 target 0 lun 0 (ada1,pass1) <SanDisk Extreme 0001> at scbus2 target 0 lun 0 (pass2,da0) The dmesg | grep ada1 shows the following: Feb 24 18:54:31 kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 Feb 24 18:54:31 kernel: ada1: <WDC WDS480G2G0B-00EPW0 UK450000> ACS-2 ATA SATA 3.x device Feb 24 18:54:31 kernel: ada1: Serial Number 183541800480 Feb 24 18:54:31 kernel: ada1: 600.00MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) Feb 24 18:54:31 kernel: ada1: Command Queueing enabled Feb 24 18:54:31 kernel: ada1:457872MB (937721856 512 byte sectors) Mario Em seg., 24 de fev. de 2020 =C3=A0s 15:27, Pete Wright <pete@nomadlogic.org= > escreveu: > > > On 2020-02-24 09:58, Mario Olofo wrote: > > Hello John, thank you for your reply. > > > > Yesterday I reinstalled the 12.1 on a VirtualBox virtual machine, did t= he > > same steps and it didn't corrupted the ZFS, so I think that the problem > is > > in the FreeBSD's driver for m.2 SSD. > > Besides the corruption of the filesystem, I forgot to mention that I > > noticed a little noise on disk writes on FreeBSD, but not on Linux or > > Windows. > > I found some old threads about incorrectly params for sector size for > > Samsung's SSD, but nothing about WD. > > If someone responsible for the driver need help to solve this problem, = I > > can reinstall the FreeBSD on my machine and compile a custom kernel to > > gather debug information. > > Unfortunately you haven't provided much in details regarding the > hardware you are running as far as FreeBSD see's it. I can confirm I > have had many systems using m.2 for quite a while and have had zero > issues. Could you provide some of these details? > > (assuming this is an NVMe device): > $ sudo nvmecontrol devlist > $ sudo pciconf -lv nvme0 > > if your device isn't NVMe and is a sata device then this info may be > helpful as well: > $ sudo camcontrol devlist > > and your dmesg will also probably be helpful here as well. I think > getting at least this basic info will help determine where the issue is > cropping up. > > cheers, > -pete > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP4Gn9Cy1w=ftw5QrdCFhWOQ_TaOOK=Wj2NGDC6R81fGPPAB6w>