In my case it was a little easier to see since the whole folder was gone.
On Sat, Mar 27, 2021 at 9:51 AM Roger Heflin wrote:
> On Sat, Mar 27, 2021 at 6:50 AM Shawn Badger wrote:
> >
> > I see what happened now. I had moved my /boot to a new partition but
> didn't purge the old partition. It t
On Sat, Mar 27, 2021 at 6:50 AM Shawn Badger 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.2
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
loadi
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
[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
wrote:
[root@images backups]# lsblk -f /dev/sdc
NAME FSTYPE FSVER LABEL UUID FSAVAIL
FSUSE% MOUNTPOINT
sdc
└─sdc1 xfsc2619e30-3bea-4e1d-a7a1-2e72e37a96b2
On Fri, Mar 26, 2021 at 8:36 AM Jorge Fábregas
wrote:
> On 3/25/21 10:52 PM, Shawn Badger 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.
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@lists.fedorapro
I have a 10TB drive that is formatted with XFS and it has been working fine
for a number of years and 2 days ago I did an update and now I cannot mount
it any longer. I get "unknown filesystem type 'xfs'." from mount all of a
sudden after updates.
xfs_repair can see the volume and shows it with no
