this post was submitted on 30 Jul 2026
26 points (96.4% liked)
Linux
14526 readers
672 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You should ALWAYS back up any important/irreplaceable data before making any changes to your hard drives, even if you think the risk is low. Accidents happen.
You can move the drive from one slot to the other, the drive's UUID should not change. You'll just need to change the boot drive selected in UEFI. Physically swapping the drives will be faster, easier and less failure-prone than trying to move your boot and root partitions between drives.
For editing drive formats and partitions, the best tool is gparted: https://gparted.org/
It's convenient to have gparted installed on a USB drive so that you can live boot it and use it to make changes to the system drive(s). With gparted you can simply erase the Windows drive and create a new partition formatted for Linux (probably ext4).
If you are not already familiar with editing disk partitions and formats, you should read some tutorials first: https://gparted.org/articles.php
As for encryption, some Linux installers have this as a selectable option during the install process. If Mint does, you should consider reinstalling anyway to use that, as you are more likely to have it working properly.
If you just want to encrypt your data partition(s) you can implement LUKS with cryptsetup: https://linuxvox.com/blog/linux-luks-encryption/
Note that this is the most basic use, it does not cover FDE. If you want to also encrypt /boot so that your computer will not start without being unlocked, that is more complicated to set up:
!! YOU SHOULD READ A LOT OF INFORMATION BEFORE ATTEMPTING THIS !!
https://askubuntu.com/questions/1470391/luks-tpm2-auto-unlock-at-boot-systemd-cryptenroll
https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html
Be aware that doing anything wrong in this process is likely to leave you with an unbootable system, and unable to recover any data from the encrypted partition/drive. You need to be sure that the steps you're going to take are relevant for your hardware and OS before you start, and that you have all of the necessary utilities installed.
Again, if Mint has a selectable option for this in its installer, you will have much better chances of success reinstalling with that.
Don't skip the backup.
Thanks for all the info. The reason I didn't want to do a clean install wasnt because I didn't want to back things up. I just knew I would forget game saves or have program settings revert to default or whatever and spend the next couple weeks slowly running into small issues with my setup.
Pull the current Linux drive. Install Linux with encryption to the current windows drive. Put the other drive back in, copy files and settings over, then wipe it.
You could also use cryptsetup-reencrypt to encrypt the current Linux drive in place. I've done it, works great. But you should always have a backup of anything you can't afford to lose.
You're welcome, and yeah growing pains every time with a new install. But you do it a little better each time.
One recommendation - when you do reinstall, don't use the default/automatic partitioning. Manually set up your /home directory as a separate partition from /root. This lets you reinstall the OS without having to touch your user files. When you reinstall again, all you have to do is select the existing /home partition to use as the new install's home (and make sure not to format it). This makes your install a lot more flexible, and your OS a lot more disposable.
If you do manual partition configuration, don't forget to also create a /swap partition that is at least 1.5x the size of your RAM.
Another benefit of a separate home you can keep is that a lot of linux-native programs store their preferences and other stuff in ~/.config or ~/.share, so you get the added bonus of not having to set these programs up again as well.
Separating home is unnecessary these days with btrfs, Fedora for example will let you reinstall while preserving /home/.
I generally feel more comfortable having /home as a separate partition. It makes editing my partitions with external tools like gparted very easy, and I can just wipe /root whenever I like without having to think too much about. Also, are we considering btrfs to be reliable now? Last time I looked at it, it was still in the prototype/unstable phase and I chose ZFS for my server instead.
Another reason I keep /home separate is that I have systems with multiple Linux versions installed. Each has their own /root, and they share /boot, /swap and /home.
It's the default for fedora, ubuntu, opensuse, cachyos, so i'd say yes, or at least it's feature set is worth it's "unstability".
This would work just fine with mount points on btrfs, probably not on a regular distro as you can't usually customize them like this, but on a terminal based install like arch? not a problem.