Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 232869

Re: Unable to open *.vmdk: Insufficient permission to access file

$
0
0

(Please just assume I appreciate your responses, because I do  )

 

WoodyZ wrote:

 

The .log file does show the failure but there are many lines of text for same that I cannot decipher.  I had hoped to send the file to support @ VMWare but as mentioned in my initial post, I do not seem to have access to same...

 

If your comfortable with it you can attach here and one of us will try and help.  If you need to sanitize it a bit first, like replace a user name with something generic etc, that's fine.  Just attach it as a file, not copy and paste the contents!

 

I cannot locate the log file I reviewed after the upgrade, in which it showed all 3 VMs and that is what I was referring to -- the individual VM log does not exist for the now inaccessible VM, which makes sense since it was inaccessible

 

...but I wonder if the issue is not related to when I first setup that VM: I think I cloned it but then determined that it needed more disk space than the source of the clone.  I had to use an expander for the partiition.  I wonder if that got kaboshed by the upgrade as I see that it now shows no HD.  Maybe I would be better off doing a clean install of a new VM -- at least the data is backed up and can be recovered to same.


Viewing all articles
Browse latest Browse all 232869

Trending Articles