Librem15v3: Boot failed after PureOS 8 update >> Cannot open access to console, root account is locked >> Press any key loop
Open, Unbreak Now!Public

Description

Hello guys,

this issue is happening 2 times in a row and is completely blocking the normal work.
After initially successful installation of PureOS 8, after a certain amount of time some package during update is causing the Librem15v3 to get into a deadlock stating: Cannot open access to console, root account is locked >> Press any key loop{F304091}
You can find a detailed message in the attached images.

Please help resolving this ASAP!

Many thanks!

More detailed picture with messages on the 2nd attachment.

gorgeous assigned this task to mladen.Jul 14 2019, 10:52 AM
gorgeous added a comment.EditedJul 18 2019, 7:26 AM
In T792#14834, @mladen wrote:

@gorgeous Did you try this procedure: https://tracker.pureos.net/w/troubleshooting/broken_upgrade/#problem-2 (solution for problem 2)?

No, unfortunately it is not applicable for me. I have only 1 kernel (4.17), because I didn't use the laptop much after the last installation. The next time I have worked on it, it showed, there are system updates and I accepted to install them. This is the result, and as I stated earlier this is happening already 2 times in a row. I really like the Librem15 model and I am your supporter, but due to such technical issues I still can't consider this machine as my main laptop.
Anyway, I have shoot a video to show you what exactly is happening. I hope this will help you track the issue and to resolve it for me and any other customers. Here is the link:
https://libretube.org/videos/watch/e918b31e-958e-49e3-8352-cc24888182cb
if there are problems with the first video link, here is the same video on YouTube:
https://youtu.be/JGFSB6MhA8U

@mladen & @Erik_Leroux please help me with this issue! :(
Many thanks!

@gorgeous I suggest you do a re-install, you will save yourself a lot of time. Your installation seems very broken.

I can do that, of course, but as I said already, this is happening for the 2nd time, after a new/clean installation from a USB flash drive with a PureOS8 ISO image. After installing some of the system updates, this issue appears. How can I be sure this would not happen again?

Squid added a subscriber: Squid.EditedMon, Jul 29, 11:17 AM

I can do that, of course, but as I said already, this is happening for the 2nd time, after a new/clean installation from a USB flash drive with a PureOS8 ISO image. After installing some of the system updates, this issue appears. How can I be sure this would not happen again?

@gorgeous If I were you, I would

  1. get the latest (14-Jul-2019) image from https://downloads.puri.sm and do a fresh install
  2. enable the firewall by running
sudo ufw enable
  1. update by running
sudo apt update

followed by

sudo apt full-upgrade

then

sudo reboot
  1. run
sudo apt autoremove

... just in case you have unnecessary packages

My advise is to never run

apt upgrade

That would be all.

PS: I'm unsure whether you're writing the image onto the USB thumb drive correctly. https://tracker.pureos.net/w/recommendations/burn-using-dd/ Alternatively, you can use optical media (you can find out whether the install disk is corrupted or not by re-imaging the install disk onto the hard drive. The checksum of the obtained image should be identical to the original ISO's).

Kind regards

jjakob added a subscriber: jjakob.Sun, Aug 11, 11:21 AM

The "root account is locked" is due to a 2015 Debian change to harden security to prevent the single user mode passwordless shell. Link to the bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802211 IIRC it was meant more for publicly exposed systems, as the security benefits for an already fully encrypted system are very small, but it causes a lot of pain when trying to recover your system. I disabled it on mine with a workaround patch that's in the bug report.

As for the other error, it might be a wrong LUKS disk encryption password. Do you have a different keyboard layout set in the OS? The console might be expecting US layout. (if your install is old, it might not have had the console layout set correctly) If not, your system might well be broken and would require a "apt-get -f install" in the recovery shell, which you say doesn't work, so your only option then would be to chroot into it from a live USB (do a crtyptsetup open on the root luks, mount it, then chroot as normal).

Also I've been doing exclusively apt-get dist-upgrade on all Debian based distros for years, and never had problems. I've never used apt-get upgrade or apt upgrade. My thinking is that if a upgrade only upgrades packages, but the maintainers downgraded some due to a bug or packaging error, the upgraded packages might expect the downgraded packages to work.

Add Comment