Date: Sat, 24 Sep 2022 17:11:11 +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-u5yBXhHqmJ@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 --- Comment #4 from Timothy Guo <firemeteor@users.sourceforge.net> --- (In reply to Timothy Guo from comment #3) My SN550 was brought into a pretty bad state that it triggers AER flood on a Linux system and the BIOS was also affected that I can't even enter the BIOS setup page. As a desperate last resort, I move the disk into another machine (a NUC box= ). Magically the NUC box recognized the broken disk without problem, and booted just fine (Actually I lied, it landed on a prompt saying it's a FreeNAS data disk, which at least proves the disk can read just fine). Now after I moved it back to my home server box, the disk backs to live once again. I'm able to scrub the ZFS pool on this disk and find no data error at all. This time, I didn't run into any issue with APST enabled or disabled, which= is really surprising. Let me switch back to the offending FreeNAS system to see how it behaves th= is time. Is this really a physical connection problem? How could it be -- I di= dn't use any adapter cable but directly hook it onto the M.2 slot on my motherbo= ard. --=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-u5yBXhHqmJ>