Reporting back:
"sudo vgck -t vg" reports that no changes would be made, it seems to be looking in /dev/sda rather than /dev/nvme0n1.
"sudo vgscan" first reports that /dev/sda open failed and then successfully detects the vg using metadata type lvm2.
Reporting back:
"sudo vgck -t vg" reports that no changes would be made, it seems to be looking in /dev/sda rather than /dev/nvme0n1.
"sudo vgscan" first reports that /dev/sda open failed and then successfully detects the vg using metadata type lvm2.