Ask Your Question

Unable to boot with kernel 4.17

asked 2018-07-02 10:28:49 -0500

alexela gravatar image

updated 2018-08-27 04:25:53 -0500

I recently updated my workstation to kernel 4.17.3, earlier I was using 4.16.16, but I am having an issue when booting: system hangs with an error, saying that hibernation cannot continue, but I did not hibernate my system and with 4.16 it boots just fine. The error is the following:

[ TIME ] Timed out waiting for device dev-mapper-fedora\x2d\x2dlvm\x2dswap.device
[DEPEND] Dependency failed for Resume from hibernation using device /dev/mapper/fedora--lvm-swap

It will also write a couple of messages in green (Reached target local file system), but it will not go on. I am currently avoiding the problem by using the old kernel. How can I solve this?


In my grub config there was resume=/dev/mapper/fedora--lvm-swap: I proceeded removing it, and the dependency failure disappeared, but there is still a problem: the system will not boot.

Is there a way to retrieve the log of an interrupted boot? I tried with journalctl -k -b -1 but I don't think it reflects the failed boot.

edit retag flag offensive close merge delete



Try with resume=/dev/mapper/fedora--lvm-swap boot parameter. If it works add it permanently editing /etc/default/grub and running grub2-mkconfig

fcomida gravatar imagefcomida ( 2018-07-02 12:22:50 -0500 )edit

Thanks fcomida, but sadly it is not working.

alexela gravatar imagealexela ( 2018-07-03 02:30:40 -0500 )edit

I have the same problem :(

LizardLad_1 gravatar imageLizardLad_1 ( 2018-07-15 23:12:10 -0500 )edit

2 Answers

Sort by » oldest newest most voted

answered 2018-09-12 04:25:32 -0500

alexela gravatar image

I updated to kernel 4.18 (from updates-testing) and the issue is gone:

dnf update kernel --enablerepo=updates-testing

Thanks to user antikythera from the forum.

edit flag offensive delete link more

answered 2018-07-16 03:02:55 -0500

LizardLad_1 gravatar image

I fixed it! I had to regenerate initramfs. To do this execute

sudo dracut --regenerate-all --force

This should fix your issue!

edit flag offensive delete link more


That's great! I'm going to try asap. Do you have any reference to bug or issues? How did you come up with this solution?

alexela gravatar imagealexela ( 2018-07-17 04:01:33 -0500 )edit

Sadly, this is not working for me :( Actually, after this my screen goes black and it won't boot. I cannot even see log messages anymore.

alexela gravatar imagealexela ( 2018-07-17 04:08:59 -0500 )edit

Question Tools

1 follower


Asked: 2018-07-02 10:28:49 -0500

Seen: 711 times

Last updated: Sep 12 '18