I'm an Idiot - New PVE Install - Old PVE LVM's

[Blueduck3285]

So I wanted to move my Proxmox install off of a drive that was connected to my HBA, to an PCIE NVME drive.

When I did that, the Proxmox installer asked to move my old date to PVE-OLD-XXXX. Well now I cannot access any of that info to move my VM's and associated connections to the new install.

Long story short, I had to do yet another new install on a USB SATA Drive as my server doesn't recognize the NVME drive as a bootable device.

So I am on new install 2, I can add drives from my old install as LVM's. that have data on them but cannot access it. They were a part of a zpool in my Truenas VM.

Here I am, a boy, standing in front of my service, needing access to those drives to keep working on my business files.

 

[leesteken]

Do you have backups of those VMs? Otherwise, their configuration can only be read from the old /etc/pve/qemu-server/ directory when the old Proxmox installation is succesfully started.
If you can create new empty VMs (with the same configuration, as you remember it) on the new LVM storage, you should be able to copy all the data of the old virtual disks to the new ones.
Maybe your can show the output of lsblk, vgscan and lvscan to give an idea of the organization of your drives with the new/current Proxmox installation (with the old drive attached)?

 

[Blueduck3285]

Do you have backups of those VMs? Otherwise, their configuration can only be read from the old /etc/pve/qemu-server/ directory when the old Proxmox installation is succesfully started.
If you can create new empty VMs (with the same configuration, as you remember it) on the new LVM storage, you should be able to copy all the data of the old virtual disks to the new ones.
Maybe your can show the output of lsblk, vgscan and lvscan to give an idea of the organization of your drives with the new/current Proxmox installation (with the old drive attached)?

I have backups, but they are on the drives from the original install.

I was able to boot into initramf and use the MV command to rename the original files to remove the "-OLD-" from them and boot back into the OS.

 

[leesteken]

I have backups, but they are on the drives from the original install.

Good, then you only need to copy them over somehow.

I was able to boot into initramf and use the MV command to rename the original files to remove the "-OLD-" from them and boot back into the OS.

I'm not sure if that's a good idea, if you want to connect the physical drive to another system. Can you boot that system and put the backup(s) on a removable drive? Then you can transport them to the working cluster and simply restore them.

 

[alexskysilk]

So I am on new install 2, I can add drives from my old install as LVM's. that have data on them but cannot access it. They were a part of a zpool in my Truenas VM.

I'll avoid asking why you did it this way, but what's stopping you from mounting the zpool in proxmox and have access to all your stuff? you dont actually need the VM...

 

[Blueduck3285]

I'll avoid asking why you did it this way, but what's stopping you from mounting the zpool in proxmox and have access to all your stuff? you dont actually need the VM...

When I tried to mount the disks in a new install of proxmox, it would only try to mount the "Available" amount.

Everything I have read through the forum and Proxmox documentation wasn't working.

My workaround worked and my old setup is running like nothing happened.

 

[alexskysilk]

When I tried to mount the disks in a new install of proxmox, it would only try to mount the "Available" amount.

might be worthwhile to discuss this a bit for other users down the road. please explain what you did, and what does "available" mean in this context.

Typically if you had disks with a zfs signature on them, its a simple matter of
zpool import [pool] -f

which would make the entire pool at your disposal.

 

[Blueduck3285]

might be worthwhile to discuss this a bit for other users down the road. please explain what you did, and what does "available" mean in this context.

Typically if you had disks with a zfs signature on them, its a simple matter of
zpool import [pool] -f

which would make the entire pool at your disposal.

All of my drives were/are attached to my VM's as LVM's. I didnt exactly know what I was doing to start.

I choose proxmox because I could do a lot with it. I run a VM for Truenas which has 4 1tb lvm's attached that I have as a raidz1. I didnt have 4 drives at first, I bought more over time and added them to truenas and expanded my raid.

This is probably why things went wrong is because they are all LVM's and not zfs.