Subject: Unable to Recognize Previous LVM Disk After Proxmox Reinstallation

[maria13old]

Hello,

I recently reinstalled Proxmox VE on my system disk, and I'm encountering an issue where Proxmox is unable to recognize the LVM disk from the previous installation that contains my virtual machines. Here's a summary of my situation:

• The system disk was successfully reinstalled, and Proxmox is operational.
• The disk containing the virtual machines (nvme1n1) is visible in the system when using the lsblk command, but it does not appear in the LVM management commands (pvs, vgdisplay).
• The output of lsblk shows the disk (nvme1n1) and its partition (nvme1n1p1), but it seems that the partition is not recognized as a physical volume by LVM.
• I attempted to initialize the partition as a physical volume using pvcreate /dev/nvme1n1p1, but it did not resolve the issue.

Here is the output of lsblk:

luaCopy code
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme2n1 259:0 0 465.8G 0 disk
├─nvme2n1p1 259:3 0 1007K 0 part
├─nvme2n1p2 259:4 0 1G 0 part /boot/efi
└─nvme2n1p3 259:5 0 464.8G 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 96G 0 lvm /
├─pve-data_tmeta 252:2 0 3.4G 0 lvm
│ └─pve-data-tpool 252:6 0 337.9G 0 lvm
│ ├─pve-data 252:7 0 337.9G 1 lvm
│ ├─pve-vm--100--disk--0 252:8 0 4M 0 lvm
│ ├─pve-vm--100--disk--1 252:10 0 32G 0 lvm
│ └─pve-vm--100--disk--2 252:11 0 4M 0 lvm
└─pve-data_tdata 252:4 0 337.9G 0 lvm
└─pve-data-tpool 252:6 0 337.9G 0 lvm
├─pve-data 252:7 0 337.9G 1 lvm
├─pve-vm--100--disk--0 252:8 0 4M 0 lvm
├─pve-vm--100--disk--1 252:10 0 32G 0 lvm
└─pve-vm--100--disk--2 252:11 0 4M 0 lvm
nvme0n1 259:1 0 465.8G 0 disk
├─red5002-red5002_tmeta 252:3 0 4.7G 0 lvm
│ └─red5002-red5002 252:9 0 456.3G 0 lvm
└─red5002-red5002_tdata 252:5 0 456.3G 0 lvm
└─red5002-red5002 252:9 0 456.3G 0 lvm
nvme1n1 259:2 0 1.8T 0 disk
└─nvme1n1p1 259:6 0 1.8T 0 part

I'm seeking advice on how to properly recognize and utilize

 

[Kingneutron]

> I attempted to initialize the partition as a physical volume using pvcreate /dev/nvme1n1p1, but it did not resolve the issue.

#1 question: Do you have backups?? Not sure, but pvcreate may have wiped data; I'm afraid this might be a TIFU moment...

From ' man pvcreate '
[[
pvcreate initializes a Physical Volume (PV) on a device so the device is recognized as belonging to LVM. This allows the PV to be used in a Volume Group (VG). An LVM disk label is written to the device, and LVM metadata areas are initialized.
]]

#2 question: Did you try ' vgchange -a y ' ?

 

[maria13old]

root@maria13old:~# vgchange -a y
6 logical volume(s) in volume group "pve" now active
root@maria13old:~#

but,no Dislks unused