Usually .device units are needed by /etc/fstab entries (or some other .mount). From the shape of the UUID it looks like it's the /boot or /efi mount for your EFI System Partition (or *some* FAT32 partition in any case), which might have gotten corrupted. In the emergency mode, compare any UUID= or /dev/disk/by-uuid entries in your fstab against either `lsblk -f` (if that works in emergency mode) or `blkid -c /dev/null`.
The "0 0" and "0 1" settings in /etc/fstab are not a boot order nor a mount order. The last field is the *filesystem check* order, and changing from "0 0" to "0 1" enables fsck for that filesystem (which on many Linux distros is meaningless for your root filesystem since that is already mounted by the time /etc/fstab can be read – it has to be checked at an earlier stage (in the initramfs) anyway). On Wed, Sep 10, 2025 at 9:22 PM Christian M. <lucsayb...@gmail.com> wrote: > Greetings, > > I'd like to ask for help with my personal machine if that is okay. I'll > list the errors first then explain how I think it occured, and then what I > have done so far. > > The system of mine is stuck in emergency mode. The error from the > journalctl is transcribed by me with some abbreviation (in parentheses) and > listed by line to break it up a bit: > > Each Line is prefaced with: > Sep 10 13:29:47 fedora > > Line 1: > audit[1]: SERVICE_STOP pid(id),uid(id),ses(id), > subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" > exe="(PATH)/systemd" hostname=? addr=? terminal=? res=success' > > Line 2: > kernel: kauditd_printk_skb: 35 callbacks suppressed > > Line 3: > kernel: audit: type(id) audit(id): pid,uid,auid,ses(ids) > subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" > exe="(PATH)/systemd" hostname=? addr=? terminal=? res=success: > > Line 4: > sytemd[1]: dev-disk-by\x2duuid-ACB0\x2d8373.device: Job > dev-disk-by\x2duuid-ACB0\x2d8373.device/start timed out. > > Line 5: > systemd[1]: Timed out waiting for device > dev-disk-by\x2duuid-ACB0\x2d8373.device - /dev/disk/by-uuid/ACB0-8373 > > LINES 6-10: > Subject: A start job for unit dev-disk-by\x2duuid-ACB0\x2d8373.device has > failed > Defined-By systemd > Support: (this mailing list) > A start job for dev-disk-by\x2duuid-ACB0\x2d8373.device has finished with > a failure. > The job identifier is 236 and the job result is timeout. > > Incase any of the values I replaced with (id) are needed, for my own > reference, the actual 1st line number is 3169. I transcribed this my hand > on my cell phone and it was hell, lol. > > > So, I actually don't know if this error message is related to my overall > problem: my fedora PC is stuck booting into emergency mode. The speculated > cause is my PC was installing a kernel update when a shutdown command was > executed. Specifically I ran, "sudo dnf update && shutdown now". Normally > this installs updates and gracefully shutdown afterwards. > > > I have so far: > 1) regenerated initramfs for all kernels > 2) Rebuilt GRUB configuration > 3) Reset my root user password (this solved the error message before > emergency mode which said that the OS was unable to load the root user's > account) > 4) Edited the /etc/fstab to have root directory setting changed from 0 0 > to 0 1 so it should presumably boot first. > No affect will likely change it back. > > I dont know for sure if this is a drive issue as searching the internet > has tried to tell me. I believe and hope the transcribed error message > above is the cause and fixing that will restore my system. > > Any assistance is appreciated! > > Regards, > Christian >
