@minute The NVMe model of @serpent might not be the issue. I saw the exact same error messages in dmesg as @serpent did with three different NVMe drives after resuming from suspend with a vanilla rescue system booted from SD-Card and the NVMe drive just mounted somewhere before suspending:
- Western Digital WDC WDS100T2B0C-00PXH0
- Transcend 220S M.2 2280 (TS1TMTE220S)
- Kingston NV2 NVMe SSD
[ 807.925640] nvme nvme0: I/O 20 QID 0 timeout, disable controller
[ 808.069698] nvme nvme0: Identify Controller failed (-4)
[ 808.074998] nvme nvme0: Removing after probe failure status: -5
[ 808.101611] nvme0n1: detected capacity change from 1953525168 to 0
See Confirmed Working NVME Drives - #33 by josch and the post after it.