Drives not mounting after upgrading from 39 to 40

Ask Fedora
, ,
1

I upgraded to fedora 40 a couple of days ago from 39, and everything went haywire. I eventually figured out that my drives weren’t mounting, and after running ‘sudo mount -a’ everything magically started working again. however, upon restarting, all my drives are unmounted again. after remounting, I have to update all the settings I’ve made since the last restart.

I’ve tried to select the previous version from grub, but even though I can get to the menu, I can’t change selections, as if it doesn’t recognize my keyboard input, and it autoboots to f40 after a few seconds. I don’t recall what my fstab looked like prior to upgrade, but I wouldn’t expect it to have changed with the upgrade. i’m guessing it’s something in grub, but idk what I would be looking for or how I would make the update.

/dev/mapper/fedora_localhost--live-root /                       ext4    defaults        1 1
/dev/mapper/fedora_localhost--live-home /home                   ext4    defaults        1 2
/dev/mapper/fedora_localhost--live-swap none                    swap    defaults        0 0

/dev/sda1 /mnt/gamma ext4 defaults,x-gvfs-show 0 2
/dev/sdb1 /mnt/alpha ext4 defaults,x-gvfs-show 0 2
/dev/sdc1 /mnt/delta ext4 defaults,x-gvfs-show 0 2
/dev/sdd /mnt/sigma ext4 defaults,x-gvfs-show 0 2
UUID=2473673f-112c-4704-9cb6-c4b4b989c9e0 /boot ext4 defaults,x-gvfs-show 1 2
2

Look in the journal to see what happened during the boot.

sudo journalctl --no-hostname -b 0

Look for the devices that do not mount and see what errors are reported.

1 Like
3

i’m not seeing anything about mount, but I saw several entries related to fstab, which seems to be causing a permission error. i’m not sure if these entries are generated from startup, or my attempts to view the file from cli.

May 28 05:50:34 systemd[1]: systemd 255.6-1.fc40 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCR>
May 28 05:50:34 systemd[1]: Detected architecture x86-64.
May 28 05:50:34 kernel: audit: type=1400 audit(1716893433.112:4): avc:  denied  { write } for  pid=1 comm="systemd" name="memory" dev="proc" ino=4026532064 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=>
May 28 05:50:34 systemd[1]: bpf-lsm: LSM BPF program attached
May 28 05:50:34 kernel: audit: type=1400 audit(1716893433.737:5): avc:  denied  { read } for  pid=667 comm="systemd-fstab-g" name="fstab" dev="dm-0" ino=1706638 scontext=system_u:system_r:systemd_fstab_generator_t:s0 tcontext=system_u:ob>
May 28 05:50:34 (sd-exec-[654]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
May 28 05:50:34 kernel: zram: Added device: zram0
May 28 05:50:34 kernel: audit: type=1400 audit(1716893434.220:6): avc:  denied  { write } for  pid=1 comm="systemd" name="memory" dev="proc" ino=4026532064 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=>
May 28 05:50:34 systemd[1]: initrd-switch-root.service: Deactivated successfully.
May 28 05:50:34 systemd[1]: Stopped initrd-switch-root.service - Switch Root.

...

May 28 05:50:34 systemd[1]: ostree-remount.service - OSTree Remount OS/ Bind Mounts was skipped because of an unmet condition check (ConditionKernelCommandLine=ostree).
May 28 05:50:34 systemd-journald[706]: Journal started
May 28 05:50:34 systemd-journald[706]: Runtime Journal (/run/log/journal/3626d56de4b6476088f3da3302990147) is 8.0M, max 319.3M, 311.3M free.
May 28 05:50:34 audit[706]: AVC avc:  denied  { write } for  pid=706 comm="systemd-journal" name="memory" dev="proc" ino=4026532064 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=0
May 28 05:50:34 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 28 05:50:33 systemd-fstab-generator[667]: Failed to open /etc/fstab: Permission denied
May 28 05:50:33 systemd-sysv-generator[675]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit >
May 28 05:50:33 systemd-sysv-generator[675]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file,>
May 28 05:50:34 systemd[1]: Queued start job for default target graphical.target.

...

May 28 05:51:41 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 28 05:52:09 audit[1950]: AVC avc:  denied  { getattr } for  pid=1950 comm="gsd-housekeepin" path="/etc/fstab" dev="dm-0" ino=1706638 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=fil>
May 28 05:52:09 audit[1950]: AVC avc:  denied  { getattr } for  pid=1950 comm="gsd-housekeepin" path="/etc/fstab" dev="dm-0" ino=1706638 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=fil>
May 28 05:52:10 geoclue[2225]: Service not used for 60 seconds. Shutting down..
May 28 05:52:10 systemd[1]: pcscd.service: Deactivated successfully.
4

So nothing about mounts… odd. I’d expect at least a memntion of the disk name.

Unrelated to the mount issue…

You have left overs from an older Fedora installation.
Check that is in /etc/rc.d and you can remove the livesys files as they are no longer used.

5

50.2.2. Relabeling a File System Red Hat Enterprise Linux 5 | Red Hat Customer Portal

2 Likes
6

this worked. thanks!

summary:

$ touch /.autorelabel
$ reboot
7

I fixed the filename typo for you.

1 Like