Here, i will name as follows:
pool_SSD2 - thin pool on secondary SSD, where you invisible logical volumes with existing data are. In Qubes guide example, they call it “poolhd0”.
SSD2 - pool name as it will appear in Disk Space Monitor, under the hard drive icon in upper right corner of your Qubes desktop. In the guide, they call it “poolhd0_qubes”.
VG_SSD2 - volume group on secondary SSD.
So, before the OS migration, record the UUID of your secondary SSD by sending it to file you save outside the old dom0:
sudo pvs > pvs_backup.txt
In the file, will be something like this with numbers instead of XXXs:
PV VG Fmt Attr PSize PFree
/dev/mapper/luks-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX qubes_dom0 lvm2 a-- 952.85g <95.99g
/dev/mapper/sda2-luks-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX VG_SSD2 lvm2 a-- <930.51g 15.77g
Once in the new OS, add the UUID of the secondary SSD back into the /etc/crypttab file on the last line, in the same format as the one above for the primary SSD. It will look something like this with numbers instead of XXXs:
luks-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX none discard
sda2-luks-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX none
Reboot to unlock the secondary SSD encryption.
Then add the pool on the secondary SSD with the command as in the guide:
qvm-pool --add SSD2 lvm_thin -o volume_group=VG_SSD2,thin_pool=pool_SSD2,revisions_to_keep=2
Now your secondary SSD logical volumes will be visible to Qubes OS.
Next, to get them registered again properly with qubesd in dom0:
First, grep to be clear which domains are on secondary SDD that you will need to rename. Grep for the virtual group:
sudo lvs | grep VG_SSD2
You will see a listing for the whole pool. The logical volumes will be listed along with their revision backups in the leftmost column. Something like this:
Now you are ready to create new LVs and rename them.
For the template-based qubes, the root LV is created by default in the dom0 pool on the primary SSD. So, it is not visible in the secondary SSD pool.
Create new blank qube for the standalone:
qvm-create --standalone --label red -P SSD2 My_NEW_Standalone_qube
For a template-based qube, would be:
qvm-create --template <your_template_name> --label red -P SSD2 My_NEW_TemplateBased_qube
Check to make sure which LVs you have to remove:
sudo lvs | grep VG_SSD2 | grep NEW
Next, to delete these NEW blank qubes’s logical volumes and their backup.
!!!Be careful!!! Don’t delete your existing data volumes by mistake.
sudo lvremove VG_SSD2/vm-My_NEW_Standalone_qube-private
sudo lvremove VG_SSD2/vm-My_NEW_Standalone_qube-private-1601010101-back
sudo lvremove VG_SSD2/vm-My_NEW_Standalone_qube-root
sudo lvremove VG_SSD2/vm-My_NEW_Standalone_qube-root-1601010101-back
Don’t try to start the new qube at this point just to see what happens. It will lead to qube hanging and being difficult to shut down.
Check to make sure you removed all of them. You should not see any listed:
sudo lvs | grep VG_SSD2 | grep NEW
Now, rename your old LVs to new:
sudo lvrename VG_SSD2 vm-My_Standalone_qube-private vm-My_NEW_Standalone_qube-private
sudo lvrename VG_SSD2 vm-My_Standalone_qube-private-1601010101-back vm-My_NEW_Standalone_qube-private-1601010101-back
sudo lvrename VG_SSD2 vm-My_Standalone_qube-private-1601010100-back vm-My_NEW_Standalone_qube-private-1601010100-back
sudo lvrename VG_SSD2 vm-My_Standalone_qube-root vm-My_NEW_Standalone_qube-root
sudo lvrename VG_SSD2 vm-My_Standalone_qube-root-1601010101-back vm-My_NEW_Standalone_qube-root-1601010101-back
sudo lvrename VG_SSD2 vm-My_Standalone_qube-root-1601010100-back vm-My_NEW_Standalone_qube-root-1601010100-back
Check to make sure you renamed all of them. You should not see any listed:
sudo lvs | grep VG_SSD2 | grep My_Stand
Now ready to start the qube from Qube Manager and rename it back to its original name, if you wish, and adjust whatever needed.
Repeat the procedure for template-based qubes, but you will not need to remove or rename their root logical volumes, because they are on the dom0 pool in the primary SSD.