I updated my system today, deleted a pacnew for locales then rebooted and I’m getting a “start job is running for /dev/disk” error. neither linux nor lts kernel works. what do i do in this situation?
can you at least take a picture of the error if you can’t post it? I mean the start job could be trying to mount the boot drive or the root drive we can’t really tell what is going on with the very little information you have given. You should also provide some basic information about the systems while your at it. You can use eos-logtool to help gather, upload and post(url to) the information.
it is actually two start jobs. it is switching between the two with no time limit. the start job is below mounted kernel configuration.
im guessing i need to arch-chroot in?
that would be the ideal thing to do so you can post information about what is failing
i just tried booting into the fallback option under the lts kernel and it adds another start job, this time a start job for dracut.
alright im chrooted in. i followed the wiki page to do it. did a ls /home to make sure it worked. i never arch chrooted before
would a simple reinstall-kernels do the trick?
If you’re able to chroot first check if the disk that was mentioned in the “start job is running for /dev/disk” is OK. Overall it would be helpful to see the full journal log of the failed boot if possible.
Hi, I’m new here and seem to have the same error. If not anon543456 of course I can open a new thread.
Get the message a “start job is running for dracut initqueue hook time/no limit” and “start job is running for /dev/disk/by-uuid/here UUID of luks encrypted disk”. Later a warning: timeout, still waiting for following initqueue hook … 90-crypt.sh
Happened after update at the same time as thread opener had the problem.
Luks encrypted disk is available and seems to be ok. Could open it with arch-chroot. Reinstall kernel doesn’t help, downgrade of systemd which was installed too before error didn’t help as well.
Just see a warning before entering emergency shell that /dev/disk/by/uuid/2f… doesn|t exist and in next line that crypto LUKS UUID 58… was not found.
Tried in the meanwhile downgrade of dracut, a dracut --regenerate without success.
I also get stuck on a start job for /dev/disk/… after upgrade. I don’t have encryption on the disk here, but I use an external SSD connected to USB. No time for extended troubleshooting right now, but I wanted to drop a note so you know that more than one user is hit.
I saw the same thing about ~2 weeks ago but after a slight delay everything proceeded normally and I think last reboot it flashed this at least once but did not stall for nearly as long. Updates can really do weird stuff sometimes 
I also got hit with this a couple days ago, presumably after an update. No encryption or external ssd here, the uuid is my root partition (I have everything in one partition except for /efi).
I was able to chroot in, partition and disk are fine. Installed linux-lts, same issue. I did eventually get it to boot by replacing dracut with mkinitcpio, regenerating the image and uki, and reinstalling systemd-boot. Not sure how much of that was necessary or what the root cause of the problem was…
To add a bit more detail, I
- installed mkinitcpio
- uncommented the
default_ukiline in/etc/mkinitcpio.d/linux.preset(as per wiki) - ran
sudo mkinitcpio -p linux(or whatever kernel you are using)
I’m pretty sure systemd-boot had nothing to do with the issue so reinstalling it was not necessary.