Solved

Permission denied to VM start after rebooting NAS

Posted on 2011-03-18
7
1,022 Views
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.
0
Comment
Question by:kathryntg
  • 3
  • 3
7 Comments
 
LVL 4

Expert Comment

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

Expert Comment

by:rjpilcher
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?
0
 

Author Comment

by:kathryntg
ID: 35169856
no I can't now but I could before the reboot.
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 
LVL 4

Expert Comment

by:rjpilcher
ID: 35169885
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
 
LVL 1

Expert Comment

by:cdrivedave
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.
0
 

Accepted Solution

by:
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
0
 

Author Closing Comment

by:kathryntg
ID: 37913849
None of the suggestions supplied worked.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

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

Suggested Solutions

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…

911 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

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now