Comment # 5 on bug 1090524 from Josef Reidinger

OK, let me structure a bit answer:

1) to know why this non-existing device ended up in default/grub_installdevice
I need y2logs from installation time ( not sure if it is not already rotated
away ).

2) regarding existence of default/grub_installdevice . We using it and it is
useful to track where installation puts its stage1. If it use generic_mbr and
if we control boot flag or user do not want it for us. This file is really
important when there is a multiboot and user expect not so aggressive behavior
he configured during installation. Why we need to store it? Because when grub2
is upgraded, it can also upgrade stage1 ( not happen often ) and in such case
we need to know where we want to install that new upgraded stage1. And of
course to show current settings in yast2-bootloader.

What we can possible discuss is to skip this file for trivial simple cases like
single disk and install to MBR. And expect all related parts already know about
such decision.

3) this file is used only when grub2 needs stage1 location so non-EFI x86_64
and ppc. For other architectures we do not have it.

So I hope I explain why we need this file. To debug this issue with I need
y2logs. Cannot do much more without it.