Search results

Update This seems to have been solved. Server freezing / hanigng was caused by root disk being full. Deleted some backups, set down retention, ran garbage collection, this freed up enough space. Recap It seems that verify and garbage-collect should never run at the same time. So the solution...

Server seems to have crashed again, somewhere at 01:00 today. ssh, ping and WebUI did not work. Had to hard-reset the server, again resulting in many backups not finishing, leaving half-done backups (status UNKNOWN) in task list and datastores. Deleted all the half-finished backups, deleted some...

Update Server somehow seems to have crashed. ping to the DNS name of the server (and IP address) were still working, but everything else was done for, no ssh, no HTTP/S. Didn't seen anything too suspicious in journalctl -p3 --since "BEFORE_CRASH" --until "AFTER_CRASH" except for a ton of unable...

Update for things I did over the weekend. Proxmox EFI Partitions After cleaning out old kernels and running proxmox-boot-tool clean + proxmox-boot-tool reinit the /boot partitions seem to be OK. # sudo proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount...

Yes, one of the disks was going bad and had to be swapped and I never had anything to do with zfs This is the thread for disk replacement, october 2024. proxmox-boot-tool clean --dry-run root@backup:~# proxmox-boot-tool clean --dry-run Checking whether ESP '3099-D8E1' exists.. Found! Checking...

I have deleted a few kernels with apt purge and removed some leftover files manually from /boot drives, now they all have 300MB - 400MB out of 500MB disk space used. I'm a little confused by the output of proxmox-boot-tool status root@backup:~# proxmox-boot-tool status Re-executing...

I am terribly sorry, I forgot to provide the proxmox-backup-manager version output. root@backup:~# proxmox-backup-manager version --verbose proxmox-backup 3.4.0 running kernel: 6.8.12-3-pve proxmox-backup-server 3.4.0-1 running version: 3.3.4...

I cannot guarantee this for the newest snapshots and backups, but most, if not all, of these have been verified before. The central PBS runs a weekly verify-job, with re-verifying of backups set to 30 days. This was fine for a long time, as the verify always completed with time to spare for...

Dear Proxmox Forum users, we have a relatively new problem occuring in our proxmox backup server setup. Since some time, more and more weekly verify show failed verify for some backups. There are currently 39 failed Backups, with verifying still going on and some backups were deleted already...

Hi @a_me, I cannot really help you all too much here, as it has been quite a long time. Windows Server itself should be able to create a backup. If I remember correctly, there's even a "Server Backup" role you can add to a Windows Server via Microsoft Server Manager. [EDIT] The Windows Server...

I did the steps above (with slight adjustements, listed below) and this should be solved now. Resilvering is currently running, will take another ~25 days to finish. Current partition layout sda 8:0 0 14.6T 0 disk ├─sda1 8:1 0 1007K 0 part BIOS...

Just to be clear, the steps would then be: # set disk offline zpool offline rpool /dev/WRONG_PARTITION_DISK # force-remove all possibly remaining data-fragments dd if=/dev/zero of=/dev/WRONG_PARTITION_DISK # copy partition table from healthy disk and write new UUIDs sgdisk...

Would these be the next correct steps? Is there something I missed? # set disk offline zpool offline rpool /dev/WRONG_PARTITION_DISK # copy partition layout and erase UUID + label (thanks ubu) sfdisk -d /dev/SOME_WORKING_DISK | sed 's/, uuid.*//; /label-id/d;' | sfdisk...

Ok, the last resilvering is done and it, again, resulted in there being no boot partition. This is the current setup: # lsblk -o +FSTYPE,PARTTYPENAME sda 8:0 0 14.6T 0 disk ├─sda1 8:1 0 1007K 0 part BIOS boot ├─sda2 8:2 0 512M 0 part...

So, after checking with cfdisk, I can see that /dev/disk/by-id/ata-ST16000NM001J-2TW113_ZRS1QMPT still has only 2 partitions instead of 3 and there's no BIOS boot partition in sight. But what else am I to do? I took a healthy disk, gave its partition table to the unhealthy disk (using sgdisk)...

Thank you for your answer. Seeing as I am replacing a disk with itself, I did the following: # the wrongly partitioned disk: /dev/disk/by-id/ata-ST16000NM001J-2TW113_ZRS1QMPT-part1 # removing the disk zpool offline rpool /dev/disk/by-id/ata-ST16000NM001J-2TW113_ZRS1QMPT-part1 zpool labelclear...

Hello dear Proxmox Backup users! One of our 4 HDDs failed in our Proxmox Backup Server. We replaced this with a new HDD and then re-silvered the whole pool. Now, after resilvering, I realised I may have made a mistake. See this screenshot: You can see here that every HDD has the following...

After updating to pve-qemu-kvm/stable,now 8.0.2-4 amd64, rollback works again! Best regards, pixelpoint

Thank you for clearing things up. I will wait until pve-qemu-kvm v8.0.2-4 hits the enterprise-repo and report back after that :) Best regards, pixelpoint

Dear Proxmox Users and Maintainers / Developers, I cannot seem to roll back (maybe only some) VMs. The full rollback log is: Logical volume "vm-196-disk-0" successfully removed. WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set...