I think you are confusing disks and partitions.Īgain, I have yet to get a single report from someone where (hd0) didn't map to the installation media ( disk) where they booted from.

I have yet to get a single report from someone where (hd0) did not map to the installation media they booted from GRUB always maps (hd0) to whatever you actually booted from. But of course, I'll be happy to try to help, if you want to take a stab at it in the meantime. So if you guys can't come up with a solution you're happy with, note that I don't have a problem with the proposed patches being reverted, as I am planning to explore this issue in more details in a month or two (since right now I'm just dropping suggestions that I haven't had a chance to properly validate, due other matters taking precedence). I think we might be able to do that by creating an early config through the -c option, but then we'll probably need to embed a few more modules which search might have dependencies on, as well as possibly chain link the config files.Īll in all, it turns out that adding support for non dd FAT32 ISO extraction boot, that keeps all the existing modes happy, is turning to be a lot more complex than adding the handful a GRUB modules I originally thought it would boil down to. Thus, for search to be useful, it would have to be issued not in the main grub.cfg but in grub-mkimage. which of course means that, since we already have those and therefore identified the location we seek, it would become a bit superfluous. Moreover, we have to account for the use of the biosdisk module (which is what Manjaro in dd mode appears to have been designed around), and I currently have no idea how that translates in terms of disk and partition identifiers for GRUB.Īs to using search, this is usually issued once grub.cfg and the GRUB modules have been located. Ideally, you'd want to use something like (hd0,msdos1), to explicitly set the partition where your GRUB boot data is located (and this is actually what I use in the core.img I built for use with Rufus), but I'm pretty sure this will only work for BIOS/MBR and not UEFI/GPT drives, which we also need here, so that's why I was trying to go with something more generic. Well, (hd0) is what seemed to work to locate files when I manually tested manjaro-gnome-18.1.0-pre2-testing-x86_64.iso from the rescue prompt.

Rufus iso extraction failed