help please, deleted the flat file i have only snapshot

[thinos]

Hi, i deleted the flat file. the vm wont start. i have read http://sanbarrow.com/sickbay.htm
changed the cid of the curent snapshots but the vm vont start it sais
Message from wmserver.sadsro: Cannot open the disk
'/vmfs/volumes/4abd189a-da3fafef-15dc-00215e4f9dc0/SERVER/SERVER+Iw-
-1-000002.vmdk' or one of the snapshot disks it depends on. Reason:
The parent virtual disk has been modified since the child was created.

is there a tool that can browse snapshots ? i trying ufs explorer but i get only a 110gb file
i need only 2 files from the snapshot.

thx for help

[thinos]

SERVER2_1-000001.vmdk

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=85bb5e2a
parentCID=0db311b5
isNativeSnapshot="yes"
createType="vmfsSparse"
parentFileNameHint="SERVER2_1.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_2-000001-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "5cb39fc99e2e93680d15fb6085bb5e2a"


SERVER2_1.vmdk

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=0db311b5
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 125829120 VMFS "SERVER2_1-flat.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "16"
ddb.geometry.cylinders = "0"
ddb.uuid = "60 00 C2 98 78 5b dd df-e0 66 b5 e0 79 25 ad 25"
ddb.longContentID = "dbdb36ee5f28ec25c3bc386d0db311b5"
ddb.virtualHWVersion = "7"
ddb.uuid.image="1af53b49-acb6-4b31-8563-62f0c2f60e05"
ddb.uuid.modification="8500f3dc-fbcc-45cf-8f07-d835e329fa3e"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification="fbdad006-b7bf-4ec4-b456-e559e628c489"


SERVER2_1.vmsd

.encoding = "UTF-8"
snapshot.lastUID = "1"
snapshot.numSnapshots = "1"
snapshot.current = "1"

snapshot0.uid = "1"
snapshot0.filename = "SERVER2_1-Snapshot2.vmsn"
snapshot0.parent = "1"
snapshot0.displayName = "test2"
snapshot0.description = ""
snapshot0.createTimeHigh = "294242"
snapshot0.createTimeLow = "1603302225"
snapshot0.numDisks = "1"
snapshot0.disk0.fileName = "SERVER2_1-000002.vmdk"
snapshot0.disk0.node = "scsi0:0"

[continuum]

Hi Thinos

in some cases you can extract files from snapshots - even when the basedisk is missing.

But most of the times this will not work. The files must be small and unfragmented - otherwise there is no chance.
To extract those files you must fake a basedisk with the same filesystem as the original basedisk used.
Then you can use UFS-explorer or just use a LiveCD ...

[thinos]

ja , aber wenn ich die vmkd datei mounte dan kann ich nur dass neue vm seehen, meine snapshot aber nicht. geht es das ich die 2 file zussamen binde?

[continuum]

erklaer mal genauer

[thinos]

die geloschte file hate das datum den letzten eintrag 26,10,09 can es nicht zo sein das der snapshot die flat nicht braucht?

ich habe mir die delta.vmdk mit totalcmd angesehen. da sien alle datten. dan glaube ich dass ich die daten rausnehmen kann. nicht?

ich habe das in google gefunden

then i used vmkfstools -i to commit or called clone the delta and parent vmdk file into single vmdk file with all changes into one.
"vmkfstools -i SRV01-000010.vmdk /vmfs/volumes/xxx-xxx-xxx/SRV01-version2/NewDisk1.vmdk

http://vikashkumarroy.blogspot.com/2008 ... fline.html

und wen ich vmplayer starte can ich nicht die snapshots sehen. ich habe sie in config
aber ich kann sie nich sehen.

[continuum]

can es nicht zo sein das der snapshot die flat nicht braucht?

definitiv nicht - ein snapshot kannst du ohne passende parent-disk nicht auslesen.

Was du in google gefunden hast ist ein anderer Fall.

jetzt mal ganz konkret:

was hast du denn derzeit ueberhaupt noch vorliegen ?

[thinos]

nur den snapshot

[continuum]

Dann leg jetzt eine neue vmdk an: 110 Gb mit demselben Controller und dem selben Dateisystem.

