Hi,
Did you have a chance to check the mount to ensure that everything is OK?
It can be some permissions issues or incorrect mount options.
Why you using direct mount instead of add the the share as a storage to PVE?
With pct create 105 local:vztmpl/debian-12-standard_12.2-1_amd64.tar.zst --storage hdd --rootfs 0 --unprivileged 0
Then I removed the content of the subvol and replaced it with the old one. The only difference is permissions: the owner is 100000...
please share the logs from the point where you add a mailbox to the list - to the point where the mail that is not blocked passes through .
and for the second point - check your browsers development console - if you see any errors in the requests ...
Hi,
yes, it's indeed on our roadmap here: https://pve.proxmox.com/wiki/Roadmap
The new affinity/anti-affinity rules introduced with Proxmox VE 9.0 were a first step into that direction.
HI there, just a quick question if Proxmox will even have a feature just like VMWare its DRS or https://github.com/gyptazy/ProxLB ?
Is there something on the roadmap?
Hi,
Seems like it's not set "#EnergyPerformanceBias=BalancedPerformance"
Thermal profile is set to "Default Thermal Profile Settings"
About mitigation just to clarify I have to edit that record in :
- /etc/default/grub and set...
I have given up on getting lxc.idmap to work.
I found a working method via this post: https://forum.proxmox.com/threads/zfs-permission-and-ownership-problems.166084/post-771442
This problem is only on proxmox backup server. Other proxmox ve systems are fine.
I thought it may be the locale
locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"...
As I hate when people never really write what the solution was and just abandon a thread:
I solved my issue as followed (credit goes to https://blog.kye.dev/proxmox-zfs-mounts ofcourse)
Create a user and group on Proxmox host:
groupadd -g...
I tried to update using Proxmox UI menu.
First I got the following error
Starting system upgrade: apt-get dist-upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
System not fully up to date...
You can not reserve 15TB if you only habe about 2TB free. You could try to reserve 1T.
zfs set reservation=1T local_backupstorage_bk01
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
local_backupstorage_bk01 14.5T 12.5T 2.05T...
Thanks Impact, I ran these as specifiued, however, it still resulted in an empty page:
<body>
<!-- Fields required for history management -->
<form id="history-form" class="x-hidden">
<input type="hidden" id="x-history-field"/>...
What was the solution? We have a similar problem on one of our proxmox hosts (this one is not that old, it was build earlier this year), it occured yesterday for the first time, and today again ;(