so far just found comapred between LEFT- working vs RIGHT not working
Discussion
dmesg | grep nvme
[ 1.105003] nvme nvme0: pci function 0000:01:00.0
[ 31.607630] nvme nvme0: Device not ready; aborting reset, CSTS=0x3
[ 31.607634] nvme nvme0: Removing after probe failure status: -19
above card not working - below is another host another which is working
dmesg | grep nvme
[ 0.969531] nvme nvme0: pci function 0000:01:00.0
[ 1.185776] nvme nvme0: missing or invalid SUBNQN field.
[ 1.187673] nvme nvme0: allocated 64 MiB host memory buffer.
[ 1.221965] nvme nvme0: 15/0/0 default/read/poll queues
[ 1.230270] nvme0n1: p1
[ 6.380481] nvme0n1: p1
[ 6.520495] nvme0n1: p1
[ 6.600428] nvme0n1: p1
[ 14.292058] nvme0n1: p1
[ 14.332419] nvme0n1: p1
[ 104.053380] EXT4-fs (nvme0n1p1): recovery complete
[ 104.053398] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
I was wiping an NVMe drive on my work laptop because I migrated to a new unit (win11, sadly...) and whilst in the GParted live, I came across this: https://github.com/linux-nvme/nvme-cli
Maybe it could be helpful for your case for diagnostics? iunno, but thought I'd let you know. Should be in most repos - it is in Debian's, that's for sure.
https://nvmexpress.org/ made that tool - my problem is with one TOSHIBHA BG3 KBG30ZMT128G 2242 NVMe (avoid this old) only which has old CHIP after worling 3 times it stopped getting recognized at kernel level so except fro dmesg and lscpi nothing else lsblk or nvme-cli cannot see it anymore. I bought few more NVMe for other purpose and one install win10 - all working fine. i may return that 1 card - BC711 i heard chip is better 
also mSATA at cheap if can get is better than SSD or HDD if can get (speed not important)
BTW win11 donot use in own hw until 2035 - Win7 can still be used - just for good graphics on screen
latest cli - https://monom.org/linux-nvme/upload/AppImage/nvme-cli-latest-x86_64.AppImage
apt install from repo is old v 1.5