Recent content by PedroDelgado

Tried that and then did a reboot. Turns out VMs and CTs won't autostart because the problem persist. I'm going to do a reinstall of Proxmox to see if I can rid of this issue. This is stressing me a lot. By the way thanks for your help :)

I will resume my post because this is a derivated question from a unsolved thread and I will ask for pardon. The unsolved thread is: https://forum.proxmox.com/threads/nfs-shares-storage-is-not-online-500-why.38778/ Situation: Around 5 or 6 weeks ago I set up a Proxmox 5.1-35 (172.16.10.101) and...

Could be a reasonable idea to install bind9 on Proxmox's base operating system (Debian Jessie)? @dcsapak, @webstaff and @vmanz could this replace pfSense router DNS and avoid too this issue? The thing is the IPv4 address for Proxmox is 172.16.10.101 and Windows Server 2012 (PDC and DNS server)...

Oh boy, I have some news about this issue and I guess is a FreeNAS-DNS problem as @vmanz and @webstaff suggested. By the way happy new year to all of you guys. So I came in into the office with the problem in my head, turn on the Proxmox server and all the same, maybe I was hoping in my mind...

Same as we, I mean Christmas. But I really hope to solve this out. Its critical for me cause I have several services on Proxmox reading and writing from FreeNAS. I really appreciate your help guys.

Hi @Whatever before the issue I was able to read and write from NFS without problem. Also if I do manually mount the NFS share through cli I'm also able to read write on the NFS. Thanks for your reply.

Did you tried adding the entry for proxmox on /etc/hosts file? I'm still stuck there.

Ok I know this is a Proxmox forum, not a FreeNAS but if I manually add an entry for 172.16.10.101 proxmox.domain on /etc/hosts this entry is deleted. More digging lead me to add entries using WebGUI in Host name data base field. However, once I added the entry on this field, /etc/hosts file do...

The same @vmanz suggested, however, there was no problem weeks before why now. I'm going to add the host on /etc/hosts and will tell you guys the outcome. Thanks both.

Right now I have not a DNS entry for the FreeNAS or Proxmox on the DC because I'am not pointing to the name, I'm using just the IPv4 addresses. I guess that's what you mean with nameserver-entry. I have the default-gw (pfSense) also as an IPv4 on FreeNAS.

Sorry for the late post showmount -e 172.16.10.10 Output on Proxmox: rpc mount export: RPC: Timed out Output on FreeNAS: RPC: Timed out showmount: can't do exports rpc

I have a Proxmox 5.1-35 (172.16.10.101) and FreeNAS 11.0-U4 (172.16.10.10) server. Everything was fine until few days ago, maybe 4 days, Proxmox stopped seeing NFS shares on FreeNAS. The message in /var/log/syslog: pve01 pvestatd[1277]: storage 'Backups' is not online This happened for all NFS...

There it is, NFS sharing doesn't supports snapshots on containers. Thanks for your help!

It's a NFS dataset share (FreeNAS). All the others are the same type. This is rare. Is there any article/post about container snapshots storage type?

I have a Proxmox server version 5.1-35 (kernel: 4.13.4-1-pve) and can't create a container snapshot, the button shows greyed out. I do can create VMs snapshots. This problem also happens on another Proxmox server version 4.4-13/7ea56165. Maybe this is a new change or simple you cannot create...