Le 16/06/2019 à 01:45, Samuel Sieb a écrit :
On 6/15/19 2:23 PM, François Patte wrote:
> Everything was ok untill grubby replaced grub2-mkconfig: when there is a
> kernel update, grubby uses the disabled sda3-sda4 partitions as the /
> parttion in the /boot/grub2/grub.cfg file.
grubby has never replaced grub2-mkconfig. They are independent.
grub2-mkconfig is never run, except maybe on the initial install.
Upgrades up to F30 have always used grubby.
So what has changed in grubby? Because all my kernel updates went
correctly upto, say last december. After that grubby writes a wrong
grub.cfg file referring to a disabled device as the / partition of my
system. And, as I said in my previous mail, this deive no more exists.
> I have now destroyed these partitions but grubby still uses them and
> writes a faulty /boot/grub2/grub.cfg file.
>
> Where does it find that these partitions still exist?
grubby only copies the information from the previous kernel in the
grub.cfg file.
I would say that this is not right, here are the two first menu-entries
in my gub.cfg after the last kernel update:
<---------------------------------------------
menuentry 'Fedora (5.1.8-200.fc29.x86_64) 29 (Twenty Nine)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-5.0.19-200.fc29.x86_64-advanced-98c1a7d2-d497-44b1-b48d-78544fe08c79'
{
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid09
insmod ext2
set root='mduuid/eb8b5efe5a8f9369e940a0f383d63ad1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='mduuid/eb8b5efe5a8f9369e940a0f383d63ad1'
595e9373-6e40-425b-8041-07aca776a98b
else
search --no-floppy --fs-uuid --set=root
595e9373-6e40-425b-8041-07aca776a98b
fi
linux /vmlinuz-5.1.8-200.fc29.x86_64
root=/dev/mapper/fedora-racine ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1
rd.md.uuid=95c11201:1509169a:860a8b84:c49f865c
rd.lvm.lv=debian/deb-racine
rd.md.uuid=eb8b5efe:5a8f9369:e940a0f3:83d63ad1
rd.md.uuid=4a28174a:f38b4938:233f85f7:6ce585a8 rd.lvm.lv=systeme/swap
quiet LANG=fr_FR.UTF-8
initrd /initramfs-5.1.8-200.fc29.x86_64.img
}
menuentry 'Fedora (5.0.19-200.fc29.x86_64) 29 (Twenty Nine)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-5.0.19-200.fc29.x86_64-advanced-98c1a7d2-d497-44b1-b48d-78544fe08c79'
{
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid09
insmod ext2
set root='mduuid/eb8b5efe5a8f9369e940a0f383d63ad1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='mduuid/eb8b5efe5a8f9369e940a0f383d63ad1'
595e9373-6e40-425b-8041-07aca776a98b
else
search --no-floppy --fs-uuid --set=root
595e9373-6e40-425b-8041-07aca776a98b
fi
linux /vmlinuz-5.0.19-200.fc29.x86_64
root=/dev/mapper/debian-deb--racine ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1
rd.md.uuid=95c11201:1509169a:860a8b84:c49f865c
rd.lvm.lv=debian/deb-racine
rd.md.uuid=eb8b5efe:5a8f9369:e940a0f3:83d63ad1
rd.md.uuid=4a28174a:f38b4938:233f85f7:6ce585a8 rd.lvm.lv=systeme/swap quiet
initrd /initramfs-5.0.19-200.fc29.x86_64.img
}
<--------------------------------------
As you can see the root partition for kernel 5.1.8 is
root=/dev/mapper/fedora-racine while for kernel 5.0.19 it is:
root=/dev/mapper/debian-deb--racine
Running manualy grub2-mkconfig corrects this mistake.
Moreover /dev/mapper/fedora-racine does not exist:
ls -l /dev/mapper:
lrwxrwxrwx. 1 root root 7 16 juin 10:02 annexes-data -> ../dm-4
lrwxrwxrwx. 1 root root 7 16 juin 10:02 annexes-sauvegardes ->
../dm-5
crw-------. 1 root root 10, 236 16 juin 10:02 control
lrwxrwxrwx. 1 root root 7 16 juin 10:02 data-home -> ../dm-7
lrwxrwxrwx. 1 root root 7 16 juin 10:02 debian-deb--opt -> ../dm-6
lrwxrwxrwx. 1 root root 7 16 juin 10:02 debian-deb--racine -> ../dm-0
lrwxrwxrwx. 1 root root 7 16 juin 10:02 systeme-chiffre -> ../dm-3
lrwxrwxrwx. 1 root root 7 16 juin 10:02 systeme-swap -> ../dm-1
lrwxrwxrwx. 1 root root 7 16 juin 10:02 systeme-var -> ../dm-2
> I can't upgrade my system now because I fear that the boot config file
> will refer to a partition wich no longer exists on my system.
You don't mention which Fedora version you are using.
f29 and I want to upgrade to f30 using dnf system upgrade but I want to
solve this mystery before because I fear to get an unbootable system
after upgrade.
Starting with
F30, grub uses BLS by default
I don't know BLS is....
Thank you for any help.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte