On Sun, 28 Aug 2022 18:11:13 -0700
stan via test <test(a)lists.fedoraproject.org> wrote:
Update:
One of the problems is probably due to the fact that the system no
longer mounts any partition in fstab except the root partition of the
fedora I am running. My wallpapoz gets its wallpaper photographs from
a directory on a data partition. It also fails on the swap partition.
Aug 28 17:16:27 fedora systemd[1]: Failed to mount
mnt-to_archive.mount - /mnt/to_archive. Aug 28 17:16:27 fedora
systemd[1]: mnt-to_archive.mount: Failed with result 'exit-code'. Aug
28 17:16:27 fedora systemd[1]: mnt-to_archive.mount: Mount process
exited, code=exited, status=32/n/a
Aug 28 17:16:16 fedora systemd[1]: Failed to activate swap
uuid\x3da4377658\x2d7454\x2d45ed\x2daaf2\x2d355f80cc9e9a.swap -
/uuid=a4377658-7454-45ed-aaf2-355f80cc9e9a. Aug 28 17:16:16 fedora
systemd[1]:
uuid\x3da4377658\x2d7454\x2d45ed\x2daaf2\x2d355f80cc9e9a.swap: Failed
with result 'exit-code'. Aug 28 17:16:16 fedora systemd[1]:
uuid\x3da4377658\x2d7454\x2d45ed\x2daaf2\x2d355f80cc9e9a.swap: Swap
process exited, code=exited, status=255/EXCEPTION
And a little later,
Aug 28 17:16:16 fedora swapon[510]: swapon: cannot open
/uuid=a4377658-7454-45ed-aaf2-355f80cc9e9a: No such file or directory
blkid can find all the missing partitions, and they have the right
uuid, the same as in /etc/fstab.
Booted an older Fedora, and it had no problems mounting all the drives
and swap. So, not the drives.
Booted F37 with older kernels that worked just fine before these
updates, now have the mount problem. So, the update changed something
in the boot process. It wasn't mount that changed, because that wasn't
updated (the util-linux-core package hasn't changed since Aug 5). I
look at that list of packages, and I don't see anything in there that
should affect boot. systemd is the same, and that is what handles the
mounting of swap and drives. The same systemd worked fine before a
reboot after the updates, and still boots the system, just doesn't
mount anything but the root partition.