Description of problem:
Following upgrade from Mageia 5 to Mageia 6, I tried to switch from grub to grub-2 via MCC (Configure system startup) and it failed with the following crash report :
Le programme « drakboot » a planté avec l'erreur suivante :
grub2-install failed: Installation pour la plate-forme i386-pc.
grub2-installÂ : attentionÂ : Le systÃ¨me de fichiers Â«Â fatÂ Â» ne prend pas en charge l'embarquage.
grub2-installÂ : attentionÂ : L'embarquage est impossible. GRUB ne peut Ãªtre installé sur cette configuration qu'en utilisant les listes de blocs. Cependant, les listes de blocs ne sont PAS fiables et leur utilisation est déconseillée..
grub2-installÂ : erreurÂ : refus de continuer avec les listes de blocs.
...propagated at /usr/lib/libDrakX/any.pm line 269.
...propagated at /usr/libexec/drakboot line 49.
drakbug::bug_handler() called from /usr/libexec/drakboot:49
Thème utilisé : Adwaita
Pour soumettre un rapport de bogue, cliquez sur le bouton Signaler.
Cela ouvrira une fenêtre de navigateur sur Bugzilla où vous trouverez un formulaire à remplir. L'information affichée ci-dessus sera transférée vers ce serveur
Il est très utile d'inclure dans votre rapport la sortie des commandes suivantes : « lspcidrake -v », « blkid ».
Vous devriez attacher les fichiers suivants : /etc/modprobe.conf, /etc/fstab, /boot/grub/menu.lst, /boot/grub/devices.map ainsi que /etc/lilo.conf.
Version-Release number of selected component (if applicable):
Always on my system. Don't know what part of it is relevant to the crash.
Steps to Reproduce:
1. On my system, Go to MCC, startup -> Configure system startup
2. Choose Grub 2 graphical mode option
5. The crash report appears after the wait window.
Thanks for the report, François.
This issue has already been reported before, but don't worry, your report helps to know how many users are affected by this issue.
*** This bug has been marked as a duplicate of bug 20023 ***
*** Bug 21726 has been marked as a duplicate of this bug. ***
The issue is that when one switches from grub-legacy to grub2 on a non UEFI system, the list of boot devices is filtered for generic bootloader needs by bootloader::allowed_boot_parts() but we don't know yet that the user will later switch to grub2
However grub2 has more restrictions... See:
But as the switch to grub2 is done _after_, we got bit...
We could add a later check: if grub2 has been selected, we could popup with an error message.
Aka rerunning bootloader::allowed_boot_parts() and making sure the choosen boot_device is part the new list.
Switch from grub to grub-2 fails =>
drakboot crashed when switching to GRUB2 (grub2-install: error: will not proceed with blocklists)Source RPM:
Does it still valid in mga7 and Cauldron?
This message is a reminder that Mageia 6 is end of life.
Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL) within 3 weeks from 2020-08-05.
Package Maintainer: If you wish for this bug to remain open because you plan to
fix it in a currently maintained version, simply change the 'version' to a later
Mageia version prior to Mageia 6's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.
Although we aim to fix as many bugs as possible during every release's lifetime,
sometimes those efforts are overtaken by events. Often a more recent Mageia
release includes newer upstream software that fixes bugs or makes them obsolete.
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as OLD.