[solved] reinstall node

[otto001]

Hi,

I am using proxmox 6.1.7 on one "main" server and a workstation I am using for running guests when I need to down the main-server.
However, the HDD of the workstation was faulty and I have to re-install it.
What is the best practice to delete and re-add the node in proxmox? I would like to use the same IP and name if possible...
best regards and thanks in advance,
Otto

 

[otto001]

No one? Of course I used several search functions, but I could not find anything which gave me the feeling of being sure.
I do not want to destroy my nodes...
Best regards and thanks in advance,
Otto

 

[Stoiko Ivanov]

* Were the 'main server' and 'workstation' part of a PVE cluster?
* if yes - check our reference documentation about joining and deleting cluster-nodes: https://pve.proxmox.com/pve-docs/chapter-pvecm.html

* did you have any guests on the broken hdd? (then they are most likely gone and need to be restored from the last backup)

In any case make sure you have a backup of your data before proceeding

I hope this helps!

 

[otto001]

Thanks for your answer!
Yes, they were part of a cluster. No guests on the broken hdd (luckily).
My question is regarding the same name and ip thing.
I read, that a removed node may never ever be re-added with the same name and/or ip - and I do not want to break the cluster by doing it wrong. (I am just a little bit unsure).

From the docs:

At this point you must power off hp4 and make sure that it will not power on again (in the network) as it is.

Is it enough to do a "pvecm delnode workstation" on the "main server", then re-setup the workstation and re-add it to the cluster?

 

[Stoiko Ivanov]

first: make a backup of everything important (at least vm-disks and configs in /etc/pve)!!
check the docs: https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_separate_node_without_reinstall

remove the node completely (compare `pvecm status` output, and check that there is no folder '/etc/pve/nodes/<NODENAME>' anymore

then try to add the freshly installed node

 

[otto001]

thank you! I will try this next weekend as I am abroad...

 

[otto001]

Thanks a lot! worked!
I am just having a problem with live migration now. After migrating a (debian buster) machine from one node to the other, the machine dies shortly after migration, without any error during migration. hm....
even in the console window nothing reacts (altough I can see the last X screen) - only a reset of the VM helps. this is weird.

 

[otto001]

oh, the versions of the node look pretty similar to me:

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-5
pve-kernel-helper: 6.1-5
pve-kernel-4.15: 5.4-12
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.3.13-3-pve: 5.3.13-3
pve-kernel-5.3.13-2-pve: 5.3.13-2
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-4.15.18-24-pve: 4.15.18-52
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-15-pve: 4.15.18-40
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

and

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-5
pve-kernel-helper: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

 

[otto001]

Hm. Thought about that. One of the Servers is an AMD system, the other one Intel. Could that cause this migration problem?

 

[otto001]

oh oh: https://forum.proxmox.com/threads/can-i-move-vms-from-intel-to-amd.63798/
seems that this wont work

 

[Stoiko Ivanov]

Hm. Thought about that. One of the Servers is an AMD system, the other one Intel. Could that cause this migration problem?

yes migration between intel and amd do not work reliably and cause hangs quite often - you might get better results if you set the cpu of the guest to kvm64 - but even then I would expect live-migration to fail most of the time