On Tue, Mar 11, 2014 at 11:02 PM, Rustom Mody <[email protected]> wrote: > On Tue, Mar 11, 2014 at 9:53 PM, Jordan Uggla <[email protected]> wrote: >> On Mon, Mar 10, 2014 at 8:21 AM, Rustom Mody <[email protected]> wrote: >>>> menuentry "Debian bootloader" { >>>> search --set --label Debian500G >>>> multiboot /boot/grub/i386-pc/core.img >>>> } >>> >>> Tried this. I get: >>> >>> Welcome to Grub (in inverse video) >>> error file not found >>> Entering rescue mode >>> grub rescue> >>> >>> How I tried: >>> >>> At the grub prompt I gave the following >>> multiboot (hd0,5)/boot/grub/core.img >>> >> >> Note that "root=(something,else); multiboot >> (hd0,5)/boot/grub/core.img" is *not* functionally equivalent to >> "root=(hd0,5); multiboot (hd0,5)/boot/grub/core.img". The multiboot >> loader actually uses the value of $root and passes that information >> along to the kernel its loading, in the case of loading grub it's used >> to find the correct device value for $prefix. >> >> Try actually using "search --set=root --fs-uuid=UUID_HERE; multiboot >> /boot/grub/core.img". > > Same result; viz. I get this > > Welcome to Grub (in inverse video) > error file not found > Entering rescue mode > grub rescue> > > Slightly different words if I put --fs-uuid=UUID_HERE > Exactly the above when there is no '=' sign > > Also tried with label (which is my original) -- same thing > > I preceded that line by a > insmod multiboot
I tried with debug=all to see if I could come closer to the problem. Gives me so much output its unmanageable. So: Is there something other than 'all' to see more focused output? _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
