The "draklive-install" program crashed. Drakbug-16.104 caught it. I had just created the root password grub2-install failed: Installing for i386-pc platform. grub2-install: error: unable to identify a filesystem in hostdisk//dev/sdb; safety check can't be performed. ...propagated at /usr/lib/libDrakX/any.pm line 268. Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/any.pm:268 any::installBootloader() called from /usr/lib/libDrakX/any.pm:238 any::setupBootloaderUntilInstalled() called from /usr/sbin/draklive-install:332 main::setup_bootloader() called from /usr/sbin/draklive-install:70 main::install_live() called from /usr/sbin/draklive-install:42 Theme name: oxygen-gtk Kernel version = 3.19.8-desktop-3.mga5 Distribution=Mageia release 5 (Official) for x86_64 CPU=Intel(R) Pentium(R) CPU G4400 @ 3.30GHz
CC: (none) => thierry.vignaud, zen25000Summary: draklive-install crashed => draklive-install crashed ("grub2-install: error: unable to identify a filesystem in hostdisk//dev/sdb; safety check can't be performed")Source RPM: draklive-install-2.6-1.mga5 => draklive-install-2.6-1.mga5, grub2
Please attach the output of: su fdisk -l from a terminal running in the LIVE system running on your hardware. Use the "Add an attachment" option above comment 1.
Assigning to Barry (unofficial grub2 maintainer) and CC'ing Mageia tools group (for draklive-install)
CC: (none) => mageiatools, marja11Assignee: bugsquad => zen25000
Keywords: (none) => NEEDINFO
Note to self: Is this LVM? https://bbs.archlinux.org/viewtopic.php?id=153900
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Created attachment 8476 [details] Outout of fdisk -l This may no longer be valid as I've removed the two legacy HDDs that I moved from my old system.
OK, so we now don't know which drive was involved as assignments will have changed when the drives were removed. I will close this as invalid as we can't really investigate further. If you do replicate this in future please feel free to reopen this bug report.
Status: NEW => RESOLVEDResolution: (none) => INVALID