On Sun, 2022-08-28 at 18:34 -0700, stan via test wrote: > On Sun, 28 Aug 2022 18:11:13 -0700 > stan via test <test@xxxxxxxxxxxxxxxxxxxxxxx> 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. systemd doesn't exactly *do* the mounting, it just...farms it out. Those errors look almost like it's literally trying to mount the device `/uuid=a4377658-7454-45ed-aaf2-355f80cc9e9a` , which obviously isn't going to work... Can you show your /etc/fstab or the systemd mount units (whichever you're using) for these mounts? Can you mount the devices manually with e.g. mount /dev/real/path/to/target /mnt/to_archive or whatever? -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
