Date: Sat, 24 Sep 2022 15:58:42 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262969] NVMe - Resetting controller due to a timeout and possible hot unplug Message-ID: <bug-262969-227-SoG1Z8v1Vt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262969-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262969-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262969 Timothy Guo <firemeteor@users.sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |firemeteor@users.sourceforg | |e.net --- Comment #3 from Timothy Guo <firemeteor@users.sourceforge.net> --- I have an WD SN570 1TB NVME drive which suddenly run into this controller r= eset problem after about 2 months of active usage. Once this problem shows up it reproduces on every reboot. I'm still trying to confirm if this is an OS driver issue or disk issue. The disk appears to behave differently on different OS. When I switched to Linux, the same problematic disk appears to react to different APST config = and I was able to get it pass some short read-only tests (DD, disk-wide find, g= rep in kernel tree etc.) with APST disabled.=20 No matter if this observation is real or not, it encouraged me to switch ba= ck to my FreeBSD box and try ZFS scrub. Unfortunately the disk fails terribly = this time and I couldn't even get it back to work in Linux as the drive appears = to get stuck in some low power state... Will try dig deeper to see if there is anything I can do to get it back. BTW, the SMART log does not report any error for this drive... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262969-227-SoG1Z8v1Vt>