Renaming node -> volumes not reachable

jlgarnier

Member
May 25, 2021
12
2
8
Auriol, France
Dear Community,

On my lab servers, I decided to rename one node, which had already running VMs. I followed the instructions given in the video here: https://www.youtube.com/watch?v=2NzLYKRVRtk and managed to perform the renaming without any problem.

However, I have some issues with existing volumes. Here's the current storage configuration:

Capture d’écran 2024-11-15 140200.png

What happens:
  • I have a 'backups' volume for it to store daily backups, which is now not reachable (msg: error listing snapshots - 400 Bad Request (500))
  • LVM disk displays a hierarchy originating from the old node name: pve/dev/sda3.
  • LVM-Thin disk has a 'data' volume which is still attached to the previous name (volume group = pve)
  • I also have a local-lvm volume which is also not reachable (msg: no such logical volume NEWNAME/data (500))...
Thus Proxmox Backup Server doesn't work as expected and previous backups are not accessible. Unfortunately, I used PBS to backup the VMs I wanted to move to another node...

Capture d’écran 2024-11-15 144308.png

What's your advice to fix this? It looks like the renaming process has missed something...

Thanks in advance for any help!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!