Updated and now no VMs will load: Duplicate VG name

kn2mUc

New Member
Jan 30, 2016
23
0
1
41
Im new to Proxmox and recently created a single machine setup booting forma Intel 750 nvme drive running a few basic services to test with. Everything was going well until I tried passing through my motherboard (x9srl-f) SATA controller, it didn't work so I tried updating the 'kernel' file from the GUI > Updates option and rebooted in the hope it might resolve some bug but it caused my VMs to stop booting. To remove any dependancies I then upgraded all the out of date parts and rebooted again. Still no luck. I need to go and learn more about proxmox but wondered is there an easy way to get back from here?


Code:
WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
WARNING: Duplicate VG name pve: Existing LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3 (created here) takes precedence over rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ
WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
kvm: -drive file=/dev/pve/vm-100-disk-1,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/pve/vm-100-disk-1': No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=60b6021a-317f-4689-b884-0a693d25a580' -name leecher -smp '4,sockets=4,cores=1,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 8192 -k en-us -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:3f4311333688' -drive 'file=/var/lib/vz/template/iso/cbpp-1.0-amd64-20150428.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/dev/pve/vm-100-disk-1,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=32:65:63:32:65:32,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

ls of the missing folder shows the following

Code:
# ls -l /dev/pve
total 0
lrwxrwxrwx 1 root root 7 Aug 17 00:08 data -> ../dm-4
lrwxrwxrwx 1 root root 7 Aug 17 00:08 root -> ../dm-0
lrwxrwxrwx 1 root root 7 Aug 17 00:08 swap -> ../dm-1


package version

Code:
Proxmox Virtual Environment 4.2-17/e1400248
Node 'proxmox'
Logs
()
proxmox-ve: 4.2-60 (running kernel: 4.4.15-1-pve)
pve-manager: 4.2-17 (running version: 4.2-17/e1400248)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.15-1-pve: 4.4.15-60
lvm2: 2.02.116-pve2
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-43
qemu-server: 4.0-85
pve-firmware: 1.1-8
libpve-common-perl: 4.0-71
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-56
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6-1
pve-container: 1.0-72
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.3-4
lxcfs: 2.0.2-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80


and a screenshot of the error during boot process

proxmox.png

and the corresponding sysctl status lvm2-activation-early.service error

proxmox2.png

thanks for any pointers in advance,
 
Does this shed any further light?

