Extend vm-pool instead of adding another pool.
➕ : You don't need to juggle qubes between two pools like in the secondary storage setup.
➖ : Chances of data loss due to drive failure are higher.
Also, for encrypted setups I haven't figured out how to print what device is being unlocked during boot. It can be annoying, but it seems like system simply follows the order in /etc/crypttab. I tend to successfully guess it. Please help if you know anything about this.
Locate the device you want to add to the pool using lsblk or other tools.
pvcreate $device
vgextend $vg $device
lvextend -l +100%FREE $pool
$device is the device you want to add to the pool. Most likely partition on a physical device, like /dev/sdb1, /dev/nvme1p1, or /dev/mapper/mydevicename if you're using encrypted partition.$vg is the lvm volume group. You can list them using vgs. Most likely you have only one group. If you have more, you can deduct which one you need from outputs of pvs or lvs. See which group is used for qubes' lvs or to which group your existing qubes drive belongs to.$pool is the lvm pool to extend. vm-pool by default, but you can list logical volumes and pools using lvs, it will be listed in the "pool" column for logical volumes of your virtual machines as well as a separate entry.This is very flexible. As you can see, almost anything can be used as the $device, be it physical device, partition, or encrypted partition. Same with the pool, you can add different amount of volume to it, not necessarily all free space available in the volume group. See man lvextend.
The algorithm for encrypted partition is a bit different, follow secondary storage : Example setup of second drive until you end up with an auto-mounted luks partition, after that continue with the step 2.