On 2020-09-11 07:26, ktono via qubes-users wrote: > I have a Qubes 4.0.3 setup that uses an NVMe SSD for storage and boots using > UEFI. My motherboard has 2 NVMe slots, so I still had one free slot. > Everything worked fine on Qubes. > > Then, I decided to install a second NVMe SSD (the same model). After doing > that, booting Qubes only puts me into Dracut Emergency Shell. > > The error messages I get: > > ``` > So I think Qubes is trying to boot with the new, empty SSD or something like > that. > Hi,
Have you tried switching the hard disks slots? Are you using direct EFI or GRUB? > When I use a Qubes USB installer to get a shell, I can still find my old SSD. When I do `cryptsetup open /dev/nvme<...>` on my old SSD, I can then `fdisk -l` to find the names of all my AppVMs, etc., so it's not like the space was wiped. What numbers has your old disk assigned? Theorically the boot hard disk uuid is passed as kernel argument: "rd.luks.uuid=......" So a change with major/minor numbers should not affect. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8610fd70-df72-a0a8-3cad-30360f08a81a%40riseup.net.
