Search results

Good news. I think I may have solved my issue at least. On my Synology there are two ethernet ports. Once a fairly long time ago I configured both of them and forgot about it, but only connected the secondary interface. When doing 'strace rpcinfo -p 192.168.0.1" which is the interface that...

On the sourceforge-link it seems "steved" removed default functionality of random port opening in July 2018 and made it a kernel option. He intends to remove the functionality entirely later on when nobody uses it because people complained about the functionality, but from what can read we're...

root@proxmox:~# mount -vvvvt nfs 192.168.x.x:/volume1/nfs /mnt/pve/NFS2 mount.nfs: timeout set for Tue Mar 24 15:41:37 2020 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.x.x,clientaddr=192.168.x.x' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options...

It would appear this interferes with destruction of machines as well. I put a machine on iSCSI storage and whenever I destroy that the task fails with "storage 'NFS2' is not online"

Forgot to add, but "rpcinfo -p x.x.x.x" also gives "no route to host".

I have the same setup and the exact same issue. NFS does not work, but iSCSI for example does. Synology NAS and proxmox 6.1-8. The NFS share worked prior to upgrade from version 5. The network has not been changed so it was the upgrade that broke something. And telneting port 111 from proxmox...