How to add extra partitions to Fedora Gnome / KDE

I am attaching a /etc/fstab inline after I point out my problem.
I have serveral other partitions that I need to add to the Fedora 35 KDE system. The same requirement occurred for Fedora 35 Gnome.
I am addind a /Backup /share /music /Development, a /LinuxStuff and a /scratch1 to /etc/fstab.
I follow the steps of verifying the UUID= values, and all the rest.
I create the directory entries as indicated, and then run the command that is indicated on the /etc/fstab Command = sudo systemctl daemon-reload.
I also test mount each of the above directoryies.

On a reboot, I am locked out, the system only loads all the directories save /tmp, as read-only.
The mounts have not taken place.

This is what I had to do to correct the problem for Gnome,
Use the installation USB and visit the recover section, and select root00 of the Fedora installation.
After confirming my selection and the message to enter root mode with chroot… I do re-enter, I immediately exit and then, reboot takes place.
The system reboots, runs selenix autorelabel, and reboots — the system with the new directories loads as one expects.

A similar situation occurred today with the Fedora KDE respin. BUT the respin has no emergency recover option in the boot menu. I believe this is an oversight. However using the Fedora workstation USB, I was able, following the above actions, recover the system.
Below is the Before / after of the /etc/fstab The part listed as AFTER is currently the one in use for Fedora KDE respin.


**# /etc/fstab**
**# Created by anaconda on Mon Nov 22 15:03:51 2021**
**# 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=ef14d4ca-b2df-4793-9766-0ee833285806 / btrfs subvol=root00,compress=zstd:1 0 0**
**UUID=e56ea04c-f221-4b1c-afc3-123f740e8f89 /boot ext4 defaults 1 2**
**UUID=61C4-78B0 /boot/efi vfat umask=0077,shortname=winnt 0 2**
**UUID=ef14d4ca-b2df-4793-9766-0ee833285806 /home btrfs subvol=home00,compress=zstd:1 0 0**
**UUID=50ed96c9-b5b8-452f-ad9c-9b5e59168f0b /LinuxStuff xfs defaults,noatime 0 0**
**UUID=0bbd3f52-6d7a-456d-8475-e35137d6932f /Development xfs defaults,noatime 0 0**
**UUID=b521e017-013f-40ca-bce9-aa3bc8c35c15 /share btrfs defaults,noatime,compress=zstd:1,autodefrag,commit=120 0 0**
**UUID=c04682c7-7fdb-490e-a29a-3b745c3acb4a /scratch1 xfs defaults,noatime,noauto,user 0 0**
**UUID=f31faa18-1781-4d07-91a5-f799306b5d88 /Backup btrfs defaults,noatime,compress=zstd:1,autodefrag,commit=120,noauto,user 0 0**
**UUID=ef53596d-8ec6-42c7-ad98-10bfc187bc62 /music btrfs defaults,noatime,compress=zstd:1,autodefrag,commit=120,noauto,user 0 0**
**UUID=0ece8188-e470-4e8a-875c-c849e358cbf5 /ISOs ext4 defaults,noatime 0 0**