Code:
# lvscan -a -v
    Using logical volume(s) on command line.
    Finding all volume groups.
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3 (created here) takes precedence over rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ
  ACTIVE            '/dev/pve/swap' [8.00 GiB] inherit
  inactive          '/dev/pve/root' [96.00 GiB] inherit
  ACTIVE            '/dev/pve/data' [811.39 GiB] inherit
  ACTIVE            '/dev/pve/data_tdata' [811.39 GiB] inherit
  ACTIVE            '/dev/pve/data_tmeta' [104.00 MiB] inherit
  inactive          '/dev/pve/lvol0_pmspare' [104.00 MiB] inherit
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  inactive          '/dev/pve/swap' [8.00 GiB] inherit
  ACTIVE            '/dev/pve/root' [96.00 GiB] inherit
  inactive          '/dev/pve/data' [997.69 GiB] inherit
  inactive          '/dev/pve/vm-101-disk-1' [32.00 GiB] inherit
  inactive          '/dev/pve/vm-101-state-Snapshot1' [1.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-101-disk-1_Snapshot1' [32.00 GiB] inherit
  inactive          '/dev/pve/vm-103-state-first_snap' [8.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-103-disk-1_first_snap' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-103-state-taketwo' [8.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-103-disk-1_taketwo' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-103-disk-1' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-103-state-takethree' [8.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-103-disk-1_takethree' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-100-disk-1' [256.00 GiB] inherit
  inactive          '/dev/pve/vm-100-state-baseline' [16.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-100-disk-1_baseline' [256.00 GiB] inherit
  inactive          '/dev/pve/vm-100-state-take2' [16.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-100-disk-1_take2' [256.00 GiB] inherit
  inactive          '/dev/pve/vm-100-state-take3' [16.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-100-disk-1_take3' [256.00 GiB] inherit
  inactive          '/dev/pve/vm-100-state-take4' [16.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-100-disk-1_take4' [256.00 GiB] inherit
  inactive          '/dev/pve/snap_vm-102-disk-1_baseline' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-102-state-take2' [2.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-102-disk-1_take2' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-102-disk-1' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-102-state-take3' [4.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-102-disk-1_take3' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-102-state-take4' [4.49 GiB] inherit
  inactive          '/dev/pve/snap_vm-102-disk-1_take4' [8.00 GiB] inherit
  inactive          '/dev/pve/data_tdata' [997.69 GiB] inherit
  inactive          '/dev/pve/data_tmeta' [128.00 MiB] inherit
  inactive          '/dev/pve/lvol0_pmspare' [128.00 MiB] inherit


Code:
# fdisk -l

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 313AB020-9B39-4E5C-A87A-27831D8F1AB0

Device      Start        End    Sectors   Size Type
/dev/sda1      34       2047       2014  1007K BIOS boot
/dev/sda2    2048     262143     260096   127M EFI System
/dev/sda3  262144 1953525134 1953262991 931.4G Linux LVM

Partition 2 does not start on physical sector boundary.


Disk /dev/nvme0n1: 1.1 TiB, 1200243695616 bytes, 2344225968 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6490C7DB-0295-48B0-99AF-09D89E50E3BA

Device          Start        End    Sectors  Size Type
/dev/nvme0n1p1     34       2047       2014 1007K BIOS boot
/dev/nvme0n1p2   2048     262143     260096  127M EFI System
/dev/nvme0n1p3 262144 2344225934 2343963791  1.1T Linux LVM

Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Code:
# blkid
/dev/sda1: PARTUUID="b75fd627-4886-4a20-a655-2ffbd978a691"
/dev/sda2: UUID="D503-BBAE" TYPE="vfat" PARTUUID="df6e83d7-a29b-4235-9b6f-726b937a0c49"
/dev/sda3: UUID="DviJ1S-RTT9-kZI9-j3qD-recI-RRu3-ud2WsI" TYPE="LVM2_member" PARTUUID="69634cc0-a54d-4a6a-bbcf-a816d47631c5"
/dev/nvme0n1: PTUUID="6490c7db-0295-48b0-99af-09d89e50e3ba" PTTYPE="gpt"
/dev/nvme0n1p1: PARTUUID="632b17ef-db7c-4f03-b74f-d916ca0634c4"
/dev/nvme0n1p2: UUID="3A44-65A3" TYPE="vfat" PARTUUID="ddee5697-631d-4cdb-9ba8-ba72257f2e78"
/dev/nvme0n1p3: UUID="EcvBuE-WLEE-NrmK-Au86-vff2-jn3j-SXcZvG" TYPE="LVM2_member" PARTUUID="20107809-12da-4b79-9374-8374bd8e1e9f"
/dev/mapper/pve-root: UUID="3a280aa1-940a-4d09-8cfa-bd6d7ac8876d" TYPE="ext4"
/dev/mapper/pve-swap: UUID="9679b040-cd32-4318-aa6a-0c5245fbf89d" TYPE="swap"
 
Code:
# lvs
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3 (created here) takes precedence over rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  LV                            VG   Attr       LSize   Pool Origin                     Data%  Meta%  Move Log Cpy%Sync Convert
  data                          pve  twi-a-tz-- 811.39g                                 0.00   0.42
  data                          pve  twi---tz-- 997.69g
  root                          pve  -wi-------  96.00g
  root                          pve  -wi-ao----  96.00g
  snap_vm-100-disk-1_baseline   pve  Vri---tz-k 256.00g data vm-100-disk-1
  snap_vm-100-disk-1_take2      pve  Vri---tz-k 256.00g data vm-100-disk-1
  snap_vm-100-disk-1_take3      pve  Vri---tz-k 256.00g data vm-100-disk-1
  snap_vm-100-disk-1_take4      pve  Vri---tz-k 256.00g data vm-100-disk-1
  snap_vm-101-disk-1_Snapshot1  pve  Vri---tz-k  32.00g data vm-101-disk-1
  snap_vm-102-disk-1_baseline   pve  Vri---tz-k   8.00g data
  snap_vm-102-disk-1_take2      pve  Vri---tz-k   8.00g data
  snap_vm-102-disk-1_take3      pve  Vri---tz-k   8.00g data vm-102-disk-1
  snap_vm-102-disk-1_take4      pve  Vri---tz-k   8.00g data vm-102-disk-1
  snap_vm-103-disk-1_first_snap pve  Vri---tz-k   8.00g data
  snap_vm-103-disk-1_takethree  pve  Vri---tz-k   8.00g data vm-103-disk-1
  snap_vm-103-disk-1_taketwo    pve  Vri---tz-k   8.00g data
  swap                          pve  -wi-ao----   8.00g
  swap                          pve  -wi-------   8.00g
  vm-100-disk-1                 pve  Vwi---tz-- 256.00g data
  vm-100-state-baseline         pve  Vwi---tz--  16.49g data
  vm-100-state-take2            pve  Vwi---tz--  16.49g data
  vm-100-state-take3            pve  Vwi---tz--  16.49g data
  vm-100-state-take4            pve  Vwi---tz--  16.49g data
  vm-101-disk-1                 pve  Vwi---tz--  32.00g data
  vm-101-state-Snapshot1        pve  Vwi---tz--   1.49g data
  vm-102-disk-1                 pve  Vwi---tz--   8.00g data snap_vm-102-disk-1_take2
  vm-102-state-take2            pve  Vwi---tz--   2.49g data
  vm-102-state-take3            pve  Vwi---tz--   4.49g data
  vm-102-state-take4            pve  Vwi---tz--   4.49g data
  vm-103-disk-1                 pve  Vwi---tz--   8.00g data snap_vm-103-disk-1_taketwo
  vm-103-state-first_snap       pve  Vwi---tz--   8.49g data
  vm-103-state-takethree        pve  Vwi---tz--   8.49g data
  vm-103-state-taketwo          pve  Vwi---tz--   8.49g data
 
I have no idea whats going on, clearly beyond my knowledge at the moment but incase there are any experts here want to investigate, using the advanced options I can successfully boot in version 4.4.13-1.pve but 4.4.15-1.pve fails to start the LVM2 module causing the device to fail to mount.
 
for some reason you have multiple volume groups which have the name 'pve' (at least it seems so)
can you please post the output of
Code:
pvs
vgs
 
I found the cause of the error, enabling the Supermicro X9SRL-F SCU which provides support to an additional four onboard SATA ports causes the error.
This is with the SCU ENABLED

Code:
# pvs
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  PV             VG   Fmt  Attr PSize   PFree
  /dev/nvme0n1p3 pve  lvm2 a--    1.09t 15.75g
  /dev/sda3      pve  lvm2 a--  931.39g 15.79g


Code:
# vgs
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  WARNING: Duplicate VG name pve: Existing LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3 (created here) takes precedence over rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ
  WARNING: Duplicate VG name pve: Existing rLBxZC-tQ0c-wzqw-CGfA-ray7-qvX9-wYYslZ (created here) takes precedence over LpSlGJ-2UHC-6kf1-LJEX-xIob-pBrF-AtYoI3
  VG   #PV #LV #SN Attr   VSize   VFree
  pve    1   3   0 wz--n- 931.39g 15.79g
  pve    1  28   0 wz--n-   1.09t 15.75g


This is with the SCU DISABLED

Code:
# pvs
  PV             VG   Fmt  Attr PSize PFree
  /dev/nvme0n1p3 pve  lvm2 a--  1.09t 15.75g

Code:
# vgs
  VG   #PV #LV #SN Attr   VSize VFree
  pve    1  28   0 wz--n- 1.09t 15.75g

Any ideas if theres a way to make this work, would be handy to have access to the four additional SATA ports if possible, otherwise I have to waste a PCI slot with a HBA.

Thank you for taking a look at my thread Dominik.
 
well the output shows me that there is a hard disk /dev/sda3 which also has a lvm volume group with name pve
do you have anything connected to the sata ports?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!