I’m on a Fedora Kinoite system that is entirely on one LUKS encrypted drive, I recently added a second drive to have more space and I’m wondering how I should make use of it.
For now I formatted it completely with a new btrfs partition encrypted with LUKS and to actually add I thought I could:
- automount it to some location, not sure where I should mount it though, I’ve seen many questions online that say to avoid
/mnt
for permanent drives and also/media
(there are contrasting opinions on that, though), so I thought I could maybe sidestep this question by going with the second option which is the following - extending the already existing btrfs
/sysroot
to span across the 2 partitions on the separate drives, but I didn’t find good information on this process when LUKS is involved. It seems like that kind of operation is heavily discouraged due to risking data loss
So I wonder, what is the best approach and the one that will give me fewer headaches? If it is the second, how do I do it?
Edit: going with the first option I had an issue where the drive wouldn’t be mounted automatically at boot, I then read through my /etc/crypttab
more carefully and saw that the UUID was wrong, I had used the partition UUID (PARTUUID as seen with the blkid
command) instead of the actual device UUID, after correcting that it works and mounts correctly. Just a small oversight, the hardest to notice sometimes.
References:
(Solved, explained in the post)
I’m trying that right now, but I can’t figure out how to decrypt and mount my drive at boot, I’ve read that simply giving the drive the same passphrase as that of the first drive would enable unlocking both at boot (reference), but it didn’t work for me, the drive remains encrypted and also not mounted despite me adding the entry to
/etc/crypyttab
and/etc/fstab
I use Gnome Disks for this, even on Kinoite.
Ah interesting, is the process more automated with it?
The UI is not too complicated, which is why I like it. I use it to automatically unlock and mount my drives in /run/media/drive_name on boot.
deleted by creator