0

After just having performed a fresh installation of Ubuntu 20.04 and needing to enable Secure Boot through UEFI so it can install third-party packages, the system pops the MOK Management screen and then brings me to GRUB regardless of input.

This question minorly touches on the problems I'm having, but has no answers and does not exactly match my issue.

The primary thing you're supposed to do is locate the root partition for your system, find the /boot/grub files for it, and then load the kernel and so on from there. The issue is my system refuses to find it.

The Ubuntu system is on a 256GB SD card and was installed not even half an hour ago. The only partitions it's finding, however, are my 128GB SSD and 1TB HDD that are both Windows. This means I can't boot into my new Ubuntu system at all, since it won't find the files. This is all it can find;

  • The partition at (hd0,1) is the HDD.
  • (hd0,2) and on don't exist.
  • The partition at (hd1,1) is seemingly Linux, however the /boot/grub directories within it are empty.
  • (hd1,2) reports an unknown filesystem.
  • (hd1,3) is my SSD.
  • (hd1,4) is the Windows RE.
  • (hd1,5) and onward don't exist.
  • There exists a (proc), but the only thing in there is something called "luks_script".

Edit: After doing some further testing (and more re-installs), I've found the following information;

  1. It is NOT only limited to utilizing Secure Boot. Even after re-installing with the "third-party packages" selection unchecked, the issue still stands.
  2. After echoing $root, I've found that it's giving the aforementioned (hd1,1) partition that had its /boot/grub directory empty--this is the partition that it believes to be root.
    • /boot/grub is NOT empty after a non-Secure Boot install, and x86_64-efi/ contains grub.cfg.
  3. Said partition's /efi directory holds directories of Microsoft/, Boot/, hp/, Android/, and ubuntu/, all of which are indicative of the previous and/or current systems I've installed (or attempted to install) to the SD card--Android x86, Windows XP, HP's recovery systems, and Ubuntu.
    • The fascinating part of this is each directory holds information regarding that OS; eg. Microsoft/Boot/ holds bootmgr.efi, Android/ holds android.cfg, and so on.
    • None of these folders, as I can tell, hold the proper kernel information I need.
xTerrene
  • 263

0 Answers0