Date: Sat, 01 Apr 2023 14:30:07 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270409] NVMe: ABORTED - BY REQUEST for TOSHIBA THNSN51T02DUK Message-ID: <bug-270409-227-ef1f9JvpSm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270409-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270409 --- Comment #1 from Thierry Thomas <thierry@FreeBSD.org> --- I have tried many things: BIOS tweaking, with or without hw.nvme.use_nvd, with vmd_load, etc., but no satisfying result ATM. Note: initially, a device /dev/ntfs was shown and locked one NVMe. It was caused by KDE, and freed when I booted the machine without starting KDE. This is very strange: at some time /dev/nvd0 and /dev/nvd1 were there, nvmecontrol identify was OK for the two devices, gpart destroy of the Windows stuff, gpart create and gpart add -t freebsd-zfs were successfull, and I created two zpools on them. But they are not persistent! After a reboot, I see sometimes only one of them, and sometimes none… Remark 1: when I can see a zpool, this is always the same. And yes, when the machine ran Windows, both SSDs were always active. Remark 2: it seems that chances to get at least one NVMe are greater after a cold boot, and chances to see none of them are greater after a reboot. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270409-227-ef1f9JvpSm>