EnOS will no longer boot

Last night, everything was fine when I shut down the computer.

This morning I get this:

Starting version 249-3-arch
/dev/nvme0n1p2: clean, 363407/14655488 files, 4211836/58610556 blocks
[FAILED] Failed to start Remount Root and Kernel File Systems.
[FAILED] Failed to start Remount Root and Kernel File Systems.
[FAILED] Failed to start Remount Root and Kernel File Systems.
[  TIME  ] Time out waiting for device /dev/disk/by-uuid/E604-E8D1
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/E603-E8D1
[DEPEND] Dependency failed for /boot/efi
[DEPEND] Dependency failed for Local File Systems.
You are in emergeny mode blah blah blah

I logged in and did a lsblk -f

NAME     FSTYPE   FSVER   LABEL  UUID                        FSavail FSUSE% Mountpoints
    nvmeon1p1   vfat FAT32   NO_LABEL   4938-B1CB
    nvme0n1p2   ext4 1.0                f43bea8c-83ee-45e5-etc  196.3G  5%  /
    nvme0n1p3   swap 1                  c14cd238-e92d-43f7-etc              [SWAP]

So the error said uuid E603-E8D1 failed and it doesn’t exist.
lsblk says the uuid 4938-B1CB is the valid uuid

I then ran mkinticpio -P and grub-mkconfig -o /boot/grub/grub.cfg
in an attempt to get the proper uuid established.
Reboot and same results.

So how do I get the proper uuid established where ever it needs to be?


Did you check fstab?


Unless you are using mount units, it should be in /etc/fstab.

I don’t think it requires regerating the initramfs or grub-mkconfig because it is your EFI partition.

1 Like

Thanks guys, checking now.


1 Like

Wouldn’t you have to run grub update though if you change fstab?

If it is only the EFI partition, I don’t think so. You don’t even need the EFI partition mounted to boot the system.

If it is the root partition, that is a different scenario.

The question is why would it change?

Thanks @ricklinux and @dalto. I don’t know why, I never gave /etc/fstab a thought.
The uuids for both partition 1 (vfat) AND partition 2 (ext4) were wrong. Being in a Console window, no copy / paste. Had to type it in manually.

Anyway, all is good now and there is joy in Pudgetown.
FYI after entering the correct uuid numbers in fstab, after only a simple reboot the system came up. No grub update was necessary,

Not sure if mkinitcpio and grub-mkconfig really did anything or not.

After I thought about it, last night I set up an external SSD to install ARM on a Raspberry Pi 4b. Obviously, something went awry.

Thanks both of you for saving me a bunch of time.



I hate it when things go awry. :grinning_face_with_smiling_eyes:


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