kathryntg
asked on
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.
Is it possible to remove the NFS shares from your storage and then add them back?
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?
ASKER
no I can't now but I could before the reboot.
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.
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.
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
None of the suggestions supplied worked.