[bug #63127] failure to correctly read BPB block in GPT/UEFI setting

[Milan Durovic]

Follow-up Comment #6, bug #63127 (project grub):

I came across this article:
https://superuser.com/questions/130955/how-to-install-grub-into-an-img-file

and interestingly, the author, instead of mounting loop0p1, uses *losetup*
over *loop0p1* like:

losetup /dev/loop1 /dev/mapper/loop0p1

in order to overcome *grub-install* confusion with device mapper devices. So,
I followed the steps and this time I didn't get *grub-install* to complain
about "volume group" - it completed successfully. *Unfortunately*, I still get
the original problem, ie. when GRUB tries to read BPB parameters, it does that
from the wrong location.

I tried adding the device.map as suggested in the quoted article, but it
obviously had no effect. I'm not sure it's even used in EFI/GPT situation?
[comment #5 comment #5:]
> 
> [comment #4 comment #4:]
> > Is your grub compiled with libdevmapper support
> 
> I didn't specify it explicitly. Now I added --enable-device-mapper option
when running *configure* script, rebuilt grub, reinstalled it, and tried
everything again. Still the same outcome, same messages. I did everything
twice from scratch, just in case I overlooked something or made a mistake, but
the result and messages were identical.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63127>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/