Recent content by luison

I think this subject has been commented before but i have not found any directly related posts or documentation. In our case we use mainly LXC containers mainly for the sake of being able to share certain paths from the hosts across various containers. We either use templates or restore a...

Assuming this is a couple of years old, but wondering if anything has changed with the option of tweaking CSS for the panel in a way that "survives" updates. Did some in the past that kept getting lost after updates. Not talking about a dark mode, just been able to adjust say the top bar...

Back to trying to tune my zfs datasets, any guidance/reference document of recommended values for zfs datastores in PVE would be mostly appreciated. Particullary for the thin datastores (not sure if those can be tuned), root, data and logs. Thanks.

Thanks for prompt reply. That is the exact process performed: # proxmox-boot-tool status System currently booted with uefi So as documentation says perfomed: - cloned partitions - updated GUIDs of disks - proxmox-boot-tool format and init on all p2 of other disks # proxmox-boot-tool status...

I have to admin me and proxmox-boot-tool do not get on very well We have migrated a system to a fresh install of pve 8.2 on a 4th nvme disk from scratch (iso install). We have now completed the process, repartioned the "old" 3 nvme disks and add them to the rpool. So far so good. With equal...

Hi. I know this thread is slightly old but thought I would rather ask here as it's related rather than open a new one. I am trying to reorganize my prune policy, but need to understand the sync and particularly the namespaces before. As on a local server we have a few testing CT I am...

/dev/nvme0n1p5 536M 497M 40M 93% /mnt/testboot 500Mb all of them appartently

I guess you mean regarding root and that /var path... plenty of space there # df -h / S.ficheros Tamaño Usados Disp Uso% Montado en /dev/mapper/pve-root 42G 16G 24G 39% / # df -h /var/tmp/espmounts/ S.ficheros Tamaño Usados Disp Uso% Montado en...

I have this exact same issue when upgrading to 6.8.12-5 Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/cmdline found - falling back to /proc/cmdline Copying and configuring kernels on...

Although not being lucky with feedback I am still stuck with this which I am now find somehow related to our network card problems when running kernel 6.8.12-4 which I can not understand why. As explained on this reply we managed to get proxmox-boot tool to update something like the GRUB part...

As an update, we've just realised that the issue is not with our Realtek card. The motherboard has two cards and the one disconnecting constantly after the kernel upgrade is an: 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

I've been struggling for a while to make proxmox-boot-tool behave as such on my system (thread) only to discover that when I finally managed to fix my boot to (6.8.12-4-pve) my system network becomes completely unstable. In my case this is causing network disconnections every couple of minutes...

Not that I found any documentation or answers here (thanks @vesalius) but I think I finally, after months, found a "sort of" solution to this. It was only when I went ahead and read something regarding "reinit" which by the way is not documented at the wiki page So proxmox-boot-tool reinit gave...

I understand the use of variables in LXC container files is not possible, so this entry is likely intended as a suggestion unless someone explains a documented way to do it. They are actually related to bind mounts. The main one is related to being able to use something like "${VMID}" in conf...

Still stuck on this issue now considering we will have to reinstall host system as we are also moving disks to ZFS. On another server I am not 100% again with proxmox-boot-tool output, it would be great is someone could clarify if this is correct output as in does not look so to me. In this...