Wenn du damit fertig bist - poste beide vmdks

[thinos]

SERVER2_1.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=0db311b5
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 125829120 VMFS "SERVER2_1-flat.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "16"
ddb.geometry.cylinders = "0"
ddb.uuid = "60 00 C2 98 78 5b dd df-e0 66 b5 e0 79 25 ad 25"
ddb.longContentID = "dbdb36ee5f28ec25c3bc386d0db311b5"
ddb.virtualHWVersion = "7"
ddb.uuid.image="1af53b49-acb6-4b31-8563-62f0c2f60e05"
ddb.uuid.modification="8500f3dc-fbcc-45cf-8f07-d835e329fa3e"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification="fbdad006-b7bf-4ec4-b456-e559e628c489"

SERVER2_1-000001.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=85bb5e2a
parentCID=0db311b5
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="SERVER2_1.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_1-000001-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "5cb39fc99e2e93680d15fb6085bb5e2a"

SERVER2_1-000002.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=bd0f02f1
parentCID=85bb5e2a
createType="vmfsSparse"
parentFileNameHint="SERVER2_1-000001.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_1-000002-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "3e5fb0afaa3b2bf38029557abd0f02f1"

[continuum]

ich werde aus deinem letzten post nicht schlau - setz die mal in code-tags und schreib dabei was das sein soll

[thinos]

SERVER2_1 - haupt flat file

Code: Alles auswählen

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=0db311b5
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 125829120 VMFS "SERVER2_1-flat.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "16"
ddb.geometry.cylinders = "0"
ddb.uuid = "60 00 C2 98 78 5b dd df-e0 66 b5 e0 79 25 ad 25"
ddb.longContentID = "dbdb36ee5f28ec25c3bc386d0db311b5"
ddb.virtualHWVersion = "7"
ddb.uuid.image="1af53b49-acb6-4b31-8563-62f0c2f60e05"
ddb.uuid.modification="8500f3dc-fbcc-45cf-8f07-d835e329fa3e"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification="fbdad006-b7bf-4ec4-b456-e559e628c489"



SNAPSHOT 1 von SERVER2_1

Code: Alles auswählen

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=85bb5e2a
parentCID=0db311b5
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="SERVER2_1.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_1-000001-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "5cb39fc99e2e93680d15fb6085bb5e2a"


SNAPSHOT 2 - die date sind hier alle

Code: Alles auswählen

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=bd0f02f1
parentCID=85bb5e2a
createType="vmfsSparse"
parentFileNameHint="SERVER2_1-000001.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_1-000002-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "3e5fb0afaa3b2bf38029557abd0f02f1"


alle files

Code: Alles auswählen

17. 01. 2010  16:39        17˙004˙544 SERVER2_1-000001-delta.vmdk
18. 01. 2010  12:17               322 SERVER2_1-000001.vmdk
17. 01. 2010  16:11    53˙452˙437˙504 SERVER2_1-000002-delta.vmdk
18. 01. 2010  00:16               307 SERVER2_1-000002.vmdk
18. 01. 2010  00:05    64˙424˙509˙440 SERVER2_1-flat.vmdk
17. 01. 2010  23:58            28˙397 SERVER2_1-Snapshot1.vmsn
17. 01. 2010  23:58            28˙404 SERVER2_1-Snapshot2.vmsn
18. 01. 2010  00:25               682 SERVER2_1.vmdk
18. 01. 2010  03:55               429 SERVER2_1.vmsd
18. 01. 2010  00:18             2˙988 SERVER2_1.vmx
17. 01. 2010  21:41               264 SERVER2_1.vmxf
17. 01. 2010  23:58            40˙703 vmware-1.log
17. 01. 2010  23:58           889˙949 vmware.log


danke

[continuum]

Das passt vorne und hinten nicht zu deiner beschreibung ???

die Dateiliste sieht doch gut aus - da scheint nichts zu fehlen...

So wie es aussieht hat SERVER2_1.vmdk 2 snapshots die alle vorhanden sind.
Aber die Groessen von der SERVER2_1.vmdk passen nicht mit den Groessen der snapshots zusammen ....

