Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Feb 2020 19:58:01 -0800
From:      Pete Wright <pete@nomadlogic.org>
To:        Mario Olofo <mario.olofo@gmail.com>
Cc:        John Kennedy <warlock@phouka.net>, freebsd-stable@freebsd.org
Subject:   Re: Running FreeBSD on M.2 SSD
Message-ID:  <81ef514d-2575-e9e2-136b-dc79d1c62d74@nomadlogic.org>
In-Reply-To: <CAP4Gn9Cy1w=ftw5QrdCFhWOQ_TaOOK=Wj2NGDC6R81fGPPAB6w@mail.gmail.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help


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 root cause and fix them.  so anyway...i got the drive today and 
i am not seeing 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 
zfs 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 Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81ef514d-2575-e9e2-136b-dc79d1c62d74>