LUKS-guided-manual-partitioning
LUKS-guided-manual-partitioning copied to clipboard
nbros652
Boots to Initramfs Busy Box
I have Windows 10 installed on my hdd with the Windows system reserved partition being the first partition on the disk followed by my Windows system partition encrypted with Veracrypt which is installed to the MBR. On my custom install I created a 1gb boot partition (where I installed Grub to) I also created an encrypted ext4 LUKS vm partition as per your guide and maybe a few others (I’ll look tonight). Anyway, my system boots and I hit escape at Veracrypt where it takes me to Grub and I boot Elementary OS. From there the Elementary logo shows up like its booting but I am not asked for a password and after that sequence is done I am taken to a Busy Box Initramfs instead of my login screen. To my recollection the only command that had an issue was update-grub but can that be the issue if Grub worked fine (maybe)?
Here are the errors thrown during boot.
I can't say that I tried this script on anything other than vanilla Ubuntu. You're mileage may very on other distributions or flavors of Ubuntu. I have noticed that sometimes the password entry box is not visible. When you get to the screen where it looks like it hangs, before it drops to the BusyBox shell you took a picture of, try typing your LUKS password and hit enter. See if it's just a case of Elementary OS not handling the password prompt well.
That didn’t seem to work and it still dropped to the Busybox.
Sent from my iPhone
On Jan 22, 2020, at 1:25 AM, nbros652 [email protected] wrote:
I can't say that I tried this script on anything other than vanilla Ubuntu. You're mileage may very on other distributions or flavors of Ubuntu. I have noticed that sometimes the password entry box is not visible. When you get to the screen where it looks like it hangs, before it drops to the BusyBox shell you took a picture of, try typing your LUKS password and hit enter. See if it's just a case of Elementary OS not handling the password prompt well.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
This is classic bad grub config. I think specifically in your case, grub can't find the encrypted medium it should be passing off to, and so it just hangs. You should be able to press <Escape> when you see the elementary logo and you should see the grub commands being run as it tries to find the target partition.
I had a problem (I think with Kubuntu 19) where the update-grub script just wouldn't complete because of a long timeout waiting for the grub probe utility to try and not find anything. I found that issue was specific to that version, when I successfully installed an older version of the same OS. You might try another version of elementary...
