On 06.02.2017 15:24, Dave Smith wrote:
Had to rebuild my work computer, first motherboard ever to go out on me. Replaced with an ASRock H97 Pro4 board with an i5 processor and 4G of ram. Using the graphics from the i5 since it is just a work machine. Have 2 hard drives attached, one for Leap 42.2 and one for Windows.
I reinstalled Windows 7 first and then Leap 42.2. All was good. I then upgraded Windows to version 10. I have just discovered I can no longer boot into Leap. I select Leap 42.2 from the grub boot menu and it begins the boot process. The system goes into emergency mode just after successfully mounting all the file systems. I didn't even know there was an emergency mode. Kind of nice actually. I reviewed the journal but could not see anything obvious that would be causing this. No messages indicating why.
Any ideas? Could the Windows 10 upgrade have played a role in this somehow. I have done a couple of other upgrades without issue. I have not done much past the basic install so my next step will be a reinstall of Leap if no one can offer any insight.
Hi, are you using UEFI or BIOS/Legacy to boot? Grub2, grub2-efi, with or without secure boot? Do you by any chance have entries in /etc/fstab that mount your windows partitions? If so, comment those out, windows 10 doesn't by default shut down the filesystems properly so you end up in emergency when you try to mount those. That being said: I have Windows 10 and Leap 42.2 on a ASrock Z97 Pro4 and I'm having all kind of fun with uefi secure boot. Basically I can't boot leap in secure boot because windows insists on wiping all keys off the efi partition, except for its own keys. Does not happen that way on my laptop or my work laptop, only on that desktop at home. Cheers MH -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org