So, I got tired of having to manually get rid of the no subscription nag pop up every time I upgraded Proxmox. It became tedious. Eventually I wrote an APT hook that listens for package updates. Whenever apt runs, it triggers a sed command to find and replace the line of JS that triggers the nag pop-up.

First, open shell from the dashboard.

Create the apt hook:

nano /etc/apt/apt.conf.d/99-pve-nag-remover

Paste the following into the new configuration file:

DPkg::Post-Invoke { "sed -i.bak \"s/res.data.status.toLowerCase() !== 'active'/false/g\" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js"; };

Save the file and exit nano.

Restart the web service:

systemctl restart pveproxy.service

Now every time you run update/upgrade, the no-subscription nag will automatically be disabled.

Hi everyone,

I am planning to reinstall one of my Proxmox nodes and switch from LVM/LVM-thin to ZFS.

The server currently uses a MegaRAID 9341-4i controller. Proxmox sees the storage like this:

NAME   SIZE   MODEL    SERIAL
sda    7.3T   MR9341   00ad5e9e0ea511a62c10

The disk model is shown as MR9341 makes me think Proxmox is currently seeing a MegaRAID virtual disk rather than the physical disks directly.

My questions are:

• Does the caching of the MegaRAID have any benefit for ZFS?
• Is the MegaRAID 9341-4i suitable for ZFS when configured in JBOD mode?
• Does this controller provide proper disk passthrough, including SMART data and individual disk serial numbers?
• Would it be better to replace it with a proper HBA in IT mode?

Any advice from people using this controller with Proxmox and ZFS would be appreciated.

Hey Gang!

PVE 9.2.3

Intel Arc B60 / B70 / B50 GPU Passthrough (working just fine with windows 11 guest!)

For some reason, I am unable to install Ubuntu 26.04 with the Intel Arc card in pass-through, it fails at some point during OS init, even during the installer/liveCD. This occurs on Ubuntu 26.04 Server and Desktop.

The server installer gets to the point of:

"Finished systemd-journal-catalog-update.service - rebuild journal catalog" - and then the entire VM locks up.

The Desktop OS installer silently fails during the OS loading spinner, also locking up. (Presumably the same cause?)

Bizarrely, this issue does not happen on Ubuntu 24.04, and install/runtime happens without any problems, along with win11 running my GPUs quite happily.

Anyone got any ideas?

I'm sure that this will have been asked before, but I'm not 100% I'm using the right wording so I couldn't find anything form a google search.

I have proxmox v8.xx running on a mini PC
Home assistant,
A Debian install mostly running docker
and an LXC container for Pihole

I logged in to the dash for the 1st time in a while and saw the banner that 8.xx is going out of support. I know for the documentation back when v9 released that the update path is to either flatten the machine and install 9 and restore the VMs from backup or to migrate to another box.

I have a couple of spare SSDs kicking around. I don't have any spare PCs of the same spec so I'm wondering if I could do the install and base config of proxmox on a spare SSD in another machine, then swap the hard drive to the original PC, different CPU, motherboard more ram etc then restore the VMs form backup to minimise downtime and general grief from the rest of the house over the lack of wifi & light switches

Proxmox installed on 1TB drive, allocated 256GB, the rest I wish to use for whatever (700GB+), not extend!!, aka create another partition for use, which is not visible in system :)

I forgot how to do this, so can anyone help?, short of taking drive out and running through Parted, which pains me.

Cheers ma deers! :D

I have a pc x99 with 128 gig of ram. I have punch of .vmx files form vmare how do I import this in promox