It's the second time in a short period where I've found a VM not starting and reporting as (inaccessible). I do not know why this happens, but I just found a quick solution for it (instead of creating a new VM using existing disk). The only thing you need to do is browse the datastore and remove the .vmxf file. Problem solved.

The vmxf isn't that important and gets recreated. It hold some insignificant stuff in xml format:

cat w30008.vmxf
<?xml version="1.0"?>
<Foundry>
<VM>
<VMId type="string">52 7e f4 7e f4 f1 1c d8-59 b3 2c d5 76 0d 0a 45</VMId>
<ClientMetaData>
<clientMetaDataAttributes/>
<HistoryEventList/></ClientMetaData>
<vmxPathName type="string">w30008.vmx</vmxPathName></VM></Foundry>