Hi all! My first post here so bear with me please . I'm coming here in an attempt to explore the possibilities of talking to a stubborn nvme drive using kernel level pci methods such as by using setpci or nvme-cli among others. My motives are pretty clear, first of all a dopamine shot from fixing this instead of RMAing my drive and ofc recovering my data.

The story is for the most part simple: enabled hyper-v on thuh windows, system BSODed and froze due to bad nvme drivers - the drive no longer responds after a forced power cycle - thnx samsung and msft!
Cold booting causes some hang during POST and the drive led is constantly blinking at the same pace no matter the environment. many environments cannot boot at all while the drive is inserted.

dmesg on ubuntu live looks like this
Code:
dmesg | grep nvme
[ 0.687202] nvme nvme0: pci function 0000:02:00.0
[ 31.250882] nvme nvme0: Device not ready; aborting reset
[ 31.250889] nvme nvme0: Removing after probe failure status: -19
lsblk reports no block devices related to nvme at all, so no way to do anything using hdparm, etc. I had some success with semi bricked ssds using hdparm in past, on several occasions actually.

lspci reports the device's memory controller however:
Code:
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
I have tried using a samsung bootable utility to reflash the firmware but the environment doesn't detect the device either and just runs a reboot script.
What I've done is unpacked the initramfs of this utility and extracted the binaries in order to try and reflash the drive from a more robust and feature packed environment. I'm wondering if there could be a way(has to be) to persuade the device through some of it's pci capabilities or other kernel level methods to stop doing what it's doing and to let me detect it and reflash it.
I'm not a beleiver in modern hardware failures, especially not when it's a 2year old 99% life left ssd. I'm quite certain this is a logical issue and there has to be a way to fix it !

Your help is loads welcome, please join me in this adventure!

update: after a cold reboot nvme list now outputs(after a 30sec hang):

identify failed
NVMe status: Unknown(0x371)

after trying nvme list I now see dmesg throwing up some real treasure of errors:

[ 9.097300] nvme nvme0: pci function 0000:03:00.0
[ 9.097340] nvme 0000:03:00.0: enabling device (0100 -> 0102)
[ 9.222273] nvme nvme0: 7/0/0 default/read/poll queues
[ 9.234497] nvme0n1: p1 p2
[ 41.920083] nvme nvme0: I/O 961 QID 1 timeout, aborting
[ 72.612735] nvme nvme0: I/O 961 QID 1 timeout, reset controller
[ 84.130092] nvme nvme0: I/O 16 QID 0 timeout, reset controller
[ 164.607159] nvme nvme0: Device not ready; aborting reset
[ 164.627443] blk_update_request: I/O error, dev nvme0n1, sector 976773104 op 0x0READ) flags 0x80700 phys_seg 1 prio class 0
[ 164.627511] nvme nvme0: Abort status: 0x371
[ 195.250087] nvme nvme0: Device not ready; aborting reset
[ 195.250094] nvme nvme0: Removing after probe failure status: -19
[ 225.829326] nvme nvme0: Device not ready; aborting reset
[ 225.829566] Buffer I/O error on dev nvme0n1, logical block 122096638, async page read
[ 225.834098] Buffer I/O error on dev nvme0n1p2, logical block 121947888, async page read
[ 225.834462] Buffer I/O error on dev nvme0n1p1, logical block 148208, async page read
[ 225.854260] nvme nvme0: failed to set APST feature (-19)

I'm wondering, since the device won't respond as an nvme block device would there be a pci level method or an argument that would give the controller a jolt ?