this post was submitted on 26 Jan 2025
32 points (92.1% liked)

Linux

49418 readers
2362 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
32
What's the best way to add a secondary drive? (lemy.lol)
submitted 5 days ago* (last edited 5 days ago) by [email protected] to c/[email protected]
20 comments fedilink hide all child comments
 

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:

  1. 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
  2. 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:

you are viewing a single comment's thread
view the rest of the comments
[–] rtxn 14 points 5 days ago* (last edited 5 days ago) (1 children)

If you have a specific purpose in mind for the drive, then mounting it statically is probably the easiest solution.

My setup is:

  • 2 TB NVMe
    • 200 GB partition at /
    • The rest (~1.8 TB) mounted at /games
  • 1 TB SATA SSD mounted at /home
  • 3 TB HDD mounted at /hdd

/mnt and /media are used differently based on the OS. /mnt is supposed to be used for temporary manual mounts, but you can use it (or a subdirectory) as a permanent mount point. /media is meant to contain mount points for dynamically mounted removable devices, but modern systems generally use /run/media/$USER for that purpose; I would personally avoid it nevertheless.

[–] [email protected] 3 points 5 days ago* (last edited 5 days ago) (2 children)

(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

[–] that_leaflet 3 points 5 days ago (1 children)

I use Gnome Disks for this, even on Kinoite.

[–] [email protected] 1 points 5 days ago (1 children)

Ah interesting, is the process more automated with it?

[–] that_leaflet 3 points 5 days ago

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.