Patrick D.,check note after that line grub2-install --boot-directory=/boot /dev/sda "# Note: your drive may have another device name. Check for it with mount command output." Any case is diffrent you need to figure out for youself what is your setting. On Wed, 2019-06-26 at 10:08 +0200, Patrick Dupre wrote: > Hello Igor, > > I did not have to use your recommendations. > But you say > grub2-install --boot-directory=/boot /dev/sda > 1) I though it was not recommended for a efi boot. > 2) is it always in /dev/sda (if the /boot/efi is on sdb)? > > ===================================================================== > ====== > Patrick DUPRÉ | | email: > pdupre@xxxxxxx > Laboratoire interdisciplinaire Carnot de Bourgogne > 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE > Tel: +33 (0)380395988 > ===================================================================== > ====== > > > > Sent: Tuesday, June 25, 2019 at 9:09 PM > > From: "Igor Bezrodnik" <ledeni@xxxxxxxxxxxxxxxxx> > > To: users@xxxxxxxxxxxxxxxxxxxxxxx > > Subject: Re: Booting impossible > > > > Patrick, you need this steps to boot your system : > > > > Using the GRUB2 boot prompt > > > > If improperly configured, GRUB2 may fail to load and subsequently > > drop > > to a boot prompt. To address this issue, proceed as follows: > > > > 1) Load the XFS and LVM modules > > > > insmod xfs > > insmod lvm > > > > 2) List the drives which GRUB2 sees: > > > > grub2> ls > > > > 3) Study the output for the partition table of the /dev/sda > > device. > > It may look similar to the following example on a dos partition > > table > > with three partitons. will look something like this: > > > > (hd0) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1) > > > > or similar to this output on a gpt partition table of the > > /dev/sda > > device with four partitions. > > > > (hd0) (hd0,gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) > > > > 4) Probe each partition of the drive and locate your vmlinuz and > > initramfs files. > > > > ls (hd0,1)/ > > > > The outcome of the previous command will list the files on > > /dev/sda1. If this partition contains the /boot directory, it will > > show > > the full name of vmlinuz and initramfs. > > > > 5) Set the root partition. > > > > grub> set root=(hd0,3) > > > > 6) Set the desired kernel. > > > > grub> linux (hd0,1)/vmlinuz-3.0.0-1.fc16.i686 root=/dev/sda3 > > rhgb > > quiet selinux=0 > > # NOTE : add other kernel args if you have need of them > > # NOTE : change the numbers to match your system > > > > 7) Set the desired initrd. > > > > grub> initrd (hd0,1)/initramfs-3.0.0-1.fc16.i686.img > > # NOTE : change the numbers to match your system > > > > 8)Boot with the selected settings. > > > > grub> boot > > > > 9)When the system starts, open a terminal. > > > > 10)Enter the grub2-mkconfig command to re-create the grub.cfg > > file > > to enable GRUB2 to boot your system. > > > > grub2-mkconfig -o /boot/grub2/grub.cfg > > > > 11) Enter the grub2-install command to install GRUB2 to your > > hard > > disk to use of your config file. > > > > grub2-install --boot-directory=/boot /dev/sda > > # Note: your drive may have another device name. Check for it > > with > > mount command output. > > On Tue, 2019-06-25 at 19:20 +0200, Patrick Dupre wrote: > > > Hello, > > > > > > The situation is becoming worst and worst. > > > I tried an grub2-install /dev/sda > > > Now, I cannot boot at all. > > > I just enter in to a grub menu from here I am stuck. > > > Can I collect a bit of help? > > > > > > Thank. > > > > > > ================================================================= > > > ==== > > > ====== > > > Patrick DUPRÉ | | email: > > > pdupre@xxxxxxx > > > Laboratoire interdisciplinaire Carnot de Bourgogne > > > 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE > > > Tel: +33 (0)380395988 > > > ================================================================= > > > ==== > > > ====== > > > _______________________________________________ > > > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > > > To unsubscribe send an email to > > > users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > Fedora Code of Conduct: > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > List Guidelines: > > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: > > > https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