Da fehlen mir wichtige Details ....

[thinos]

Code: Alles auswählen

Please answer the following questions as good as you can.
Not all question apply to all cases - anyway the more info you provide the better the chances.

Download this txt-file and edit it with a simple texteditor like notepad or Kate.
Do not use Word.     

1. Basics

[  thinos  ]  Name or nicname at VMTN or VMware-forum
[  thinos@gmail.com  ]  email
[    ]  date
[    ]  phone
[    ]  skype




2. Attached information :

[ x  ] detailed filelisting - including size, date (and permissions if Linux host)
[ x  ] current vmx
[   ] all vmware.logs available in the VM-directory
[   ] all vmdk-files smaller than 100 kb
[   ] vmsd-file
[   ] all other files smaller than 100 kb
[   ] screenshot of snapshotmanager
[   ] screenshot of datastorebrowser
[   ] screenshot of error-message - if not possible writedown the message as good as you remember it
[   ]


! Please use *.jpg, *.png or *.gif for screenshots !

[    ] All files are zipped - please specify name of zip-archive 
[    ] in case the archive is password protected - specify password



3. When was the last successful use of the VM ?     
[ 16.1  ] date and time of last successful use


4. Which platform was used for last successful start - please specify
[   ]  ESX 4
[ x  ]  ESX 4i
[   ]  ESX 3.5
[   ]  ESX 3.5i
[   ]  ESX 3
[   ]  VMserver 2 - Linux
[   ]  VMserver 2 - Windows
[   ]  VMserver 1 - Windows
[   ]  VMserver 1 - Linux
[   ]  Workstation 6.5  Windows
[   ]  Workstation 6.5  Linux 
[   ]  Workstation 6.0  Windows
[   ]  Workstation 6.0  Linux 
[   ]  Workstation 5.5  Windows
[   ]  Workstation 5.5  Linux 
[   ]  Workstation 5.0  Windows
[   ]  Workstation 5.0  Linux 
[   ]  Workstation 4.5  Windows 
[   ]  Workstation 4.5  Linux   
[   ]  Fusion 2
[   ]  Fusion 1
[   ]  other - please specify


5.Which platform was used when the issue occured ? - please specify
[ x  ] host uses 64 bit CPU
[   ] host uses 32 bit CPU


[   ]  ESX 4
[ x  ]  ESX 4i
[   ]  ESX 3.5
[   ]  ESX 3.5i
[   ]  ESX 3
[   ]  VMserver 2 - Linux
[   ]  VMserver 2 - Windows
[   ]  VMserver 1 - Windows
[   ]  VMserver 1 - Linux
[   ]  Workstation 6.5  Windows
[   ]  Workstation 6.5  Linux 
[   ]  Workstation 6.0  Windows
[   ]  Workstation 6.0  Linux 
[   ]  Workstation 5.5  Windows
[   ]  Workstation 5.5  Linux 
[   ]  Workstation 5.0  Windows
[   ]  Workstation 5.0  Linux 
[   ]  Workstation 4.5  Windows 
[   ]  Workstation 4.5  Linux   
[   ]  Fusion 2
[   ]  Fusion 1
[   ]  other - please specify

In case Windows or Linux is the used Platform - please specify
[   ]  Linux distribution
[ x ]  Windows Version



6. Is the VM in use right now
[    ] yes
[ x ] no


7. Which filesystem is the VM stored on ?
[   ] VMFS - blocksize 1 MB
[   ] VMFS - blocksize 2 MB
[   ] VMFS - blocksize 4 MB
[   ] VMFS - blocksize 8 MB
[ x  ] NTFS
[   ] FAT32
[   ] FAT
[   ] EXT2
[   ] ESX3
[   ] other - please specify .....

8. How much free space is available in the directory/datastore where the VM is stored ?
{ 20gb  ] Gb

9. Did you ever get any CRC errors when using the drive where the VMs are stored on ?
[   ] yes
[ x  ] no

10. Is the VM a Clone ?
[ x  ] no
[   ] linked Clone
[   ] full Clone

