Search results

I hope this is the correct logs :) INFO: starting new backup job: vzdump --compress zstd --mode stop --quiet 1 --storage local --all 1 --mailnotification failure INFO: Starting Backup of VM 100 (lxc) INFO: Backup started at 2021-08-09 04:00:04 INFO: status = stopped INFO: backup mode: stop...

Manual backups (and snapshots) work just fine (I just tested both). It is only the automated backup that fails/hangs.

I'm not sure what you mean by "full task log of the backup" if it isn't the /var/lib/vz/dump/ logs (which has no log)? Is there another log of the backup process?

Hello experts! I have a CT that got caught in Config Locked (Backup) which I fixed by unlocking it (hoping it was a fluke) but it still does it. I have no idea why since the storage doesn't seem to be the problem (all other CT/VM run backup without getting locked). I do see an error in the log...

I agree it is a drop in the bucket but to not turn this into a philosophical discussion on SSD longevity maybe one could boil it down to this: Can you disable that "additional logging (API access log mostly)"? If possible without breaking the system (and at their own risk) that seems to make...

Would it be possible to add a Reboot option (server, not guests)?

I found the problem. It was a mount problem. By default proxmox uses /dev/sdX mapping in fstab (a very old way to mount drives). Using a modern UUID setup fixes the problem and proxmox no longer boots up broken. Why an empty disk can break the network is beyond me but it is clearly a proxmox or...

If I understand your question correctly @wolfgang you are asking if the server boots up from the drive? If so no it does not. It does boot from the RAID normally. EDIT: "Normally" was clearly the wrong word. It does boot from the RAID but it boots up in rescue mode or something. EDIT 2: Well...

UPDATE for anyone finding this via a search: The solution is in the last post. TLDR; use UUIDs in fstab. For some reason proxmox uses the old /dev/sdx system and it breaks boot. I just tried to add new drives to my Proliant server but it boots up with all network interfaces as DOWN and an error...