I updated my system a little while back and after reboot, I get the error “timed out waiting for device /dev/desk…” along with a few dependency errors about file systems, file system check, etc.
It seems to be failing to find the disk. Can someone help me with this?
Can we see the contents of /etc/fstab and the output of lsblk -o name,type,fstype,size,uuid
Also, the complete errors you are seeing would be very helpful.
Hi Dalto,
I think I am going to need to login using an ISO since the below asks for my root password, my normal password doesn’t seem to work. Is there a separate root password I should know? I can’t get past “Give root password for maintenance (or press Control-D to continue):”
The Errors are as follows:
[ TIME ] Timed out waiting for device /dev/desk/by-uuid/4365…
[DEPEND] Dependency failed for /home/workstation0/Toshiba
[DEPEND] Dependency failed for Local Files systems.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uui/4365…
You are in emergency mode. After logging in, type “journalctl”…
Quite possibly you will need to boot off the ISO.
By default, the installer sets them to be the same password. However, you can override that or if your password has changed during the install they may be different.
Downloading an ISO now. Where can I find instructions on booting into that drive?
So I tried to chroot in using the above link. I can see the hard drive, but when I try to access using 'sudo cryptsetup open /dev/sda2 mycryptdevice I get "no key available with this passphrase. I am pretty sure the password is correct. I also checked to make sure caplocks wasn’t on. Was there any update that caused issues with encrypted drives? It has been a several weeks since the update killed the computer. I just haven’t had the chance to get to it till now.
to be able to get into it still needs the info about your partitions:
the contents of
/etc/fstaband the output oflsblk -o name,type,fstype,size,uuid
I am accessing using a live ISO and am unable to chroot in so there is thing if /etc/fstab
lsblk -o name,type,fstype,size,uuid
[liveuser@eos-2022.08.05 ~]$ lsblk -o name,type,fstype,size,uuid
NAME TYPE FSTYPE SIZE UUID
loop0 loop squashfs 1.6G
sda disk 119.2G
├─sda1 part vfat 300M 36EE-XXXX
├─sda2 part crypto_LUKS 110.1G cf2991b1-db38-XXXX-182b21b2b115
└─sda3 part crypto_LUKS 8.8G ea763b8d-0f5c-XXXX-7fe0dc38087a
sdb disk 931.5G
└─sdb1 part 931.5G
sdc disk iso9660 14.9G 2022-08-05-07-19-08-00
├─sdc1 part iso9660 1.7G 2022-08-05-07-19-08-00
└─sdc2 part vfat 104M 826B-8B64
sr0 rom 1024M
sda disk 119.2G
├─sda1 part vfat 300M 36EE-XXXX
├─sda2 part crypto_LUKS 110.1G cf2991b1-db38-XXXX-182b21b2b115
└─sda3 part crypto_LUKS 8.8G ea763b8d-0f5c-XXXX-7fe0dc38087a
we can see /dev/sda2 is indeed your system partition so as long the partition is intact you should be able to open the encryption with your passsphrase (not the user password)
You can also open it from gparted on the livesession as mentioned in the wiki too…
Without LUKS open up the containment there is not much we can do.
You are right, I was trying to log in with my password. Was able to access drive. working on mounting.
After unlocking, I can get to sudo mount /dev/mapper/mycryptdevice /mnt
but am having trouble with the below.
sudo mount /dev/sdXn /mnt/efi
nice!
by any chance you are using BTRFS?
and sudo mount /dev/sdXn /mnt/efi is not correct … you need to put in your esp device what should be /dev/sda1 and inaddition i bet you are using grub ? and older install not installed with latest release? so the ESP is mounted under /boot/efi and according to this fact this would be the command:
sudo mount /dev/sda1 /mnt/boot/efi
I think I am using LUKS. That worked. I was able to mount at sda1 /mnt/boot/efi. Have pasted the commands below. What are next steps?
[root@EndeavourOS /]# lsblk -o name,type,fstype,size,uuid
NAME TYPE FSTYPE SIZE UUID
loop0 loop 1.6G
sda disk 119.2G
├─sda1 part 300M
├─sda2 part 110.1G
│ └─mycryptdevice crypt 110.1G
└─sda3 part 8.8G
sdb disk 931.5G
└─sdb1 part 931.5G
sdc disk 14.9G
├─sdc1 part 1.7G
└─sdc2 part 104M
sr0 rom 1024M
[root@EndeavourOS /]#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=36EE-B488 /boot/efi vfat umask=0077 0 2
/dev/mapper/luks-cf2991b1-db38-44df-b0eb-182b21b2b115 / ext4 defaults,noatime 0 1
/dev/mapper/luks-ea763b8d-0f5c-4581-89f1-7fe0dc38087a swap swap defaults,noatime 0 2
UUID=43651a5d-3f0d-4d20-b147-7fa7e710283c /home/workstation0/1Toshiba >
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Obviously, this partition is missing and the reason to your problem.
lsblk should show unmounted UUIDs. Maybe use The Force?
sudo lsblk -f
sudo blkid
It may be the UUID of the unlocked partition. Those won’t show unless you run lsblk with the luks partition unlocked.
Could this mean that it may be a race condition? Why not using the similar to the others (cryptsetup) entries in fstab?
I have never used encryption… 
This is lsblk after chrooting in:
[root@EndeavourOS /]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.6G 1 loop
sda 8:0 0 119.2G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
├─sda2 8:2 0 110.1G 0 part
│ └─mycryptdevice 254:0 0 110.1G 0 crypt /
└─sda3 8:3 0 8.8G 0 part
sdb 8:16 0 931.5G 0 disk
└─sdb1 8:17 0 931.5G 0 part
sdc 8:32 1 14.9G 0 disk
├─sdc1 8:33 1 1.7G 0 part
└─sdc2 8:34 1 104M 0 part
sr0 11:0 1 1024M 0 rom
[root@EndeavourOS /]#
We need lsblk -o name,type,fstype,size,mountpoint,uuid