http://bugzilla.opensuse.org/show_bug.cgi?id=1076779 http://bugzilla.opensuse.org/show_bug.cgi?id=1076779#c33 --- Comment #33 from Ludwig Nussel <lnussel@suse.com> --- This is a special case I think. Here YaST creates a chroot for the purpose of specially crafting an installation for the target system. So special measures may need to be taken. Anyways, another option would be to run the os-prober outside the chroot, ie within the installation environment and only inject it's findings into the target. Since /etc/grub.d/30_os-prober is quite expensive anyways, I'd favor removing that and converting it into some standalone script that can be called by e.g. YaST when needed rather than each bootloader update. Not sure if that is doable short term though :-) -- You are receiving this mail because: You are on the CC list for the bug.