I believe the lvm module for grub is not robust enough to safely handle
these types of installations, especially without a partition table. LVM
uses the second 512byte sector to store its pvlabel (by default). In an
MBR environment, this would area would be used for grub2's core.img
data. Im not sure what happens to the core.img in a partitionless
environment, but I suspect it does the same thing.
I attempted to get a similar environment running, but gave up after
hitting the same road blocks you are.
Jack Waterworth, Red Hat Certified Architect
OpenStack Technical Support North America
Red Hat Global Support Services ( 1.888.467.3342 )
On 02/15/2015 05:44 AM, Andrei Borzenkov wrote:
В Sat, 14 Feb 2015 22:35:30 -0500
Dylan Taft <[email protected]> пишет:
Before I go crazy with this,
http://lists.gnu.org/archive/html/grub-devel/2013-09/msg00113.html
this patch would also probably solve the issue. Is support for
something like that already upstream? LVM can leave enough space for
grub to use for the complete boot loader with bootloaderareasize and
that completely avoids the headache with block maps.
As you could see, this specific patch was rejected by grub maintainer,
unfortunately nothing followed it.
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
