While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Get over 60 games free with Prime Gaming right now - many work on Steam Deck / Linux
- Unified launcher for Windows games on Linux (UMU) v1.1.3 out now
- Proton Experimental gets a big change for video playback in games on Steam Deck / Linux
- Portal 2 project lead wants Valve to return to single-player games
- Factorio 2.0 and Factorio: Space Age DLC are out now
- > See more over 30 days here
-
Save & Sound is a big live show celebrating music in ga…
- Salvatos -
Factorio: Space Age sold over 400,000 copies and sets a…
- dvd -
Steam Deck - SteamOS 3.6 officially out with improved p…
- tuubi -
Co-op dungeon crawler Barony gets a big free expansion …
- Soulprayer -
Factorio: Space Age sold over 400,000 copies and sets a…
- Soulprayer - > See more comments
- New addition to articles
- Liam Dawe - remote desktop software?
- LoudTechie - error: unexpectedly disconnected from boot status demon…
- BlackBloodRum - Digital Foundry did a video about Bazzite.
- Linux_Rocks - Why sometimes piracy is justified?
- dvd - See more posts
View PC info
When I had boot issues with my Pop!_OS installation, I was able to use my MintStick (Linux Mint live USB) to troubleshoot and fix the problem. The Mint Team always includes a number of very useful tools for troubleshooting problems on their live USB. In this case, perhaps Disks or GParted might help where SMART data is concerned?
View PC info
I'm considering doing this in the future, because it just causes too many headaches when something goes pear-shaped... My understanding is that for most "mainstream" distros, the default encryption used isn't all that strong, anyway.
Well, I've had a partial win - using this solution, I was able to decrypt my storage drive from a "live" session... But I can't seem to mount the storage drive using this command (as per the 'Ask Ubuntu' answer ):
udisksctl mount -b /dev/mapper/ubuntu--vg-root
If I had to take a guess, I'd say it's because I'm running Pop!_OS and not Ubuntu; but even when I tried "pop" and "popos", I was given the following errors:
Error looking up object for device /dev/mapper/pop--vg-root
Error looking up object for device /dev/mapper/popos--vg-root
Any ideas what I should use instead of "ubuntu"?
I think that if I can mount the drive from within the "live" session, manually backup the data and then do a "clean" install, I can work around this problem... It's not the perfect solution by any stretch of the imagination, but one which keeps my data safe.
Last edited by Pengling on 27 October 2024 at 11:31 pm UTC
Optionally switch to root:
$ sudo su -
If you skip above, just append sudo to the following.
Start by listing your partitions:
Note: This will work fine on bash, but zsh may throw a no matches found if one of those are missing, in that case just remove the missing one. For example: $ fdisk -l /dev/sd*
$ fdisk -l /dev/{hd*,sd*,nvm*}
This will show partitions from all regular drives, now read through it until you find your drive (See disk model). Under that you'll see a list of partitions, for example it might read "/dev/sda3"
There will probably be multiple partitions on your boot drive, some listed as "EFI System" and such. Try the largest partition first that says "Linux filesystem" or "unknown" (Unknown can occur in some LUKS setups, and does not indicate a problem in that case).
The largest one may be /dev/sda3 for example. Let's try to unlock it:
$ cryptsetup luksOpen /dev/sda3 data3
Let's mount it:
$ mkdir /mnt/data3
$ mount -t auto /dev/mapper/data3 /mnt/data3
If successful you should now see your data in /mnt/data:
$ ls /mnt/data3
On most configurations the largest partition is probably your home directory. Repeat the process for other smaller partitions if they exist, replacing "3" with the partition number, for example to mount an encrypted /dev/sda2:
$ cryptsetup luksOpen /dev/sda2 data2
$ mkdir /mnt/data2
$ mount -t auto /dev/mapper/data2 /mnt/data2
This will likely be your filesystem root ( / ) directory. You can swap and change then numbers or devices as needed, the process is the same.
When done, for each one just do:
$ umount /mnt/data2
$ cryptsetup luksClose data2
While swapping numbers as needed. :-)