I also had an issue that when rebooting with sysrq+reisub the drive sometimes wouldn't show up, but after reseating the drive that doesn't seem to be an issue anymore.
]]>Maybe try a non-arch distro for good measure. Fedora might do the trick becasue it is quite upstream-close.
]]>nvme_core.default_ps_max_latency_us=0
completely fixed the issue. Setting it to 5500 vs 0 also seemed to work, going to test that after I'm sure I don't need to return the drive.
So now this seems like some bug to me, now what do I do with it? I've read the bug guidelines and this seems upstream to me? There are 2 mentions of this fix on the arch wiki, for example here: https://wiki.archlinux.org/index.php/So … drive/NVMe but they are about an older kernel and Samsung drives. Might be something for the wiki to save others some potential headaches?
BTW this is on a Asus laptop, the drive in the Kingston A2000 1TB. LTS or stable doesn't matter. I also dual booted Manjaro to see if it was the drive or my Arch install and it was the same there.
]]>