Created attachment 3627 [details] bootloader warning During installation, (testing: Mageia-3-beta3-x86_64-DVD.iso), an "ERROR" dialog is displayed if / is on an LVM partition, an no other /boot has been created. This used to be valid, as grub cannot read files from LVM volumes. However, grub2 supports this, so the error message should be changed, or ideally, not displayed at all. If not displaying it at all, then installer should defualt to using grub2 in this case, and display a warning if the user selects any other boot loader. See screenshot.
Blocks: (none) => 416
maybe only change the message ? (as bootloader choice is at the end so could be hard to manage)
Keywords: (none) => USABILITYVersion: 2 => CauldronAssignee: bugsquad => thierry.vignaud
Well, changing the message is something that hopefully could be done for Mageia 3. Doing something smarter, like picking the correct boot loader later on would be better, but might be a Mageia 4 thing.
File: fsedit.pm SVN path: svn://svn.mageia.org/svn/soft/drakx/trunk/perl-install Current SRC Line: 472 approx #- NB: if the LV doesn't exist, lv_nb_pvs returns 0 die N("You cannot use the LVM Logical Volume for mount point %s since it spans physical volumes", $mntpoint) if $mntpoint eq '/boot' && isLVM($part) && lvm::lv_nb_pvs($part) > 1; cdie N("You've selected the LVM Logical Volume as root (/). The bootloader is not able to handle this when the volume spans physical volumes. You should create a separate /boot partition first") if $mntpoint eq "/" && isLVM($part) && lvm::lv_nb_pvs($part) != 1 && !fs::get::has_mntpoint("/boot", $all_hds); The conditional on this seems really odd to me. I think it's a bug. lvm::lv_nb_pvs($part) seems checks the number of existing LVs. This number can be 0, but can also be larger. Problems exist are: if /boot is created on LVM, no warning about grub2 being needed If / is created on LVM before /boot, warning about the volume spanning physical volumes, even when it does not. No message if it's created after /boot
Further testing on this: Even with two different PV's, LV spanning both, a single / filesystem, installing with grub2 works fine.
Removing block on bug 416 as this is not release critical.
CC: (none) => zen25000Blocks: 416 => (none)
Adding block on bug 416 back since it allows to track all grub2-related issues.
There's several issues: - I don't think that would work w/o setting "GRUB_PRELOAD_MODULES=lvm" - grubenv cannot be used, so we couldn't offer anymore to choose the default entry - some special code would be needed for some cases such as encrypted LVM, ... that needs some options (setting GRUB_ENABLE_CRYPTODISK, ...) - I'm not sure grub2 can handle all LVM features (eg: a LVM using RAID features) I think the default of having a split /boot on a regular partition is sane. If you do want to have /boot on LVM, there's plenty of tutorials on internet that explain how to do so _after_ the install
See https://wiki.gentoo.org/wiki/LVM#Using_LVM_in_an_initramfs for an example of grub2 limitation regarding LVM
commit 1873a160a01f41474434865c66dd09ba5f733d13 Author: Thierry Vignaud <thierry.vignaud@...> Date: Mon Jul 4 17:55:50 2016 +0200 do not warn about no bootloader can boot LVM... ...as grub2 can (mga#9426) --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=1873a160a01f41474434865c66dd09ba5f733d13
Closing
Status: NEW => RESOLVEDResolution: (none) => FIXED