11.In case of a linked Clone - is the parent VM/ disk still available and healthy ?
[   ] yes
[   ] no
[ x  ] unknown


12. In case the VM is running on a ESX - do you have access via WinSCP or FastSCP or similar tools ?   
[   ] yes
[ x  ] no - only Datstorebrowser is available

13. Some questions about the history of the VM ... please mark all that applies
[   ] is the VM an import of a physical machine ?
[   ] has the VM been moved cross VMware platforms ?
[   ] the VM is a fresh installation on current plaform ?
[   ] error occured during or after a snapshotmanager-operation
[   ] error occured during or after a vmdk-resize-operation
[   ] error occured after VMware-application crash
[   ] error occured after a crash of the host (Windows, Linux, MAC or ESX)
[   ] error occured after a disk-failure
[ x  ] error occured after the drive on which the VM is stored run out of space


14. The following tools  are available ...
[ x ] Linux LiveCD with Java support
[   ] BartPE
[   ] MOA
[   ] ESXi USB-stick
[ x  ] Windows Recovery tools like UFS-explorer, GetDataBack or similar     

15. How do you rate your skills with this tools ... (1=good, 2=average, 3=noob)

[ x ] Windows commandline
[ x ] Linux commandline
[   ] ESX commandline tools


is it enought? or should i add something?

[continuum]

You need to explain why the size of your basedisk does not match the size of youir snapshots - as soon as I understand that issue I can come up with suggestions - but not before that.

Did you ever expand the vmdk with vmkfstools ?

[thinos]

nein, die basedisk habe ich nachher gemacht, meine basedisk habe ich ausgeloscht.
dan habe ich die basedisk in der grose wie war sie in anfang.

ich habe keine nicht mit vmkfstools gespielt.

[continuum]

the new basedisk is too small - you must use the same size as the original and that was 110 Gb

[thinos]

can i enlarge the disk or should i make a new one?

[continuum]

create a new one - and format it with the very same filesystem your corrupt disk used

[thinos]

done what next?

[continuum]

post the 3 files again

[thinos]

SERVER2_1 - main flat file

Code: Alles auswählen

# Disk DescriptorFile
version=1
encoding="windows-1250"
CID=fffffffe
parentCID=ffffffff
isNativeSnapshot="no"
createType="monolithicFlat"

# Extent description
RW 230686720 FLAT "SERVER2_1-flat.vmdk" 0

# The Disk Data Base
#DDB

ddb.virtualHWVersion = "7"
ddb.longContentID = "cf0178fe7e857b960f1d7e85fffffffe"
ddb.uuid = "60 00 C2 99 31 47 2c 94-a1 a0 4a de 07 fe d7 63"
ddb.geometry.cylinders = "14359"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

SNAPSHOT 1

Code: Alles auswählen

version=1
encoding="UTF-8"
CID=85bb5e2a
parentCID=0db311b5
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="SERVER2_1.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_1-000001-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "5cb39fc99e2e93680d15fb6085bb5e2a"

SNAPSHOT 2 - the file with the data

Code: Alles auswählen

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=bd0f02f1
parentCID=85bb5e2a
createType="vmfsSparse"
parentFileNameHint="SERVER2_1-000001.vmdk"
# Extent description
RW 230686720 VMFSSPARSE "SERVER2_1-000002-delta.vmdk"

# The Disk Data Base
#DDB

ddb.longContentID = "3e5fb0afaa3b2bf38029557abd0f02f1"

Files :

Code: Alles auswählen

17. 01. 2010  16:39        17˙004˙544 SERVER2_1-000001-delta.vmdk
18. 01. 2010  12:17               322 SERVER2_1-000001.vmdk
17. 01. 2010  16:11    53˙452˙437˙504 SERVER2_1-000002-delta.vmdk
18. 01. 2010  00:16               307 SERVER2_1-000002.vmdk
18. 01. 2010  19:18   118˙111˙600˙640 SERVER2_1-flat.vmdk
17. 01. 2010  23:58            28˙397 SERVER2_1-Snapshot1.vmsn
17. 01. 2010  23:58            28˙404 SERVER2_1-Snapshot2.vmsn
18. 01. 2010  19:18               491 SERVER2_1.vmdk
18. 01. 2010  03:55               429 SERVER2_1.vmsd
18. 01. 2010  00:18             2˙988 SERVER2_1.vmx
17. 01. 2010  21:41               264 SERVER2_1.vmxf
17. 01. 2010  23:58            40˙703 vmware-1.log
17. 01. 2010  23:58           889˙949 vmware.log

