On 04/20/2017 05:43 PM, Dave Smith wrote:
This is a first for me. I am running a dual boot machine. Leap 42.2 and Windows 10 Pro, each on their own SSD.
BE CAREFUL!!! I have the exact same setup (except I have Leap 42.2 on a 1T WD Black drive). Keep windows on windows alone and Leap on it's own disk alone. If you boot via MBR, there is a very real risk, every kernel and grub update will overwrite the MBR on your Win10 drive installing grub and a menu-entry to chain-load windows instead of only updating the MBR on your Leap disk. This drives me crazy. Even explicitly configuring grub install in /etc/default/grub and specifying the disk/by-UUID for the drive, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/disk/by-uuid/3cadab5b-13b4-4dce-84d3-05e2070f741c splash=silent quiet showopts" is not enough to prevent grub on openSuSE for trouncing the MBR on your windows drive due to the way openSuSE uses OS_PROBER to locate all drives and write a boot record there as it attempts to determine how to load the OS on whatever disk it finds. You can set the option in the same file: GRUB_DISABLE_OS_PROBER="true" Even with the uuid for the boot drive specified and OS_Prober diabled, openSuSE still overwites the Win10 MBR. So the word is "caution"... To prevent this unwanted behavior which forces me to have to recovery the windows boot record, etc.., I now add a 'lock' to grub to prevent any reinstall or update, and as an extra precaution, I though an Arch drive in the normal windows drive bay for `grub` updates. This may be overkill, but Linux now never touches my Win10 drive and Win10 never touches my Leap drive -- and that is the way it should be to begin with. There is a lot more info on this in my 2 prior threads on the subject within the last 4-5 months. Good luck with your dual-boot setup. I have the dual-boot there, but I also virtualize Win7 on Leap via Virtualbox. It is far easier to simply start windows as a Linux guest OS eliminating all boots required. I'll still start the Win10 install every couple of weeks and let it update, primarily so it is ready for use when I need it without having to wait though a 50 min. update when booting into it for the first time in a couple of weeks... -- 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