boot hangs

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

Post Reply
svantoviit
Old Dear Hen
Posts: 750
Joined: Sun Feb 28, 2010 17:55
Contact:

boot hangs

Post by svantoviit » Mon Jan 07, 2019 21:18

After entering the LUKS password upon start up it seems nothing happens for while. Suddenly the boot continues as usual.

Kernel info:

Code: Select all

$ uname -rp
4.18.0-sabayon Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
$ equo query installed -vq linux-sabayon
sys-kernel/linux-sabayon-4.18.20
journactl does not show anything useful, the only thing I could find is a 2 minute gap in dmesg:

Code: Select all

[Mon Jan  7 20:14:11 2019] dracut: Scanning devices dm-0  for LVM logical volumes vg/lv_root vg/lv_swap
[Mon Jan  7 20:14:11 2019] dracut: inactive '/dev/vg/lv_root' [80.25 GiB] inherit
[Mon Jan  7 20:14:11 2019] dracut: inactive '/dev/vg/lv_swap' [<16.66 GiB] inherit
[Mon Jan  7 20:14:11 2019] dracut: inactive '/dev/vg/lv_home' [834.09 GiB] inherit
[Mon Jan  7 20:16:20 2019] dracut: Scanning for all btrfs devices
[Mon Jan  7 20:16:20 2019] dracut: Scanning devices dm-0  for LVM logical volumes vg/lv_root vg/lv_swap
[Mon Jan  7 20:16:20 2019] dracut: ACTIVE '/dev/vg/lv_root' [80.25 GiB] inherit
[Mon Jan  7 20:16:20 2019] dracut: ACTIVE '/dev/vg/lv_swap' [<16.66 GiB] inherit
[Mon Jan  7 20:16:20 2019] dracut: inactive '/dev/vg/lv_home' [834.09 GiB] inherit
[Mon Jan  7 20:16:20 2019] dracut: PARTIAL MODE. Incomplete logical volumes will be processed.
[Mon Jan  7 20:16:20 2019] dracut: PARTIAL MODE. Incomplete logical volumes will be processed.
[Mon Jan  7 20:16:20 2019] dracut Warning: Cancelling resume operation. Device not found.
How to debug and make boot fast again?

greyghost99
Baby Hen
Posts: 1
Joined: Mon Sep 23, 2019 20:29

Re: boot hangs

Post by greyghost99 » Mon Sep 23, 2019 21:24

Same here after an upgrade. I found the reason somehow is that the swap device isn't properly found by systemd/kernel/whoever. If you remove the resume= settings on the kernel commandline, it boots right away without the 2min gap. However, I was not able to get rid of the issue and retain the resume feature.
So I opted for a fresh installation of 19.03, only to find out that (contrary to what was written in the announcement) full disk encryption is utterly broken there and cannot be used at all. Moving forward the installer image again, but the latest nightly build keeps crashing on me before I can even start an installation.

Oh, well... This used to be a more stable distribution with a better installer (which, at some point, even supported installing to software raid setups, all long gone).

Post Reply