I can’t boot my tumbleweed system. Earlier I tested a windows11 bootable USB, saw that it worked and stopped the process on the 2nd screen (before making any changes to the existing system).
Now when I try to boot it tries to load some nonexistent disk for 1:30 min, which times out. And then it shows Dependency Failed for some media mount and then the Local File System.
Here are the logs of these errors, everything else seems to be loading okay. Please help.
Apr 26 14:44:06 localhost systemd[1]: dev-disk-by\x2duuid-494C\x2dE3EE.device: Job dev-disk-by\x2duuid-494C\x2dE3EE.device/start timed out.
Apr 26 14:44:06 localhost systemd[1]: Timed out waiting for device /dev/disk/by-uuid/494C-E3EE
Subject: A start job for unit dev-disk-by\x2duuid-4946\x2dE3EE.device has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
start job for unit dev-disk-by\x2duuid-494C\x2dE3EE.device has f inished with a failure.
The job identifier is 171 and the job result is timeout
Apr 26 14:44:86 localhost systemd[1]: Dependency failed for run/media/lyubo/C80C-1FF4
Subject: A start job for unit run-media-lyubo-c80c\x2d1ff4.mount has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit run-media-lyubo-C80C\x2d1FF4.mount has f inished with a failure
The job identifier is 170 and the job result is dependency.
Apr 26 11:41:06 localhost systemd[1]: Dependency failed for Local File Systems
Subject: A start job for unit local-fs.target has failed
Defined-By: systemd
Support: [link, same as above]
start job for unit local-fs.target has finished with a failure
The job identifier is 167 and the job result is dependency.
Apr 26 14:44:06 localhost systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 26 14:44:06 localhost systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Apr 26 14:44:06 localhost systemd[1]: run-media-lyubo-C80C\x2d1FF4.mount: Job run-media-lyubo-C80C\x2d1FF4.mount/start failed with result 'dependency'.
Apr 26 14:44:06 localhost systemd[1]: dev-disk-by\x2duuid-494C\x2dE3EE.device: Job dev-disk-by\x2duuid-494C\x2dE3EE.device/start failed with result 'timeout'.
The UUIDs that failed appear to belong to FAT filesystems, possibly to installation media or other USB sticks attached during installation. Go ahead and login at that text prompt, navigate to /etc/fstab, and look for lines there that have those UUIDs. If you find them, add to their options sections a comma and either nofail or noauto using nano /etc/fstab or any other plain text editor you’re familiar with. This should permit a normal boot during which you can more easily determine what filesystems those UUIDs belong to.
I think I did it right since it didn’t wait for the UUID to load this time. But now it’s giving me a similar error and I have no idea why. The logs are 3000 lines and I have no idea what to look for - it’s all green now.
But if I understand the initial error, there is something wrong with vfat file system? But I don’t know how to fix that either.
All I see in that image suggests an NVidia GPU problem (nothing about FAT), proprietary drivers I think, which is something others such as NVidia wizard @malcolmlewis would need to help with. I never use them. At least you have a login prompt from which logs can be inspected (e.g. journalctl -xb; key in / aile to search for lines that include “Failed”) and collected, and repairs can be made. Possiblyexit might get you further along after logging in.
The nvidia looks fine … I think the PF_ALG indicates a USB device and the NET: suggests it might be a usb wifi usb adaptor perhaps? A quick search of PF_ALG says people are using usb_modeswitch to get around it but’s that’s out of my wheelhouse … do you have a usb wifi dongle plugged in? Maybe just remove it temporarily and reboot to see if that helps
Edit: now that I look closer is seems to be bluetooth related … maybe use sysctl to disable bluetooth temporarily?
Now that I double-double check bluetooth looks fine too … @hui is right … this post Similar problem gives lots of clues … now it’s definately outta my wheelhouse
Hey everyone, thanks for all the suggestions!
Following the post linked by @dart364 , I deleted the problematic UUID from fstab (I believe it was a USB stick that was no longer plugged in).
Then I just ran ‘exit’ once after the login prompt, as suggested by @mrmazda and booted normally. Did a few resets, a system update, opened a bunch of programs, GPU heavy games and so far everything seems to be working normally. I consider this a closed case. Thanks again!
PS - some context for other suggestions mentioned above: I have a USB dongle for Bluetooth, no WiFi adapter (internal or external), connected with an Ethernet cable
