I have a dual-boot set up with Windows 10 on an internal SSD in my laptop and Garuda is hosted on an external SSD which I sometimes unplug.
I have had this issue for some time and I usually fix it by rebooting over and over until it works but this time it has not been successful.
I tried running a previous snapshot with no success
I tried running with fallback initramfs as well as recovery mode and I get the following:
[196.5574111] dracut-initqueue[462]: Warning: dracut-initqueue: starting timeout scripts
[196.558168] dracut-initqueue[462]: Warning: Could not boot.
Warning: /dev/disk/by-uuid/802f85f7-7c2c-4f8e-b049-c67c4202c3eb does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue.
Type "journalct1" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
Press Enter for maintenance
(or press Control-D to continue);
[318.7967391 dracut-initqueue[462]: Warning: Not all disks have been found.
[ 318.7982581 dracut-initqueue[462]: Warning: You might want to regenerate your initramfs.
Hi there, welcome to the forum!
If the problem is recurring and usually “solved” rebooting over and over, i’m afraid this could be due to a disk slowly dying (or maybe a loose SATA connector).
Anyway, you could try booting from a live USB, chroot into your system (if it works that would be a good sign) and try a
garuda-update
Additionally, if the update does not trigger it due to a kernel update, you could try a
I will try it when I’m home at night, but just wanted to mention some stuff:
Rebooting over and over doesn’t work any more
The SSD is relatively new (5 months) and last time I checked its health (1 month ago) it was in pristine condition. I can maybe check again with Windows.
I often run garuda-update, so I don’t think that would fix the issue.
Also, I don’t know how the whole booting from a live USB works and how that would/could let me access the OS on the external SSD any differently. If you could provide a link to a tutorial or something like that, I think that would help me.
The suggestion for a garuda-update was mainly for “good hygene”, in case a new update was available and especially if a kernel update was available, which would trigger a dracut-rebuild (which could anyway be launched manually), since your error seems to be related to the initial ramdisk not being loaded, and that one is generated by dracut.
Here is a tutorial about chroot, which does manually what is done with the dedicated button in the live USB (grub installation excluded):
