This is still existent on pve 7.2 when adding a node via cli and IP.
Please enter superuser (root) password for '10.2.121.212': ********
Establishing API connection with host '10.2.121.212'
The authenticity of host '10.2.121.212' can't be established.
X509 SHA256 key fingerprint is...
I never had this after I always checked I:
make sure that disks are wiped and initalized with GPT BEFORE I create them as osds
EVEN they are GPT "NO" after osd creation because of ceph lvm
have correct network-time (check chrony!)
most of the times when I had gui problems regarding ceph it is...
I dont have this problem anymore (Im also on 7.2) but as you can see in the history I had it in dec 2020. I dont think its a bug more a little interruption on the network or so. That usually appears if you have network issues. You can fix it by restarting the osds that are affected from this...
Do not bond Corosync, as it can increase latency, thats something you dont want because it can result in fencing (= rebooting) of nodes. Just use two single links, and you could use ceph link as a third fallback (if you want).
check ip a and the output of cat /etc/network/interfaces maybe the major upgrade (debian 10 -> debian 11) changed some of your nics regarding their names. If so, edit /etc/network/interfaces so it fits the new name(s).
We got a message from WD today that there is a fw related bug in wd nvme firmware, that can cause nvme command timeouts and failures in linux/proxmox. Maybe this can also fix your problem. You might have a older fw on it. I will write an wiki artikel on howto update the fw - but you can use...
thanks for the post, this is definetly something I will look into it in the feature. So to fully have working vms on backup node you still need to sync vm-config-files right? Any other things that might not be covered in your tutorial? Can you give more explanation for this...
Ich hab mal den Kollegen Bescheid gegeben, die werden sich demnächst mit dem Vorschlag zum Tausch von Mainboard / CPU melden - je nachdem was dann getauscht werden muss, kann der Rest dann zurück. Sorry für die Umstände! Danke & VG
https://unix.stackexchange.com/questions/257203/booting-stops-at-loading-initial-ramdisk ggf. mal probieren - eher unwahrscheinlich aber n Versuch wärs wert.
#in /etc/default/grub add dis_ucode_ldr in this way
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash dis_ucode_ldr"
Moin! :) Vielleicht mal von nem Debian/Ubuntu Live Linux starten und schauen ob die Reboots auch dort auftreten?
Ansonsten könnte man je nach Möglichkeit auch mal neu installieren und den ZFS-DATA Pool importieren (vorher VM-Hüllen backupen usw...