• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1059
  • Last Modified:

Permission denied to VM start after rebooting NAS

I recently connected a NAS to our virtual infrastruce and provisioned it with two NSF shares.  I was able to successfully connect the shares to our 2 ESX 4 hosts and was able to browse the storage.  I then created 2 vm's on the shares and all was good.  Then, the knuckleheads in compliance thought it appropriate to blast out patches and the NAS (HP X1400 running Windows 2008r2 Storage Server) was rebooted.  The NAS reconnected to the ESX hosts but when I try to power on the vm's I get a permission denied error.  I did have a permission issue during the initital NFS Share setup which was resolved by adding the ESX hosts IP's into the NFS permissions.  Nothing changed prior to the reboot so I'm clueless as to why I would get an permission denied or even where to start troubleshooting.  All the hardware is on VMWare's HCL so I'm good there.  I followed VMWare's best practice and used a dedicated switch configuration and on a seperate vlan.  Any direction or help would be invaluable as I'm supposed to finish this phase of the project by Monday.
0
kathryntg
Asked:
kathryntg
  • 3
  • 3
1 Solution
 
rjpilcherCommented:
Is it possible to remove the NFS shares from your storage and then add them back?  
0
 
rjpilcherCommented:
It actually sounds like you've got a permissions issue on the 2008 server - can you create folders or move files on the NFS share from VI or vCenter or SCP?
0
 
kathryntgAuthor Commented:
no I can't now but I could before the reboot.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
rjpilcherCommented:
I would suggest recreating another share using these instructions:

http://www.astroarch.com/wiki/index.php/Setting_up_Windows_Services_For_UNIX_%28SFU%29_NFS

Then test and compare (or just move your VMs) - you'd likely want to test after another reboot to make sure it doesn't occur again.
0
 
cdrivedaveCommented:
Sounds to me like you have a pre-existing lock file in the share.

Can you create new VMs on the share? If so, just copy the base disks (vmdk files) to a new folder and assign them to new VMs (vmx files). That will eliminate the lock on the old file and allow you to start the VMs. Then you can compare the files in the two directories and figure out which one is the lock file.
0
 
kathryntgAuthor Commented:
None of the suggestions worked.  I think there was an error in the original configuration which it worked only until polled (not sure that makes sense but that's the closest I can get).  I recreated the NFS share and provisioned our VI and now everything works like a charm.  Thakns
0
 
kathryntgAuthor Commented:
None of the suggestions supplied worked.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now