Hello again, The BIOS in this computer allows the setting of a boot order for internal disks. Moving sdg to the top produces a clean boot process.
Thank you. -- Luís Moreira de Sousa Molenweg 4 6871 CW Renkum The Netherlands Phone: +31 628 544 755 Email: luis.de.so...@protonmail.ch RingID: ring:7ca91d83f4f9dec82fec9f1144b8e5c1ef2a110c URL: https://sites.google.com/site/luismoreiradesousa > -------- Original Message -------- > Subject: Re: Permanently fix absolute location of the GRUB folder > Local Time: 14 November 2017 2:37 PM > UTC Time: 14 November 2017 13:37 > From: luis.de.so...@protonmail.ch > To: Pascal Hambourg <pas...@plouf.fr.eu.org> > help-grub@gnu.org <help-grub@gnu.org> > > Thank you Pascal for the clarifications. How can this be solved? Instructing > the BIOS to boot from sdg? Or by doing something with the GRUB installed in > sda? > > Just for reference: I can confirm that sda once had an OS installed, but it > was Windows. > > Regards. > -- > Luís > >> -------- Original Message -------- >> Subject: Re: Permanently fix absolute location of the GRUB folder >> Local Time: 13 November 2017 11:50 PM >> UTC Time: 13 November 2017 22:50 >> From: pas...@plouf.fr.eu.org >> To: help-grub@gnu.org <help-grub@gnu.org> >> >> Le 13/11/2017 à 09:10, Luís Moreira de Sousa a écrit : >> >>> I recently hit a relatively common problem whit the Ubuntu 16.04 installer, >>> that misconfigures the location of the GRUB folder [0]. In such cases the >>> system boots into a rescue shell with the following messages: >>> error: file '/grub/i386-pc/normal.mod' not found. >>> >>> Matches : >>> >>> => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 >>> of >>> the same hard drive for core.img. core.img is at this location and looks >>> for (,msdos1)/grub. >>> >>> the missing "/boot" in the path means that this GRUB was installed with >>> /boot on a separate partition. >>> >>> This means GRUB was able to boot, but it is looking for its modules in the >>> wrong place. The well known solution is to instruct GRUB on the fly on the >>> location of its modules [1]. In my case this is: >>> grub rescue> set prefix=(hd1,msdos2)/boot/grub >>> >>> meaning that another GRUB was installed on another drive (hd0 is always >>> the boot drive in BIOS boot) with /boot in the root partition. Matches : >>> >>> => Grub2 (v2.00) is installed in the MBR of /dev/sdg and looks at sector 1 >>> of >>> the same hard drive for core.img. core.img is at this location and looks >>> for (,msdos2)/boot/grub. >>> >>> My guess is that the system is booting GRUB in BIOS/legacy mode from >>> sda, which contains a remain of GRUB from a previous installation, not >>> from sdg. Fortunately for you, the two GRUBs are compatible enough. >>> >>> Also, it seems that /dev/sdg contains both EFI and BIOS/legacy GRUBs. >> >> --------------------------------------------------------------- >> >> Help-grub mailing list >> Help-grub@gnu.org >> https://lists.gnu.org/mailman/listinfo/help-grub _______________________________________________ Help-grub mailing list Help-grub@gnu.org https://lists.gnu.org/mailman/listinfo/help-grub
