Search results

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...

How does importing an existing QCOW disk work? I created a VM, stored the QCOW home assisant disk on storage, and then manual renamed it to the disk name as created by the VM. Or is there a fancier option which just allows you to select the disk via the Proxmox webgui? Disabling 'Secure Boot'...

For saving power at home I am working scheduling my Proxmox Lab to auto start in the morning and auto shutdown in the evening. 1) Auto start-up is time-based triggered from the BIOS (and if needed on another time triggered with a WoL command) A) Auto start-up works via BIOS time-based trigger B)...

For others needing some support with this a well. I replaced the disk in the 'zpool' as follow: - Find the identifier of the old unavailable disk: zpool status (result in my case: 927291685244328713) - Find the identifier of the new disk: ls -l /dev/disk/by-id (result...

In case a disk is broken it occurs that UEFI/ BIOS thinks it's an encrypted disk then. I ordered a new disk as replacement in my pool. Useful links in this regard: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J/index.html...

Considering below info would that rule out a software error? If not what's the best way to revive the disk? lsblk -f gives zpool status -v zpool gives

I will check this evening, but I already switched of all Self-Encrypting Drive features in the BIOS and the harddisks themself do not have SED... It's a Asrock Z390M-ITX/ac motherboard. Strange thing is that this behavior just 'popped' up out of the blue and was not always the case.

I have a BIOS/ UEFI with the following Proxmox storage configuration: - 1 NVM storage for Proxmox OS (unencrypted); - 1 SSD for caching and logging (unencrypted); - 2 HDD's for data only in Raid-1 ZFS configuration with one unencrypted and one encrypted file system. When I boot the system cold...

Got thing up and running with Debian VM, Docker Engine, and Portainer Community. I will write a small how to and post it here for others.

First of all I love Proxmox with KVM and LXC, but for quick testing solutions for my work I need to be able to run Docker. Simply because some solutions are only available as Docker container and I don't have time to install an application completely manual. Any recommendation for and easy to...