min
/
lanzaboote
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #233 from alois31/troubleshooting-docs 

docs: Add troubleshooting documentation
This commit is contained in:
nikstur 2023-10-03 22:06:18 +02:00 committed by GitHub
parent 8154cef11c 7b4d1250b7
commit bccf7738d5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 60 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -13,8 +13,8 @@ supports UEFI.
## ⚡ Quickstart ⚡
If you want to try this out, head over [here](./docs/QUICK_START.md) for
instructions.
If you want to try this out, head over [here](./docs/QUICK_START.md) for instructions.
In case of any issues, have a look at the [troubleshooting document](./docs/TROUBLESHOOTING.md).
## 🪛 Get Involved 🪛

7
docs/QUICK_START.md
View File

@ -284,13 +284,6 @@ System:
That's all! 🥳
## Troubleshooting
If your system doesn't boot with Secure Boot enabled, the most likely
issue is that Lanzaboote could not verify a cryptographic hash. To
recover from this, disable Secure Boot in your firmware
settings. Please file a bug, if you hit this issue.
## Disabling Secure Boot and Lanzaboote
When you want to permanently get back to a system without the Secure

58
docs/TROUBLESHOOTING.md Normal file
View File

@ -0,0 +1,58 @@
# Troubleshooting
## Bootloader installation fails with "Failed to install files. … No space left on device (os error 28)"
During the bootloader installation process, Lanzaboote must copy the kernel and initrd to the EFI system partition (ESP).
It is quite possible that the ESP is not large enough to hold these files for all installed generations, in which case this error occurs.
In this case, you must first delete some generations (e.g. run `nixos-collect-garbage --delete-older-than=7d` to delete all generations more than one week old).
After that, some space on the ESP must be freed manually.
To achieve this, delete some kernels and initrds in `/boot/EFI/nixos` (they will be recreated in the next step if they are in fact still required).
Finally, run `nixos-rebuild boot` again to finish the installation process that was interrupted by the error.
It is recommended run a garbage collection regularly, and monitor the ESP usage (particularly if it is quite small), to prevent this issue from happening again in the future.
**Warning:** It is recommended to not delete the currently booted kernel and initrd, and to not reboot the system before running `nixos-rebuild boot` again, to minimize the risk of accidentally rendering the system unbootable.
## Power failed during bootloader installation, and now the system does not boot any more
Due to the shortcomings of the FAT32 filesystem, in rare cases, it is possible for the ESP to become corrupted after power loss.
With Lanzaboote enabled, this will lead to "secure boot errors" or "hash verification failures" (the exact wording depends on the firmware).
In these cases, recovery is usually still possible with the steps below.
**Note:** If the system fails to boot after the Linux kernel has already been started, then the problem is not caused by a corrupted ESP.
In this case, the steps below will not help, and standard rollback procedures should be followed instead.
### The system can still boot an older generation
In case an older generation still works, the recovery can be carried out from within the booted system.
1. Run `nixos-rebuild boot`.
This should reinstall all generations and thus overwrite the corrupted files.
2. Reboot the system, it should now work again.
### The system cannot boot any generation anymore
If no available generation can boot any more, the system must be recovered from a rescue system.
First make sure that you have a recent NixOS install medium available.
**Note:** Nix versions from before August 2023 contain a bug that can prevent `nixos-enter` from working.
A more recent medium must be used for the recovery procedure to work reliably.
1. Disable Secure Boot in the firmware settings.
The NixOS install medium is not signed and thus cannot be booted when Secure Boot is active.
2. Boot the NixOS install medium.
3. Mount all partitions belonging to the system to be recovered under `/mnt`, just like you would for installation.
1. In case the ESP does not mount, or only mounts in read-only mode, due to corruption, try `fsck.fat` first.
If that fails as well or the ESP still does not mount, it needs to be reformatted using `mkfs.fat`.
4. Enter the recovery shell by running `nixos-enter`.
Then, run `nixos-rebuild boot` to install the bootloader again.
5. Exit the recovery shell and unmount all filesystems.
6. Reboot the system to verify that everything works again.
7. Enable Secure Boot again in the firmware settings.
## The system doesn't boot with Secure Boot enabled
It is the most likely issue that Lanzaboote could not verify a cryptographic hash.
To recover from this, disable Secure Boot in your firmware settings.
Please file a bug, if you hit this issue.