Tumbleweed won't boot after installing updates and rebooting the system

Hello,

So, I was using openSUSE Tumbleweed with ext4 partition. It’s a dual boot setup with Windows 11.
After performing a “sudo zypper dup” today, installing updates which also included kernel updates from 6.10.7 to 6.10.8 I think, it recommended me to restart the system. After restarting I’m greeted with this:

[ 4.385143][ T388] amdgpu 0000:0a:00.0: amdgpu: Secure display: Generic Failure
[ 4.385152][ T388] amdgpu 0000:0a:00.0: amdgpu: SECUREDDISPLAY: query secured
display TA failed. ret 0x0

Since I’m using ext4, I have no snapshot to rollback to. Is there any way to solve this issue?
My system is AMD 3400G with integrated Vega GPU, 16 GB Ram. 14 actually since 2 GB is taken by the integrated GPU.
I’m a newbie into the Linux universe.

Thanks

Depending on how often you upgrade, you likely met with a kernel upgrade (on 20240906) and a kernel-firmware upgrade (on 20240903) that apparently caused a mismatch that is a recurrent and often harmless problem (just google for “amdgpu: Secure display: Generic Failure”).
Meanwhile you should still be able to boot the previous kernel (at the boot menu scroll down to “advanced options”).
You may also try to rebuild the initramfs to see if that helps with:

sudo dracut --hostonly --force

I have no AMD GPU atm, so wait for an expert to give more specific advice if the above doesn’t help.

I tried to boot the previous kernel, but the result was the same. I haven’t tried this sudo dracut method yet but when I typed anything with sudo then it said something like, sudo is not recognized as a command.

Boot with plymouth.enable=0 and without quiet on the kernel command like. It may show some more information.

To do the above, at the grub menu press “e” for “edit” and look for the line beginning with “linuxefi”, edit as directed and then press F10 to boot.
You may also append a “3” (without quotes) to boot to a command line.

@arvidjaar @OrsoBruno This is what I see after adding plymouth.enable=0 and removing quiet.

The problem clearly is

Failed to start File System Check on /dev/disk/.... (your /root filesystem, from your other thread)

so either something really bad happened to your /root filesystem or something happened with the latest systemd-presets-common-SUSE upgrade from snapshot 20240829, if you didn’t upgrade for a couple of weeks?
Nothing apparently related to AMD hardware or graphics subsystem.
@arvidjaar surely has more insight on that.

You’re right. I just checked the particular partition where Tumbleweed was installed by using a third-party app on my Windows and turns out almost all the data on that partition has been wiped. The used space was something like 10 GB befire but now it’s only 168 MB.
How could an update wipe all the data?
Okay, as I wrote the previous part of my comment, I decided to check on Windows’s own Disk Management software which shows apparently the whole partition is free. That’s probably because Windows can’t read ext4 file system. So decided to check via another third-party app which is showing 12 GB is used like it is supposed to be.
Three different results in three different app. I think something is wrong with the partition I created.
So, I won’t bother you guys anymore on this. I need to figure out what went wrong with the created partition.
Thanks everyone for trying to help.

Exactly, you must use e.g. a live Linux system to check and maybe repair that partition.
You may find a Tumbleweed Rescue CD here or a working KDE TW here but any rescue/live Linux should be able to check and repair an ext4 partition.
Don’t be afraid to ask if you need help, you are welcome.

Thanks. Currently I’m trying out a different distro to check if there is any issue with my partition and will come back to Tumbleweed later.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.