Fedora 24 fails to boot (to 4.7.6-200) after 'dnf upgrade': mount: unknown filesystem type 'vfat'

asked 2016-11-05 06:37:43 -0500

mjbright gravatar image

This morning I performed a 'dnf update' (whilst booted on 4.7.6-200 kernel) to be able to pass from 4.7.6 to 4.8.4 to avoid the Dirty Cow vulnerability.

Since then I can boot neither the old 4.7.6 kernel, nor the new 4.8.4 kernel (separate problem asked here`).

I'm now "successfully" booted on 4.7.3 (!!) to enter this question.

4.7.6-200 boot problem:

So my system now fails to boot into 4.7.6 dropping into emergency mode.

Running 'journalctl -xb' shows a couple of 'Unknown filesystem type' errors.

Unit proc-fs-nfsd.mount fails: "unknown filesystem type 'nfsd'"

Nov 05 09:41:13 giraufab3.emea.hpqcorp.net mount[846]: mount: unknown filesystem type 'nfsd'
Nov 05 09:41:13 giraufab3.emea.hpqcorp.net systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited status=32
Nov 05 09:41:13 giraufab3.emea.hpqcorp.net systemd[1]: Failed to mount NFSD configuration filesystem.
-- Subject: Unit proc-fs-nfsd.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit proc-fs-nfsd.mount has failed.
--
-- The result is failed.

Unit boot-efi.mount fals, "unknown filesystem type 'vfat'"

Nov 05 09:41:22 giraufab3.emea.hpqcorp.net systemd[1]: Mounting /boot/efi...
-- Subject: Unit boot-efi.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit boot-efi.mount has begun starting up.
Nov 05 09:41:22 giraufab3.emea.hpqcorp.net mount[1369]: mount: unknown filesystem type 'vfat'
Nov 05 09:41:22 giraufab3.emea.hpqcorp.net systemd[1]: boot-efi.mount: Mount process exited, code=exited status=32
Nov 05 09:41:22 giraufab3.emea.hpqcorp.net systemd[1]: Failed to mount /boot/efi.
-- Subject: Unit boot-efi.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit boot-efi.mount has failed.
--
-- The result is failed.

So 'dnf upgrade' has broken my future (4.8.4) and current (4.7.6) kernel boot.

For info (probably not relevant, I guess vfat needs to be hardwired into the kernel):

find /lib/modules/4.* -iname 'vfat' /lib/modules/4.7.3-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz /lib/modules/4.7.6-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz /lib/modules/4.8.4-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz

> find /lib/modules/4.* -iname '*vfat*'
/lib/modules/4.7.3-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz
/lib/modules/4.7.6-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz
/lib/modules/4.8.4-200.fc24.x86_64/kernel/fs/fat/vfat.ko.xz

Any ideas?

edit retag flag offensive close merge delete

Comments

rebuild initramfs for your failing kernels, vfat doesn't need to be "hardwired", the reason for having the initramfs system around is to avoid "hardwiring" everything

fcomida gravatar imagefcomida ( 2016-11-06 06:01:03 -0500 )edit