Installer doesn't warn about unbootable config (/boot on LVM)

[mukesh agrawal]

Installed 5.04 in expert mode, with the LVM installer-module enabled.
Placed /boot on a logical volume, and installed. LILO failed to boot
the system (stuck at "Loading linux...............................").

I suspect the problem is that LILO (and probably GRUB as well)
doesn't support booting from a logical volume. If that's the case,
it would be nice to have the installer warn the user when he
attempts to put /boot on a logical volume.

[Colin Watson (cjwatson)]

As I remember, LILO with /boot on LVM worked fine the last time I tested it.
I'll try again ...

[towsonu2003 (towsonu2003)]

I guess this is a duplicate of bug # 29858 , where the reporter says
"Tried in vmware to do a clean install of dapper flight 3 and select "erase all my drives and use lvm" and it fails to boot."

Though this one was filed earlier, the other one is confirmed and marked as high importance.

[towsonu2003 (towsonu2003)]

leaving the decision to someone w/ more experience...

[Luke has no name (lukehasnoname)]

When installing using the 8.10 RC 64bit alternate disc:

I was able to assign my root (and thus /boot) partition to an LVM. This caused GRUB installation to fail, and LILO installation to take place. LILO couldn't boot into Ubuntu.

LOOOONG story short (I reinstalled Ubuntu several times and Vista once), I tried installing Fedora, which, when I tried to put my root partition on an LVM, warned that it was not possible to do so. I then realized what I had been doing wrong.

FIX: Either get GRUB to recognize bootable partitions on LVM (GRUB 2, right?) or have the installer warn when a user attempts to put their /boot on an LVM.

[Phillip Susi (psusi)]

This works these days thanks to grub2.