Date: Fri, 28 Feb 2020 01:44:21 -0300 From: Mario Olofo <mario.olofo@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Running FreeBSD on M.2 SSD Message-ID: <CAP4Gn9AqK0BEmWhJ%2BqPqHcqN__GYf6tyonW6dwnvRqf-a2_www@mail.gmail.com> In-Reply-To: <81ef514d-2575-e9e2-136b-dc79d1c62d74@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> <CAP4Gn9Cy1w=ftw5QrdCFhWOQ_TaOOK=Wj2NGDC6R81fGPPAB6w@mail.gmail.com> <81ef514d-2575-e9e2-136b-dc79d1c62d74@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the update. May you share what quirks was detected for your card and firmware to see if it matches mine? The only way I was able to run FreeBSD 12-STABLE on the SSD was using the suggested sysctl vfs.zfs.trim.enabled=3D0 Maybe the problem really is a combination of factors, for the person that filed a bug on bugzilla the fix was setting the quirks 4k and broken_trim, but for me the real block size is 512bytes and only setting the flag broken_trim didn't help... Mario Em sex., 28 de fev. de 2020 =C3=A0s 00:58, Pete Wright <pete@nomadlogic.org= > escreveu: > > > On 2/24/20 11:13 AM, Mario Olofo wrote: > > 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) > > > just wanted to provide an update here. so i had a system that needed a > new root drive and figured that the price of this device was worth a shot= . > i figured if it has issues it'd be a good opportunity to help find the ro= ot > cause and fix them. so anyway...i got the drive today and i am not seein= g > any issues with it so far. here's the device on my end: > > $ sudo camcontrol devlist > <WDC WDS480G2G0B-00EPW0 UK450000> at scbus0 target 0 lun 0 (ada0,pass0) > <AHCI SGPIO Enclosure 2.00 0001> at scbus2 target 0 lun 0 (ses0,pass1) > $ > > i am running 12-STABLE, with an encrypted zfsroot device. i've pumped > about 10gigs through it so far restoring my homedir with no issues, and z= fs > scrub has run without any corrupted blocks detected. > > so i don't think it's an issue with this specific m.2 device, perhaps > there is something odd happening in your local env though that is causing > this issue to crop up. > > -pete > > -- > Pete Wrightpete@nomadlogic.org > @nomadlogicLA > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP4Gn9AqK0BEmWhJ%2BqPqHcqN__GYf6tyonW6dwnvRqf-a2_www>