12:20 p.m.
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(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
1:23 p.m.
On Tue, 25 Jun 2019 19:20:32 +0200
"Patrick Dupre" <pdupre(a)gmx.com> wrote:
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?
It sounds like you are throwing mud at the wall, and hoping something
will stick. That's a recipe for disaster when troubleshooting computer
systems. Calm and methodical, that's the way.
I know only a little about UEFI booting, though I recently got it
working. My understanding is that there can be only one
default uefi /boot/efi. So, if you wanted the second system installed
to be bootable directly, you should have created a /boot/efi for the
second install on the disk where it was installed. You then could use
the firmware boot selection to switch to the alternate if the default
isn't what you want. I *think* the last installed uefi system is the
default in the firmware. Do you have a rescue CD / USB stick you can
boot from? You can then mount /mnt/sysimage for the system you want to
repair, and chroot there to do your repairs. I think you need to
re-install the shim and grub-efi. e.g.
dnf reinstall grub2-efi shim-ia32 shim-x64
That system will then be the default boot for uefi. You should
probably run
grub2-mkconfig -o grub.cfg
in /boot/efi/EFI/fedora after you do the reinstall. That should give
you a bootable system to work from.
This is a little out of date, but has useful information. It says
there that grub-install will render a uefi system unbootable, which is
your experience.
https://superuser.com/questions/596317/how-would-i-reinstall-the-grub-efi...
Here's the official Fedora uefi docs.
https://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Secure_Bo...
1:52 p.m.
On Tue, 25 Jun 2019 11:23:49 -0700
stan <upaitag(a)zoho.com> wrote:
working. My understanding is that there can be only one
default uefi /boot/efi.
To clarify, there can only be one fedora bootable from each /boot/efi.
A single version of any other OS can also be booted from the
same /boot/efi. So you could have fedora, suse, ubuntu, debian,
windows, etc. installed, and they could all be selected and boot from
that same /boot/efi, but not a second version of any of them.
Kind of clumsy, and makes it hard to run a backup version of Fedora
other than by putting it on a different disk, and booting from the
firmware selection menu. i.e. hitting F2 or Delete during boot.
2:59 p.m.
Hello,
Thank for your suggestions.
Here is the current situation.
After I installed the 2nd boot system on sda6 with a /boo/efi on the sdb1
(the 2 systems could mount the same /boot/efi), I have never been able to
boot on the original system.
I have a grub2-mkconfig to generate a grub.cfg which has never work properly
to boot the 1st OS (which has originally installed in fedora 28, actually, I noted
large differences between the fedora 28 and fedora 30 grub.cfg files).
Then, I made a grub2-install -o /dev/sda.
This created a "mess", I only got a grub shell.
Fortunately, I have a mbr saved for sda and I reinstalled the default mbr,
and I also had a /boot/efi saved. Hence, I reinstalled the old
/boot/efi.
Lucky, I was able to boot on my "old" system.
I booted 2 times and then I run grub2-mkconfig /boot/efi/fedora/grub.cfg
because I wanted to be able to have the option of booting of 2 systems.
But, then, no way to reboot, any of the systems.
I tried tons of times from the bios configuration. No way.
I tried to boot by using the "old" (the one which has working for the
last boot) grub.cfg, and the new one, but same result.
In the best situation, I could read something like:
error file /EFI/x64_86-efi/increment.mod not incremented.
(it was fast that it was hard to read).
I do not understand, because I have 2 other machines with 2 or 3 boots (with 1 or
3 disks, one in efi and one is legacy) in fedora 30
and I cannot complain.
I just see one difference for this one: it has 2 disks,
the ssd in mounted in sdb (with the /boot/efi in sdb1) with one
system on sdb, and the second (new) system in sda (sda6).
I just do not understand why it is so much a problem.
Now, what to do?
It seems that I am stuck with the bios!
options
1) destroy the sda6? and try to boot !!!
2) boot on the stick and make a chroot?
and fix what has to be fixed? But I have no idea.
3) Reinstall the sda6, but then how to have the 2 systems running?
Why I would be more successful the 2nd time?
4) Other options?
Thank for your help.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
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 2:52 PM
> From: "stan via users" <users(a)lists.fedoraproject.org>
> To: users(a)lists.fedoraproject.org
> Cc: stan <upaitag(a)zoho.com>
> Subject: Re: Booting impossible
>
> On Tue, 25 Jun 2019 11:23:49 -0700
> stan <upaitag(a)zoho.com> wrote:
>
> > working. My understanding is that there can be only one
> > default uefi /boot/efi.
>
> To clarify, there can only be one fedora bootable from each /boot/efi.
> A single version of any other OS can also be booted from the
> same /boot/efi. So you could have fedora, suse, ubuntu, debian,
> windows, etc. installed, and they could all be selected and boot from
> that same /boot/efi, but not a second version of any of them.
>
> Kind of clumsy, and makes it hard to run a backup version of Fedora
> other than by putting it on a different disk, and booting from the
> firmware selection menu. i.e. hitting F2 or Delete during boot.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
>
8:53 a.m.
On Tue, 25 Jun 2019 21:59:27 +0200
"Patrick Dupre" <pdupre(a)gmx.com> wrote:
Hello,
Thank for your suggestions.
Here is the current situation.
After I installed the 2nd boot system on sda6 with a /boo/efi on the
sdb1 (the 2 systems could mount the same /boot/efi), I have never
been able to boot on the original system.
This accords with my understanding: there is no chainloading of efi
systems. A single /boot/efi boots a single OS instance.
I have a grub2-mkconfig to generate a grub.cfg which has never work
properly to boot the 1st OS (which has originally installed in fedora
28, actually, I noted large differences between the fedora 28 and
fedora 30 grub.cfg files). Then, I made a grub2-install -o /dev/sda.
This created a "mess", I only got a grub shell.
Fortunately, I have a mbr saved for sda and I reinstalled the default
mbr, and I also had a /boot/efi saved. Hence, I reinstalled the old
/boot/efi.
So, you updated a bios F28 to efi F30? I don't know how well that is
supported, but it sounds like a recipe for trouble.
Lucky, I was able to boot on my "old" system.
I booted 2 times and then I run
grub2-mkconfig /boot/efi/fedora/grub.cfg because I wanted to be able
to have the option of booting of 2 systems. But, then, no way to
reboot, any of the systems. I tried tons of times from the bios
configuration. No way. I tried to boot by using the "old" (the one
which has working for the last boot) grub.cfg, and the new one, but
same result. In the best situation, I could read something like:
error file /EFI/x64_86-efi/increment.mod not incremented.
(it was fast that it was hard to read).
I do not understand, because I have 2 other machines with 2 or 3
boots (with 1 or 3 disks, one in efi and one is legacy) in fedora 30
and I cannot complain.
But on those other systems are you trying to boot a second efi OS from
the first /boot/efi system? On my efi install, when I run
grub2-mkconfig, it finds all the bios installations and creates menu
entries for them, so I can boot them from the efi system.
I will be installing a second efi system on a different disk, so I will
be able to test how this works with two efi systems in a setup similar
to yours. I just don't think I will be able to boot the second efi
install from the first, and vice versa.
I just see one difference for this one: it has 2 disks,
the ssd in mounted in sdb (with the /boot/efi in sdb1) with one
system on sdb, and the second (new) system in sda (sda6).
I just do not understand why it is so much a problem.
Now, what to do?
It seems that I am stuck with the bios!
options
1) destroy the sda6? and try to boot !!!
2) boot on the stick and make a chroot?
and fix what has to be fixed? But I have no idea.
3) Reinstall the sda6, but then how to have the 2 systems running?
Why I would be more successful the 2nd time?
4) Other options?
I think you should create the EFI partitions on /dev/sda, EF00 (2MB),
EF01 (2MB), EF02 (1GB), and then reinstall the OS on /dev/sda putting
the /boot/efi in the newly created EF02 partition on /dev/sda. That
will get you a working efi install of F30. From there you can clean up
the F28-F30 upgrade to ensure that it too can boot efi. But I don't
think you can expect to boot either of the efi installs from the
other. You will have to select the non-default efi install from the
firmware boot menu.
9:12 a.m.
Hello,
The issue is fixed. But I cannot really gives a recipes.
The issue was in the generation of the grub.cfg
1) It did let boot on system 1 when generated by system 2 (it looks that a efilinux
and efiinitrd were missing). This let me boot on system 1.
2) When I booted on system 1, the new grub.cfg yjay generated did not let me
boot on system 2. However, after I did it again and gain, it finally generated
a correct file which let me boot both systems.
I noted that the structure of the grub.cfg files generated differ according to with
system
generates it.
I also noted that sometimes, some partitions which were not mounted because
there were not in the fstab, could never be mounted: busy! A rebooting
solves the issue!
>
> On Tue, 25 Jun 2019 21:59:27 +0200
> "Patrick Dupre" <pdupre(a)gmx.com> wrote:
>
> > Hello,
> >
> > Thank for your suggestions.
> > Here is the current situation.
> > After I installed the 2nd boot system on sda6 with a /boo/efi on the
> > sdb1 (the 2 systems could mount the same /boot/efi), I have never
> > been able to boot on the original system.
>
> This accords with my understanding: there is no chainloading of efi
> systems. A single /boot/efi boots a single OS instance.
>
> > I have a grub2-mkconfig to generate a grub.cfg which has never work
> > properly to boot the 1st OS (which has originally installed in fedora
> > 28, actually, I noted large differences between the fedora 28 and
> > fedora 30 grub.cfg files). Then, I made a grub2-install -o /dev/sda.
> > This created a "mess", I only got a grub shell.
> > Fortunately, I have a mbr saved for sda and I reinstalled the default
> > mbr, and I also had a /boot/efi saved. Hence, I reinstalled the old
> > /boot/efi.
>
> So, you updated a bios F28 to efi F30? I don't know how well that is
> supported, but it sounds like a recipe for trouble.
>
> > Lucky, I was able to boot on my "old" system.
> > I booted 2 times and then I run
> > grub2-mkconfig /boot/efi/fedora/grub.cfg because I wanted to be able
> > to have the option of booting of 2 systems. But, then, no way to
> > reboot, any of the systems. I tried tons of times from the bios
> > configuration. No way. I tried to boot by using the "old" (the one
> > which has working for the last boot) grub.cfg, and the new one, but
> > same result. In the best situation, I could read something like:
> > error file /EFI/x64_86-efi/increment.mod not incremented.
> > (it was fast that it was hard to read).
> >
> > I do not understand, because I have 2 other machines with 2 or 3
> > boots (with 1 or 3 disks, one in efi and one is legacy) in fedora 30
> > and I cannot complain.
>
> But on those other systems are you trying to boot a second efi OS from
> the first /boot/efi system? On my efi install, when I run
> grub2-mkconfig, it finds all the bios installations and creates menu
> entries for them, so I can boot them from the efi system.
>
> I will be installing a second efi system on a different disk, so I will
> be able to test how this works with two efi systems in a setup similar
> to yours. I just don't think I will be able to boot the second efi
> install from the first, and vice versa.
>
> > I just see one difference for this one: it has 2 disks,
> > the ssd in mounted in sdb (with the /boot/efi in sdb1) with one
> > system on sdb, and the second (new) system in sda (sda6).
> > I just do not understand why it is so much a problem.
> > Now, what to do?
> > It seems that I am stuck with the bios!
> > options
> > 1) destroy the sda6? and try to boot !!!
> > 2) boot on the stick and make a chroot?
> > and fix what has to be fixed? But I have no idea.
> > 3) Reinstall the sda6, but then how to have the 2 systems running?
> > Why I would be more successful the 2nd time?
> > 4) Other options?
>
> I think you should create the EFI partitions on /dev/sda, EF00 (2MB),
> EF01 (2MB), EF02 (1GB), and then reinstall the OS on /dev/sda putting
> the /boot/efi in the newly created EF02 partition on /dev/sda. That
> will get you a working efi install of F30. From there you can clean up
> the F28-F30 upgrade to ensure that it too can boot efi. But I don't
> think you can expect to boot either of the efi installs from the
> other. You will have to select the non-default efi install from the
> firmware boot menu.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
>
10:01 a.m.
On Thu, 27 Jun 2019 16:12:10 +0200
"Patrick Dupre" <pdupre(a)gmx.com> wrote:
Hello,
The issue is fixed. But I cannot really gives a recipes.
The issue was in the generation of the grub.cfg
1) It did let boot on system 1 when generated by system 2 (it looks
that a efilinux and efiinitrd were missing). This let me boot on
system 1. 2) When I booted on system 1, the new grub.cfg yjay
generated did not let me boot on system 2. However, after I did it
again and gain, it finally generated a correct file which let me boot
both systems.
I noted that the structure of the grub.cfg files generated differ
according to with system generates it.
I also noted that sometimes, some partitions which were not mounted
because there were not in the fstab, could never be mounted: busy! A
rebooting solves the issue!
Good effort! But, as you say, not a recipe. And the inconsistency in
behavior, whew; that's not how computers are supposed to work. I hope
I have better luck.
1:31 p.m.
On Tue, 25 Jun 2019 19:20:32 +0200, Patrick Dupre wrote:
Hello,
The situation is becoming worst and worst.
I tried an grub2-install /dev/sda
When did you run that command? Within a running working installation?
And why did you run it?
> 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?
2:09 p.m.
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(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
=====================================================================
======
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
3:08 a.m.
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(a)gmx.com
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(a)fedoraproject.org>
> To: users(a)lists.fedoraproject.org
> 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(a)gmx.com
> > Laboratoire interdisciplinaire Carnot de Bourgogne
> > 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> > Tel: +33 (0)380395988
> > =====================================================================
> > ======
> > _______________________________________________
> > users mailing list -- users(a)lists.fedoraproject.org
> > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> > 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@lists.fedoraproject.org
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
>
5:07 a.m.
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(a)gmx.com
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(a)fedoraproject.org>
> To: users(a)lists.fedoraproject.org
> 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(a)gmx.com
> > Laboratoire interdisciplinaire Carnot de Bourgogne
> > 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> > Tel: +33 (0)380395988
> > =================================================================
> > ====
> > ======
> > _______________________________________________
> > users mailing list -- users(a)lists.fedoraproject.org
> > To unsubscribe send an email to
> > users-leave(a)lists.fedoraproject.org
> > 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@lists.fedoraproject.org
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
5:35 a.m.
Patrick D.,check note after that line
grub2-install --boot-directory=/boot /dev/sda
This is what I do not understand:
--boot-directory=/boot is the default
then
grub2-install /dev/sda
But again it is not recommended with efi
> "# 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(a)gmx.com
> > 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(a)fedoraproject.org>
> > > To: users(a)lists.fedoraproject.org
> > > 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(a)gmx.com
> > > > Laboratoire interdisciplinaire Carnot de Bourgogne
> > > > 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> > > > Tel: +33 (0)380395988
> > > > =================================================================
> > > > ====
> > > > ======
> > > > _______________________________________________
> > > > users mailing list -- users(a)lists.fedoraproject.org
> > > > To unsubscribe send an email to
> > > > users-leave(a)lists.fedoraproject.org
> > > > 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@lists.fedoraproject.org
> > > _______________________________________________
> > > users mailing list -- users(a)lists.fedoraproject.org
> > > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> > > 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@lists.fedoraproject.org
> > >
> > _______________________________________________
> > users mailing list -- users(a)lists.fedoraproject.org
> > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> > 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@lists.fedoraproject.org
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
>
2:31 p.m.
Patrick if you use uefi system once you boot do this steps:
) sudo grub2-install /dev/sda/
2) sudo dnf reinstall grub2-efi-x64 shim-ia32 shim-x6
3) sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
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(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
=====================================================================
======
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
3:46 p.m.
Ok
On Wed, 2019-06-26 at 11:45 -0700, Samuel Sieb wrote:
On 6/25/19 12:31 PM, Igor Bezrodnik wrote:
> Patrick if you use uefi system once you boot do this steps:
> ) sudo grub2-install /dev/sda/
Please do not suggest this any more. On an EFI system, it will not
help
and might harm things.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
9:48 a.m.
On Tue, Jun 25, 2019 at 8:11 PM Patrick Dupre <pdupre(a)gmx.com> wrote:
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.
"grub2-install /dev/sda" isn't good on EFI.
On Fedora, you need:
grub2-install --target=x86_64-efi
--boot-directory=/boot/efi/EFI/fedora --efi-directory=/boot/efi
/dev/sda
10:38 a.m.
I am curious.
Checking in the info
--boot-directory=DIR'
Install GRUB images under the directory 'DIR/grub/'
It means that in your example, it will be installed in
/boot/efi/EFI/fedora/grub
while the default is /boot
On my machine there is not /boot/grub (inly a /boot/grub2) and no
/boot/efi/EFI/fedora/grub
Is this information correct?
In addition, on which criterion would you choose between /dev/sda and /dev/sdb?
the partition of /boot/efi ?
> On Fedora, you need:
>
> grub2-install --target=x86_64-efi
> --boot-directory=/boot/efi/EFI/fedora --efi-directory=/boot/efi
> /dev/sda
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
>
1800
days inactive
1803
days old
19 comments
6 participants
participants (6)
-
Igor Bezrodnik -
Michael Schwendt -
Patrick Dupre -
Samuel Sieb -
stan -
Tom H