From owner-freebsd-stable@freebsd.org Fri Feb 28 03:58:11 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B3D7A258B43 for ; Fri, 28 Feb 2020 03:58:11 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48TG3N5KH7z4TDD for ; Fri, 28 Feb 2020 03:58:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.206] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 5fd4360d (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 28 Feb 2020 03:58:07 +0000 (UTC) Subject: Re: Running FreeBSD on M.2 SSD To: Mario Olofo Cc: John Kennedy , freebsd-stable@freebsd.org References: <20200224144602.GA64065@phouka1.phouka.net> <437a5eae-03c8-737d-48bf-39e2e9163d6d@nomadlogic.org> From: Pete Wright Message-ID: <81ef514d-2575-e9e2-136b-dc79d1c62d74@nomadlogic.org> Date: Thu, 27 Feb 2020 19:58:01 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Rspamd-Queue-Id: 48TG3N5KH7z4TDD X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.05 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[nomadlogic.org]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.75)[ip: (-9.29), ipnet: 174.136.96.0/20(-4.04), asn: 25795(-0.39), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2020 03:58:11 -0000 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 >          at scbus0 target 0 lun 0 (ada0,pass0) >   at scbus1 target 0 lun 0 (ada1,pass1) >              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   at scbus0 target 0 lun 0 (ada0,pass0)    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