On 3/25/21 10:52 PM, Shawn Badger wrote: > Has anyone else seen this or know where to point me to get the issue > resolved? No, I haven't seen this. Can you share the output of "lsblk -f" ? Regards, Jorge _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org 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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

What kernel version? i.e. uname -r At the time of the mount failure, what do you get for: $ lsmod | grep xfs xfs 1892352 0 $ dmesg | grep -i xfs [ 717.658384] SGI XFS with ACLs, security attributes, scrub, quota, no debug enabled I suspect you get neither of the above results. Try: $ sudo modprobe xfs Now try mount. Does that work? -- Chris Murphy _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org 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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Looking into the kernel deeper it appears that for some reason tit is trying to load modules from the 5.10 kernel instead of the 5.11 kernels that are installed. I also just realized that it reports that I am still running a 5.10 kernel even though I don't even have one installed. Wow, I must have messed up grub somewhere along the lines. Thank you everyone for your help. On Sat, Mar 27, 2021 at 3:29 AM Shawn Badger <shawn(a)badger.pro&gt; wrote: > [root@images backups]# uname -r > 5.10.22-200.fc33.x86_64 > [root@images backups]# lsmod | grep xfs > [root@images backups]# modprobe xfs > modprobe: FATAL: Module xfs not found in directory > /lib/modules/5.10.22-200.fc33.x86_64 > [root@images backups]# > > On Fri, Mar 26, 2021 at 12:39 PM Chris Murphy <lists(a)colorremedies.com&gt; > wrote: > >> What kernel version? i.e. uname -r >> >> At the time of the mount failure, what do you get for: >> >> $ lsmod | grep xfs >> xfs 1892352 0 >> $ dmesg | grep -i xfs >> [ 717.658384] SGI XFS with ACLs, security attributes, scrub, quota, >> no debug enabled >> >> I suspect you get neither of the above results. Try: >> >> $ sudo modprobe xfs >> >> Now try mount. Does that work? >> >> -- >> Chris Murphy >> _______________________________________________ >> users mailing list -- users(a)lists.fedoraproject.org >> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org >> 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/users@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> >

On Sat, Mar 27, 2021 at 6:50 AM Shawn Badger <shawn(a)badger.pro&gt; wrote: > > I see what happened now. I had moved my /boot to a new partition but didn't purge the old partition. It turns out that even though it wasn't mounting the old partition grub is still pointing to it for the kernels and since the 5.10.22 is the latest kernel on that partition it is the one it is loading. > I just kept doing my updates not noticing that it was running the old kernel after the reboots until the 5.10.22 kernel "aged" out and was removed from the system. I am surprised it comes up at all. > > > One would have to know exactly what is and is not built into an initrd by dracut. What is included will allow the node to boot and at least get the root filesystems mounted so it can change root into it, but may not be able to mount any filesystems with filesystems not needed for boot. Usually the only obvious things like usb and/or network break when you no longer have a /lib/modules for the kernel. So generally it is not at all obvious as only a few items fail here and there, and some of those items (say firewall/iptables) aren't going to often be obvious (outside of the systemd start failure scrolling by). I booted a rescue kernel missing a /lib/modules a few days ago, and the non-bonding single network interfaces worked and almost everything else worked but network bonding did not work as that was not in the initrd. I figured out quickly the module was missing but it took me another minute or 2 to realize all of the kernels modules were missing (the directory structure for it was still there). _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org 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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure