Unable to activate storage

[cdsJerry]

I'm running Proxmox 2.2-32/3089a616 with three VMs on an 8 core machine. I backup to a NAS each night. I haven't made any changes to the system in a few months now.

This morning I found an error in the backup report. Two of the VMs backed up normally but the third did not.
************
102: May 01 23:47:34 INFO: received signal - terminate process
102: May 01 23:47:36 ERROR: Backup of VM 102 failed - command '/usr/lib/qemu-server/vmtar '/mnt/pve/Backups-IOMEGA/dump/vzdump-qemu-102-2013_05_01-23_42_49.tmp/qemu-server.conf' 'qemu-server.conf' '/mnt/vzsnap0/images/102/vm-102-disk-1.qcow2' 'vm-disk-ide0.qcow2'|lzop >/mnt/pve/Backups-IOMEGA/dump/vzdump-qemu-102-2013_05_01-23_42_49.tar.dat' failed: exit code 1
***********
I tried to access the backup NAS from inside the Proxmox GUI. I can access the summary page and permissions page. Summary shows it's not active and has a size of 0, used 0, avail 0. I can't access the content page at all. It comes up with "unable to activate storage 'Backups-IOMEGA' - directory '/mnt/pve/Backups-IOMEGA' does not exist (500)". This is the same target as the first two backups.

If I click on the top level server view and select the Backkups-IOMEGA device It shows it's enabled.

Thank you in advance for any help offered.

 

[udo]

Hi,
is the nas mounted?
What is the output of

mount
df -h

Udo

 

[cdsJerry]

When you ask if the NAS is mounted... in the Promox GUI? I'm not sure where it says mounted, but under the Summary it's Enabled, but not Active.

At the mount command I get:
mount
/dev/mapper/pve-root on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext4 (rw)
/dev/sdb1 on /boot type ext4 (rw)
/dev/sda1 on /backups type ext4 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
container on /proc/vz/container type cgroup (rw,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)
192.168.2.114:/mnt/pools/A/A0/Backups on /mnt/pve/Backups-IOMEGA type nfs (rw,vers=3,addr=192.168.2.114)

At the df - h command I get:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 95G 1.5G 89G 2% /
tmpfs 7.9G 0 7.9G 0% /lib/init/rw
udev 7.9G 216K 7.9G 1% /dev
tmpfs 7.9G 19M 7.9G 1% /dev/shm
/dev/mapper/pve-data 800G 646G 154G 81% /var/lib/vz
/dev/sdb1 495M 35M 436M 8% /boot
/dev/sda1 1.8T 976G 765G 57% /backups
/dev/fuse 30M 16K 30M 1% /etc/pve
df: `/mnt/pve/Backups-IOMEGA': Permission denied

Keep in mind it's writing the other two VMs to the same target without an error. I see the permission denied from above, but how could it write two VMs but not the third if it thinks it doesn't have permission to access the NAS?

If I connect to the NAS from Windows (sorry) and try to delete any of the old backup files or logs, it says "You require permission from Unix User\nobody to make changes to this file". Is that a clue?

 

[cdsJerry]

Ok, so that permission denied error was bothering me. If I go onto my NAS and change the permissions on that share to allow everyone read/write access I'm then able to browse in the "Content" tab in Proxmox. Of course so can everyone else, but it's a clue, or at least I think it is. Where do I set the authentication for a NAS share in Proxmox? If I can specifically define it that might solve the problem.

Of course it doesn't explain why 1) the other two VMs backup fine 2) this VM backed up fine until last night. So I don't know what changed or how to fix it.