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