I think I saw the exact same failure today. Same drive and fw gen. Running Ubuntu and the drive died after a restart. Fwiw I’ve trying to update the fw BIOS over the last couple of days. I submitted a support request.
I just found this thread as I opened up my laptop to start work today and the drive was completely dead. I booted off a live USB and the drive doesn’t even show up in lsblk or nvme list. Nothing in dmesg. I put it in an M.2 USB-C enclosure and hooked it up to another machine and I don’t even see anything in dmesg, so this seems completely dead.
Attached: Internal M.2
LUKS: Is this the default full disk encryption with Fedora? If so, yes.
Died: After waking from sleep
Purchased from Framework in October 2011 as part of my DIY kit
Linux: Fedora 39, whatever the most recent kernel was for that. It was up to date.
WDS500G1XHE-00AFY0
DOM: 3-May-2021
Had this happen to me yesterday as well, all very similar apart from it seems to have taken the storage controller on the mainboard with it (12th gen intel i7-1280p). I can no longer boot to or properly see any internally attached m.2 drive. When booting from USB everything seems to work fine. Not sure if anyone else experienced this and managed to resolve it?
Support ticket is in. Loved the laptop otherwise so hopefully can get this resolved in a meaningful way.
How is the SN850 attached: Internally
Was LUKS in use: Yes
Died after sleep or died on reboot/cold boot: After sleep
Was the drive purchased from us? If so, which date(s): Yes, order date was 28 Jan 2022, 500GB WD Black SN850 - WDS500G1X0E-00AFY0
Which Linux distro and kernel used in this instance: Pop_os! 6.9.3-76060903-generic
I suspect you will find the m.2 module is OK, seeing you can’t use any m.2 module. I’d wait until FW service resolve the problem before trashing your m.2 module.
Had the same thing happen to me today.
How is the SN850 attached: Internally
Was LUKS in use: Don’t know what this is
Died after sleep or died on reboot/cold boot : After (short) sleep - see below
Was the drive purchased from us? If so, which date(s): Yes, order date was 19 May 2022, 1TB WD Black SN850
OS: Windows 10
Model / SN: WDS100T1X0E-00AFY0 / 22047A800083
I was working on my machine with an attached monitor in my office, removed the monitor, closed the lid and disconnected power and moved downstairs to the living room. Left machine for 5 to 10 minutes, opened it up and saw the “Default boot device missing…” message. Various attempts so far to recover the machine have been unsuccessful. Will raise a support ticket shortly
LUKS is a mechanism some linux installations use for disk encryption. Since you’re running Win10, the answer is “no”.
Dino
1 Like
My internal SSD also died a few weeks ago but it was a Gigabyte Aorus GEN4, I thought the boot loader was missing but when I finally got around to trying to repair Pop OS it did not find the internal SSD. Tested it in an M.2 enclosure with my desktop was still unable to see the SSD. Replaced the internal one with another drive and seems to be working fine now.
Is it okay if I fill out the same details here even though I didn’t use the WD850?
How is the SN850 attached: Internally
Was LUKS in use: Yes
Died after sleep or died on reboot/cold boot: Reboot
Was the drive purchased from us? If so, which date(s): Yes, 17 March 2023
Which Linux distro and kernel used in this instance: NixOS unstable, rebooted to upgrade kernel from 6.10.6 to 6.10.7
How is the SN850 attached: Internally.
Was LUKS in use: N/A (Windows)
Died after sleep or died on reboot/cold boot: Sleep/Running overnight
Was the drive purchased from us? If so, which date(s): Yes, 2 September 2022
Which Linux distro and kernel used in this instance: Windows 11
How is the SN850 attached: Internally
Was LUKS in use: No
Died after sleep or died on reboot/cold boot: Reboot
Was the drive purchased from us?: Yes, 16 Sept 2022 (part of DIY 12th gen intel edition, batch 4)
WDS100T1X0E-00AFY0, DOM: 02/09/2022
Which Linux distro and kernel used in this instance: Manjaro with latest stable (well, almost latest, disk failed right after reboot from successfull update).
How is the SN850 attached: Internally
Was LUKS in use: not sure but i guess no as i didn’t used any encryption
Died after sleep or died on reboot/cold boot: After Reboot
Was the drive purchased from us?: Yes, 21 Nov 2021
Which Linux distro and kernel used in this instance: Proxmox 8.1 - i don’t know which kernel sry
Hi,
I don’t know if this might be the cause, but I hear some time ago that some ssd/nvme firmware had a bug such that after a period of time it would fail permanently due to the internal log filling up. There was a firmware fix for the problem.
Does anyone know what firmware their device was on before it failed?
Note, I don’t know if this bug was related to the SN850 or some other make of ssd.
On a more positive note.
In this situation, it is the controller that has failed, and not the flash memory, so if you have lost something valuable, you can take it to a recovery company and get your data back.
Hopefully you have taken backups, so all you need is a replacement ssd. Worth checking with the SSD manufacturer, because sometimes they have warranty that is 2 or even 5 years.
Tap its serial number in here:
I have a SN850X and it is warranty until 2027 !!! 
How is the SN850 attached: Internally
Was LUKS in use: Don’t think so
Died after sleep or died on reboot/cold boot : Cold boot
Was the drive purchased from us? If so, which date(s): Yes. 16 Jan 2022. 1TB WD Black SN850 - WDS100T1X0E - 00AFY0, SN: 21384L805021
Which Linux distro and kernel used in this instance: Ubuntu 20 (not sure exactly which kernel)
How is the SN850 attached: Internally.
Was LUKS in use: No
Died after sleep or died on reboot/cold boot: I think it was sleep.
Was the drive purchased from us? If so, which date(s): No, purchased from BestBuy on 11/7/21. PN: WDBAUY0010BNC-WRSN
Which Linux distro and kernel used in this instance: Windows 10.
I occasionally had the issue where my 11th gen FW13 would be at a black screen or at the screen where it can’t find the boot device and I would have to manually power cycle. This seemed to stop occurring after a BIOS update to (I think) 3.17. A week or so ago it happened again and the drive could no longer be seen, even after using an NVME enclosure connected to a different PC.
I got a Samsung 990 EVO as a replacement and updated the BIOS to 3.20 and haven’t seen any issues yet. Also updated to Win11 when I had to reinstall.