Re: boot/grub

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank again,

with the -v option, I have
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002,0001
Boot0000* fedora	HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
Boot0001* Hard Drive	BBS(HD,,0x0)..GO..NO........o.I.N.T.E.L. .S.S.D.S.C.2.K.W.1.8.0.H.6....................A...........................>..Gd-.;.A..MQ..L.V.C.T.L.2.6.4.6.4.0.6.Z.8.1.B.0.N.G. . ........BO..NO........o.W.D.C. .W.D.1.0.E.Z.E.X.-.2.2.M.F.C.A.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.C.W.6.C.3.Y.E.Z.2.S.K.P........BO..NO........o.M.a.x.t.o.r. .6.Y.0.8.0.M.0....................A...........................>..Gd-.;.A..MQ..L.2.Y.C.3.H.3.E.2. . . . . . . . . . . . ........BO
Boot0002* CD/DVD Drive	BBS(CDROM,,0x0)..GO..NO........o.D.R.W.-.2.4.D.5.M.T....................A...........................>..Gd-.;.A..MQ..L.3.K.G.F.Q.6.2.G.2.8. .7. . . . . . . . ........BO

If I understand correctly,
I boot on Boot0000  which is on partition 3 (hd0) using /boot/efi/EFI/fedora/grubx64.efi

However, I do not understand how does this work with multi disks.
We have
/boot/efi/EFI/fedora/grubx64.efi
on each disk ?
Which does not seem to be the case.

If I run
grubby --info=ALL

I get only the boot system available on the mounted system

What bothers me also is the date of /boot/efi/EFI/fedora/grub.cfg
-rwx------. 1 root root 15119 Jun  9  2019

I can regenerate it and I have
set default_kernelopts="root=/dev/mapper/VolSys_1-root ro rd.lvm.lv=VolSys_1/root "
I guess from
cat /etc/default/grub 
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys_1/root"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

But the rest of /boot/efi/EFI/fedora/grub.cfg is not coherent:
There is no menuentry matching the kernels which are on this disk.
There are mixing which old kernels (fc28) from other disks.

Now,
I boot on another disk (fc30)
There is no
/boot/efi/EFI/fedora/grub.cfg
It means that after update of the kernel, 
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
has not been run.

Thus, I am confuse.

In case of multidisks, what does what?


===========================================================================
 Patrick DUPRÉ                                 | | email: pdupre@xxxxxxx
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===========================================================================

>
> On 5/31/20 1:45 PM, Patrick Dupre wrote:
> > Thanks,
> > You are correct.
> > I also have Boot000F* Fedora
> > from this distribution (BootCurrent: 000F)
> > and
> > BootCurrent: 0000
> > Timeout: 1 seconds
> > BootOrder: 0000,0002,0001,0003,0004,0005
> > Boot0000* fedora
> >  From another one.
> > I wanted to understand what this means.
> > There is logic in this numbers.
> 
> I assume you're looking at the output of "efibootmgr", use "efibootmgr 
> -v" for more info.  That gives you the list of configured boot entries 
> in the EFI which will be different in each computer.  Fedora will take 
> the first available slot it finds.  Those are 4 digit hex numbers.  The 
> BootCurrent indicates which entry is currently booted.  The BootOrder 
> shows which entries it will try in order until it gets one that works.
> _______________________________________________
> 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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux