pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 pve lvm2 a-- 237.97g 15.99g
/dev/sda datastore2 lvm2 a-- 894.25g 95.25g
vgs
VG #PV #LV #SN Attr VSize VFree
datastore2 1 8 0 wz--n- 894.25g 95.25g
pve 1 4 0 wz--n- 237.97g 15.99g
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vm-100-disk-0 datastore2 -wi-ao---- 130.00g
vm-102-disk-0 datastore2 -wi-ao---- 80.00g
vm-103-disk-0 datastore2 -wi-ao---- 25.00g
vm-103-disk-1 datastore2 -wi-ao---- 150.00g
vm-104-disk-0 datastore2 -wi-ao---- 200.00g
vm-105-disk-0 datastore2 -wi-ao---- 100.00g
vm-107-disk-0 datastore2 -wi-a----- 64.00g
vm-108-disk-0 datastore2 -wi-a----- 50.00g
data pve twi-aotz-- <151.63g 19.72 1.97
root pve -wi-ao---- 59.25g
swap pve -wi-ao---- 8.00g
vm-101-disk-0 pve Vwi-aotz-- 30.00g data 99.68
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 894.3G 0 disk
├─datastore2-vm--100--disk--0 253:0 0 130G 0 lvm
├─datastore2-vm--103--disk--0 253:1 0 25G 0 lvm
├─datastore2-vm--103--disk--1 253:2 0 150G 0 lvm
├─datastore2-vm--102--disk--0 253:3 0 80G 0 lvm
├─datastore2-vm--104--disk--0 253:4 0 200G 0 lvm
├─datastore2-vm--105--disk--0 253:5 0 100G 0 lvm
├─datastore2-vm--107--disk--0 253:6 0 64G 0 lvm
└─datastore2-vm--108--disk--0 253:7 0 50G 0 lvm
sdb 8:16 0 476.9G 0 disk
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 512M 0 part /boot/efi
└─nvme0n1p3 259:3 0 238G 0 part
├─pve-swap 253:8 0 8G 0 lvm [SWAP]
├─pve-root 253:9 0 59.3G 0 lvm /
├─pve-data_tmeta 253:10 0 1.6G 0 lvm
│ └─pve-data-tpool 253:12 0 151.6G 0 lvm
│ ├─pve-data 253:13 0 151.6G 1 lvm
│ └─pve-vm--101--disk--0 253:14 0 30G 0 lvm
└─pve-data_tdata 253:11 0 151.6G 0 lvm
└─pve-data-tpool 253:12 0 151.6G 0 lvm
├─pve-data 253:13 0 151.6G 1 lvm
└─pve-vm--101--disk--0 253:14 0 30G 0 lvm
Volume group "vgname" not found
Cannot process volume group vgname
Volume group "datastore3" not found
Cannot process volume group datastore3
Here is the resultIt is missing from all of the outputs. Is "sdb" the underlying device for datastore3? If it is - it seems to be missing LVM signatures.
Check "fdisk -l /dev/sdb", as well as "journalctl |egrep "datastore3|sdb" " for any errors in activation.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
fdisk -l /dev/sdb
Disk /dev/sdb: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: KINGSTON SKC6005
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Feb 20 12:14:29 BCScloud lvm[565]: 3 logical volume(s) in volume group "datastore3" monitored
Feb 20 12:14:29 BCScloud lvm[831]: pvscan[831] PV /dev/sdb online, VG datastore3 is complete.
Feb 20 12:14:29 BCScloud lvm[831]: pvscan[831] VG datastore3 skip autoactivation.
Feb 20 12:27:28 BCScloud lvm[4972]: pvscan[4972] /dev/sdb not an lvm device.