Steps to produce:
I did a fresh reinstall of Qubes Release 4.0.3 from a backup and I was then able to login without problem.
Then, I installed Windows on another “disk” (see more context here below). All went fine.
When I wanted to boot my machine on Qubes, Qubes asked for my password.
Unusual long period of time after entering my password.
Error messages come:
[long colums of numbers] preceding…
Could not boot. /dev/disk/by-id/md-uuid-xxxxxxxxxxxx does not exist Starting Dracut Emerg ncy Shell... Warning: /dev/disk/by-id/md-uuid-xxxxxxxxxxxx does not exist Generating "/run/initramfs/rdsosreport.txt"` Entering emergency mode. Exit the shell to continue. Type "journalctl" 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. dracut:/#
If I type
ls -l /dev/disk/by-id/, I can indeed see that
md-uuid-xxxxxxxxxxxxis not present.
dracut:/#invite makes Qubes going on booting and, at very first sight, things look normal.
I have 2 SSD in RAID0. On this RAID0, I created two volumes. Qubes was installed on the biggest and then Windows on the smallest.
“Qubes devices / View and manage devices” icon to attach drives and USB sticks to VMs:
It seems to me that there are now more entries in this tool than before the Windows installation. I can now see things like:
dom0: md126 - ()
dom0: md126p1 - ()
dom0: md126p2 - ()
Do I have GRUB or EFI?
I guess I have only EFI since I only have:
[xxxxx@dom0 ~]$ ls /boot/grub/ splash.xpm.gz [xxxxx@dom0 ~]$ ls /boot/grub2/ themes [xxxxx@dom0 ~]$
… but I have I have a full
- Could you help me define what happened?
- What should I do to fix the problem?
- Will there be after-effects?
I don’t know what I got into, so your help is greatly appreciated. Thank you!