Recent content by macamba

Havecyou added the post-up rule to the interfaces in /etc/network/interfaces as explained in my previous post.

Post update: Upgraded to Proxmox 9 and still NiCS crashes. This time with hardware failure in log. Adding post-up to interface in /etc/network/interfaces -suggested already in this thread- seems to work for me: iface nic0 inet manual post-up /sbin/ethtool -K nic0 gso off gro off tso off...

At first I thought random. But after testing both Nic’s crash under load.

Just upgraded incl. kernel update and now have this issue. My NICS are integrated on motherboard and it’s a mini server on steroids with no space for alternative NIC. Server is headless so manual software reset of NIC’s also not practical. I will try if disconnecting/ connecting network cables...

Didn't look yet into what secure boot encompasses. Assuming secure boot enables TPM for secure key storage and assuring boot integrity. Than you stand fully correct that it does not make sense on a non-encrypted rpool.

Thansk. Fully disabling CSM on the motherboard worked! Even setting all related CSM settings to enforce UEFI explicitly didn't work (so not disabling fully). Enabling Secure Boot after words is that possible with UEFI?

Just reading 'https://pve.proxmox.com/wiki/Host_Bootloader' and understand that when I install PVE root on ZFS without secure boot enabled it's suppose to use UEFI boot by default. Since this is true in my case I wonder why it uses GRUB instead. What can I do to make sure UEFI boot is used? Also...

Initially I derived it from the Proxmox web interface. Issuing 'efibootgmr -v' results in: How can I switch to UEFI? And why did my previous install had UEFI out-of-the-box?

I am doing a fresh install of my Proxmox with VE 8.2.2. because I wanted the OS installed on a ZFS raid 1 filesystem on two NVME ssd drives. After my install I see my Boot mode = Legacy Bios although I recall that my previous install (not ZFS raid 1 and only one NVME ssd) had Boot mode set to...

The maintenance I referred to above is indeed hardware maintenance. I am trying to add a pcie riser expansion card for 2 nvme ssd’s. The two nic’s I use are onboard of the motherboard. So surprised this is relates. Thanks for letting me know. Learned something.

All kind of network checks resulted in no solution. What I noticed is that enp3s0 was new in the Proxmox interface list (see screenshot above) and enp2s0 disappeared in 'ip a' (see screenshot above). Updated configuration of VMBR1 from enp2s0 to enp3s0 Port/ Slave and it works. Of course happy...

Additional info: Command 'ip a' show the following. Note that enp2s0 is missing!

I have routers physically connected to my Proxmox server: 1) DMZ: 192.168.2.x. Router: 192.168.2.254 (vmbr0) 2) LAN: 192.168.178.x Router 192.168.178.1 (vmbr1) VM's and containers using the LAN network are still working fine. VM's and containers using the DMZ only are suddenly not reachable...

Solved with 'zpool import zpool'

I am in the middle of a migration to a new Proxmox version and took the opportunity to add a new ZFS pool -i.e. 'zpool8tb' (ZFS raid1)- with two new 8TB disks. The old ZFS pool -'i.e zpool' (ZFS raid1 with two 4tb disks) will be used for backup purpose. After moving Proxmox data i.e. VM's...