> On Tue, 6 Jun 2017 20:18:31 +0200, Markus Wigge said:
> to update this old thread while stretch is knocking on the door I found
> out that the "device.map" is making the trouble for me.
I found out, that device.map is not needed any more in grub 2.00. From
the NEWS file:
* grub-mkd
> On Tue, 6 Jun 2017 20:18:31 +0200, Markus Wigge said:
> Unfortunately something different happens as well for "grub-install".
> Only fixing the grub.conf does not result in a bootable system. I also
> have to run "grub-install /dev/sda" again for the system disk.
Sure, you need
Hi Thomas,
to update this old thread while stretch is knocking on the door I found
out that the "device.map" is making the trouble for me.
Attached you find a diff of two grub.cfg files one was created with a
"device.map" present (the ".broken" one) and the other without.
Unfortunately something
> On Wed, 10 Aug 2016 18:33:31 +0200, Markus Wigge said:
> I'm trying to install a stretch VM with more or less the same settings I
> have for jessie (same config directory).
You say, that this disk_config works on jessie but not on stretch?
> #disk_config:
>> disk_config dis
Hi Thomas,
shouldn't grub be installed in the mbr of the used harddrives (e.g. /dev/sda
and /dev/sdb) of the lvm, if / is on lvm-volumes?
IMHO the grub.cfg etc should be in /boot/grub (so no problem while /boot has
its own partition - /boot inside the lvm-Volume might be inaccessable for grub)
I can confirm this problem on jessie (did not tested stretch yet).
Before trying to fix it for stretch, I like to understand what should
happen, and why the GRUB_PC/10-setup script does not work in this
situation.
In my test BOOT_DEVICE was aslso set to /dev/vg1/root and
BOOT_PARTITION was not set
