[RESPONDED] WDC Black 850sn (rev 01) not recognised upon boot after suspend to disk

After suspending to disk (as I do a lot), I booted the device again and it does not recognize my disk.

Running a livecd I see this:

root@regolith:~# dmesg -T | grep nvme
[Mon Feb 13 16:29:48 2023] nvme 0000:01:00.0: platform quirk: setting simple suspend
[Mon Feb 13 16:29:48 2023] nvme nvme0: pci function 0000:01:00.0
[Mon Feb 13 16:29:59 2023] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
[Mon Feb 13 16:29:59 2023] nvme nvme0: Removing after probe failure status: -19

Is there a way to get the disk back working or is this broken?
This is my main device, and I cannot work anymore until I get a new disk or second device.

Bios version:

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
Table at 0x439E0000.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
        Vendor: INSYDE Corp.
        Version: 03.17
        Release Date: 10/27/2022
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 12 MB
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                8042 keyboard services are supported (int 9h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 3.17

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: Framework
        Product Name: Laptop

Did you fiddle around with the following setings?


Because this helps on various issues. Sadly, my NVME is broken so I am gonna return it.
It disconnects randomly because the controller automatically shuts down. I dont have this issue with my new drive.


I can’t boot anymore from the disk, it’s not recognised anymore…
I can go in a liveusb environment and I see the disk through lspci, but that’s it.

The error is what dmesg shows when trying to boot.


Then I guess its time to contact Framework support and get your backups.

Edit: which dmesg messages do you get when you plug in your drive?

This is a hardware issue, your best course of action is to get a ticket opened with the hardware team.