**           AFTER**
**# /etc/fstab**
**# Created by anaconda on Mon Nov 22 15:03:51 2021**
**# 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.**
**#<file system>                            <mount>      <type> <options>                                                        <dmp pass> <xref>            <label/uuid>**
**UUID=ef14d4ca-b2df-4793-9766-0ee833285806 /            btrfs  subvol=root00,compress=zstd:1                                      0  0     #/dev/nvme0n1p11  fedora_localhost-live**
**UUID=e56ea04c-f221-4b1c-afc3-123f740e8f89 /boot        ext4   defaults                                                           1  2     #/dev/nvme0n1p10**
**UUID=61C4-78B0                            /boot/efi    vfat   umask=0077,shortname=winnt                                         0  2     #/dev/nvme0n1p1**
**UUID=ef14d4ca-b2df-4793-9766-0ee833285806 /home        btrfs  subvol=home00,compress=zstd:1                                      0  0     #/dev/nvme0n1p11  fedora_localhost-live**
**UUID=50ed96c9-b5b8-452f-ad9c-9b5e59168f0b /LinuxStuff  xfs    defaults,noatime                                                   0  0     #/dev/nvme0n1p5   LinuxStuff**
**UUID=0bbd3f52-6d7a-456d-8475-e35137d6932f /Development xfs    defaults,noatime                                                   0  0     #/dev/nvme0n1p4   Development**
**UUID=b521e017-013f-40ca-bce9-aa3bc8c35c15 /share       btrfs  defaults,noatime,compress=zstd:1,autodefrag,commit=120             0  0     #/dev/nvme0n1p8   sharebtrfs**
**UUID=c04682c7-7fdb-490e-a29a-3b745c3acb4a /scratch1    xfs    defaults,noatime,noauto,user                                       0  0     #/dev/sdc4        Scratch1**
**UUID=f31faa18-1781-4d07-91a5-f799306b5d88 /Backup      btrfs  defaults,noatime,compress=zstd:1,autodefrag,commit=120,noauto,user 0  0     #/dev/sdc1        Backupsdc**
**UUID=ef53596d-8ec6-42c7-ad98-10bfc187bc62 /music       btrfs  defaults,noatime,compress=zstd:1,autodefrag,commit=120,noauto,user 0  0     #/dev/sdc2        Music**
**UUID=0ece8188-e470-4e8a-875c-c849e358cbf5 /ISOs        ext4   defaults,noatime                                                   0  0     #/dev/sdc3        ISOs**

If you are having a problem with file systems mounting as RO, it generally means some file system is corrupt and thus cannot load as RW, forcing the system into read only mode to mount file systems.

You seem to be using 4 different file systems, which is confusing to me, with btrfs, xfs, ext4, and efi file systems.

You have not posted the actual messages you get when booting, nor have you posted the output of either dmesg or journalctl -b so we cannot have a clue as to the exact cause.

Look at the messages you see from those 2 commands and see if you can identify which device is failing to mount properly (likely / ) then it will need either fsck or the btrfs equivalent run to clean up the corruption. Once that is done then things should mount properly at boot time.

- obsolete -

It works fine with Fedora 35 gnome and Fedora 35 KDE ( after doing the repair). No issues with ubuntu, SUSE EndeavourOS and with Any other distro that supports btrfs.

I write C code and need to test my stuff with these other distros.

The only issue I have is only immediately following the new fresh install where I add the mentioned to the fstab that originated from the installer.

Hello @lsatenstein ,
Since what you say here

Tells me it could be a SeLinux related snag. You likely have to run restorecon, if you can boot the system. It’s too bad the installers didn’t catch the selinux relabling requirements better with existing partitions being added. There must be a way to do it before the reboot happens.

if I understand the problem correctly: use gnome disc - transfer of ownership (recursive).
Other partition: blivet-gui

Yes, it is the repair that fixes the issue. But I do have 4 active disks with many partitions located on that computer. the repair step, selinux autorelabel takes a good half hour to do the tour.

I also discovered the cause After I reformat the fstab lines of /, /home, /boot and /boot/efi, then the issue arises. Otherwise there is no issue.

With restrictions to the padding out and adding the cross reference at the right, the program I wrote and that I use to beautify/cross reference,/check fields/check mounts/ and fstab parameters needs to know how to advise selinux of the change.

What can I run after I modify the /etc/fstab’s top 4 entries (/boot/efi, /boot / and /home) so as to avoid the need to boot into recovery mode. That information should be on the top comments to the fstab file.

I am freely giving out the source to my program. If you can break it or improve it, I will be pleased to incorporate your changes. It is all in C within a git repository. The compiled program is called fstabxref

If I am understanding correctly the real issue is the need to do the autorelabel for selinux.

You can modify your program to do that automatically by adding a command that does ‘touch /.autorelabel’ (obviously with root privileges). It then would halt and do the autorelabel during the next boot so selinux would not force it to the emergency mode.

You could also consider putting selinux in permissive mode so it would not force the autorelabel at boot time. That can be done by editing /etc/selinux/config and changing the line that says

A third option, after the fstab entries have been changed and the file systems remounted would be to manually relabel everything
I found this link that suggests how to do that task.

There have not been many changes in how it works so should still be relevant. Basically the commands are ‘fixfiles relabel’ or ‘restorecon’