Latest activity
-
Kkocio replied to the thread [SOLVED] Zabbix ZFS storage size check.Zabbix agent is running on PVE node and it sees ZFS storage as normal mounted directories, which are empty - that's what Linux system tools (like df) can see. This is a special PVE way of mounting storage volumes which causes this problem. You...
-
SS3v|\| replied to the thread Ideale Server-Konfig für externen Speicher.Lieber "Ich bin mir nicht sicher also mach ich lieber nix - da mach ich schon nix falsch?" - Dann wären wir heute noch bei Hyper-V! Meine Favoriten sind lieber "nach bestem Wissen und Gewissen", "aus Fehlern lernen" und "frage so wird Dir...
-
Zur Node in der GUI hat Falk schon das Richtige gesagt, der Ordner unter /etc/pve/nodes/ ist das Problem. Fürs Quorum schau mal in /etc/pve/corosync.conf rein, stehen da die gelöschten Nodes noch in der nodelist? Nach nem sauberen delnode sollte... -
OOnslow replied to the thread [SOLVED] Backup fails with reference to old SMB share.@JayB21 , I'm glad that my replies helped you :) . I understand that your issue is now resolved. Please mark the thread as "solved" by editing the subject and selecting the prefix [SOLVED] from the drop-down menu.
-
UdoB replied to the thread [SOLVED] Zabbix ZFS storage size check.Not sure if I understood correctly... Either: the Zabbix agent is running inside the guest, right? Of course if reports the view from its OS point of view. ...or: to monitor the host (or the whole cluster, if present) take a look at...
-
BBu66as replied to the thread Cluster aufgelöst - no quorum.Zur Node in der GUI hat Falk schon das Richtige gesagt, der Ordner unter /etc/pve/nodes/ ist das Problem. Fürs Quorum schau mal in /etc/pve/corosync.conf rein, stehen da die gelöschten Nodes noch in der nodelist? Nach nem sauberen delnode sollte...
-
TTErxleben replied to the thread verify state failed.Wie bereits vermutet, steht in deinem Log nur WAS nicht passt und nichts darüber WARUM es es so ist. Da helfen auch keine älteren, vollständige Logs. P.S.: Lösche auf deinem PBS die Sicherungen, die nicht verifiziert werden konnten und warte auf...
-
Ist es nicht, ich habe u.a. aufgrund der im folgenden Vortrag dargelegten Pitfalls nie damit angefangen und der Vortrag hat meine Entscheidung für mich bestätigt (es war am Ende halt wirklich so schlimm, wie ich befürchtet habe mit meinen...
-
SS3v|\| replied to the thread verify state failed.Sorry - hat etwas gedauert. Bei mir hat es das Log irgendwie nicht mehr angezeigt - also musste ich einen neuen Verify anstossen. Der läuft zwar noch aber es sind schon ein paar Fehler aufgetauch: 2026-07-18T15:30:47+02:00: SKIPPED: verify...
-
Ccrlt replied to the thread VM processes stall when rebooting adjacent node.Myself as well, when I originally searched this issue I couldn't find much so I assumed it was something on my end but if it seems to be more widespread maybe this thread will gather some attention from the maintainers?
-
BBu66as reacted to ManDal's post in the thread BackupPilot - Desktop Backup Client für Proxmox Backup Server with
Like.
BackupPilot 1.0.7 ist ab sofort verfügbar. Mit diesem Update wurde vor allem die Verwaltung von Pre- und Post-Backup-Hooks deutlich verbessert. Neu können bestehende Hooks direkt bearbeitet werden. Name, Befehl und optional das... -
Rrobertlukan replied to the thread VM processes stall when rebooting adjacent node.I am actually surprised that Proxmox shutdown procedure does not handle this situation differently = gracefully, by introducing a delay/dependency into bringing down network interface only after OSD processes are stopped. I have experienced...
-
JJayB21 reacted to Onslow's post in the thread [SOLVED] Backup fails with reference to old SMB share with Like.
If I understand correctly your posts, now you have removed those "disks" from the definitions of the VMs (and it helped). If so, the backup plan you created was OK. That is, it wasn't the reason of the errors. The VMs' configs were the reasons.
-
Rrobertlukan reacted to crlt's post in the thread VM processes stall when rebooting adjacent node with Like.
Thank you! I added stopping OSDs into the procedure and I did not experience the issue when I rebooted a node just now. I will continue doing this during the next set of updates/reboots.
-
OOnslow replied to the thread [SOLVED] Backup fails with reference to old SMB share.If I understand correctly your posts, now you have removed those "disks" from the definitions of the VMs (and it helped). If so, the backup plan you created was OK. That is, it wasn't the reason of the errors. The VMs' configs were the reasons.
-
Ccrlt reacted to robertlukan's post in the thread VM processes stall when rebooting adjacent node with Like.
I have noticed very similar behavior when Ceph nodes are rebooted. I have noticed that reboot or poweroff command does not give enough time for OSDs to cleanly stop. In my case OSD require about 12 seconds to stop as they have about 10GB of RAM...
-
Ccrlt replied to the thread VM processes stall when rebooting adjacent node.Thank you! I added stopping OSDs into the procedure and I did not experience the issue when I rebooted a node just now. I will continue doing this during the next set of updates/reboots.
-
JJayB21 replied to the thread [SOLVED] Backup fails with reference to old SMB share.Just that the scsi0 did not reference either target for the vms that backup worked on
-
JJayB21 replied to the thread [SOLVED] Backup fails with reference to old SMB share.Well that was easy. Thanks. For my education, any ideas why those would exist on those 2 and no others? I'm pretty sure I created my backup plan for all of them at the same time.,
-
OOnslow replied to the thread [SOLVED] Backup fails with reference to old SMB share.I'm afraid I don't understand this sentence :-(.