Search results

The man page for zpool trim [1] provides a good explanation. Basically TRIM is used to discard unused storage blocks in the filesystem. This improves SSD performance and lifespan as it does not need to continually delete old blocks on every write. It also allows thinly provisioned storage to...

It's unfortunate that you couldn't get proxmox to install directly, but your situation does remind me of a similar forum post from some weeks back, in which a user could not get Proxmox to boot, but could boot Debian. In the end, the problem was fixed by updating the BIOS. I'll share the post...

A patch has been sent to remove the old user entry from shadow.json upon deletion [1]. However for the rest, this is currently intended behavior. [1] https://lists.proxmox.com/pipermail/pbs-devel/2021-April/002724.html

Hi, In the advance options of the edit disk menu, there is a 'backup' checkbox which specifies whether or not a particular disk should be included in a backup job.

Hi, Are you using HA on the cluster? And did you run the updates simultaneously or one after the other? The "Package Updates" section [1] in the High Availability section of the docs has some notes on why this could cause issues. In addition, due to fencing [2], when individual nodes lose...

These represent two different levels of the boot sequence and are not swap-able. I believe what you might want is to enable legacy bios boot. This should be carried out in your computer's bios and has nothing to do with the Proxmox installation. You can search online for how to enable this for...

Yes you can unmount it manually, and this will have to be done on every host.

Unfortunately, I can see no obvious issues in any of the details you provided. Could you try updating your systems to the latest available version and see if the problem persists?

In this case, this is the intended behavior. Both the pvesm remove command line tool and the API only remove the configuration from Proxmox VE. It does not affect the underlying data or mount point, just PVE's awareness of it. To properly remove the mount, you would need to remove the entry from...

Hey, What steps did you take to remove it?

Hey, Proxmox Backup Server can be installed on top of Debian and as a result, Proxmox VE [1]. The only concern here is that your backup server is not decoupled from the system being backed up, so system failures can cause some inconvenience at best. It supports file level backups [2][3], which...

The backup log that you posted doesn't seem to show any issues. Did this particular backup also lock up your system? In the system log that you posted, there is no mention of the backup job for ct1016 finishing. A log from an occurrence where the job never finishes could be more helpful. Double...

Could you post the output from the task itself also? It can be found in the GUI under<nodename> -> Task History or /var/log/vzdump/<vm/ct>.log. Is your instance of Proxmox Backup Server local or in a remote location? What kind of storage is the backup server using for this datastore?

Ah sorry to hear! But keep me posted if you manage to find anything anyway, and we'll what's to blame :)

A patch has been submitted [1], which likely addresses the issue you're having here. And you are correct. At this point in time, the way in which proxmox-backup-api fails causes a clean stop of the service, so systemd does not attempt to restart it. With this, the discussion about whether this...

You should probably look at the output of something like for i in $(pgrep proxmox-backup); do lsof -np $i; done, when this happens to understand what's actually using all the open files, in case this is a bug. I wouldn't recommend increasing the file limit until that is known. To my knowledge...

Excellent, I'm glad you found the sollution! You can mark the thread as [SOLVED] in order to help others find it easier :)

Have you also tried to boot using legacy support mode rather than uefi? Are there any updates available for the BIOS of the machine? If booting in legacy doesn't work, you could also attempt to reinstall grub from within the rescue system or from the debian installer? Worst case scenario, you...

This isn't actually an error message, just a notice that a bug for the hardware exists. Given that your CPU only has two physical cores, I'd keep SMT enabled and would also not mess with crng in any case (as it's likely unnecessary). In the bios, i would check for items such as device boot...

At the moment this is not possible.