I am encountering the same issue. After upgrading and rebooting the boot throws a number of failed to decrypt errors without ever prompting for the password, but I have the additional joy of not being able to boot into recovery mode – I get the same error here. This is on a purism 13. Now my computer is unusable. I will most likely be installing a another os because none of the solutions here have worked and I am at a bit of a loss on how to proceed.
5 months later. still no solution. 3 weeks ago i had some time off from work so i dedicated it to getting support via email. 1 command line / day for 5 days of things that i already did from reading the forums and still no luck. Then all of a sudden, no call no show. support has disappeared. So, if anyone sees negative information in social media regarding PureOS, this might be why. And if someone from PureOS tells me in social media to email support, i will refer to this. PureOS engineers are damn smart, but for some reason they are not going about this fix the right way. Identify the conditions that lead to this, have the user query their system to see if the conditions exist, and then execute the commands to resolve the conditions… I’m very angry right now because I told my wife she could get this awesome machine for me. Now she thinks its a lemon and linux is stupid. Great.
While I admit it’s unfortunate that you’ve been having issues, is there something preventing you from reinstalling the OS? If you just want a working computer, that would probably be the fastest and easiest way to get going again.
Thank you for seeing/replying to my post. The only reason that i haven’t done that yet is that i think its silly. I like to know the reasons why operating systems break and the solutions. And I like to execute the fixes. IF the conditions that cause the problem are known and there is a way to resolve, we do that, we fix it. It seems to me that its fixable, but maybe its not because of encryption related reasons. If its not, we just need to be flat out told that we MUST re-install. I also find the one command at a time process painstakingly slow. I’d rather provide some diagnostic info about the system so that the PureOS team can identify the exact solution. Unless the exact solution is unknown, which would also be beneficial information. I will figure out how to back up and re-install. That brings a new issue: how does that impact my Librem Key? should i address this in a different post? thanks again.
Ok, trying to catch up on this thread. I doubt I’ll be able to help, 'cause it seems like you know at least as much as I do, but just to confirm:
- If you try to boot normally, it fails and gives the
- You can boot into recovery successfully
- Booting into recovery and re-running
sudo apt update && sudo apt full-upgradestill leaves you with a broken system
Edit: 4) And you’ve tried these steps? https://tracker.pureos.net/w/troubleshooting/broken_upgrade/
Is that right?
That is mostly accurate. Instead of 2. Booting into recovery, i just boot into my original kernel: 4.16.02, since its available in the advanced menu and still works. I assumed that this was just as good as recovery mode when re-running update/full-upgrade. Which yes, still leaves broken system(cryptsetup error). so for the most part, yes, that is right. additional note: i have executed several full-upgrades that try to boot using the latest kernel(first 4.18, then 4.19), but they all fail; booting to 4.16.02 works fine, no recovery mode required. I’m running out of time today for this today, so I will try to compile the solutions attempted to date by this weekend and add them to this forum or another email support ticket. then i will investigate a re-install.
Can you paste the cryptsetup error as well? I’ll look for it in the thread but it would be good to confirm.
Have you tried getting past the cryptsetup errors by modifying /etc/default/grub?
Is what works for me. You’ll have to run;
I do have that commented out line in my grub file: # GRUB_ENABLE_CRYPTODISK=y
i’ll have to follow up later with my exact cryptsetup err msg. (something like LUKS … cryptsetup failed. then a bunch of failed log ins, drops me to initramfs. at no point during the time the boot messages are scrolling can i submit a login)
submitting to email@example.com since forum not designed for support. Tried this couple weeks ago and haven’t heard back since 6/16. putting ATTN Jeremiah in content of email.
Just to be explicit: when you login using the 4.16.02 kernel, you have run
sudo update-initramfs -u and it doesn’t fix anything?
I believe i did try that last week. I will try again.
Yes i ran sudo update-initramfs -u and it did not resolve this situation. For reference to this issue, from 2015! This is greek to me. so i’ll need help interpreting: https://unix.stackexchange.com/questions/164403/unlock-luks-encrypted-debian-root-with-key-file-on-boot-partition
You see this same error?
cryptsetup: WARNING: target sdaX_crypt uses a key file, skipped.
What is the error on your machine? Can you take a picture or write it down?
Was this ever resolved? Experiencing very similar issue only if you hit Escape and select an older kernel you can still get into the device, run all the update commands that do not work and validate a few things. My brand new V5 Librem 15 has 4 options total:
one newest kernel (this one will not boot bc of bad password)
one newest recovery(loops are fun)
older kernel (this lets you in)
older kernel recover (this also lets you in)
If not it is cool, I will reimage the laptop when the PureOS USB and Key arrive. Likely will just use an alternate linux distro until them.
This is the standard grub menu you’re seeing with regular kernels and recovery kernels.
That is correct Jeremiah, very good, the underlying issue is that straight out of the box after going through the simple process of configuring and getting familiarized with the Librem 15v4 with PureOS for the first time (for myself anyways as it was the first time using PureOS as my goal was simply to support linux Hardware, free software and I think the killswitches/built in hardware tamper protection were what made me pull the trigger…so small learning curve for myself)
Fact is I simply ran and likely you can validate by grabbing one of the new Librem 15v4 laptops fresh out of the box, add a couple apps, tweak a few settings, run apt-get update && apt-get upgrade, then on the next reboot and the following likely appears:
ERROR: (luks-07f23b4f-d170-4148-b8f1-60b1cec24d20: cryptsetup failed, bad password
No matter what I tried until I found this forum from my phone I could not log in because of this. Thanks to this post and the person who explained the ESC select different kernel work around I was at least able to get into the laptop. I was relieved I was not the only one experiencing the issue as stated above, it was my out of the box experience. I attempted all the fixes recommended in this post and on the wiki as I was able to get access via the old recovery kernel thus I tried all suggestions.
The actual fix that worked for me last night was as follows:
1.) Locate a USB (If you do not have one, buy one, currently PureOS is out of stock but it will be shipped soon, anytime after 8 aug 2019 they may be restocked so if new to Linux or want simplicity order the $10 PureOS thumb drive, I did but out of stock…)
2.) Download PureOS (pureos.net)
3.) Flash the USB with bootable PureOS via Etcher or Rufus
4.) Look up the advanced Install instructions to erase and create the partitions
on separate computer/phone or print out unless your memory is good and are more familiar with Linux
5.) Plugin the USB, boot into Option 3 and follow the instructions verbatim (note: reference was for a 8GB of memory so if 16GB or 32GB increase the swap size, there are 2x rules that some folks opt for.)
6.) Open terminal and run the update/upgrade command, do a few preference tweaks for good measure
7.) Pray to your respective god(s)
8.) Wallah worked for me so far and all I lost was a few days worth of tweaks, history and stuff I did not care about
Being that this is a common issue, perhaps provide the $10 dollar USB and a tiny booklet of instructions or document in the USB until it is resolved to help out new customers in the future.
Although the Wiki has been helpful, sometimes a document to open up and follow along with without the need for internet is nice and takes up almost no space on the usb-drive. Although, version control, tech writing processes being implemented can take time/resources for a problem that many folks do not experience and/or will be resolved by next version. Sometimes it really is the little things people appreciate. Then again your common customer may be a little more Linux savy and enjoy spending time figuring out why this error appeared out of nowhere and they can not log into a brand new laptop.
I am grateful this post exists because of the person who explained that you could hit ESC and select the older kernel that allows you in only all the recommended actions to fix it however, non of them worked for me so I was not locked out of it completely for long.
Hopefully any customer who see’s this saves time by re installing PureOS if this happens to them. Part of me is really curios why this happened out of the box (Received this last Friday) yet, the Advanced Installation procedure with the download has yet to experience the same issue.
The Librem 15v4 with PureOS is a really good configuration and it is really simple to get used to. I just do not want any new users to get discouraged by these things which is easy to do when you just want things to be simple and work. Someone else may not have another computer or usb stick to available to fix this so hopefully mine was just not configured correctly or the laptop out of the box has an older distro version then the one on the website which enables the upgrade to produce the bug. (I will have to check my video of the unboxing and pictures capturing the error when I get home to see if that guess is at all possible)
Either way, it works great now and am still content with the purchase. Hopefully this is helpful to someone.
This is extremely helpful - thanks for taking the time to write up your work, much appreciated.
As for mitigation on the PureOS side, we believe that this issue is in fact corrected. Unfortunately its entirely possible that the older image without the fix was used to flash your laptop, in which case, I apologize. It ought to be a newer image. I will work on updating that on our web site and I know we’ve updated it internally.
Should you, or anyone else, want a newer image, we have them available here:
We also have live images which boot from a USB or SDcard if you change your BIOS.
No this was not resolved for me. Yes, i’m familiar with logging in via the advanced menu/original kernel(for me 4.16-02) After trying everything in the forums and suggested by support via a long email exchange, I gave up for a bit. too busy. I originally told them I did not want to reinstall, i thought that was an odd solution. I guess thats what i’ll have to try though. that makes me sad and discouraged. That just means the actual cause/solution either were not discovered or were unsolvable, either way, that doesn’t inspire confidence for me with Pure. I see a few people latched on to this convo below. I’m sort of glad other people are experiencing this. Have a good day, hope your machine is functioning normally.