Recent content by koshak

have checked another host, and yes, all fresh backups are encrypted now, thank you!

hmmm, its solved the problem on my home server, will check another server tomorrow, thank you

root@pve:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve) pve-manager: 6.2-11 (running version: 6.2-11/22fb4983) pve-kernel-5.4: 6.2-6 pve-kernel-helper: 6.2-6 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.60-1-pve: 5.4.60-2 pve-kernel-5.4.44-2-pve: 5.4.44-2 pve-kernel-5.4.41-1-pve...

still not fixed today I have made a fresh PBS install, added datastore(with encryption key) to PVE, and found that backup of old VM(which was previously backed up to another unencrypted pbs datastore) is unencrypted, while new VM(no previous backup) backup is encrypted

Looks very similar, thanks, will wait for an update.

have found that VM, which was backed up before I copied generated key to /etc/pve/priv/ keep unencrypted state for later backups, was trying to delete old backups - nothing changed

Ok, thanks aaron, I'm already installed Proxmox over Debian buster with separate pool for boot, just wanted to know if it possible by Proxmox iso installer. The new Ubuntu 19.10 installer create a separate boot pool by default, It will be nice if Proxmox did the same in the future releases.

Is it possible to do by Proxmox installer iso?

Reinstalling is ok, but my HP Gen8 doesn't have UEFI support.

Hi! Have installed Proxmox 6.0 from iso, created encrypted dataset, for example rpool/encrypted, and grub fall into rescue at next reboot. I found that right after creating encrypted dataset grub started refuse to recognize zfs. # grub-probe /boot -vvv ... grub-core/fs/zfs/zfs.c:2112: zap: name...