I don’t have to input my encryption password for this first screen. After pressing Enter and after the system takes around 10 seconds to move on, I get to the usual encryption password screen. This second screen requires the proper password to be input. If a wrong password is input then the system stays on this screen.
Before I started having this issue 3 weeks ago, after pressing the power button to start my laptop, I would directly get the second screen asking for the encryption password.
This is not ideal to now have a third step inserted that requires to press Enter + waste an additional 10 seconds during the startup process.
For what it is worth, this is some of the content of the grub file located in etc/default/grub
I deleted the contents of /var/log/boot.log
Then I powered the laptop off.
Finally I started the laptop up.
This is the content of the /var/log/boot.log file
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Volume group “luks” not found
Cannot process volume group luks
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Volume group “luks” not found
Cannot process volume group luks
/dev/mapper/luks-708e0d88-4db9-4713-a5ac-aea1abe6e832: clean, 479801/29327360 files, 58147508/117306241 blocks
[ 21.282609] libvirt-guests.sh[976]: libvirt-guests is configured not to start any guests on boot
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR='PureOS'
GRUB_CMDLINE_LINUX_DEFAULT="quiet cryptdevice=UUID=2ad2d1b8-9969-4645-b888-82a3b3fcdbd3:luks-2ad2d1b8-996$
GRUB_CMDLINE_LINUX="i915.modeset=0"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_ENABLE_CRYPTODISK=y
The line with your GRUB_CMDLINE_LINUX_DEFAULT= looks cut at the end by $
"quiet cryptdevice=UUID=2ad2d1b8-9969-4645-b888-82a3b3fcdbd3:luks-2ad2d1b8-996$
Just to confirm. Having same problem as OP. Appeared after last software-update several weeks ago. Didn’t use the laptop anymore afterwards except 2 or 3 times as it used to be a pain in the a.
Will delete the whole system and install it the 3rd time since buying it - not exactly what one would call reliable. Next time after without disc-encryption as so far it only created unnecessary problems.
Ok, I’m pretty sure there’s a problem that the computer thinks one of the drives needs a password when actually it doesn’t. I would advise you email purism directly as getting it wrong could, in theory, leave you (heaven forbid it) with… The GRUB recovery terminal. As such I recommend you contact purism directly with your lsblk, crypttab, fstab and ask them what the correct configuration is. Sorry for not being able to be much help I had hoped it was just a GRUB misconfiguration.
@ajlok I hear you. Bought the laptop in may and I seem to have all the bugs people are reporting on this forum at the same time. What’s annoying is the lack of communication. Customers are pretty much left waiting for ‘fixes’ without any communication from Purism about time-frame.
It sounds like this may be very similar to the problem reported in this other thread. In that case I was asked for a password three times: once by Grub, then once for each of the encrypted partitions (root and swap). I was able to resolve it by taking the steps in the tutorial linked in that thread.
Purism will be trying their best to solve these issues. But GNU/Linux requires a level of technical understanding to utilise its full potential, things like full drive encryption (which can be done in windows but not as securely as GNU/Linux), updating all drivers and programs with a single command and no restart (unless its kernel yet), automatic dependency install instead of downloading dodgy .exe files, the ability to edit every config file (so if you want to you can disable the GUI for password entry or change the logo animation), that you use you can directly edit the code have it peer reviewed by world-class coders and finally if it is of good quality for it to be pushed to billions of devices worldwide, that you can run the kernel on everything from a $5 computer to every single top 500 supercomputer. So yes GNU/Linux is not windows but that’s because Windows is s**t. Because Windows is a literal prison that restricts and constrains you BY DESIGN. So yes while I agree that GNU/Linux can be frustrating and hard, this is the price paid for vastly numerous advantages of running GNU/Linux, both technical and ethical. So please be patient with purism and post your issues both hear and on the tracker (if you prefer to tag me and I’ll upload them).