For some background information I purchased a Framework 13 with the AI 300 Series and brought my own RAM and Storage, both newly purchased, about a year ago and has been working great. I also was running Cachy OS. The issue started when I unplugged it in the morning and it felt a bit hot. When I booted it up, however, Cachy OS told me that the screen locker was broken. I tried to follow the instruction on screen to fix it but none of the keyboard shortcuts were working. I then fully rebooted to see if that would fix the problem but when I did I was encountered by it telling me it couldn’t find a boot drive. I have recently been able to open it up and have inserted the drive into an extra m.2 port on my desktop and it was not detected and also got hot quite quickly. To me this seems like a dead drive, and am planning on RMAing it, but I am concerned that if I put in another one it might get fried as well. Any thoughts?
This just happened to me on a Framework 13 AI 300 series.
The problem is that the boot partition on my SSD had stuff deleted.
I had to re-install systemd-boot and reconfigure it. I got help from someone over at the CachyOS forums. Together we deduced that systemd-boot had been wiped out by a recent update (not sure which package and version).
But would this cause the drive to not be detected by my desktop?
Depends on what “detected” means.
In my case, the internal SSD was not detected as a boot drive (didn’t show up in BIOS Boot Manager). It did show up if I booted from a live USB and then scanned the system using the lsblk command in LINUX.
If you are not even seeing the drive at all in Windows Device Manager or Windows Disk Management or LINUX lsblk, then yes, your SSD is probably dead.