Ask Your Question
0

Kernel 4.9.3 won't boot

asked 2017-01-15 10:38:44 -0600

msum gravatar image

updated 2017-01-18 11:10:49 -0600

Edit: Important info

I managed to access the log from the failed boot with journalctl -x -b -1. I suppose the following lines are responsible for the problem:

sty 18 16:53:33 desktop systemd[1]: Mounting /boot/efi... 
sty 18 16:53:33 desktop mount[631]: mount: nieznany typ systemu plików 'vfat'
sty 18 16:53:33 desktop systemd[1]: boot-efi.mount: Mount process exited, code=exited status=32
sty 18 16:53:33 desktop systemd[1]: Failed to mount /boot/efi.

The second line says: unknown filesystem type 'vfat'.

Background info: I have a dual boot Fedora 25 / Windows 10 install with UEFI secure boot enabled. The boot partition is of type FAT (because of Windows as far as I know).

The original post

I have just upgraded to kernel 4.9.3 on Fedora 25. At boot time, I get a bunch of ACPI errors (see the attachment) and a message that informs me that I'm in "emergency mode" and asks to hit Enter to continue. If I hit Enter, the same message pops out once more and nothing other happens.

A bit of info about my hardware:

$ lspci
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #4 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10f1 (rev a1)
02:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

The screen I get at boot

Edit: kernel 4.8 works without problems.

edit retag flag offensive close merge delete

Comments

1

I can't read all the language there on the screen, but I think you're actually at a prompt for the root password. Can you try that, and then run the suggested journalctl -xb? Also, is this kernel 4.9.3-200.fc25.x86_64? I think those ACPI errors are probably actually just noise and not the real source of the problem.

mattdm gravatar imagemattdm ( 2017-01-15 13:23:16 -0600 )edit

The Polish text says: "Cannot access the console, the root account is locked. More information on the manpage sulogin(8). Press Enter to continue." It doesn't ask for password.

msum gravatar imagemsum ( 2017-01-15 15:40:33 -0600 )edit

3 Answers

Sort by » oldest newest most voted
1

answered 2017-01-18 16:07:59 -0600

msum gravatar image

updated 2017-01-18 16:10:57 -0600

I solved the problem. I'm not sure whether this is an answer to the question, because the real cause turned out to be something different than I described, but I'll post it anyway... I did the following steps:

  1. Reinstall the kernel packages:

    sudo dnf reinstall kernel kernel-core kernel-headers
    
  2. After this step, the kernel booted properly, but gdm crashed with a "something went wrong"-screen before showing the login screen. The reason for that was a corrupted package kmod-nvidia-4.9.3-200.fc25.x86_64, which caused the nvidia kernel module not to load. I did:

    sudo dnf remove kmod-nvidia-4.9.3-200.fc25.x86_64-1\:375.26-1.fc25.x86_64
    sudo akmods --force --kernels 4.9.3-200.fc25.x86_64
    

    which rebuilt the kernel module.

Now everything works.

edit flag offensive delete link more
0

answered 2017-01-16 22:20:46 -0600

xmetax gravatar image

Runs great for me. Same kernel version on Intel graphics. It will be best to boot to the kernel you can use and run the suggested command as root:

journalctl -xb

This will generate useful output, please post your results here for review.

edit flag offensive delete link more

Comments

I have updated my post, please have a look at the top of it.

msum gravatar imagemsum ( 2017-01-18 11:09:04 -0600 )edit

Are you still able to boot to Windows?

xmetax gravatar imagexmetax ( 2017-02-03 23:19:33 -0600 )edit
-4

answered 2017-01-16 15:43:52 -0600

F25 is so broken. I see 3 posts a day about Fedora not booting after kernel update. Happens to me also. I just use the original kernal from the original install and do dnf -x kernel* update. For some reason the devs don't care. Come back tomorrow and see more posts about Fedora not booting after kernel updates...

edit flag offensive delete link more

Comments

3

Concluding that F25 is broken because of one's lack of know-how/experience on dealing with bugs/issues will definitely be counter-productive if your intention is to gain the skills to deal with any issues as they arise. Fedora is often considered a "cutting edge" distro, which is great because we get the latest Linux has to offer. However, there are times where something unexpected can potentially happen after a major update.

Having the patience to deal with and learn from these experiences will only benefit you on your Linux journey.

Just saying.

xmetax gravatar imagexmetax ( 2017-01-16 22:14:28 -0600 )edit

Question Tools

2 followers

Stats

Asked: 2017-01-15 10:33:24 -0600

Seen: 3,253 times

Last updated: Jan 18 '17