Comment 1 for bug 23835

You did hit a set of bugs here:

lilo cannot understand correctly LVM2 metadata.
The hoary case at first install the kernel was probably (for sure i would say)
in a set of contiguos blocks that gave lilo
the possibility to read it.

lilo-installer did allow wrongly to install lilo with /boot on LVM2 device. lilo
has still several limitations reading from LVM1 and 2.

There are no known partition layouts changes between hoary and breezy kernels
(otherwise i won't be able to write right now ;)).

I assume that new version of lilo in breezy has a more strict controls of what
can do or not, and the command it issues to gather
some information from the device mapper, will consequently fail given that it
might issue the wrong request.

Colin, given that we have no control over lilo upstream, i suggest we fix
lilo-installer to handle this case properly and refuse
to install.

Fabio