Pour continuer dans la curiosité:
[root@taran entries]# ls /boot/
5a68123777134e458e146023b9704f82 efi elf-memtest86+-5.01 extlinux grub2 initramfs-0-rescue-5a68123777134e458e146023b9704f82.img loader lost+found memtest86+-5.01 vmlinuz-0-rescue-5a68123777134e458e146023b9704f82
[root@taran entries]# rpm -ql kernel-core|grep boot
/boot/.vmlinuz-5.1.7-300.fc30.x86_64.hmac
/boot/System.map-5.1.7-300.fc30.x86_64
/boot/config-5.1.7-300.fc30.x86_64
/boot/initramfs-5.1.7-300.fc30.x86_64.img
/boot/vmlinuz-5.1.7-300.fc30.x86_64
/boot/.vmlinuz-5.1.8-300.fc30.x86_64.hmac
/boot/System.map-5.1.8-300.fc30.x86_64
/boot/config-5.1.8-300.fc30.x86_64
/boot/initramfs-5.1.8-300.fc30.x86_64.img
/boot/vmlinuz-5.1.8-300.fc30.x86_64
/boot/.vmlinuz-5.1.11-300.fc30.x86_64.hmac
/boot/System.map-5.1.11-300.fc30.x86_64
/boot/config-5.1.11-300.fc30.x86_64
/boot/initramfs-5.1.11-300.fc30.x86_64.img
/boot/vmlinuz-5.1.11-300.fc30.x86_64
/boot/.vmlinuz-5.1.12-300.fc30.x86_64.hmac
/boot/System.map-5.1.12-300.fc30.x86_64
/boot/config-5.1.12-300.fc30.x86_64
/boot/initramfs-5.1.12-300.fc30.x86_64.img
/boot/vmlinuz-5.1.12-300.fc30.x86_64
Pourtant rpm -qV kernel-core ne dit rien.
Sinon je ne pense pas que les entrées seront plus complètes au prochain boot, je n'ai rien fait.
ps: grubby comme dit sera vite déprécié avec bls:
[root@taran entries]# grubby --info /boot/vmlinuz-5.1.12-300.fc30.x86_64
The param /boot/vmlinuz-5.1.12-300.fc30.x86_64 is incorrect
[root@taran entries]# uname -a
Linux taran.in.noisy.linuxed.net 5.1.12-300.fc30.x86_64 #1 SMP Wed Jun 19 15:19:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@taran entries]#