Emergency Dracut Shell errors. Boot Drive unable to login to Qubes OS

Hi @lovely, welcome to the Community!

Just guessing. Did you attempt to restore your installation with the using a Qubes USB stick?

@fsflover I tried that. It does the same thing. How do you recommend restoring it? it goes to the same shell screen

I tried rescue a qubes os system.

Should I try troubleshooting? do we have next steps for each of these processes? I’m willing to pay someone for the help.

@fsflover I performed the qubes os system step and it asks for my password then after it will say “you dont have any partitions. Rebooting”

I loaded the hard drive with the qubes os installation onto a computer with gparted and here is the report:

/dev/sdc1 = EFI System partition Fat32 600mib (7.89 mib used) flags = boot; esp
/dev/sdc2 | file system: ext4 | 1 gib
/dev/sdc3 [Encrypted lvm2 pv | mount point = qubes_dom0 | 181.76 gib
unallocated | 1.00 mib

I am willing to pay $50 + tip in btc to whomever can give me 1on1 support to solve this issue.

1 Like

Unfortunately this is beyond my level of expertise. All I can do is to point out to a couple of semi-relevant threads:

I am willing to pay $50 + tip in BTC to anyone who can provide 1on1 support to solve this ASAP.

My other thread isn’t getting any user support.

I get the errors in shell after the gui boot screen:

“Warning: /dev/qubes_dom0/root does not exist”

“Warning: Not all disks have been found.”

“Warning: You might want to regenerate your initramfs”

/dev/qubes_dom0/swap does not exist

crypto LUKS UUID ****************** (long character string) not found

I loaded the hard drive with the qubes os installation onto a computer with gparted and here is the report:

/dev/sdc1 = EFI System partition Fat32 600mib (7.89 mib used) flags = boot; esp
/dev/sdc2 | file system: ext4 | 1 gib
/dev/sdc3 [Encrypted lvm2 pv | mount point = qubes_dom0 | 181.76 gib
unallocated | 1.00 mib

Even in such case, you should not create new topics for the same problem. Every new post in your original thread puts it to the top of Qubes OS Forum, so if anyone can help, they should already see it. I’m merging this thread to there to help other users find (future) solution more easily.

I need your help @tanky0u and willing to pay in xmr please assist!

@BEBF738VD and @51lieal can you guys help me out with this?

Hi,
please let me understand…
If You boot from usb , get a recovery shell and try lsblk /dev/sdc3, what’s the UUID You get?
Cheers,
M.

1 Like

I think Mila is on the right track – my question would be:

Does the output from[1]

lsblk /dev/sdc3 | grep luks

match what GRUB has as

rd.luks.uuid=luks-...

?

[1] Adjust sdc3 to match the name of your drive.

1 Like

@mila It says “not a block device” when typing lsblk /dev/sdc3 in shell using recovery

@ChrisA

same thing when i type in: lsblk /dev/sdc3 | grep luks

"not a block device"

I checked gparted in a different linux distro, and these are the /dev’s i found below

/dev/sdc1 = EFI System partition Fat32 600mib (7.89 mib used) flags = boot; esp
/dev/sdc2 | file system: ext4 | 1 gib
/dev/sdc3 [Encrypted lvm2 pv | mount point = qubes_dom0 | 181.76 gib
unallocated | 1.00 mib

Did remember to check/adjust the name of the drive?

1 Like

how do i find the name of my drive. I don’t remember my name. the Label name? the label name was New G thats the option that I get when I go into boot manager and it lets me select windows or New G (aka Qubes OS)

Oh - the name is /dev/sdc3 … can you try a plain:

lsblk 

?

with lsblk here is what i found
name sdb 183gb 0 disk
sdb1 600mb
sdb2 1gb
sdb3 | SIZE 181 gb
sdc 20gb disk /run/install/repo

In that case, I think you are looking for

lsblk /dev/sdb3
2 Likes

ok that worked.
It says:
sdb3 MAJ:MIN 8:19 RM: 1 size: 181.8G RO: 0 type: part Mountpoint: ( it is empty here )

I tried the second command: lsblk /dev/sdb3 | grep luks
it doesn’t display anything.

I had to check from another machine - try with:

blkid | grep -i luks

and try:

mkdir -p /mnt/foo
mount /dev/sda1 /mnt/foo
grep luks /mnt/foo/EFI/qubes/grub.cfg

– the first should give you the UUID of the encrypted volume - the second should show you the UUID that the machine looks for on boot – are they identical?

2 Likes