From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
My disk is encrypted with LUKS and I wanted to make it auto-unlock using TPM.
I can't enter UEFI as I have fastboot enabled.
Could anyone help me please? 🫡
You are going to need to run a rescue system to get this sorted, for example from an USB stick. Usually you can enter UEFI setup by just spamming the button on boot (F2, F12, F10, Del, look up what your system uses). If that doesn't work you can either reset the BIOS settings, using the jumper or button (see manual again, removing the battery is internet lore and almost never required, just use the jumper). Another option is to remove your boot drive, that will prevent fastboot from working, so the next boot will be a regular one.
Depending on your BIOS and with fast boot, you might need to just hold one of the keys while booting instead of spamming it on boot.
Assuming this is an ATX or ITX PC, there's likely a way to reset UEFI so you can disable fastboot and change your settings, or at least boot from a recovery USB.
There's usually something like a button or 2 pins you can short on your motherboard to reset the settings. If your machine has dual BIOS, there will be a switch you can flip, though you'll probably need to update the UEFI again once you do that.
In the worst case (and this should work on almost any device), remove the CMOS battery, let the device sit for a few minutes, then put that battery in. That should clear all settings, including fastboot, and allow you to do recovery stuff - just make sure you fix the time before going on the internet.
Do you have GRUB? If yes you can edit your kernel command line and append "init=/bin/bash", see if at least this gives you a prompt, this has saved me a couple of time in the past. Else booting on a USB and mounting your boot partition may help to fix it.
BTW I also have LUKS and I'm using TPM, using tpm2-initramfs-tool, first, it failed because I forgot the tpm modules in initrd, but I always have 2 kernels installed and only modify one initrd at a time to have a safe boot if I have a problem, like I had!
I tested tpm2-initramfs-tool with proper tpm2 modules and it worked.
I also tested with clevis-initramfs and clevis-tpm2 and it's even easier, no messing with crypttab.
Also, as long as you can break GRUB and append "init=/bin/bash" it is not secure of course, you can then prevent grub editing or not using grub at all.
I had this same error a few months ago when a drive was failing to mount because (unbeknownst to me) it was overheating. I turned the system off for a few hours before troubleshooting (I had errands to run). When I came back, the system booted without issue.
If you're looking for an easy troubleshooting step, have you tried turning off the system for several minutes (and unplugging it) and then powering it back on?
Yeah me too. i had (unknowingly) made it necessary for the system to run in fstab, and I had knowingly disconnected it.
Try disabling TPM in the bios/uefi by spamming DEL or ESC or F10 or F12 or F9 or ENTER
I had this issue and it was because I told grub to support dual booting from two different disk drives (one of them USB) and then I removed the USB drive. Linux-boi still tried to enforce booting from the now not-connected drive.
I can't remember exactly what I did, but there may be something about a systemd unit which can be removed/disabled - or maybe I did some fishing around in fstab to remove the drive it thought should exist but wouldn't always (and then probably did an update-initramfs -u or similar.
Perhaps an issue with the TPM, try disabling it to see whether it boots up.