The "drakboot" program crashed. Drakbug-17.88 caught it. Trying to set up boot system. I have three OSs installed: Mageia, Antergos, KaOS. grub2-install failed: Installing for i386-pc platform. grub2-install: error: install device isn't specified. ...propagated at /usr/lib/libDrakX/any.pm line 269. ...propagated at /usr/libexec/drakboot line 49. Perl's trace: drakbug::bug_handler() called from /usr/libexec/drakboot:49 Theme name: Adwaita Kernel version = 4.9.28-desktop-1.mga6 Distribution=Mageia release 6 (Official) for x86_64 CPU=Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
Duplicate to #21583 *** This bug has been marked as a duplicate of bug 21583 ***
Status: NEW => RESOLVEDCC: (none) => yullawResolution: (none) => DUPLICATE
(In reply to Martin Volf from comment #1) > Duplicate to #21583 > > *** This bug has been marked as a duplicate of bug 21583 *** At first sight they look the same, and maybe they'll turn out to be the same bug in the end, but for now that bug is about failure to install on a x86_64-efi platform and this one about failing to install on a 32bit legacy system. @ Steve Please attach log.txt that is the result of running, as root: journalctl -a --since="2017-08-19 20:00" --until="2017-08-20 08:00" > log.txt *adjust* date and time in that commant, so that you get the logs from right before you started to set up the boot system until right after the crash.
Keywords: (none) => NEEDINFOCC: (none) => mageiatools, marja11, zen25000Summary: drakboot crashed => drakboot crashed (grub2-install failed: Installing for i386-pc platform. grub2-install: error: install device isn't specified.)Resolution: DUPLICATE => (none)Status: RESOLVED => REOPENED
s/commant/command/
(In reply to Marja van Waes from comment #2) > > @ Steve > > Please attach log.txt that is the result of running, as root: > > journalctl -a --since="2017-08-19 20:00" --until="2017-08-20 08:00" > > log.txt > > *adjust* date and time in that command, so that you get the logs from right > before you started to set up the boot system until right after the crash. Can you please attach that file, Steve?
Since there are insufficient details provided in this report for us to investigate the issue further, and 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 their 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.
Status: REOPENED => RESOLVEDResolution: (none) => OLD