Thanks for this clarification. I have very similar question with some changes:
I am about to install the latest fedora 43 on my desktop.
I have 3 Disks, one of which is SSD and the other big ones are HDD.
I am going to read the fedora installation guide. In the meantime I would appreciate any comments on the best way to format my disks and use them during fedora installation.
So-far I realised that the small SSD disk will be used for root and one of the big HDD disks will be used as /home.
As I have 2 HDD (1 and 2 TB each) Will it be possible to somehow merge them into one unit and use the whole 3TB as my /home ?
Technically, you can do this (called a striped volume, possible with LVM (and any filesystem on top) or btrfs, but I would recommend not doing it for one reason. If one drive in your striped volume fails, your entire data is gone. So either have a real good backup in place, or just have the two drives separated. Though you can mount the second drive (1TB HDD) to appear in /home/sina/1TBdata) or use links (mount 1TB drive to /mnt/1TB and link it in your home dir).
As you have already an installed system, you can also keep everything as is, and link the two larger HDDs into your existing /home dir (or mount it there) - no reinstall required.
The Idea of using symlink is very interesting and useful. I realized so-far that /etc/fstab is the important file to check when someone needs to link a storage device to any address in linux.
It seems to me however that as I did not selected the two HDD disks in Anaconda installer during installation phase, the three mount points /, /boot and /home are now installed on my SSD disk. And there are no information about two HDD drives in /etc/fstab. I guess that I need to reinstal fedora while selecting all 3 of my disks and then :
locate / and /boot to the SSD.
locate /home to HDD1
create a symlink for HDD2 to point to HDD1.
Am I right?
Bellow shows the content of my fstab file:
#
# /etc/fstab
# Created by anaconda on Mon Feb 9 09:44:41 2026
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=7602087d-d620-4999-a428-174b581ffe66 / btrfs subvol=root00,compress=zstd:1 0 0
UUID=e54ff3ff-f365-49f7-a9ca-cbd8bbd08d74 /boot ext4 defaults 1 2
UUID=7602087d-d620-4999-a428-174b581ffe66 /home btrfs subvol=home00,compress=zstd:1 0 0
Please don’t post pictures of text… just post the text. Pictures and screeenshots can’t be searched or indexed, and consume more resource than straight text.
Post the output from lsblk -f so we can see exactly what you currently have configured. (as pre-formatted text using the </> button above or surrounding it with three backticks)
You only need to add the disks to the existing fstab but don’t forget the comment:
After editing this file, run 'systemctl daemon-reload' to update systemd units generated from this file.
Then boot the live USB, copy data to the disks, rename the old directories, and add symbolic links to the new locations. I usually leave the /home/username directories and use symbolic links for directories with lots of data after copying them to new mass storage space. You can rename the original big data directories so the original names can be used for the symbolic links. After you have backups for the added storage you can delete the original big data directories.
The one thing I am surprised of is that sdb1 and sdc1 have the same UUID, how come? Did you format them as a single logical volume? Did you set them up as RAID0 (striping/pooling) volume? I guess someone else can answer, I personally don’t use btrfs.
Thanks a lot. There are many things I need to wrap my head around with this topic (and with Linux in general)! Regarding your question, as I was not the one who last managed the file system of this desktop I cannot say it for sure, but yes, your guess is probably very accurate on volume “stripping”.
Thanks a lot. There are many things I need to wrap my head around with this topic (and with Linux in general)! Regarding your question, as I was not the one who last managed the file system of this desktop I cannot say it for sure, but yes, your guess is probably very accurate on volume “stripping”.
I did some reading on “mounting” and followed your comments regarding :
editting fstab file.
running systemctl daemon-reload command.
creating /mnt/hdd1 folder
restarting the system with the live USB
At this point I can see that 3 options for mounting becomes available while requiring my authentification.
when I did mount one of the options and in parallele run lsblk, I saw that new line is added to the recognized filesystems. However when I restarted and returned to the actual installe/etc/fsd fedora that line is gone and there is no new information about the mounted device. what should I do to make this mounted HDD permanently available?
This is the content of my new fstab:
# Created by anaconda on Wed Feb 11 11:04:09 2026
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=99215c5c-077e-48ad-83e7-16582cafe957 / btrfs subvol=root,compress=zstd:1 0 0
UUID=1ec9b78b-39aa-4cf9-9c91-1dab1e44cd8e /boot ext4 defaults 1 2
UUID=99215c5c-077e-48ad-83e7-16582cafe957 /home btrfs subvol=home,compress=zstd:1 0 0
UUID=0029c177-403a-4040-bd24-e3e8b44ed9f2 /mnt/hdd1 btrfs defaults,nofail,compress=zstd:1 0 0