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 ?s 15:27, Pete Wright <pete at 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 the > > 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 at nomadlogic.org > @nomadlogicLA > >
On 2020-02-24 11:13, 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) > > 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 >Thanks Mario, When you run into issues or filesystem corruption do you see anything in the dmesg buffer or in /var/log/messages? -pete -- Pete Wright pete at nomadlogic.org @nomadlogicLA
On 2/24/20 12:13 PM, Mario Olofo wrote:> 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)Ok, so it's a SATA M.2 SSD - one of these: https://shop.westerndigital.com/products/internal-drives/wd-green-sata-ssd#WDS480G2G0B -- Rebecca Cran
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 at nomadlogic.org @nomadlogicLA