Emergency mode after update.

[pearl tinsel]

Hi everyone,
Yesterday installed Mint for first time on a dual boot with Windows 11. Installation went fine, no issues. Then I decided I would update everything using the update tool. Restarted my computer, no the system hangs on Mint logo and then enters emergency mode. The suggested Ctrl+D does nothing. Have tried to restart multiple times, no effect. Windows boot is still working fine, thankfully. Any suggestions to remedy would be appreciated!

My machine is a 2019 Acer Helios Predator with updated 32gb RAM, for what it is worth.

[cyan river]

Hi JD. That sounds awful. Thankfully your Windows system is fine. Could you please get us a picture of your screen in emergency mode?

Usually, there are information logs there that tells us why your system went into emergency mode. That'd really be helpful.

[pearl tinsel]

Thank you, will post some up a bit later when baby goes to bed 🙂

[pearl tinsel]

Okay, so I was tinkering around with it. It seems in the BIOS that the boot mode had been changed, so I switched it back to AHCI and it seems to work again. I have not tried Windows mode since, but hoping that works with this change.

Also, since updating Mint, I am now no longer able to notice my 2nd monitor plugged into my laptop (plugged into mini-display port). I suspect this is associated with Secure Boot, but I am worried that turning off Secure Boot can play badly with Windows?

Have updated to latest recommend Nvidia drivers too.

[cyan river]

Yeah, it's right to switch to AHCI for Linux. Not sure what that entails for Windows (like keeping AHCI) but from my experience, it has been pretty alright.

[cyan river]

Run mokutil --sb-state in your terminal. That should tell you if Secure Boot is enabled or not.

But generally, disabling Secure Boot should be fine for either.

Not sure if Windows 11 requires SB to be on, but it shouldn't really be a problem.

If you can't disable SB for some reason, please refer to this string of messages: #1429152383018991697 message

[pearl tinsel]

I'll try turning it off in BIOS and go from there. It is definitely On, it says in BIOS.

I have read reports that Secure Boot can play funny with Nvidia drivers...
Which is odd, because the monitor was working fine when I first installed Mint. Then I updated with software update and nvidia update and it all went haywire.

[cyan river]

Secure Boot checks the signature in the operating system's bootloader to see if it matches a registered key in the UEFI firmware. If a match is found, the boot process proceeds. If Secure Boot cannot verify the boot loader, the system will generate an error and the boot process will halt. Most of today's computers are configured with UEFI firmware.

[cyan river]

Applies similarly to Nvidia drivers. You have to enroll your keys manually for it to work, which I believe is already addressed here.

You bet I'm somehow happy despite using iGPU... everything with my little Latitude potato just works here.

[pearl tinsel]

Thank you! Will check this out later 🙂

Thanks for helping me out!

[cyan river]

No worries, my pleasure :>

[pearl tinsel]

Turned off Secureboot and monitor now showing up!

[cyan river]

Would you look at that!

[surreal hill]

@normal gust apologies for the ping stunner, but I figured you'd like seeing another example of a happy user

after turning off secure boot

[pearl tinsel]

And the Windows boot still works -- I just have to change the sata boot mode whenever I want to use it. Small nuisance, but I anticipate I will be using Windows much less as time progresses.