Hi, im new here. I have limited experience with ssh, bash etc. Ive been using qubes os for about 2 months now and it was working pretty good except a few wierd errors. My backups had issues. They got stuck at 100%. When i tried to verify the backups i also got errors. Im still testing this out so nothing too important was on it so i didnt think twice about the backup errors.
However the real problems started happening when just now while i was installing snap store to my debian-11 template while running a backup simutaneously… the terminal said the installation was successful but i was unable to create an appvm based off template. It gave my errors saying dom0 couldnt create vm. I thought a restart would do the trick… boy was i wrong…
Im able to enter my password to unlock LUKS but it throws me this error shortly after everytime.
Thankfully not much important information is lost. But ive spent the last 2 months playing with different configurations to see what works best. Ive left notes on which configs i like best but a lot of it hasnt been backed up
Id appreciate some help
Other information: i have dual boot on with windows (veracrypt). Secure boot is off. My windows os is running fine
A quick & dirty workaround for anyone stumbled on this
A really quick & dirty ad-hoc workaround would be to rename all find_existing_installations to _find_existing_installations in the /usr/lib*/python*/site-packages/pyanaconda/rescue.py file and then re-run anaconda rescue: anaconda --rescue --lang us
I would like to do this but all I can find is /usr/lib64/python3.8/site-package/pyanaconda/rescue.py without _find_existing_installations. There is such a file under /usr/lib64/python3.8/site-package/pyanaconda/modules/storage/devicetree/rescue.py but even when appending an underscore before the function and resetting anaconda, there is nothing under /mnt/sysimage.
Hey, first off… apologies for untimely response. The law firm has been busy.
I wasnt able to copy the rdosreport because qubes wasnt able to detect my usb. I followed some instructions on another thread that said to type in ‘blkid’. I have tried re formatting the disk to NFTS, exfat, fat etc. No luck
So i tried something from another thread with someone with a similar problem. See below.
I clicked ‘e’ and removed ‘quiet’ and edited the rd.luks… as per instructed above. Then clicked ctl +x to reboot in verbose. Please see screenshot for result
The following showed up. I tried blkid again but the result was the same. Then i plugged my usb in and it seemed it was found but not authorized for use. Trying blkid again, yielded the same result unfortunately.
Someone suggested this issue came up with having two different drives in the laptop.
I know in previous versions of Qubes I had problems with having an OS on both drives, so I blanked the second one, and it allowed it to function. I have thought of opening my laptop and unplugging the drive I am not using now. Anyone have thoughts if that might work?
I have an Alienware 15 R2 which has Qubes on one drive and another OS on the second drive.
Someone suggested that the problem is actually in Python? What is on Line 19.
I am not much help in this, but I thought if I added symptoms someone might find a common factor. ??