Search results

Thank you for your effort. It seems pretty risky at this point. Also I was wondering why Proxmox does not state this requirement in the wiki or on their website.

Hello, is 4GB sufficient to install Proxmox on it (mirrored ZFS root)? Best regards

I read your blogpost prior to posting but found that it did not match my case since I was guessing that, as said, the procedure would be less complex but apparently is not. As recommended by @Dunuin it is probably the best to just reinstall Proxmox. Thanks for your help.

Correct. Every time Proxmox gets a kernel update it takes ages to finish it. If possible I would like to move Proxmox to this new pool as well. I was hoping that this procedure would be easier as the original pool remains.

Hello, I think about adding faster drives to my setup that currently consists of 4 harddrives in a RAIDZ-2 configuration. There will be no drives removed, just added. The goal would be to run Proxmox and some VMs on this faster pool. My main question is now if I can make this transition...

Unsolving this because I get the error again. Thread with the same issue: https://forum.proxmox.com/threads/cifs-smb-unable-to-activate-storage-directory-does-not-exist-or-is-unrecheable.100779/

Hello, I want to update this. The backup is working again. Maybe there was an update that fixed the issue. Best regards

I forgot to answer the second question. Backing up to a local storage is working without any issues.

There is something: From then that reconnecting happens every 180 seconds.

Hello, my recent issue regarding backup to CIFS is that the backup never finishes, it just gets stuck without any error or log message. The issue is most likely on the PVE side. As example the following VM was backed up: disk-size: 120G regular backup-size (lzo): 21,5 G The backup is issued...

I solved it myself. The problem were old virtio-drivers that were not signed and prevented Windows from finding the disk. Solution is to first install up-to-date virtio drivers, then replace the old with the new EFI-disk and finally proceed as described in the link above.

Reason for this crash is that the CIFS storage runs out of memory and gets killed:

Hello, is there a procedure to enable Secure Boot on a Windows 10 guests that have been installed with an old EFI disk? With my Linux guests removing the EFI disk and replacing it with a "new" 4m disk worked (had to re-add the boot option like described here...

Still interested in this question. Can I disable NDP in a static environment?

Update: The CIFS storage was indeed not reachable/broken. But IMO it is a bug if that breaks the proxmox webinterface.

A Backup-job gets canceled like so:

Hello, I have a CIFS share mounted from within Proxmox and lately there are some real issues with the webinterface and Backups to that share. I suspect that the only related Log message is the following: But I´m not sure though. The symptoms are that all VMs and Storages get a questionmark...

Hello, when you add an IPSet ipfilter-net# (# is a placeholder) to a KVM machine it becomes active immediately even though the corresponding option is not enabled. Best regards, Afox

hi, no because I need static addresses for firewalling etc.. I helped myself using openssl rand -hex 8 although it doesn´t add colons.

Hello, is there a tool to generate a random IPv6 address within a given Subnet (e.g. /64) on Linux? Thanks and best regards, Afox