{"id":137363,"date":"2026-05-29T08:00:00","date_gmt":"2026-05-29T08:00:00","guid":{"rendered":"https:\/\/fedoramagazine.org\/?p=43395"},"modified":"2026-05-29T08:00:00","modified_gmt":"2026-05-29T08:00:00","slug":"installing-fedora-linux-across-two-disks","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2026\/05\/29\/installing-fedora-linux-across-two-disks\/","title":{"rendered":"Installing Fedora Linux Across Two Disks"},"content":{"rendered":"

\"\"<\/p>\n

A year ago, a family member gave me a 2019 laptop that wouldn\u2019t run Windows anymore. And of course, I immediately installed Fedora Linux on it. While my day-to-day Fedora Linux system is a desktop PC, it\u2019s nice to have a laptop to take with me when I do workshops or conference demos.<\/p>\n

However, the laptop has a physical \u201cspinning heads\u201d hard disk, so it is really slow to boot. I timed it; the laptop takes almost two minutes to go from \u201cpower on\u201d to \u201clogin prompt.\u201d And that\u2019s a very long time when you\u2019re at the front of the room, waiting to start a demo.<\/p>\n

I thought about replacing the hard disk with a solid state drive, but when I opened the laptop to make sure the drive was replaceable, I saw that the laptop also supports an NVMe solid state drive in addition to the hard disk.<\/p>\n

<\/span> <\/p>\n

\n
\"Laptop<\/figure>\n<\/div>\n

This presented an interesting opportunity: I could put in an NVMe drive and install Fedora Linux across two disks. Specifically, I wanted to boot Fedora Linux from the NVME drive, and keep extra apps and other data on the hard disk. I use several big third-party apps for my demos, which I install in both \/opt<\/em> and \/usr\/local<\/em>, and it\u2019s a huge pain to download and install those extra applications whenever I upgrade Fedora Linux. (I prefer to wipe and reinstall when I upgrade Fedora Linux, so I always have a clean starting point.) If I could keep \/opt<\/em> and \/usr\/local<\/em> on the hard disk, I could preserve those when I install the next version of Fedora Linux.<\/p>\n

Installing Fedora Linux to the NVMe<\/h2>\n

After installing a new NVMe drive in the laptop, I needed to reinstall Fedora Linux. I prefer the Xfce desktop, so I downloaded the Fedora Xfce spin<\/a> and booted the installer. When the installer reached the \u201cDestination\u201d step, it prompted me for the target disk. I clicked \u201cChoose destination\u201d and selected the NVMe disk:<\/p>\n

\n
\"Fedora<\/figure>\n<\/div>\n

The rest of the installation ran normally. The Fedora Linux installer set up the partitions automatically on the new NVMe drive, encrypted my data, and installed the operating system.<\/p>\n

\n
\"Fedora<\/figure>\n<\/div>\n

With Fedora Linux on the NVMe drive, booting took seconds instead of minutes. Again, I timed it: about 20 seconds to go from \u201cpower on\u201d to \u201clogin prompt.\u201d That\u2019s a huge improvement!<\/p>\n

Setting up partitions on the hard disk<\/h2>\n

The disk partition app in the Fedora Xfce is GParted, which makes it easy to set up the hard disk with new partitions. However, GParted\u2019s main limitation is that it can\u2019t set up encrypted volumes<\/a> for you. If you want to use encryption, you\u2019ll need to use the command line and run cryptsetup<\/em> on your own.<\/p>\n

However, I\u2019m not very concerned about encrypting my \/opt<\/em> and \/usr\/local<\/em> partitions. These are just third-party apps, not private data. My personal data will be saved to my home directory, which is safely encrypted on the NVMe drive. So I decided to set up regular partitions, formatted as ext4 filesystems.<\/p>\n

I used GParted to delete the old partitions on the hard disk, and define three partitions that were each about 300 GB: \/opt<\/em> (which I labeled as opt<\/em>), \/usr\/local<\/em> (labeled usrlocal<\/em>) and \/backup<\/em> (labeled backup<\/em>). GParted created the partitions and wrote an ext4 filesystem on each.<\/p>\n

\n
\"Disk<\/figure>\n<\/div>\n

However, the \/usr\/local<\/em> filesystem has a directory tree in it already, such as \/usr\/local\/bin<\/em> and \/usr\/local\/lib<\/em>, although these directories will be empty after installing Fedora Linux. I wanted to copy the original directories to the new filesystem. The easiest way to do that is to add the new usrlocal<\/em> partition somewhere else and then copy the old \/usr\/local<\/em> to the new partition. Adding a partition to a directory is called mounting, and the directory itself is called a mount point.<\/p>\n

First, I needed to create a new mount point for the usrlocal<\/em> partition, which can be located anywhere on the filesystem. Since this was temporary, I created it under \/tmp<\/em> then mounted the new partition using the mount<\/em> command:<\/p>\n

$ sudo mkdir \/tmp\/usrlocal\n$ sudo mount LABEL=usrlocal \/tmp\/usrlocal<\/pre>\n
Then I copied the contents of the old \/usr\/local<\/em> to the new \/tmp\/usrlocal mount point. The -a<\/strong> or –archive<\/strong> option copies everything:<\/p>\n
$ cd \/usr\/local\n$ sudo cp --archive * \/tmp\/usrlocal<\/pre>\n
After the process is complete, I unmounted the new partition:<\/p>\n
$ sudo umount \/tmp\/usrlocal<\/pre>\n
Adding the partitions to the system<\/h2>\n
To make sure the new partitions are automatically mounted every time my laptop reboots, I needed to add them to my \/etc\/fstab<\/em> file. This is a special file that contains the filesystem table, which is a list of partitions that the system can find on the disk and where to mount them. For example, my default \/etc\/fstab<\/em> file looks like this:<\/p>\n
#\n# \/etc\/fstab\n# Created by anaconda on Sat May 23 20:15:13 2026\n#\n# Accessible filesystems, by reference, are maintained under '\/dev\/disk\/'.\n# See man pages fstab(5), findfs(8), mount(8) and\/or blkid(8) for more info.\n#\n# After editing this file, run 'systemctl daemon-reload' to update systemd\n# units generated from this file.\n#\nUUID=c10ec138-be4b-4513-89b7-749ef4a0605e \/ btrfs subvol=root,compress=zstd:1,x-systemd.device-timeout=0 0 0\nUUID=a87b1ed4-4951-4da1-a4a4-a5c48f1f3b28 \/boot ext4 defaults 1 2\nUUID=9AD9-2C52 \/boot\/efi vfat umask=0077,shortname=winnt 0 2\nUUID=c10ec138-be4b-4513-89b7-749ef4a0605e \/home btrfs subvol=home,compress=zstd:1,x-systemd.device-timeout=0 0 0<\/pre>\n
Each line in the \/etc\/fstab<\/em> file is divided into several fields: the identifier for the filesystem (to learn more about these, see Persistent Identifiers for Storage Devices<\/a> in the Fedora online documentation), the mount point, the filesystem type, a list of mount options, and two optional fields that control if backup software should \u201cdump\u201d the filesystem to backup media (use 0 for never<\/em>) and what order the fsck<\/em> command should check filesystems when needed (usually 1 for the root filesystem, or 2 for other filesystems). I added these lines to my \/etc\/fstab<\/em> file, which defined the mount points for each of my new filesystems:<\/p>\n
LABEL=backup \/backup ext4 defaults,noatime 0 2\nLABEL=opt \/opt ext4 defaults,noatime 0 2\nLABEL=usrlocal \/usr\/local ext4 defaults,noatime 0 2<\/pre>\n
This is an internal drive, so it should be there every time the laptop boots up. If you add removable storage to the \/etc\/fstab<\/em> file, such as a USB drive, you should add the nofail<\/strong> option to this list of mount options. Otherwise, if the partition is not available when Linux starts up, the system will hang.<\/p>\n
With these lines in the \/etc\/fstab<\/em> file, I ran these commands to reload the \/etc\/fstab<\/em> file, create the \/backup<\/em> mount point, and mount each of the filesystems:<\/p>\n
$ sudo systemctl daemon-reload\n$ sudo mkdir \/backup $ sudo mount \/backup\n$ sudo mount \/opt\n$ sudo mount \/usr\/local<\/pre>\n
This generated an SELinux alert right away, complaining that the new \/usr\/local<\/em> filesystem lacked the correct security context. The security information wasn\u2019t \u201ccarried over\u201d when copying the old \/usr\/local<\/em> directory tree. Fortunately, the SELinux error provides the solution:<\/p>\n
\"Text<\/figure>\n
To restore the default SELinux security contexts to the new \/usr\/local<\/em> directory tree, I ran the restorecon<\/em> command. The -v<\/strong> option will print what it does to fix the system:<\/p>\n
$ sudo restorecon -v \/usr\/local
Relabeled \/usr\/local from system_u:object_r:unlabeled_t:s0 to system_u:object_r:usr_t:s0
Relabeled \/usr\/local\/lost+found from system_u:object_r:unlabeled_t:s0 to system_u:object_r:usr_t:s0<\/pre>\n
Filesystem flexibility<\/h2>\n
With just a few extra steps, I was able to use two disks with Fedora Linux, which lets me take full advantage of the storage on my laptop. The operating system now runs from the very fast NVMe drive, while my big third-party applications in \/usr\/local<\/em> and \/opt<\/em> run from the hard disk.<\/p>\n","protected":false},"excerpt":{"rendered":"
A year ago, a family member gave me a 2019 laptop that wouldn\u2019t run Windows anymore. And of course, I immediately installed Fedora Linux on it. While my day-to-day Fedora Linux system is a desktop PC, it\u2019s nice to have a laptop to take with me when I do workshops or conference demos. However, the […]<\/p>\n","protected":false},"author":2,"featured_media":137364,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[45,61,46,47],"class_list":["post-137363","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fedora-os","tag-fedora","tag-fedora-project-community","tag-magazine","tag-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/137363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=137363"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/137363\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/137364"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=137363"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=137363"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=137363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}