New local LVM HDD is showing 0 space available

[biddy]

I recently added a 2TB WD Red HDD to my household machine running ProxmoxVE. My present goal is to pass the 2TB to the Openmediavault NAS VM I am running and use it for household media purposes. I added the hdd to a new volume group via the command line and then with the WebGUI I added the storage to Proxmox. The volume shows up and registers as the correct size, but Proxmox reports it as 0 space available.

Here's the output of cat /etc/pve/storage.cfg

dir: local
        path /var/lib/vz        content images,iso,vztmpl,rootdir
        maxfiles 0

lvm: data
        vgname seagate-drive
        shared
        content images

dir: images
        path /mnt
        content images
        maxfiles 4

dir: BACKUPS
        path /media/passport-backups
        shared
        content backup
        maxfiles 4

lvm: wd-red
        vgname wd-red
        shared
        content images

Here's the output of df -h:

Filesystem            Size  Used Avail Use% Mounted on
udev                   10M     0   10M   0% /dev
tmpfs                 1.6G  508K  1.6G   1% /run
/dev/mapper/pve-root   12G  1.5G  9.8G  14% /
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 3.2G   22M  3.2G   1% /run/shm
/dev/mapper/pve-data  193G   76G  118G  39% /var/lib/vz
/dev/sda1             495M   58M  412M  13% /boot
/dev/fuse              30M   16K   30M   1% /etc/pve
/dev/sdd1             1.9T  1.2T  684G  64% /media/passport-backups

I'm not seeing the wd-red in the df -h command, is there a step I missed when adding the disk via LVM?

 

[udo]

Hi,
lvm hasn't an filesystem per default - lvm support block devices (like an hdd) on which you can create an filesystem - or use the LV for an VM as hdd. This is mean by lvm: + content images.

To understand see the output of

pvs
vgs
lvs

100% full of an VG mean, that you use all space with an LV?!

Udo