Permission denied to VM start after rebooting NAS

Posted on 2011-03-18
Last Modified: 2012-05-11
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.
Question by:kathryntg
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3

Expert Comment

ID: 35169837
Is it possible to remove the NFS shares from your storage and then add them back?  

Expert Comment

ID: 35169850
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?

Author Comment

ID: 35169856
no I can't now but I could before the reboot.
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.


Expert Comment

ID: 35169885
I would suggest recreating another share using these instructions:

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.

Expert Comment

ID: 35208874
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.

Accepted Solution

kathryntg earned 0 total points
ID: 36379810
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

Author Closing Comment

ID: 37913849
None of the suggestions supplied worked.

Featured Post

Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question