Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Can't get to Grub Menu even after running boot repair - Windows 10/LXLE dual boot

  1. #11
    Join Date
    Jul 2014
    Location
    Somewhere in Portugal
    Beans
    48
    Distro
    Xubuntu

    Re: Can't get to Grub Menu even after running boot repair - Windows 10/LXLE dual boot

    Quote Originally Posted by oldfred View Post
    configfile (hd0,5)/boot/grub/grub.cfg
    This worked perfectly! I can access Grub menu, and I have tried and successfully entered both LXLE and Windows from it

    Now I want to be able to just access Grub menu when I turn on the computer, instead of having to type this everytime (which is the behaviour I'm getting).

    I re ran boot repair, this time from LXLE installed on my SSD. This is the output

    Code:
    An error occurred during the repair.
    Error: NVram is locked (Ubuntu not found in efibootmgr). Please report this message to boot.repair@gmail.com
    
    Please write on a paper the following URL:
    https://paste.ubuntu.com/p/bs4N7g5NHf/
    
    
    In case you still experience boot problem, indicate this URL to:
    boot.repair@gmail.com 
    
    Locked-NVram detected.
    I googled it and found https://askubuntu.com/questions/1325...nvram-detected saying it's a hardware error, which is weird, as everything is working correctly and so I will disregard this information. It doesn't appear to be my exact situation.

    I also googled the fix you gave me and it seems like it is just making grub load the correct configuration file: that is my understanding from https://wiki.archlinux.org/title/GRU...rated_grub.cfg

    Do you know how to proceed now?

    By the way, at this point I am already very thankful <3

  2. #12
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Can't get to Grub Menu even after running boot repair - Windows 10/LXLE dual boot

    I thought the Locked NV-RAM was an UEFI setting.
    Some systems not only have UEFI Secure Boot but have added UEFI settings to lock ESP and/or lock USB boot for added security.
    Was UEFI updated?
    Sometimes you may not know it as Windows updates may include an UEFI update. And now many systems can be updated from Ubuntu/Linux with fwupdate entry in grub or systemd.

    But if you have UEFI entry and the configfile works, then it may just be something else.
    But I am not seeing problem. GUIDs & UUIDs all look correct.

    The chain of boot process is UEFI using GUID/partUUID finds ESP and loads shimx64.efi.
    Then in ESP is a 3 line grub.cfg that uses a configfile entry like you now are manually typing. Lines 267 thru 269. It does search by UUID for your / where grub.cfg for install is. You are just typing in what search should find.

    I use browser search & plug in GUID/partuuid in UEFI entry and it finds ESP.
    Then from ESP I use UUID of its search to find / (or /boot)
    Those all look consistent which they should from a grub reinstall using Boot-Repair.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  3. #13
    Join Date
    Jul 2014
    Location
    Somewhere in Portugal
    Beans
    48
    Distro
    Xubuntu

    Re: Can't get to Grub Menu even after running boot repair - Windows 10/LXLE dual boot

    Quote Originally Posted by oldfred View Post
    I thought the Locked NV-RAM was an UEFI setting.
    Some systems not only have UEFI Secure Boot but have added UEFI settings to lock ESP and/or lock USB boot for added security.
    Was UEFI updated?
    Sometimes you may not know it as Windows updates may include an UEFI update. And now many systems can be updated from Ubuntu/Linux with fwupdate entry in grub or systemd.

    But if you have UEFI entry and the configfile works, then it may just be something else.
    But I am not seeing problem. GUIDs & UUIDs all look correct.

    The chain of boot process is UEFI using GUID/partUUID finds ESP and loads shimx64.efi.
    Then in ESP is a 3 line grub.cfg that uses a configfile entry like you now are manually typing. Lines 267 thru 269. It does search by UUID for your / where grub.cfg for install is. You are just typing in what search should find.

    I use browser search & plug in GUID/partuuid in UEFI entry and it finds ESP.
    Then from ESP I use UUID of its search to find / (or /boot)
    Those all look consistent which they should from a grub reinstall using Boot-Repair.
    I did not manually update UEFI. I have no idea if Windows did it by itself.

    I'm sorry I haven't been able to dig in to figure out what is happening. It seems to just work with the hack you gave me, and I'm ok with typing it everytime I turn on the computer. Should I follow the link in your message about "UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295" to see if there is anything else I can do, when I try to make GRUB get to the configfile automatically?

    I'm now experiencing another bug when booting. Do you think they are related? This is it: https://ubuntuforums.org/showthread.php?t=2482071

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •