urgent- mount PVE partitions to recover data (boot failure after upgrade)

[JJayceCA]

Hello
While happily using pve6.x and I decided to migrate to 7.1 as I wanted to have the same versions on all the PVE servers
Prior upgrade, all requirements were met but after upgrade, the server could not reboot.
I don’t have a physical access to the server, however I am able to access to the server in a rescue mode.
I unfortunately did not save all containers outside of the PVE (I know… I should have :-/) before this upgrade.

I intend to reinstall the server entirely
Would you please guide me thru the steps to mount the pve partition(s) in order to recover data to a remote server ?
Any help would be greatly appreciated.

Thank you
Jack

 

[Dunuin]

You can access the virtual disks from rescue mode by mounting the ZFS pool or LVM. But then the config files are still missing. These were mounted in "/etc/pve/lxc" and "/etc/pve/qemu-server" but when running rescue mode you will find these folders empty as nothing will be mounted there because for that you would need the pve-cluster service running. The files in "/etc/pve" are actually stored in a SQLite DB and then get mounted there by fuse using the PMXCFS filesystem. See here: https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)
I guess you also didn't backupped your "/etc/pve" folder while PVE was working?

 

[JJayceCA]

I guess you also didn't backupped your "/etc/pve" folder while PVE was working?

Unfortunately no !
Thank you for your feedback

 

[JJayceCA]

Apparently, the server did reboot and there is a proxmox login; however, the server cannot be joined via SSH, and no ping.
It seems to be a nerwork issue.
I am not if I should be happier thinking the server was able to boot.
Would there be another an easy fix in rescue mode without loosing the vm data?

 

[leesteken]

Apparently, the server did reboot and there is a proxmox login; however, the server cannot be joined via SSH, and no ping.
It seems to be a nerwork issue.

Check if the name of the (second) network interface ip a matches with the network configuration nano /etc/network/interfaces and change it (all occurrence) if necessary. Make sure to do this from the Proxmox host console without booting from a USB or CD.