Not Booting after updating today. Timed out waiting for device /dev/gpt-auto-root

[ZachariasFrings]

Hello everbody,
after updating eralier this week my wayland environment didnt work anymore (I checked the forum and saw that there is now a fix for this :))

Sadly after updating again today my PC is no longer able to boot.

The Startjob: dev-gpt/x2dauto/x2droot-device.start is timing out, after which the emergency shell opens.

I am not that well versed with linux kernel-stuff. I am running a Nvidia-Graphics card. The update included a nvidia update so i think it might have to do with it?

Could anyone help me figure this out?

[xircon]

Attention Nvidia GPU / Driver users! update to latest kernel and drivers could cause issue on plasma wayland

Read here: And here: [2024-10-02_13-08] Fix for systemd-boot bootloader: You would need to fire up a terminal (e.g. Konsole) and edit the file /etc/kernel/cmdline with your favourite text editor like this: sudo nano /etc/kernel/cmdline There you should see a single line where you append the parameter nvidia_drm.fbdev=1 Also make sure that the parameter nvidia_drm.modeset=1 is present somewhere in this line. Otherwise append it too. If using nano as your text editor, just hit CTRL+…

Is it this?

[ZachariasFrings]

Thx for the qick reply. Sadly I cant seem to acces the /etc/kernel dir in the emergency-shell. (The dir doesnt exist)

[xircon]

Chroot in from your install media, edit file, exit chroot and reboot. Am not near a Linux box as at work, but the instructions for chroot are on the wiki.

Or… just boot from the install media and mount the drive in dolphin navigate to the directory in dolphin and press f4 for a terminal and edit the file with sudo nano <file-name>

[ZachariasFrings]

I dont see how a problem with Wayland could lead to a system not booting. Or am i missing something?

[ZachariasFrings]

I chrooted into my system, changed the kernel parameters for systemd and the problem still persists.

Could it have anything to do with gpt?
I have really no idea so far

[xircon]

Looks like it may be, I just assumed it was the wayland issue.

[ZachariasFrings]

Okay, I managed to solve it:

A update via pacman or yay (I didnt notice it during that time) had an error.

After restarting my gpt wasnt able to auto-configure my root partition.

What i needed to do was:

1. chroot into my system via a iso-bootstick of endeavouros
2. print out the the UUIDs of my paritions with blkid
3. look for the UUID of your root-parition (usually with the label “endeavouros)”
4. go into super user via sudo su
5. cd into /efi/border/entries/(Or the location of your bootloader-entries)
6. Add the argument root=UUID=<UUID of your root-partition> to the options line (append with a blank space)
7. exit out of chroot
8. reboot the system

I hope this helps someone who has the same Problem
Feel free to message me if you have further problems