Bug 12343 - installer should suggest grub2 if /boot is on lvm
Summary: installer should suggest grub2 if /boot is on lvm
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: 4errata
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-01-17 19:10 CET by Manuel Hiebel
Modified: 2016-06-17 12:36 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Manuel Hiebel 2014-01-17 19:10:59 CET
Description of problem:


An OS with the /boot partition in a lvm will not work with grub. It works fine with grub2. So it should be suggest if it's the case.

(if / is in lvm and /boot not it works with grub)

Maybe we can check at http://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n583 if partition /boot has tag "isLVM" (from fs/type.pm) 

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-01-20 19:04:19 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=12362
Whiteboard: (none) => 4errata

Comment 1 Marja Van Waes 2016-04-26 12:02:01 CEST
This bug report hasn't seen any action since before Mga4 release. Is it still valid in current cauldron (or, for traditional installer: with the 6dev1 snapshot, or for live isos with Mga5)?

Keywords: (none) => NEEDINFO

Comment 2 Thierry Vignaud 2016-04-29 15:08:31 CEST
Well, the accepted standard is to split /boot on a non LVM partition.
That what does every distro.

For the record, the initial suggestion was about then:
http://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm?id=1fe2940bbaa1196b33684634b2b1f8172d61e954#n583

Which is now:
http://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm?id=cabf32daa05edf617be2325ba65899e3df0f7b2d#n661
Comment 3 Thierry Vignaud 2016-06-17 12:36:34 CEST
We default grub2 in mga6

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.