31
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Jul 2026
31 points (100.0% liked)
Linux
66096 readers
324 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
I'm a btrfs noob, so I'm skipping any tools that may fix the disk, try those first.
If the media isn't dying, try a file carving tool like photorec. Idk if testdisk supports btrfs but it's worth a try, it's my go-to for undelete and finding lost partitions.
Edit: missed most of your post. First you need to check the kernel logs using the dmesg command. Look for errors that may explain why the disk doesn't show up, especially if it lists scsi or sata in the message.
Edit again: you may want to check the disk's self reported heath using "smart" data. Many bios menus show this info, and there are programs to get it on Linux. If there are too many read or write errors, you need to decide how important the data is. Professional recovery can probably get all of your data if you stop using the drive now and send it in. DIY recovery using a file carving tool would work best if you have another disk to make an image of the failing one with. ddrescue would be the tool for the job to create the image. If you don't have another disk large enough, and the files aren't super important, you can run file carving on the failing disk directly, but the more you use it the greater chance the disk will corrupt more data.
Latest DMESG logs are several days old, I'm not sure I had this problem back then. Nothing seems to be useful there, standard USB connect/disconnect stuff.
I enabled S.M.A.R.T. in BIOS, it seems it doesn't see an issue with the drive (PredictFailure in wmic is FALSE)
PhotoRec and TestDisk do not see the disk when booted from live media, only the 15GB drive itself and 804MB loop0.
Can you post your dmesg output from booting a live USB? Maybe there will be a clue in there.
How is this ssd connected? Nvme? Sata?
When you boot a recovery image does it have any dmesg logs though? You should see something there when you try to mount it
Does "fdisk -l" show all your partitions on that drive?