If I boot my laptop up and select Suse to boot to first, it will act like it is loading and then present me with an error message:
"Welcome to Emergency Mode! After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, “systemctl default” to try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):
This seems only to happen if and only if I boot to Suse FIRST. If I boot into Windows and then restart the machine and select Suse at the boot menu, it works fine!
What the heck is going on?
Also, not sure if this is tied in or not…but the boot menu “Grub” randomly changes and/or duplicates the entries. Drives me nuts!
I don’t really know what is going on, though I have a guess.
Can you try this:
Boot Win10. Then restart, and boot opensuse.
Now shutdown from opensuse.
Does it now start up properly when the first boot is to opensuse after that shutdown?
What I’m guessing, is that you are seeing theh problem of Windows fast shutdown, which leaves the Windows file system in an unstable state and opensuse is refusing to mount it. If that guess is correct, then it should boot up fine when you have done a shutdown from opensuse.
With fast shutdown, Windows leaves the file system in an unstable state. But if you reboot, instead of shutdown, from windows, then it puts the file system into a clean state.
If this turns out to be the issue, then the good news is that you can disable fast shutdown in Windows.
I’ve seen others with this issue. It can happen if there are somehow duplicate files in “/etc/grub.d”. I think that happens when you edit one of those files, and then grub is updated. It keeps your edited file, but puts another with a filename ending in something like “.rpmnew” so that you can inspect the changes and merge them into your file.
However, I’m again only guessing. You have given very little information on what is happening.
On my laptop, I get two entries to boot Windows 7. That is because it can be booted using the main Windows partition and it can be booted using the recovery partition. I just ignore the duplication.
