Can't mount 2nd partition of old VM drive

[NoctOs]

So I'm trying to mount two old HDD's which used to sit in my old Proxmox v3 node so I can extract some files that one VM had on it.

The first HDD went fine, I used # kpartx -a /dev/MediaAux/vm-210-disk-1 to map it then I did # mount /dev/mapper/MediaAux-vm--210--disk--1p1 /mnt/oldnfs/ to mount it and it worked fine, lovely.

Now when I did the same for my other HDD kpartx mapped two partitions:

vg_media01-vm--210--disk--1p1 : 0 2097152 /dev/vg_media01/vm-210-disk-1 2048
vg_media01-vm--210--disk--1p2 : 0 3904894976 /dev/vg_media01/vm-210-disk-1 2099200

The first "p1" is of type xfs and could be mounted like normal but the other one "p2" is of type "LVM2_member" so I can't mount it

# blkid /dev/mapper/vg_media01-vm--210--disk--1p*
/dev/mapper/vg_media01-vm--210--disk--1p1: UUID="9db07863-1495-46f1-b61c-4c43fe0cff9e" TYPE="xfs" PARTUUID="000bacd4-01"
/dev/mapper/vg_media01-vm--210--disk--1p2: UUID="AF2XjX-gvUe-c4Ix-md0p-1bWd-DayP-DdsvAS" TYPE="LVM2_member" PARTUUID="000bacd4-02"

# mount /dev/mapper/vg_media01-vm--210--disk--1p2 /mnt/oldnfs4/
mount: /mnt/oldnfs4: unknown filesystem type 'LVM2_member'.

From my googling this usually happens becuase two VGs have the same name or because the LV is inactive.
There doesn't seem to be any duplicate VGs and lvscan shows that it's active.

# pvscan
  PV /dev/sde1   VG vg_media01      lvm2 [<1.82 TiB / 12.00 MiB free]
  PV /dev/sdb1   VG MediaAux        lvm2 [<1.82 TiB / 12.00 MiB free]
  Total: 2 [<3.64 TiB] / in use: 2 [<3.64 TiB] / in no VG: 0 [0   ]

# lvscan
  ACTIVE            '/dev/vg_media01/vm-210-disk-1' [<1.82 TiB] inherit
  ACTIVE            '/dev/MediaAux/vm-210-disk-1' [<1.82 TiB] inherit

I'm sure I'm misunderstanding how these file-systems work, if any gurus out there mind explaining how I'm supposed to do this then I would be eternally grateful

 

[NoctOs]

After a lot of googling and testing I remembered something dumb... like really dumb. "Didn't I have an encrypted partition on this partition?"

Yeah, it was just encrypted and now it works after opening it with cryptsetup.