Date: Tue, 25 Feb 2020 10:04:07 -0500 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Daniel Kalchev <daniel@digsys.bg> Cc: Mario Olofo <mario.olofo@gmail.com>, Mark Millard via freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Running FreeBSD on M.2 SSD Message-ID: <1D2EB492-F287-40B3-A52C-C1A464C7C3C3@gromit.dlib.vt.edu> In-Reply-To: <0936F546-2839-4190-88A1-A7D2BADBB210@digsys.bg> References: <CAP4Gn9DFAoQtq6NP4hZ-Jq=ddnhp7Bzc_X%2BSce2FPVWn6kjASg@mail.gmail.com> <202002250115.01P1F9KX090465@mail.karels.net> <CAP4Gn9CqCSk5Lof_-05j1S0EWmTdB_HRfOe5zVig5khf7wJ0ow@mail.gmail.com> <188F34DA-192C-4D44-96B5-18A7DAE8EC67@digsys.bg> <6028c786-8610-01d9-818e-6f69a2fe9645@ingresso.co.uk> <CAP4Gn9D5FwZFrrS9uyYFU6MoRpppTcDYZdzRKqH5CPywUSJCZQ@mail.gmail.com> <0936F546-2839-4190-88A1-A7D2BADBB210@digsys.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 25, 2020, at 9:03 AM, Daniel Kalchev <daniel@digsys.bg> wrote: > 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. >=20 > But for FreeBSD, an mechanical SATA, hybrid SATA or SSD SATA will use = exactly the same SATA driver. It depends on the chipset. >=20 > It is possible however, that the timing between the drive and the SATA = controller might be different and that is causing the problem. In a similar vein, I had an old MacBook Pro 2011 model. Its SATA = chipset would negotiate SATA III speeds but any disk I/O at that speed = would soon lead to widespread data corruption. SATA II drives and = slower would be fine: no corruption. The funny thing was that this wasn't an issue when I used earlier = versions of macOS: the problem only seemed to manifest when I "upgraded" = to Mojave (IIRC). I surmised that maybe at that time period, whatever = quirks or workarounds in the earlier OS versions no longer applied, and = so whatever had caused the SATA III replacement drive to work (e.g., by = force-negotiating at the slower speed) no longer did. :-( So, maybe a quirk/workaround that is in Linux and Windows but not in = FreeBSD for you hardware *might* be a possibility? Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1D2EB492-F287-40B3-A52C-C1A464C7C3C3>