Arch Linux

Skeleton2323

Member

Registered: 2024-09-14

Posts: 60

[SOLVED] Timed out waiting for device after motherboard upgrade

Hello there, I upgraded my system from a maximus 7 hero to a maximus 8 hero (4th gen to 6th gen intel board) but everything else apart from the MB, RAM and CPU was the same. I reinstalled windows by erasing every partition, including the EFI partition except for the arch root partition (no seperate partitions for home, var, etc, etc). GRUB was inevitably erased and after I installled windows normally, I booted the arch installation with SystemRescueCD 12.03 with its' load linux from disk feature. While it did find the partition, it came up to an emergency shell. I then reinstalled grub on the efi partition and regenerated the configuration file. And while GRUB worked again with my configuration as well as os-prober, for some reason I get stuck on the fsck clear screen without the ability to getty or change tty with the shortcut.

I'm using SDDM, KDE and Wayland with the propriatery NVidia drivers.

journalctl -D /var/log/journal -b from within a chroot
https://0x0.st/P-nA.txt

(Note that the system is not up to date. Is doing an update with the system in this state a good idea?)
Also the journal seems way too small and is seemingly missing a full minute of logs up until when it logs the reboot, is this normal?

Any help to get the system going is appreciated!

edit: sysrescuecd version fixed

edit: striked out irreleavnt information, i updated the system, check 2nd reply. also fixed title to more accurately inform about the error

Last edited by Skeleton2323 (2026-01-06 18:06:21)

Skeleton2323

Member

Registered: 2024-09-14

Posts: 60

Re: [SOLVED] Timed out waiting for device after motherboard upgrade

welp, turns out I needed to leave the system for about 2 minutes on the fsck clean screen for the disk job to time out
it's odd to me since why would a disk related job would fail if fsck shows clean? more accurately why would fsck print "clean" if the service craps out afterwards?

Here's a more relevant boot log with the system booting by its own GRUB, with the job timing out. I'm still thrown into an emergency shell
https://0x0.st/PoUv.txt

Notice the /boot/efi related errors. The system always mounts the efi partition located on nvme0n1p1
Is it an fstab issue? After the motherboard upgrade, I kept the same SSD and both the root and the efi partitions are numbered in the same order (1 and 5 respectively).
Any help to steer me in the right direction is appreciated!

edit: forgot to mention I upgraded the system today, about 30 minutes or so before the boot log. i also regenerated the initramfs with both -p linux and -P options and updated grub. still no dice
edit: here is my fstab
https://0x0.st/PoUh.txt

Last edited by Skeleton2323 (2026-01-06 16:06:02)

Skeleton2323

Member

Registered: 2024-09-14

Posts: 60

Re: [SOLVED] Timed out waiting for device after motherboard upgrade

issue solved, it was a mismatched uuid