Comment # 4 on bug 1200717 from Michael Chang

If (In reply to Ulrich Windl from comment #3)
> (In reply to Michael Chang from comment #2)
> > Is it possible for you to try again
> > 
> >  update-bootloader --reinit
> > 
> > Reboot to see if the problem reproducible ? Would it be possible to attach
> > the grub.cfg when you see the problem ? Thanks.
> 
> I kind of simplified the procedure:
> 1) Save the current grub.cfg under a different name
> 2) run "update-bootloader --reinit"
> 3) diff old and new files
> 
> As there were no differences, I guess booting will succeed, unless there are
> some other effects. So I skipped trying boot.

The same update-bootloader call is used in rpm's %posttrans to update grub2. If
it cannot be reproduced again from console, then something fishy is in the
update environment to break the grub.cfg.

I also have setup 15.3 for test but couldn't reproduce as well.

> 
> The only thing that is special in my configuration is that the disk is
> encrypted and rootfs is on LV, thus:
> ryptomount -u ebdc168af0f1481bb6a54c5cdbafed95
> set
> root='lvmid/W0LKbn-AyLt-ErrA-sH5I-AEX3-Vhl4-qf2oMD/OcYEfE-eE8f-nmcq-Ivvp-
> KMa2-DvVM-G3Mi5U'

This is supported and should work.

I'd suggest to test a few more updates and come back with the broken grub.cfg
attached if that happens again.