Proxmox 1.8 NFS Mount Problem

[Acorp]

Hi,

I am having a problem with a Proxmox 1.8 server I just moved to a data center from my local network. When attempting to create a new virtual machine from the web interface, I receive the following error:

[4183]ERR: 24: Error in Perl code: 500 read timeout

I did a search and found this thread on the Proxmox forums:

http://forum.proxmox.com/threads/2664-perl-error-500-read-timeout

While the problem is different, Dietmar's suggestion from that thread to run "pvesm list -a" yielded the clue:

mount.nfs: mount to NFS server '192.168.1.12' failed: timed out, giving up
command '/bin/mount -t nfs 192.168.1.12:/mnt/Sammi160/PVE/Backup /mnt/pve/FreeNAS' failed with exit code 32

I had set up an NFS share for backup storage prior to removing this server from my local network (and sending it to the DC), however I forgot to remove the NFS mount from Proxmox's control, so it is still looking for it. This was set up in "Proxmox -> Configuration -> Storage", however when I return there to try to remove the NFS storage from the web page, Proxmox again hangs up with the error from above.

I know any experienced Linux admin could probably resolve this in a flash, but any ideas about how I can remove, from the CLI, Proxmox's expectation to have access to this NFS share as I can't access it from within the Proxmox web page?

TIA,

- Acorp
www.acorp.net

 

[tom]

remove the storage in /etc/pve/storage.cfg
(if you have a cluster, do it on the master)

 

[Acorp]

Thanks Tom, that was exactly what I needed.

- Acorp
www.acorp.net