8.10: Error mounting from disk library after reboot

Support
1

Hi,

We are running two almost identical Alma Linux systems running 8.10 currently. Today we ran the usual update process (dnf update). Which completed fine. We rebooted both systems and one of them wont come back up.

systemctl status for the mount path returns:
“wrong fs type, bad option, bad superblock on /dev/mapper/vgDisklib-lvMountpath01”
“mount process exited, code=exited status=32”

The wrong fs type seems odd as we only applied updates, unless the process corrupted the fs. The system is cloud hosted virtual machine.

Would appreciate any guidance on how to go about correcting this or investigating further.

Thanks

2

Just to add some mote context as we work through it. The mount in question is part of the fstab and errors on boot. But will mount manually via the mount command. The device passes fsck OK.

I have been informed by the storage team that all is well on that side, but remain unconvinced.

Still investigating, but suspect this is something on the storage side. Will update this once confirmed.