Hi @VictorSTS ,
You are correct. If there are existing entries in the iSCSI database (iscsiadm -m nodes) at the time of the upgrade, they will cause issues when you try to modify them afterward. Other scenarios can also lead to problems, for...
IIUC, this may/will affect iSCSI deployments configured on PVE8.x when updating to PVE9.x, am I right? New deployments with PVE9.x should work correctly?
Thanks!
Hello everyone, This is a brief public service announcement regarding an iSCSI upgrade incompatibility affecting PVE 9.x.
A bug introduced in iscsiadm in 2023 prevents the tool from parsing the iSCSI database generated by earlier versions. If...
Can't really recommend anything specific without infrastructure details, but I would definitely use some VPN and tunnel NFS traffic inside it, both for obvious security reasons and ease of management on the WAN side (you'll only need to expose...
On one of my training labs, I have a series of training VMs running PVE with nested virtualization. These VM has two disks in a ZFS mirror for the OS, UEFI, secure boot disabled, use systemd-boot (no grub). VM uses machine: q35,viommu=virtio for...
Hi, this should be resolved with Proxmox VE 9.1: When KRBD is enabled, RBD storages will automatically map disks of VMs with a Windows OS type with the rxbounce flag set, so there should be no need for a workaround anymore. See [1] for more...
It's unclear if you are using some VPN or direct connection using public IPs (hope not, NFS has no encryption), but maybe there's some firewall and/or NAT rule that doesn't allow RPC traffic properly? Maybe your synology uses some port range for...
There are two operations that are happening in the background when adding NFS storage pool in PVE:
- health probe
- mount
When you are doing manual mount, the health probe is skipped.
In PVE case the health probe is a "showmount" command...