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

Re: "The file specified is not a virtual disk" error after machine Kernel Panic'd.

$
0
0

Karaminder, after a cursory review of the information in the support bundle I can tell you that the Disk Data Base section of the Disk DescriptorFile for "Virtual Disk-000008.vmdk" is truncated, hence corrupted and part of the reason why you're getting the error message.  I've also found other issues however it's a long holiday weekend (July 4th) so I'm not where I can take the time to dig into this further until after the weekend.  Maybe someone else will help before I can get back to this.

 

JSYK The other issues I see are in the Extent description of the Disk DescriptorFile for "Virtual Disk-000008.vmdk" and "Virtual Disk-000006.vmdk" .

 

In "Virtual Disk-000008.vmdk" the Extent description is "Virtual Disk-000006-s0##.vmdk" and in "Virtual Disk-000006.vmdk" the Extent description is "Virtual Disk-000007-s0##.vmdk" and normally the Extent description should have the same as in the 00000#-s portion of the file name.  If you look at the other Disk DescriptorFile for the other snapshot disks you'll see what I mean.

 

As and example looking at "Virtual Disk-000001.vmdk","Virtual Disk-000002.vmdk", "Virtual Disk-000003.vmdk", "Virtual Disk-000004.vmdk" and "Virtual Disk-000005.vmdk" the  Extent description shows  "Virtual Disk-00000#-s0##.vmdk" where the first # you see in the 00000# portion is the same as in the name of the disk and the last # in the -s0## portion increments from 1 to 11 respectively.

 

So something got messed up, probably while trying to consolidate snapshots, and don't have the time to analyze further till after the weekend.


Viewing all articles
Browse latest Browse all 192300

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>