Date: Tue, 05 Nov 2024 11:19:46 +0000 From: "Dave Cottlehuber" <dch@FreeBSD.org> To: "Tomasz CEDRO" <tomek@cedro.info> Cc: "Warner Losh" <imp@bsdimp.com>, freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: nvme device errors & zfs Message-ID: <620f4e82-aa69-4af0-bd22-b21203ab8745@app.fastmail.com> In-Reply-To: <CAFYkXjkdvq29aFvNfkmFjb%2BZN8gPJgZFMr942iju=KVcwieDYw@mail.gmail.com> References: <3293802b-3785-4715-8a6b-0802afb6f908@app.fastmail.com> <CANCZdfpPmVtt0wMWAYzhq4R0nkt39dg3S2-zVCCQcw%2BTSugkEg@mail.gmail.com> <ad8551cc-a595-454b-8645-89a16f60ab0f@app.fastmail.com> <CAFYkXjkdvq29aFvNfkmFjb%2BZN8gPJgZFMr942iju=KVcwieDYw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Nov 2024, at 11:10, Tomek CEDRO wrote: > Magician software can upgrade firmware and perform other checks, works > on Windoze macOS and Android: that will be difficult, I don't have an nvme capable thing for any of those. > Another idea is maybe disk overheats and resets itself to cool down? that is a great point, the mainboard comes with inbuilt heatsinks, but when I assembled it, the 2nd nvme slot heatsink looked a lot less bulky than the other one, I remember distinctly wondering if it would cope. If it happens again I'll see if I can get a temp measurement at the time of failure. I would hope temperature throttling would not be quite so brutal, to remove itself from the bus entirely, but its a reasonable explanation. A+ Dave =E2=80=94=E2=80=94=E2=80=94 O for a muse of fire, that would ascend the brightest heaven of inventio= n!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?620f4e82-aa69-4af0-bd22-b21203ab8745>