I am unable to boot into my fedora so I wanted to edit the fstab from a live disc but it won’t let me do systemd daemon-reload after chroot! Please see the following image.
How are we supposed to edit fstab?
As I understand it you are fixing a problem using the live CD image.
That allowed you to edit the /etc/fstab to include your fix.
You then attempt to do daemon-reload - but the live CD system is not the one that you have changed fstab for.
What you have to do to test your edit is reboot into your system, with the live CD removed.
As seen in the attached image I execured the systemd daemon-reload command after doing chroot.
Are you saying that systemd daemon-reload is not necessary if I reboot to my Fedora Installation? The problem is that the problematic mount points are still creating problems while I reboot even though I commented those in the fstab. I thought that systemd daemon-reload might edit mount unit files. So is it not necessary?
This only affects systemd runtime on already booted system.
If your problem occurs on boot, its cause should be persistent configuration.
Capture the error message during normal boot.
Also try booting other kernels to verify if the problem persists.
Then boot a live session, mount the root volume, and check the output:
grep -v -e "^#" -e "^$" /mnt/etc/default/grub /mnt/etc/fstab
lsblk -p -o +FSTYPE,UUID
When a system is booted the fstab file is turned into mount points in memory.
No files are edited.
The concept in systemd is a generator. Systemd uses generators to turn config files into units used at run time and these are in memory.