Mounting the windows partition was the problem. I commented it out and I am back in. I will delete the entry in fstab and just manually mount it when I need to get in there. Thanks for all the help. On Mon, Feb 6, 2017 at 9:51 AM, Mathias Homann wrote:

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

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-02-06 20:04, Anthony Youngman wrote:

/dev/sda2 /mnt/C-drive ntfs nofail 0 0 /dev/sda3 /mnt/D-drive ntfs defaults 0 0

Note the "nofail". I had exactly the same problem as you - if Win7 suspended then SuSE wouldn't boot :-( I now don't have any problems, although I suspect (I haven't noticed) that a suspended Win7 C: doesn't mount.

That's correct, it will not mount, but will not stop the booting either.

Mounting is a pain in the neck if Windows or networking is involved :-(

Yep. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 02/06/2017 8:48 AM, Alec Destry wrote:

My experience has been is that dual boot has always been full of problems. Instead of dual boot, you might consider making Leap 42.2 the only OS for your computer, install VMWare Workstation Player 12.5 under Leap 42.2 and then put Windows 10 in a virtual machine under VMWare Workstation Player 12.5.

I concur. Dual boot issues are the biggest source of problems I notice regardless of Distro. (Followed closely by Nvidia issues). I might look into VirtualBox instead of Vmware Player. Gamers might look into Windows as the bare-metal operating system, because there are slight performance hits being in a virtual machine. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/06/2017 11:30 AM, Richmond wrote:

But then I have no secure boot, and only Vista and XP.

Well there you go then. ;-) I turn it off in my bios as well, but lots of people can't. But its not ONLY windows that causes problems or gets hozed. Any update from ANY OS puts all other dual-booted OSes at risk of needing a technician to recover the machine. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/02/17 19:51, jdd wrote:

Le 06/02/2017 à 20:46, John Andersen a écrit :

...

But its not ONLY windows that causes problems or gets hozed. Any update from ANY OS puts all other dual-booted OSes at risk of needing a technician to recover the machine.

not true in uefi where the firmware sets the primary boot, not the os

So you need a technician to run the update then? That or the upgrade fails because it can't update the uefi? My laptop is triple boot. It was a pain to set up because I thought I knew what I was doing, and I'm used to things like Slack and gentoo and lilo, where you are usually in control. And oddly enough, SuSE, doing it automagically, was the only one iirc to actually get it to work without grief. Oh grub2, how I hate you ... to bloody clever for your own good :-( Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 06/02/2017 à 21:07, Wols Lists a écrit :

On 06/02/17 19:51, jdd wrote:

...

Le 06/02/2017 à 20:46, John Andersen a écrit :

...

But its not ONLY windows that causes problems or gets hozed. Any update from ANY OS puts all other dual-booted OSes at risk of needing a technician to recover the machine.

not true in uefi where the firmware sets the primary boot, not the os

So you need a technician to run the update then?

That or the upgrade fails because it can't update the uefi?

if you setup a double boot, you may have some clues. UEFI if running first with windows have also GPT, so no MBR and any partition can hold grub. If your distro is not UEFI/GPT compliant, change distro, UEFI is pretty old now! The primary way to change default boot is UEFI, not OS. but UEFI *can* also manage Bois legacy, so you may have (as I do) a legacy windows/msdos and openSUSE UEFI, with some difficulties booting jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 06/02/2017 à 22:40, Anthony Youngman a écrit :

Leap 42.2? Gentoo? I'm sure *they're* UEFI compliant :-) Unfortunately, new computers cost a lot more than new distros,

UEFI is around 10 years old, now, so most old computer should be compliant now. the problem is -as expected- windows install not being made in uefi mode but in legacy mode, that keep all the old problems that UEFI fixes I was myself pretty upset when UEFI come -the main problem is interface is different in any computer! But it's worth learning jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 07/02/2017 à 13:52, Carlos E. R. a écrit :

I bought this computer on 2009-11, ie, less than 10 years ago. Certainly plain bios, no talk of UEFI at the time on PCs.

first was 2005 https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#History but of course not all computer use it jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 07/02/2017 à 14:12, Richmond a écrit :

four 32 bit computers, three of which have floppy disk drives.

less than 10 years old? I also have such computer :-) but these one not dualboot, only leap 42 jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I had the same issue with Leap 42.1 on an ASUS Ultrabook. The problem was that Windows 10 does not shut down "completely", so the filesystems are left in an intermediate step. I suspect that it has to do with some fast boot technology or the other. If you press the shift key while selecting shutdown on Windows 10, it will shut down completely and properly, and Leap should boot fine. Good luck!!! Pablo Dotro On 02/07/17 10:21, Patrick Shanahan wrote:

* Richmond [02-07-17 08:13]:

...

jdd wrote:

...

Le 06/02/2017 à 22:40, Anthony Youngman a écrit :

...

Leap 42.2? Gentoo? I'm sure *they're* UEFI compliant :-) Unfortunately, new computers cost a lot more than new distros, UEFI is around 10 years old, now, so most old computer should be compliant now.

Have you done a survey? I have three 64 bit computers without UEFI, and four 32 bit computers, three of which have floppy disk drives. my desktop is an intel i7 970 build in 2010 which has UEFI available but not being used.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 07/02/2017 à 16:13, nicholas a écrit :

i thought you can turn this behaviour off by switching off fast boot INSIDE windows (in addition to the bios option)?

what works everywhere (I guess) is to ask for *reboot* and switch off manually at the reboot - this prevent every kind of hibernation jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-02-07 16:20, Pablo M. Dotro wrote:

On 02/07/17 12:13, nicholas wrote:

...

i thought you can turn this behaviour off by switching off fast boot INSIDE windows (in addition to the bios option)?

That didn't work for me. I ended up with a post it note reminding me to keep shift pressed when shutting down Windows. Thankfully, I do not boot into Windows all that often.

I don't remember what I did, but my Windows 10 halts truly, filesystem closed properly. I just followed some advice on Internet, maybe here, but I don't remember what it was. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

Richmond composed on 2017-02-06 19:30 (UTC):

John Andersen wrote:

...

Alec Destry wrote:

...

...

My experience has been is that dual boot has always been full of problems. Instead of dual boot, you might consider making Leap 42.2 the only OS for your computer, install VMWare Workstation Player 12.5 under Leap 42.2 and then put Windows 10 in a virtual machine under VMWare Workstation Player 12.5.

...

I concur. Dual boot issues are the biggest source of problems I notice regardless of Distro. (Followed closely by Nvidia issues). I might look into VirtualBox instead of Vmware Player.

...

Gamers might look into Windows as the bare-metal operating system, because there are slight performance hits being in a virtual machine.

Well, dual boot /with windows/ maybe. But read between the lines, /Windows/ has always been a problem screwing up boot sectors.

Windows "screws up" boot sectors only after a GNU installer or updater has "screwed up" boot sectors by replacing generic boot code with proprietary boot code. If GNU OSes were installing agnostically (OS neutral) by default, Windows wouldn't be doing the very same thing GNUs do, stomping on what's already there. It doesn't have to be that way: https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_u...

I keep a grub2 rescue disk on hand just in case, but I rarely get problems. But then I have no secure boot, and only Vista and XP. With multiboot, there uncommonly is any need to fumble around looking for "rescue" media. All my internal HDs have amounted to rescue disks since last century. I've been multi-booting since before Linux 0.1, somewhere around 25 years, whenever it was that OS/2 2.0 was released. Multiboot systems here outnumber single boot systems somewhere around 30+:1. Multiboot is really not hard when no GNU installer or updater is permitted to expunge generic boot code from the MBR. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org