Page MenuHomePureOS Tracker

PureOS does not boot
Open, NormalPublic

Description

This issue was initially described in the comments of https://tracker.pureos.net/T575.

PureOS fails to boot intermittently on the Librem13v4. Sometimes I need to restart the device 3 times before I get a successful boot. Basically, systemd will hang forever with a message like:

[ ***] A start job is running for /dev/mapper/luks-204dc5ca-8fbd-4b02-9833-3661ffd0c0aa (9min 38s / no limit)

The problem seems to be related to this systemd bug, which has a really similar description to the current problem, and was reported the same day as the first comment related to the problem in https://tracker.pureos.net/T575. See also https://github.com/systemd/systemd/issues/10179, which seems to be the main issue.

I have PureOS installed on other devices (Dell XPS, ThinkPads), and I only experience the problem on the Librem13.

Event Timeline

louis created this task.Feb 24 2020, 17:41

Which version of systemd are you using?

$ systemd --version
jeremiah.foster triaged this task as Normal priority.Feb 25 2020, 10:46
louis added a comment.Feb 26 2020, 17:03
$ systemd --version
systemd 241 (241)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid

Thank you for that. It looks like you're using PureOS Amber (at least, that's the version of systemd that is in PureOS Amber).

If the bug is in systemd, which looks like might be the case from the links you point to, my suggestion would be to update to a newer version of systemd. You can do that through upgrading your PureOS version to Byzantium which is our rolling release. Alternatively, you can see if you have an updated Amber system which may pull in fixes. If you were to paste your /etc/apt/sources.list file here we could determine which version of PureOS you're running.