-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NixOS does not boot #1001
Comments
@macpijan Where is the grub.cfg in this case? I wondering if a075347 is the cause or what should be improved here. Of course, the grub.cfg file you show here contains ($drive1)/ that should be dodged by the parser, but since there is now two parsers (nitrd/bin/kexec-parse-bls nitrd/bin/kexec-parse-boot) I wonder which path you NixOS is taking (I guess its bls). Both are taking /boot (mountpoint where kernel is found) as argument prior of doing the parsing. https://github.com/osresearch/heads/blob/a0753473510ec598f9db86cfb610cf61156ca5cb/initrd/bin/kexec-parse-bls Guix and Nix don't have a /boot partition from what I read by default? |
/boot/grub/grub.cfg
Yes, the official installation manual instructs to install everything (boot and rootfs) in one partition. At least when using MBR. When using GPT, they instruct to create a separate EFI partition. This is bad for several reasons. One of them is heads is trying to check hashes of all of the files in rootfs in such scenario (and they change at each boot obviously). Nevertheless, I have a separate /boot partition at /dev/sda1 and rootfs on /dev/sda2 (LVM on /dev/sda2 actually, but it does not matter) - which is also required to setup rootfs encryption. |
Quick but sufficient hack:
Have something better? |
NixOS does not boot after installation (the installer boots fine). The kexec command line is not created correctly.
The original grub.cfg file:
The
kexec_default.1.txt
created by heads:I can boot with
kexec-boot
using following entry:The text was updated successfully, but these errors were encountered: