Menu

Error msg - don't understand

Ed P
2018-01-31
2018-02-02
  • Ed  P

    Ed P - 2018-01-31

    Hi Drummer,

    I've been booting to different systems for a couple of weeks via my Grub2Win system on my EFI notebook. Today I start Grub2Win to add another OS and after I get pass the update window my normal menu window has a red box stating "The GNU Grub EFI modules are not installed" etc.

    If they are not installed how have I been able to boot multiple systems?

    BTW I'm running 1.0.15.

    Ed

     

    Last edit: Ed P 2018-02-02
  • Drummer

    Drummer - 2018-01-31

    Hey Ed,

    Check out file C:\grub2\windata\storage\gnugrub.efilevel.xxx.txt

    Note - You may have installed Grub2Win to another location than the C: drive.

    This is the file Grub2Win uses to keep track of the EFI modules.

    The xxx represents the EFI module level. If this file is missing or corrupted, Grub2Win thinks that the EFI modules are not installed.

    If the file is missing, you can rebuild it by re-installing the EFI modules. This is harmless.

    As to why the file is missing, I suspect your disk addresses may have changed or you have Grub2Win installed on multiple drives. This can get very confusing.

    Please let me know if this works for you.

    Thanks,

    Dave

     
  • Ed  P

    Ed P - 2018-01-31

    Hi Dave,

    I have 2 txt files. C:\grub2\windata\storage\gnugrub.efilevel.127.txt and C:\grub2\windata\storage\grub2win.efilevel.126.txt both of which display " Placeholder for the Grub2Win EFI bootcode level". 127 is dated 11/11/17, 126 is dated 11/5/17.

    Grub2Win is only installed on my C: drive. However, I do have a copy of it on a USB drive. My hard drive's partitions sequence is the same as they were in December though their sizes are different. C: is still sda3.

    Ok, I let Grub2Win update the EFIs and now the 126 file is gone.

    Strange. When the system was restored from a 12/12/17 backup the Windows restore included the EFI partition and C: drive and the 2 txt files were there and there was no complaints from Grub2Win then.

    Ed

     
  • Drummer

    Drummer - 2018-02-02

    Hey Ed,

    It all depends on where the grub2win.exe you are running is located.

    If you run E:\grub2\grub2win.exe from perhaps a USB drive, the program will look for E:\grub2\windata\storage\gnugrub.efilevel.xxx.txt on your E: drive.

    If you run C:\grub2\grub2win.exe then the program will look for C:\grub2\windata\storage\gnugrub.efilevel.xxx.txt on your C: drive.

    As I mentioned before, having Grub2Win copies on multiple drives can lead to a lot of confusion.

    • Dave
     
  • Ed  P

    Ed P - 2018-02-02

    Dave,

    If grub2win is operated from a USB drive it doeesn't update the USB drive's EFI folder it only updates the hard drive's EFI folder. And since the hard drive is being updated regardless of where grrub2win is being executed, grub2win should check the hard drive's C: partition for C:\grub2 and update the files there.

    A more consistent EFI process would be good. ;-)

    Ed

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.