Emergency Mode following updates on Win 10 partition

Hi,

Similar to what is described at the bottom of this thread (https://forums.opensuse.org/showthread.php/524348-Welcome-to-emergency-mode!), I installed Win 10 updates on my dual boot Thinkpad Tumbleweed/Win10 and am now hit with Emergency Mode when I try to boot Tumbleweed. (Angry face icon directed at Microsoft.)

Unfortunately, it does not appear to be an unmounted partition as referenced in that thread. Below is a subset of the journalctl log including all the stuff in red and some of the bolded stuff from the log. I can still navigate the command line, run emacs, was able to run rsync as well as a precaution. But I have no idea how to troubleshoot further. Any insights or suggestions would be greatly appreciated.


May 17 04:28:21 localhost kernel: TSC synchronization [CPU#0 -> CPU#1]:
May 17 04:28:21 localhost kernel: Measured 390087899 cycles TSC warp between CPUs, turning off TSC clock.
May 17 04:28:21 localhost kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
May 17 04:28:21 localhost kernel:   #2  #3  #4  #5  #6  #7  #8  #9 #10 #11 #12 #13 #14 #15

May 17 04:28:21 localhost kernel: audit: type=2000 audit(1621240099.164:1): state=initialized audit_enabled=0 res=1

May 17 04:28:21 localhost kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

May 17 04:28:21 localhost kernel: SCSI subsystem initialized

May 17 04:28:21 localhost kernel: VFS: Disk quotas dquot_6.6.0

May 17 04:28:21 localhost kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
May 17 04:28:21 localhost kernel: pci 0000:00:00.2: PCI INT A: not connected

May 17 04:28:21 localhost kernel:  PPR X2APIC NX GT IA GA PC GA_vAPIC

May 17 04:28:21 localhost kernel: Unstable clock detected, switching default tracing clock to "global"
                                  If you want to keep using the local clock, then add:
                                    "trace_clock=local"
                                  on the kernel command line

May 17 04:28:21 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.

May 17 04:28:22 localhost kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
May 17 04:28:22 localhost kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
May 17 04:28:22 localhost kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
May 17 04:28:22 localhost kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
May 17 04:28:22 localhost kernel: acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)


¦¦ The job identifier is 31.
May 17 04:28:22 localhost systemd[1]: Reached target Basic System.
¦¦ Subject: A start job for unit basic.target has finished successfully
¦¦ Defined-By: systemd
¦¦ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
¦¦ 
¦¦ A start job for unit basic.target has finished successfully.
¦¦ 
¦¦ The job identifier is 2.
May 17 04:28:22 localhost kernel: ccp 0000:07:00.2: enabling device (0000 -> 0002)
May 17 04:28:22 localhost kernel: ccp 0000:07:00.2: ccp: unable to access the device: you might be running a broken BIOS.
May 17 04:28:22 localhost kernel: cryptd: max_cpu_qlen set to 1000
May 17 04:28:22 localhost kernel: nvme nvme0: pci function 0000:01:00.0
May 17 04:28:22 localhost kernel: ccp 0000:07:00.2: tee enabled
May 17 04:28:22 localhost kernel: ccp 0000:07:00.2: psp enabled

May 17 04:28:22 localhost kernel: nvme nvme0: missing or invalid SUBNQN field.


May 17 04:28:24 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
May 17 04:28:24 localhost systemd[1]: initrd-parse-etc.service: Succeeded.

May 17 04:28:24 localhost systemd[1]: haveged.service: Failed with result 'exit-code'.
¦¦ Subject: Unit failed
¦¦ Defined-By: systemd
¦¦ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

May 17 08:28:25 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.

May 17 08:28:25 localhost kernel: ipmi_si: Unable to find any System Interface(s)
May 17 08:28:25 localhost kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control

May 17 08:28:25 localhost kernel: r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control

May 17 08:28:25 localhost kernel: ACPI Error: No handler for Region [ECSI] (000000001846e905) [EmbeddedControl] (20210105/evregion-130)
May 17 08:28:25 localhost kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210105/exfldio-261)
May 17 08:28:25 localhost kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:28:25 localhost kernel: ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:28:25 localhost kernel: ACPI: \_SB_.UBTC: failed to evaluate _DSM (0x6)
May 17 08:28:25 localhost kernel: ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2


May 17 08:28:26 localhost kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver

May 17 08:28:26 localhost systemd[1]: plymouth-start.service: Found left-over process 392 (plymouthd) in control group while starting unit. Ignoring.
May 17 08:28:26 localhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.

May 17 08:28:26 localhost kernel: thermal thermal_zone0: failed to read out thermal zone (-61)

May 17 08:28:26 localhost kernel: ucsi_acpi: probe of USBC000:00 failed with error -5


May 17 08:29:13 localhost kernel: ACPI Error: No handler for Region [ECSI] (000000001846e905) [EmbeddedControl] (20210105/evregion-130)
May 17 08:29:13 localhost kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210105/exfldio-261)
May 17 08:29:13 localhost kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:29:13 localhost kernel: ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:29:13 localhost kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:29:15 localhost kernel: ACPI Error: No handler for Region [ECSI] (000000001846e905) [EmbeddedControl] (20210105/evregion-130)
May 17 08:29:15 localhost kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210105/exfldio-261)
May 17 08:29:15 localhost kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:29:15 localhost kernel: ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:29:15 localhost kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20210105/psparse-529)
May 17 08:29:55 localhost systemd[1]: dev-disk-by\x2duuid-95D9\x2dCE72.device: Job dev-disk-by\x2duuid-95D9\x2dCE72.device/start timed out.
May 17 08:29:55 localhost systemd[1]: Timed out waiting for device /dev/disk/by-uuid/95D9-CE72.
¦¦ Subject: A start job for unit dev-disk-by\x2duuid-95D9\x2dCE72.device has failed
¦¦ Defined-By: systemd
¦¦ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
¦¦ 
¦¦ A start job for unit dev-disk-by\x2duuid-95D9\x2dCE72.device has finished with a failure.
¦¦ 
¦¦ The job identifier is 176 and the job result is timeout.


May 17 08:29:55 localhost systemd-update-utmp[1681]: Failed to get new runlevel, utmp update skipped.

May 17 09:20:09 localhost kernal: Buffer I/O error on dev sda1, logical block 36, async page read

@joelnc:

Buffer I/O error on dev sda1, logical block 36, async page read

Given that, from the Linux view, “/dev/sda1” is usually the VFAT “/boot/efi” partition –

  • This means that, the Windows update has modified the UEFI partition and, left a bad checksum there …

Please check that, the UEFI/BIOS has a proper view of the openSUSE EFI SHIM files – power on – F2 or Del – Advanced BIOS options …

Thank you @dcurtisfra for taking a look.

Turns out I did still have available the full graphical openSuse boot menu and was able to load a recent read-only TW snapshot from that menu option (first time I’ve done that… good to know about), and then do a ‘snapper rollback’ and things now seem okay. Given that, would you still think the Windows update was the likely culprit based on the log entries and timing (i.e., it worked fine for months, issue appeared directly following Windows updates)? I ask because I almost don’t need Win 10 on this machine, and if this might happen again (or similar) and could be avoided by just getting Windows off the drive, I would consider doing that.

From your troubleshooting suggestion, I was not really able to find that info in BIOS after going through all the menus, but maybe that’s just me. It’s a newish Lenovo setup FWIW.