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.
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.
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.
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.
@mila It says “not a block device” when typing lsblk /dev/sdc3 in shell using recovery
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?
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
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?
Wow thanks for taking the time to help out with another machine.
THE UUID’s are not identical. one is a PARTUUID and the other is the UUID.
Should I proceed with the mkdir steps?
PARTUUID and UUID should differ … the grep tells you what the machine is actually looking for on boot … does that match the UUID?
the grep didn’t identify a matching UUID. next to the first UUID it says type=“crypto_LUKS” after typing in command: blkid | grep -i luks
should I reboot and see if I see the UUID on boot?