what next?

[continuum]

SERVER2_1 - main flat file

Code: Alles auswählen

# Disk DescriptorFile
version=1
encoding="windows-1250"
CID=0db311b5
parentCID=ffffffff
isNativeSnapshot="no"
createType="monolithicFlat"

# Extent description
RW 230686720 FLAT "SERVER2_1-flat.vmdk" 0

# The Disk Data Base
#DDB
ddb.virtualHWVersion = "7"
ddb.geometry.cylinders = "14359"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

EDITIER DIE SERVER2_1.VMDK so wie hier geaendert.
In den anderen snapshot vmdk entfern die ddb.longContentID Eintraege.

In der vmx muss der vmdk-eintrag auf den snapshot 000002 verweisen - unbedingt kontrollieren !!

Danach kannst du versuchen die VM mit einer LiveCD zu booten

[thinos]

linux in vm is running, next step?

[thinos]

SERVER2_1.vmx

Code: Alles auswählen

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "7"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
nvram = "SERVER2_1.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
unity.customColor = "|23c0c0c0"
tools.upgrade.policy = "useGlobal"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"

displayName = "SERVER2"
extendedConfigFile = "SERVER2_1.vmxf"
floppy0.present = "TRUE"


numvcpus = "4"
scsi0.present = "TRUE"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsisas1068"
memsize = "5120"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "SERVER2_1-000002.vmdk"
scsi0:0.deviceType = "disk"
ide1:0.present = "TRUE"
ide1:0.clientDevice = "FALSE"
ide1:0.deviceType = "atapi-cdrom"
ide1:0.startConnected = "FALSE"
floppy0.startConnected = "FALSE"
floppy0.clientDevice = "TRUE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "VM Network"
ethernet0.addressType = "generated"
guestOSAltName = "Microsoft Windows Server 2008 (64-bit)"
guestOS = "longhorn-64"
uuid.location = "56 4d 6d 27 b0 25 4a 36-df 96 91 62 59 79 5e 09"
uuid.bios = "56 4d 6d 27 b0 25 4a 36-df 96 91 62 59 79 5e 09"
vc.uuid = "52 d7 ce 00 05 32 f0 9d-0a f8 8c 24 29 c3 74 d7"

ethernet0.generatedAddress = "00:0c:29:79:5e:09"
cleanShutdown = "TRUE"
replay.supported = "FALSE"
sched.swap.derivedName = "/vmfs/volumes/4abd189a-da3fafef-15dc-00215e4f9dc0/SERVER2_1/SERVER2_1-d32d874a.vswp"
scsi0:0.redo = ""
vmotion.checkpointFBSize = "4194304"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "160"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
scsi0.sasWWID = "50 05 05 67 b0 25 4a 30"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "1501126153"
hostCPUID.0 = "0000000a756e65476c65746e49656e69"
guestCPUID.0 = "0000000a756e65476c65746e49656e69"
userCPUID.0 = "0000000a756e65476c65746e49656e69"
hostCPUID.1 = "0001067a00040800000ce3bdbfebfbff"
guestCPUID.1 = "0001067a00010800800822010febfbff"
userCPUID.1 = "0001067a00040800000822010febfbff"
hostCPUID.80000001 = "00000000000000000000000120100800"
guestCPUID.80000001 = "00000000000000000000000120100800"
userCPUID.80000001 = "00000000000000000000000120100800"
evcCompatibilityMode = "FALSE"

ide1:0.fileName = "/vmfs/devices/genscsi/mpx.vmhba0:C0:T0:L0"
floppy0.fileName = "/dev/fd0"

tools.syncTime = "FALSE"
tools.remindInstall = "TRUE"



getting message that

Could not open virtual machine : SERVER2_1.vmx
Something is wrong with the configuration file