Search results

Hey! You can remove the suspend snapshot with running the command pvesm free <volume> on the node directly, where <volume> would be local-lvm:vm-105-state-suspend-2022-11-25 in your case. Please check again if it is the right one, as this cannot be undone.

Thank you for the extra information! Unfortunately the syslog doesn't tell us much about the problem directly, but it seems like that the there is a kernel stacktrace that couldn't be written to the syslog in time. Your configuration seems fine, but just to check: Did you also add your GPU's...

Welcome to the Proxmox forum, Michel! It would be helpful to know how you setup your GPU passthrough (e.g. cat /etc/cmdline and any /etc/modprobe.d/*, etc. you set up) and what your system log (journalctl) on your PVE host has logged before becoming unavailable.

Es scheint so als würde ein Prozess weiterhin (fehlerhaft oder nicht) auf den Datastore zugreifen. Welchen Output liefert cat /run/proxmox-backup/active-operations/RDX (wenn die Datei überhaupt existiert)? Was liefert der Kommando proxmox-backup-manager task list?

So wie von @Azunai333 schon beschrieben liegt es daran, dass der Cluster kein Quorum mehr hat und das passiert bei 2 Nodes sobald eine dieser Nodes ausfällt. Ich rate dir die vollständige Anleitung durchzuarbeiten (diese enthält an einem Punkt auch den besprochenen pvecm expected 1, solange...

Wie weit wurde der Prozess der in dem Admin Guide beschrieben wurde weiterverfolgt, um die defekte Node zu entfernen? Der Fehler erscheint, da der Cluster nicht mehr genug Stimmen hat um über den aktuellen Zustand zu entscheiden (d.h. keine Operationen mehr ausführen lässt). Deswegen ist es...

Have you checked that the BIOS and any other hardware firmware is updated to the latest version? It seems like the Dell PowerEdge servers have frequent problems with booting from PCIe NVMes regardless of the installed operating system. I don't have your setup to test or verify this, but have...

Werden am PBS Server dazu Fehler im syslog angezeigt (journalctl)? Gibt es Hinweise durch einen S.M.A.R.T test, dass es an einem Hardware Fehler liegt?

Seems like there could be a problem with the PVE Status Daemon. Does the output of systemctl status pvestatd.service contain any errors? You could try to restart the service with systemctl restart pvestatd.service on each node.

Willkommen im Forum Sebastian! Leider ist das ein bekanntes Problem bei priviligierten Ubuntu 24.04 LXC-Containern, siehe mehr dazu in diesem Forum Thread (Englisch). Kurz und knapp ist die Lösung für dieses Problem, dass man an den Container das Feature nesting hinzufügt. Das geht entweder...

Hast du bereits versucht das Netzwerk am Gast neuzustarten (systemctl restart networking.service)?

Have you tried pinging external websites by ip (e.g. 1.1.1.1) or domain name (e.g. example.com)? If you cannot reach by domain name, then it is likely that your DNS does not resolve. Otherwise, how is your network set up (post your /etc/network/interfaces?

Have you tried to double click on the "pending" start task and click on the "Stop" button? It should be located in the top menu of the task viewer window (right under the "Overview"/"Status" tabs).

Second this, especially if the container is still running. As far as I know, AdGuard Home should usually be run privileged user, except if you have set it up to be able to run it without superuser (see here).

Could you provide the config of another LXC where it works? Did you start the command via the WebGUI or in a console?

How did you migrate the Windows VMs from xcp-ng to Proxmox?

Hey there! Unfortunately I couldn't reproduce the timeout error you got. Could I ask you what version of Proxmox VE you are using and how large the qcow2 file of the original VM was and how long it (approximately) took to clone it with qm clone <vmid> <newid> --full true? In general and AFAIK...