EDIT:
This post/solution is helpful if:
Your system is installed on a USB HDD/SSD and
Your system does not start up after you enabled sys-usb
ORIGINAL:
Yesterday I enabled sys-usb. In hindsight, that was a bad idea since that caused my USB peripherals to detach and I wasn’t able to find my PS/2 mouse and keyboard. So I had to shut down the system ungracefully.
Today the decryption prompt did not show up and after a while I was confronted with this screen.
I have backups though. Is there a chance to repair the system or should I just reinstall? The LUKS partition looks healthy.
Did you install Qubes OS on a USB disk?
Yes! A sATA drive connected via USB3.
I see where this is going…
Disable qubes autostart so sys-usb won’t start on boot:
The following instructions are valid for Qubes OS R4.0 legacy mode and Qubes OS R4.1 legacy and UEFI modes. For Qubes OS R4.0 in UEFI mode, there is no GRUB, so manual boot from another operating system is needed. In several cases, there is a need to...
Also remove the rd.qubes.hide_all_usb
and usbcore.authorized_default=0
kernel command line options in GRUB if you have them.
Then check this:
Check if you have multiple USB controllers and they are available on the physical USB ports. If you have them then you can dedicate one of the USB controllers to dom0 and connect your USB disk to it and then use other USB controllers to create sys-usb.
Run this command in dom0 to see if there are multiple USB controllers available:
lspci | grep USB
Then check if there are different USB controllers connected to the different USB ports:
You can create sys-usb like this:
But in step 4 us…
Thank you for the great and quick support!