All, This was somewhat disturbing. I have 2 drives in my laptop, win10 on /dev/sda and Leap 42.2 on /dev/sdb. I boot either by selecting the drive I want to boot with the quick select bios boot option (e.g. press F9, the select hd1, hd2 of network boot) A couple of days ago, there was an update to grub2, and whatever hook is in place forced a grub reinstall. The problem is that grub installed to /dev/sda (writing itself to my win10 drive, instead of writing itself to my opensuse drive). This was quite surprising when I next tried to boot win10. Thankfully, grub detected and set up a chain-load for win10, but the issue is -- why would it touch /dev/sda, when it was booted from and running on /dev/sdb. I was able to recover/remove grub from /dev/sda with a call to bootsect, but I want to prevent this from ever happening again. I suspect part of the problem was the original installation of grub2 by yast and the creation of the archaic /boot/grub2/device.map containing '(hd0) /dev/sda' during install. I have rewritten device.map to contain (hd1) /dev/sda (hd0) /dev/sdb What I need to know is "Are there any other hooks or defaults in the way opensuse calls `grub-install` following a grub2 update that would cause it to write to /dev/sda instead of the drive opensuse is running on?" (after that we can get to 'why in the heck did an update to grub require a grub-install on a working system to begin with?' there was no kernel update or any change that would warrant a reinstall of grub to the drive) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org