Before upgrade I have one VM at second drive (storage pool).
Now, I can’t start it:
volume qubes_dom0/vm-XXXX-private missing
What possible to do? How to restore it (change pool)? Sorry, don’t know a lot about storage pools at qubes.
EDIT: qvm-prefs don’t have anything about storage “pool”.
sudo pvs show me that i have 2 pools, but AppVM don’t have this settings.
Don’t see it at qubes-manages settings also
EDIT: I found with sudo lvdisplay the path…
After that sudo mount /dev/qubes/vm-XXXX-private /mnt/ttt cd /mnt/ttt/ and i see my files…
The question how to restore my VM with this private image(?)… Seems need to change pool for this VM. How to do this
Could you describe your setup more in depth? I don’t really understand what you did exactly, something stopped working but what does it mean “one VM at a second storage pool”?
I have 2 SSDs.
One main SSD has Qubes and all AppVMs. The second SSD (thin pool) is for storage for one AppVM with a large amount of data in it. After the upgrade, it’s not possible to start the AppVM from the second SSD. As described above, the vm-XXXX-private file is present on the second SSD, but the AppVM, after the upgrade, searches for it at some other location (I guess).
I found that at /var/lib/qubes/qubes.xml for this qube all volume settings were lost.
Now, it point to main pool (vm-pool) by mistake and parameters “revisions_to_keep” also lost, it was set to 1(0) before update…
should I edit this file manually now (at least path) and reboot or how to force qubes re-read the file and/or apply new settings with correct path?
Is there any other places where I should edit thinpool for this appvm?
Interesting that at sudo lvs -av it have right thinpool for this qube (second pool as expected), but at qubes.xml as said before everything wrong.