Hello,
I am still stuck with my installation. Question Why
grub2-mkconfig
says Found Fedora Linux 36 (Workstation Edition) on /dev/sdb11 Found Fedora Linux 40 (Forty) on /dev/sdc3 Found Fedora Linux 36 (Workstation Edition) on /dev/mapper/VolSys_2-root Adding boot menu entry for UEFI Firmware Settings ... done
but in the generated file (grub.cfg) there is no reference to Fedora 40 or sdc3 In addition there are a lot of references to Linux 36 (Workstation Edition) on /dev/sdb11 ?
Thanks
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com ===========================================================================
On 4 Jun 2024, at 11:35, Patrick Dupre via users users@lists.fedoraproject.org wrote:
but in the generated file (grub.cfg) there is no reference to Fedora 40 or sdc3
Fedora use BLS (boot loader specifcations) that are in /boot/loader/entries. grub, by default, scans that folder and adds all the entries to the menu.
For example here is a example from one of my f40 systems:
/boot/loader/entries/23861aed63d748da85011d84ee28e601-6.8.10-300.fc40.x86_64.conf /boot/loader/entries/23861aed63d748da85011d84ee28e601-6.9.2-200.fc40.x86_64.conf /boot/loader/entries/23861aed63d748da85011d84ee28e601-0-rescue.conf /boot/loader/entries/23861aed63d748da85011d84ee28e601-6.8.9-300.fc40.x86_64.conf
Barry
On Tue, 4 Jun 2024 12:35:37 +0200, Patrick Dupre via users wrote:
but in the generated file (grub.cfg) there is no reference to Fedora 40 or sdc3
What do you see in the grub2.cfg file section with the "10_linux" header?
### BEGIN /etc/grub.d/10_linux ### insmod part_gpt insmod ext2 set root='hd0,gpt4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 0ab8c5a6-a344-48f8-afca-e6187c589cde else search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-e6187c589cde fi insmod part_gpt insmod fat set boot='hd0,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=boot --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 8131-80F4 else search --no-floppy --fs-uuid --set=boot 8131-80F4 fi # This section was generated by a script. Do not modify the generated file - all changes # will be lost the next time file is regenerated. Instead edit the BootLoaderSpec files. # # The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries and # populates the boot menu. Please refer to the Boot Loader Specification documentation # for the files format: https://systemd.io/BOOT_LOADER_SPECIFICATION/.
# The kernelopts variable should be defined in the grubenv file. But to ensure that menu # entries populated from BootLoaderSpec files that use this variable work correctly even # without a grubenv file, define a fallback kernelopts variable if this has not been set. # # The kernelopts variable in the grubenv file can be modified using the grubby tool or by # executing the grub2-mkconfig tool. For the latter, the values of the GRUB_CMDLINE_LINUX # and GRUB_CMDLINE_LINUX_DEFAULT options from /etc/default/grub file are used to set both # the kernelopts variable in the grubenv file and the fallback kernelopts variable. if [ -z "${kernelopts}" ]; then set kernelopts="root=UUID=0ab8c5a6-a344-48f8-afca-e6187c589cde ro resume=UUID=61d9baea-3415-4bd7-839e-62af20d6a846 " fi
insmod blscfg blscfg ### END /etc/grub.d/10_linux ###
This is the fedora 38
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 0ab8c5a6-a344-48f8-afca-e6187c589cde else search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-e6187c589cde
search --no-floppy --fs-uuid --set=boot --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 8131-80F4 else search --no-floppy --fs-uuid --set=boot 8131-80F4
What partitions do these two UUIDs refer to? You can run e.g. blkid -U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find out. Or run "blkid" and skim over the output.
This is the fedora 38
Do you mean you're running F38 and trying to reconfigure Grub2? Or what scenario is it exactly?
On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 0ab8c5a6-a344-48f8-afca-e6187c589cde else search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-e6187c589cde
search --no-floppy --fs-uuid --set=boot --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 8131-80F4 else search --no-floppy --fs-uuid --set=boot 8131-80F4
What partitions do these two UUIDs refer to? You can run e.g. blkid -U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find out. Or run "blkid" and skim over the output.
This is sda4 where Fedora 38 is installed (sda4)
This is the fedora 38
Do you mean you're running F38 and trying to reconfigure Grub2?
Yes.
Or what scenario is it exactly?
Fedora 40 is installed on sdc3 (it is an update of a Fedora 38) Since this installation is not accessible correctly, I ma running Fedora 38
Actually, I tried to do similar things from Fedora 40 without more success. In addition, this Fedora 40 is a "test" installation, I will update Fedora 38 when I will be sure that I can have control on the full installation. The risk is that I lost more control, typically on the installation of sda4
/boot/efi is on sda3
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 4 Jun 2024, at 13:11, Patrick Dupre via users users@lists.fedoraproject.org wrote:
Fedora 38 when I will be sure that I can have control on the full installation. The risk is that I lost more control, typically on the installation of sda4
The way I test out new Fedora releases is to see if the live image works on my hardware.
The other way is that I have a external USB-3 SSD drive that I use for deeper testing that needs specific software installed. For example when I had nvidia GPU I would test out the rpmfusion drivers this way.
In both cases I do not need to figure out how to setup a single grub to work with OS installed on 2 drives.
Having said that I wonder if you have two sets of BLS files that you need to merge into your preferred /boot (assuming you have multiple /boot's and f38 and an f40).
Barry
On 4 Jun 2024, at 13:39, Patrick Dupre pdupre@gmx.com wrote:

On 4 Jun 2024, at 13:11, Patrick Dupre via users users@lists.fedoraproject.org wrote:
Fedora 38 when I will be sure that I can have control on the full installation. The risk is that I lost more control, typically on the installation of sda4
The way I test out new Fedora releases is to see if the live image works on my hardware.
The other way is that I have a external USB-3 SSD drive that I use for deeper testing that needs specific software installed. For example when I had nvidia GPU I would test out the rpmfusion drivers this way.
In both cases I do not need to figure out how to setup a single grub to work with OS installed on 2 drives.
Having said that I wonder if you have two sets of BLS files that you need to merge into your preferred /boot (assuming you have multiple /boot's and f38 and an f40).
Barry
This what I have on Fedora 40 (old Fedora 38) -rw-r--r--. 1 root root 453 Jun 2 12:30 dcdc9ed7e87243ec91d6d876cf7c3384-0-rescue.conf -rw-r--r--. 1 root root 381 Jun 2 12:30 dcdc9ed7e87243ec91d6d876cf7c3384-6.3.4-201.fc38.x86_64.conf -rw-r--r--. 1 root root 378 Jun 2 12:30 dcdc9ed7e87243ec91d6d876cf7c3384-6.8.11-300.fc40.x86_64.conf -rw-r--r--. 1 root root 381 Jun 2 12:30 dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
versus -rw-r--r--. 1 root root 160 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-0-memtest86+.conf -rwxr-xr-x. 1 root root 417 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-0-rescue.conf -rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.7-100.fc38.x86_64.conf -rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.8-100.fc38.x86_64.conf -rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.9-100.fc38.x86_64.conf
Should I merge something ?
Yes, copy over the entry file that is the grub menu items you are missing. So long as you do not delete anything this should be safe to do. Then reboot test the entries.
Barry
On Tue, 4 Jun 2024 14:11:22 +0200, Patrick Dupre via users wrote:
On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 0ab8c5a6-a344-48f8-afca-e6187c589cde else search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-e6187c589cde
search --no-floppy --fs-uuid --set=boot --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 8131-80F4 else search --no-floppy --fs-uuid --set=boot 8131-80F4
What partitions do these two UUIDs refer to? You can run e.g. blkid -U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find out. Or run "blkid" and skim over the output.
This is sda4 where Fedora 38 is installed (sda4)
There are two entries! What about the second entry with UUID 8131-80F4?
On Tue, 4 Jun 2024 14:11:22 +0200, Patrick Dupre via users wrote:
On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 0ab8c5a6-a344-48f8-afca-e6187c589cde else search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-e6187c589cde
search --no-floppy --fs-uuid --set=boot --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 8131-80F4 else search --no-floppy --fs-uuid --set=boot 8131-80F4
What partitions do these two UUIDs refer to? You can run e.g. blkid -U "0ab8c5a6-a344-48f8-afca-e6187c589cde" to find out. Or run "blkid" and skim over the output.
This is sda4 where Fedora 38 is installed (sda4)
There are two entries! What about the second entry with UUID 8131-80F4?
I guess that when I run grub2-mkconfig there was a UBS key what connected on the usb poer.
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) version 6.8.11-300.fc40.x86_64 linux /boot/vmlinuz-6.8.11-300.fc40.x86_64 initrd /boot/initramfs-6.8.11-300.fc40.x86_64.img options root=UUID=da1fb213-c138-4711-aba2-76a598506283 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=fr-latin9 rd.luks=0 LANG=en_US.UTF-8 grub_users $grub_users grub_arg --unrestricted grub_class fedora
which seems fine
Now, grub loader offers me to boot on Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) I checked the command, but I get ..... error file vmlinuz-6.8.11-300.fc40.x86_64 not found
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
I also tried to replace the UUID by /dev/sdc3, but same result
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) version 6.8.11-300.fc40.x86_64 linux /boot/vmlinuz-6.8.11-300.fc40.x86_64 initrd /boot/initramfs-6.8.11-300.fc40.x86_64.img options root=UUID=da1fb213-c138-4711-aba2-76a598506283 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=fr-latin9 rd.luks=0 LANG=en_US.UTF-8 grub_users $grub_users grub_arg --unrestricted grub_class fedora
which seems fine
Now, grub loader offers me to boot on Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) I checked the command, but I get ..... error file vmlinuz-6.8.11-300.fc40.x86_64 not found
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
I also tried to replace the UUID by /dev/sdc3, but same result
/boot is a different partition for each install, so it won't be able to find the files for the other install. Multiple installations like this are a bad idea unless you really know what you're doing.
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) version 6.8.11-300.fc40.x86_64 linux /boot/vmlinuz-6.8.11-300.fc40.x86_64 initrd /boot/initramfs-6.8.11-300.fc40.x86_64.img options root=UUID=da1fb213-c138-4711-aba2-76a598506283 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=fr-latin9 rd.luks=0 LANG=en_US.UTF-8 grub_users $grub_users grub_arg --unrestricted grub_class fedora
which seems fine
Now, grub loader offers me to boot on Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) I checked the command, but I get ..... error file vmlinuz-6.8.11-300.fc40.x86_64 not found
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
I also tried to replace the UUID by /dev/sdc3, but same result
/boot is a different partition for each install, so it won't be able to find the files for the other install. Multiple installations like this are a bad idea unless you really know what you're doing.
That I do not understand There is a /boot on sdc3 with the right files.
Anyway, what else do you suggest?
I am maintaining this machine for numerous years, it always passed the updates, but from 38 to 40, the same approach fails!
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 6/4/24 1:39 PM, Patrick Dupre via users wrote:
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) version 6.8.11-300.fc40.x86_64 linux /boot/vmlinuz-6.8.11-300.fc40.x86_64 initrd /boot/initramfs-6.8.11-300.fc40.x86_64.img options root=UUID=da1fb213-c138-4711-aba2-76a598506283 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=fr-latin9 rd.luks=0 LANG=en_US.UTF-8 grub_users $grub_users grub_arg --unrestricted grub_class fedora
which seems fine
Now, grub loader offers me to boot on Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) I checked the command, but I get ..... error file vmlinuz-6.8.11-300.fc40.x86_64 not found
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
I also tried to replace the UUID by /dev/sdc3, but same result
/boot is a different partition for each install, so it won't be able to find the files for the other install. Multiple installations like this are a bad idea unless you really know what you're doing.
That I do not understand There is a /boot on sdc3 with the right files.
Anyway, what else do you suggest?
I am maintaining this machine for numerous years, it always passed the updates, but from 38 to 40, the same approach fails!
You haven't given a full explanation of your disk layout, so I'll have to make some assumptions. It appears you have 3 disks, and it's not clear what's on each one. However, the F40 install seems to be on sdc and I assume there's a /boot partition on that disk. The F38 install (on sda?) will have its own /boot partition which doesn't contain the F40 boot files, so it won't work. I don't know how this setup has ever worked.
Is there an EFI partition on sdc? If not, I suggest you create one with the Fedora boot files and add an EFI boot entry to boot from that. Then you can keep your installs completely separate and you won't have this issue.
On 6/4/24 1:39 PM, Patrick Dupre via users wrote:
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) version 6.8.11-300.fc40.x86_64 linux /boot/vmlinuz-6.8.11-300.fc40.x86_64 initrd /boot/initramfs-6.8.11-300.fc40.x86_64.img options root=UUID=da1fb213-c138-4711-aba2-76a598506283 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=fr-latin9 rd.luks=0 LANG=en_US.UTF-8 grub_users $grub_users grub_arg --unrestricted grub_class fedora
which seems fine
Now, grub loader offers me to boot on Fedora Linux (6.8.11-300.fc40.x86_64) 40 (Forty) I checked the command, but I get ..... error file vmlinuz-6.8.11-300.fc40.x86_64 not found
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
I also tried to replace the UUID by /dev/sdc3, but same result
/boot is a different partition for each install, so it won't be able to find the files for the other install. Multiple installations like this are a bad idea unless you really know what you're doing.
That I do not understand There is a /boot on sdc3 with the right files.
Anyway, what else do you suggest?
I am maintaining this machine for numerous years, it always passed the updates, but from 38 to 40, the same approach fails!
You haven't given a full explanation of your disk layout, so I'll have to make some assumptions. It appears you have 3 disks, and it's not clear what's on each one. However, the F40 install seems to be on sdc and I assume there's a /boot partition on that disk. The F38 install (on sda?) will have its own /boot partition which doesn't contain the F40 boot files, so it won't work.
This is correct, the disk sdb can be ignored for now.
I don't know how this setup has ever
worked.
This configuration was woring with F38 instead F40 (i.e., before the update). It is now 10 years that the machine is configured that way
Is there an EFI partition on sdc?
Yes ls /mnt/fedora40/boot/efi/EFI/fedora/grub* -rw-------. 1 root root 19363 Jun 2 11:12 /mnt/linux/boot/efi/EFI/fedora/grub.cfg -rw-------. 1 root root 7480 Jul 9 2022 /mnt/linux/boot/efi/EFI/fedora/grub_sdc3.cfg
If not, I suggest you create one with
the Fedora boot files and add an EFI boot entry to boot from that. Then you can keep your installs completely separate and you won't have this issue.
there is a
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Samuel Sieb composed on 2024-06-04 13:49 (UTC-0700):
Patrick Dupre via users wrote:
I am maintaining this machine for numerous years, it always passed the updates, but from 38 to 40, the same approach fails!
You haven't given a full explanation of your disk layout,
If you provide complete output from fdisk -l and/or parted -l, you might arouse interest in more potential or better help.
Disklabel type: gpt Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
Device Start End Sectors Size Type /dev/sda1 2048 6143 4096 2M BIOS boot /dev/sda2 6144 33560575 33554432 16G Linux swap /dev/sda3 33560576 34584575 1024000 500M EFI System /dev/sda4 34584576 181090303 146505728 69.9G Linux filesystem /dev/sda5 181090304 183187455 2097152 1G Linux filesystem /dev/sda6 183187456 184211455 1024000 500M Linux filesystem /dev/sda7 184211456 361486335 177274880 84.5G Linux LVM /dev/sda8 361486336 487315455 125829120 60G Linux filesystem /dev/sda9 487315456 507795455 20480000 9.8G Linux filesystem /dev/sda10 507795456 753555455 245760000 117.2G Linux filesystem
Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10EZEX-22M Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xd80d78e3
Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 167774207 167772160 80G 83 Linux /dev/sdb4 167774208 1953525167 1785750960 851.5G 5 Extended /dev/sdb5 167776256 251662335 83886080 40G 8e Linux LVM /dev/sdb6 251664384 335550463 83886080 40G 8e Linux LVM /dev/sdb7 335552512 533061631 197509120 94.2G 83 Linux /dev/sdb8 533063680 779233279 246169600 117.4G 83 Linux /dev/sdb9 779235328 820195327 40960000 19.5G 83 Linux /dev/sdb10 820197376 943077375 122880000 58.6G 83 Linux /dev/sdb11 943079424 1097168895 154089472 73.5G 83 Linux /dev/sdb12 1097170944 1098194943 1024000 500M 83 Linux
Disk /dev/sdc: 76.34 GiB, 81964302336 bytes, 160086528 sectors Disk model: Maxtor 6Y080M0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x9c5fbcd8
Device Boot Start End Sectors Size Id Type /dev/sdc2 * 2048 917503 915456 447M 83 Linux /dev/sdc3 917504 49598463 48680960 23.2G 83 Linux /dev/sdc4 49598464 160086527 110488064 52.7G 5 Extended /dev/sdc5 49600512 160086527 110486016 52.7G 83 Linux
Model: ATA WDC WDS480G2G0A- (scsi) Disk /dev/sda: 480GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:
Number Start End Size File system Name Flags 1 1049kB 3146kB 2097kB BIOS boot partition bios_grub 2 3146kB 17.2GB 17.2GB linux-swap(v1) swap 3 17.2GB 17.7GB 524MB fat16 EFI System Partition boot, esp 4 17.7GB 92.7GB 75.0GB ext4 Linux filesystem 5 92.7GB 93.8GB 1074MB ext4 Linux filesystem 6 93.8GB 94.3GB 524MB ext4 Linux filesystem 7 94.3GB 185GB 90.8GB Linux LVM lvm 8 185GB 250GB 64.4GB ext4 Linux filesystem 9 250GB 260GB 10.5GB ext4 usr_local 10 260GB 386GB 126GB ext4
Model: ATA WDC WD10EZEX-22M (scsi) Disk /dev/sdb: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags 1 1049kB 85.9GB 85.9GB primary ext4 4 85.9GB 1000GB 914GB extended 5 85.9GB 129GB 42.9GB logical lvm 6 129GB 172GB 42.9GB logical lvm 7 172GB 273GB 101GB logical ext4 8 273GB 399GB 126GB logical ext4 9 399GB 420GB 21.0GB logical ext4 10 420GB 483GB 62.9GB logical ext4 11 483GB 562GB 78.9GB logical ext3 12 562GB 562GB 524MB logical ext2
Model: ATA Maxtor 6Y080M0 (scsi) Disk /dev/sdc: 82.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags 2 1049kB 470MB 469MB primary ext4 boot 3 470MB 25.4GB 24.9GB primary ext4 4 25.4GB 82.0GB 56.6GB extended 5 25.4GB 82.0GB 56.6GB logical ext4
Samuel Sieb composed on 2024-06-04 13:49 (UTC-0700):
Patrick Dupre via users wrote:
I am maintaining this machine for numerous years, it always passed the updates, but from 38 to 40, the same approach fails!
You haven't given a full explanation of your disk layout,
If you provide complete output from fdisk -l and/or parted -l, you might arouse interest in more potential or better help. -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 6/4/24 2:57 PM, Patrick Dupre via users wrote:
Model: ATA Maxtor 6Y080M0 (scsi) Disk /dev/sdc: 82.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags 2 1049kB 470MB 469MB primary ext4 boot 3 470MB 25.4GB 24.9GB primary ext4 4 25.4GB 82.0GB 56.6GB extended 5 25.4GB 82.0GB 56.6GB logical ext4
You don't have an EFI partition on this disk. It's not even a GPT partition table. So both installations will be fighting over the EFI partition on sda. And there's no easy way to add a boot entry for this installation.
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700):
You don't have an EFI partition on this disk. It's not even a GPT > partition table. So both installations will be fighting over the EFI > partition on sda. And there's no easy way to add a boot entry for this > installation.
A multiboot GNU/Linux PC needs only one bootloader. Maybe OP's configuration can be improved through some additional information: https://forums.opensuse.org/t/how-to-have-a-custom-uefi-grub-menu-for-a-multiboot-system/133541
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700):
You don't have an EFI partition on this disk. It's not even a GPT partition table. So both installations will be fighting over the EFI partition on sda. And there's no easy way to add a boot entry for this installation.
A multiboot GNU/Linux PC needs only one bootloader. Maybe OP's configuration can be improved through some additional information: https://forums.opensuse.org/t/how-to-have-a-custom-uefi-grub-menu-for-a-multiboot-system/133541
Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200):
Disklabel type: gpt Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
Device Start End Sectors Size Type /dev/sda1 2048 6143 4096 2M BIOS boot /dev/sda2 6144 33560575 33554432 16G Linux swap /dev/sda3 33560576 34584575 1024000 500M EFI System
This sda3 is the only ESP among your 3 disks. In general, having only one ESP is perfectly fine on a GNU/Linux computer, if:
1-all installations were done in legacy/BIOS mode, and none use the ESP, or 2-all installations were done in UEFI mode, and all use it, unless more than one installation is of the same distro, in which case /etc/default/grub needs its GRUB_DISTRIBUTOR= made unique on /at least/ all-1 of the matching distros. This could become Patrick Dupre, and probably should. 3-kernels are not installed on ESP. This is OK in principle, but only if ESP is large enough to fit the expected number of kernels. In traditional UEFI installations, the ESP is not used for keeping kernels or initrds. 500M is more than adequate if no kernels are kept there, but not if multiple kernels for each Fedora release are kept there.
If on Patrick's system more than one installation was done in UEFI mode, then the UEFI installations' bootloaders will be a case of last one probably wins, usurping each other at every upgrade. The result is similar to reinstalling Windows, where Window bootloader replaces GRUB code in MBR with its own to break Linux booting. The most recently installed Fedora bootloader will be the one whose ESP entry in /boot/efi/EFI/fedora/ is in control of UEFI booting.
Please boot in UEFI mode, then gather and provide here output from: A-efibootmgr -v", and B-tree /boot/efi"
Also report for each of the 3 installations: a-value of GRUB_DISTRIBUTOR= in /etc/default/grub b-content of /etc/fstab c-input/output of lsblk -f
Thank for all these comments
Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200):
Disklabel type: gpt Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
Device Start End Sectors Size Type /dev/sda1 2048 6143 4096 2M BIOS boot /dev/sda2 6144 33560575 33554432 16G Linux swap /dev/sda3 33560576 34584575 1024000 500M EFI System
This sda3 is the only ESP among your 3 disks. In general, having only one ESP is perfectly fine on a GNU/Linux computer, if:
1-all installations were done in legacy/BIOS mode, and none use the ESP, or 2-all installations were done in UEFI mode, and all use it, unless more than one installation is of the same distro, in which case /etc/default/grub needs its GRUB_DISTRIBUTOR= made unique on /at least/ all-1 of the matching distros. This could become Patrick Dupre, and probably should. 3-kernels are not installed on ESP. This is OK in principle, but only if ESP is large enough to fit the expected number of kernels. In traditional UEFI installations, the ESP is not used for keeping kernels or initrds. 500M is more than adequate if no kernels are kept there, but not if multiple kernels for each Fedora release are kept there.
If on Patrick's system more than one installation was done in UEFI mode, then the UEFI installations' bootloaders will be a case of last one probably wins, usurping each other at every upgrade. The result is similar to reinstalling Windows, where Window bootloader replaces GRUB code in MBR with its own to break Linux booting. The most recently installed Fedora bootloader will be the one whose ESP entry in /boot/efi/EFI/fedora/ is in control of UEFI booting.
Please boot in UEFI mode, then gather and provide here output from:
OK, I see By default, I was not using UEFI to boot. It means that I used on the MBR if I understand correctly. But because I did not make a grub2-install /dev/sda (not possible in F40!) It has never been update (as I used to do). Now, booting by using UEFI and choosing the disk sda, I get the menu with F40 (on sdc) and it boots properly.
Please correct me if I am not wrong.
Sorry for all this mail exchanges for a simple thing. Any release brings is own surprise. It may be not finished. We will see.
Thank to every body.
A-efibootmgr -v", and B-tree /boot/efi"
Also report for each of the 3 installations: a-value of GRUB_DISTRIBUTOR= in /etc/default/grub b-content of /etc/fstab c-input/output of lsblk -f -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, 2024-06-05 at 13:37 +0200, Patrick Dupre via users wrote:
Sorry for all this mail exchanges for a simple thing.
Multi-boot isn't a simple thing, there's a lot of hurdles. If you needed to ask, you needed to ask. That's what the list is for.
Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200):
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
If everything was really OK, there would also be a vmlinu* there as well. https://bugzilla.redhat.com/show_bug.cgi?id=2119907
Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200):
I do not understand, because every thing seems OK The file is at the right place as well as System.map-6.8.11-300.fc40.x86_64 initramfs-6.8.11-300.fc40.x86_64.img config-6.8.11-300.fc40.x86_64 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
If everything was really OK, there would also be a vmlinu* there as well.
Of course there is vmlinuz-6.8.11-300.fc40.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=2119907
Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Tue, 4 Jun 2024 22:15:33 +0200, Patrick Dupre via users wrote:
I guess that when I run grub2-mkconfig there was a UBS key what connected on the usb poer.
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
Oh no! Messing up the installation isn't helpful. I've assumed you only wanted to analyze the grub.cfg file, since grub2-mkconfig clearly found a Fedora 40 installation. If not via os-prober (you can run that yourself, btw, to verify), then via the 10_linux section.
Anyway,... the exact scenario still isn't clear to me. It's an upgrade of F38 to F40, but why did you want to run grub2-mkconfig yourself?
And you run grub2-mkconfig with F38, but it doesn't create a working config file? What happens to the boot menu afterwards?
On Tue, 4 Jun 2024 22:15:33 +0200, Patrick Dupre via users wrote:
I guess that when I run grub2-mkconfig there was a UBS key what connected on the usb poer.
I made some progresses, but not enough I mounted the Fedora 40 / and cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
Oh no! Messing up the installation isn't helpful. I've assumed you only wanted to analyze the grub.cfg file, since grub2-mkconfig clearly found a Fedora 40 installation. If not via os-prober (you can run that yourself, btw, to verify), then via the 10_linux section.
Anyway,... the exact scenario still isn't clear to me. It's an upgrade of F38 to F40, but why did you want to run grub2-mkconfig yourself?
Because, the grub boot did not show the updated installation (F40)
And you run grub2-mkconfig with F38, but it doesn't create a working config file? What happens to the boot menu afterwards?
I can run grub2-mkconfig from both. In the grub.cfg from F38, Fedora 40 is missing but the grub.cfg from F40 may be OK. Hence, I can 1) replace grub.cfg from F38 by that of F40 2) Edit grub.cfg from F38 by adding a correct insert (DO NOT EDIT THIS FILE) 3) Edit /etc/grub.d/40_custom by adding a similar sequence
But I guess that it will do something similar to /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.11-300.fc40.x86_64.conf
Samuel S said
Number Start End Size Type File system Flags 2 1049kB 470MB 469MB primary ext4 boot 3 470MB 25.4GB 24.9GB primary ext4 4 25.4GB 82.0GB 56.6GB extended 5 25.4GB 82.0GB 56.6GB logical ext4
You don't have an EFI partition on this disk. It's not even a GPT partition table. So both installations will be fighting over the EFI partition on sda. And there's no easy way to add a boot entry for this installation.
1) I guess that gpt is not need by a small disk, 2) I can manage this disk partition, adding an efi partition (or other) if necessary.
I am waiting recommendation, and I will do the changes.
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 6/5/24 1:04 AM, Patrick Dupre via users wrote:
Samuel S said
Number Start End Size Type File system Flags 2 1049kB 470MB 469MB primary ext4 boot 3 470MB 25.4GB 24.9GB primary ext4 4 25.4GB 82.0GB 56.6GB extended 5 25.4GB 82.0GB 56.6GB logical ext4
You don't have an EFI partition on this disk. It's not even a GPT partition table. So both installations will be fighting over the EFI partition on sda. And there's no easy way to add a boot entry for this installation.
- I guess that gpt is not need by a small disk,
It has nothing to do with that.
- I can manage this disk partition,
adding an efi partition (or other) if necessary.
You can't. It's only for gpt.
I am waiting recommendation, and I will do the changes.
On 6/5/24 1:04 AM, Patrick Dupre via users wrote:
Samuel S said
Number Start End Size Type File system Flags 2 1049kB 470MB 469MB primary ext4 boot 3 470MB 25.4GB 24.9GB primary ext4 4 25.4GB 82.0GB 56.6GB extended 5 25.4GB 82.0GB 56.6GB logical ext4
You don't have an EFI partition on this disk. It's not even a GPT partition table. So both installations will be fighting over the EFI partition on sda. And there's no easy way to add a boot entry for this installation.
- I guess that gpt is not need by a small disk,
It has nothing to do with that.
I do not understand, Thisinstallation has been working during 10 years. Why I have now switch to gpt?
- I can manage this disk partition,
adding an efi partition (or other) if necessary.
You can't. It's only for gpt.
Anyway, tell me exactly how I should partition (with a minimum partition number) this disk or another one to keep this installation running properly?
I am waiting recommendation, and I will do the changes.
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-
Barry -
Barry Scott
-
Felix Miata -
Michael Schwendt -
Patrick Dupre -
Samuel Sieb -
Tim