Execute this command to list the volumes that are detected as snapshots/replicas:.You need to use the esxcfg-volume command. If you have further suggestions even bizar ones like using - please suggest them I asked for help at the homepage of the vmfs-tools - see I used scalpel to carve out user data from inside the vmdks I was able to extract vmdk descriptorfiles and vmx-files and vmware.logs and other stuff that you would expect to be inside the VMFS- headers I tried all tricks that would apply if the volumes was treated as a snapshot - but those tricks dont work I created a new vmfs-volume using exactly the same disklayout and dumped the first 1 MB of the working volume to the bad volume read the volume with latest vmfs-tools version 2.5 - compiled from source so that I get VMFS 5 support - result is "invalid magic number" rebuild a MBR-partitiontable assuming a start offset of 2048 rebuild the GPT-partitiontable assuming a start offset of 128 rebuild the GPT-partitiontable assuming a start offset of 2048 That means I can rule out all misconfigurations a la dublicate VMFS-uuids or VMFS-labels. Now I created a snapshot and boot the VM with a ESXi stateless LiveCD. Then I copied that flat.vmdk to another ESXi, created a descriptorfile for it and use it inside a VM I created a dump of the whole LUN a la dd if=/dev/disks/blabla of=/vmfs/volumes/free-datastore/diskdump-flat.vmdk
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |