From owner-freebsd-stable@freebsd.org Tue Feb 25 14:04:05 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 149DE25C642 for ; Tue, 25 Feb 2020 14:04:05 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp-sofia.digsys.bg", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Rgdv1fhJz4kr5 for ; Tue, 25 Feb 2020 14:04:02 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from [193.68.6.100] ([193.68.6.100]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.15.2/8.15.2) with ESMTPSA id 01PE3wmD026476 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 25 Feb 2020 16:03:58 +0200 (EET) (envelope-from daniel@digsys.bg) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Subject: Re: Running FreeBSD on M.2 SSD From: Daniel Kalchev In-Reply-To: Date: Tue, 25 Feb 2020 16:03:57 +0200 Cc: Mark Millard via freebsd-stable Content-Transfer-Encoding: quoted-printable Message-Id: <0936F546-2839-4190-88A1-A7D2BADBB210@digsys.bg> References: <202002250115.01P1F9KX090465@mail.karels.net> <188F34DA-192C-4D44-96B5-18A7DAE8EC67@digsys.bg> <6028c786-8610-01d9-818e-6f69a2fe9645@ingresso.co.uk> To: Mario Olofo X-Mailer: Apple Mail (2.3608.60.0.2.5) X-Rspamd-Queue-Id: 48Rgdv1fhJz4kr5 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of daniel@digsys.bg designates 193.68.21.125 as permitted sender) smtp.mailfrom=daniel@digsys.bg X-Spamd-Result: default: False [-1.86 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.961,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:193.68.21.125]; MV_CASE(0.50)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[digsys.bg]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-0.10)[ipnet: 193.68.0.0/19(-0.11), asn: 3245(-0.41), country: BG(0.04)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3245, ipnet:193.68.0.0/19, country:BG]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Tue, 25 Feb 2020 14:04:05 -0000 FreeBSD does not technically have driver for different disks. People = asked whether it is an NVMe device or SATA device, because those = interfaces have different drivers. But for FreeBSD, an mechanical SATA, hybrid SATA or SSD SATA will use = exactly the same SATA driver. It depends on the chipset. It is possible however, that the timing between the drive and the SATA = controller might be different and that is causing the problem. Did you experiment with different settings of the SATA controller in = BIOS? If the problem is related to the size of journal, that might mean for = some reason the SSD is slow. About th eonly thing an SSD might be slow = for is TRIM. Therefore, TRIM might be your problem if weirdly = implemented in that drive =E2=80=A6 so you might try to disable it and = see if the problem goes away. As it=E2=80=99s not a server, I doubt you = will notice much of performance drop. You can disable TRIM for ZFS with sysctl vfs.zfs.trim.enabled=3D0 You can put it in /boot/loader.conf. Do this before writing any data to = the pool or even creating the pool. Speaking of that, the output of=20 sysctl kstat.zfs.misc.zio_trim might tell us something. I would advise doing all such tests with ZFS, because it will spot any = flaky hardware/setup easily. Daniel > On 25 Feb 2020, at 15:28, Mario Olofo wrote: >=20 > Good morning all, >=20 > @Pete French, you have trim activated on your SSDs right? I heard that = if > its not activated, the SSD disc can stop working very quickly. > @Daniel Kalchev, I used UFS2 with SU+J as suggested on the forums for = me, > and in this case the filesystem didn't "corrupted", it justs kernel = panic > from time to time so I gave up. > I think that the problem was related to the size of the journal, that > become full when I put so many files at once on the system, or was > deadlocks in the version of the OS that I was using. > @Alexander Leidinger I have the original HDD 1TB Hybrid that came with = the > notebook will try to reinstall FreeBSD on it to see if it works = correctly. >=20 > Besides my notebook been a 2019 model Dell G3 with no customizations = other > than the m.2 SSD, I never trust that the system is 100%, so I'll try = all > possibilities. > 1- The BIOS received an update last month but I'll look if there's > something newer. > 2- Reinstall the FreeBSD on the Hybrid HDD, but if the problem is the > FreeBSD driver, it'll work correctly on that HD. > 3- Will try with other RAM. This I really don't think that is the = problem > because is a brand new notebook, but... who knows =3D). >=20 > Thank you, >=20 > Mario >=20