Search results

That worked. What a mess... :)

It works without compression: INFO: HOOK: job-init INFO: HOOK-ENV: storeid=storagebox; INFO: starting new backup job: vzdump 102 --node srv1 --compress 0 --all 0 --mailnotification always --storage storagebox --mailto it@craze.toys --mode snapshot --prune-backups 'keep-last=4' INFO: HOOK...

I saw somewhere that someone increased the timeout to 40. But I can't find it back... would that help?

Same error INFO: creating vzdump archive '/mnt/pve/storagebox/dump/vzdump-lxc-102-2022_05_24-10_02_54.tar.gz' INFO: Total bytes written: 1357475840 (1.3GiB, 28MiB/s) INFO: gzip: stdout: Input/output error

I will test

So, Hetzner moved our account to a new instance but the error remains the same. The question I have is: - we configured vzdump to use /tmp on the local filesystem as temp dir - to me it seems that the compression of the snapshot fails and not the transfer to a storage INFO: starting new backup...

I contacted Hetzner (actually did before) but they couldn't find any problems. I hope they can help this time. Will update as soon as I have feedback.

root@srv1:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.11.22-4-pve) pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc) pve-kernel-5.15: 7.2-3 pve-kernel-helper: 7.2-3 pve-kernel-5.13: 7.1-9 pve-kernel-5.11: 7.0-10 pve-kernel-5.4: 6.4-3 pve-kernel-5.15.35-1-pve: 5.15.35-3...

Thanks!

So if I execute pvesm prune-backups storagebox It will prune as configured in the GUI for storagebox?

I have mounted a SMB share for backups which proved very unreliable during the backup process. I switched to a hook script now, copying the backup file via scp to the remote destination. However, I would still like to trigger the pruning of backups as setup for this storage location. Can I do...

Unfortunately in the past weeks having reliable backups of our PVE has been impossible. There is never any run that manages to backup all VMs and LXCs without error. We already set the tmp directory to a local one but have no idea on how to improve the situation further. All backup storage is...

Tried to repair boot but to no avail. I then discovered that it would boot into safe mode. did that once. since then it runs fine and also boots up normally using scsi. I have no clue on why but I don't care too much either.

OK, I will check GPT and UEFI first and then come back.

It is migrated. It boots fine as it is...

Bluescreen I cannot provide right now, since someone is using the machine at the moment. Options below

Yes, it is the latest version. Config attached before changing to scsi. The VM runs W10. As said before, this worked flawlessly on a couple of other machines before.

Yes

Yes, and if I attached the small scsi disk it also shows correctly in the device manager (RedHat VirtIO ...)

I was hoping to upgrade my disk configuration for a Windows VM via the following steps (which worked flawless on numerous other systems before): - add small SCSI-disk to VM causing Windows to install the VirtIO drivers - change disk type from ide0 to scsi0 However, if I change the disk type...