VMware Cloud Community
Nithesh1
Contributor
Contributor

SHA1 digest of file VMware-vCenter-Server-Appliance-6.0.0.5100-2562625_OVF10-disk2.vmdk does not match manifest

I am getting the error during the installation on VCSA 6.0.

SHA1 digest of file VMware-vCenter-Server-Appliance-6.0.0.5100-2562625_OVF10-disk2.vmdk does not match manifest

I am unable to delete the .mf file as well.

Any solutions?

Tags (2)
10 Replies
thecloudxpert
Enthusiast
Enthusiast

Nithesh1 -

Have you tried downloading the ISO version rather than the Zip?

You could then mount this to your workstation / a windows sever logically close to the target location and run the installation of VCSA from there?

Reply
0 Kudos
Nithesh1
Contributor
Contributor

Tried it. Did not work.

Downloaded the ISO version.

Reply
0 Kudos
Nithesh1
Contributor
Contributor

I resolved the previous issue by downloading another version of vcenter.

Now, I have the error 2016-06-07T14:39:12.695Z: RPM Installation failed

Any suggesions

Reply
0 Kudos
thecloudxpert
Enthusiast
Enthusiast

Can you provide more information on what your actually doing?

I've never had the VCSA fail with an RPM installation error before.

What servers and vsphere version are you installing this on?

Reply
0 Kudos
djpcolar
Contributor
Contributor

I am seeing a similar problem with the VCSA 6.5 distribution:

SHA digest of file VMware-vCenter-Server-Appliance-6.5.0.5100-4602587_OVF10-disk1.vmdk does not match manifest

Extracting the OVA file from the ISO also fails to deploy.

VMware vCenter Server Appliance

2016-11-15 | 6.5.0 | 3.37 GB | iso

MD5SUM(¹): 01469bfe099292180fe97abbbf5c58db

SHA1SUM(¹): d4311f6a58f304768e86a7476446769d64fd0ece

2016-12-01T14:23:25.952Z - info: output:ERROR

+ <Errors>

+ <Error>

+ <Type>ovftool.manifest.mismatch</Type>

+ <LocalizedMsg>

+ SHA digest of file VMware-vCenter-Server-Appliance-6.5.0.5100-4602587_OVF10-disk1.vmdk does not match manifest

+ </LocalizedMsg>

+ <Arg>

+ VMware-vCenter-Server-Appliance-6.5.0.5100-4602587_OVF10-disk1.vmdk

+ </Arg>

+ </Error>

+ </Errors>

2016-12-01T14:23:33.010Z - info: output:RESULT

+ ERROR

2016-12-01T14:23:33.010Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovf

tool.manifest.mismatch</Type><LocalizedMsg>SHA digest of file VMware-vCenter-Server-Appliance-6.5.0.5100-4602587_OVF10-d

isk1.vmdk does not match manifest</LocalizedMsg><Arg>VMware-vCenter-Server-Appliance-6.5.0.5100-4602587_OVF10-disk1.vmdk

</Arg></Error></Errors></data>

2016-12-01T14:23:33.015Z - error: Ovf Service:vmrefFlag: false

2016-12-01T14:23:33.015Z - info: Cancelling timeout due to error from progress callback

2016-12-01T14:23:33.015Z - error: Progress Controller: [VCSA ERROR] - Progress callback error

2016-12-01T14:23:33.016Z - error: Progress Controller: [VCSA ERROR] - Details SHA digest of file VMware-vCenter-Server-Appliance-6.5.0.5100-4602587_OVF10-disk1.vmdk does not match manifest

Reply
0 Kudos
LUCKY1011
Enthusiast
Enthusiast

Such issues occurs if we have latency.

Hope you are having Esxi host and the ISO file located on the same location.

Thanks

Jahid Khan

Reply
0 Kudos
breakr
Contributor
Contributor

This is exaclty the issue I am having now.  My ISO seems to be corrupt but now I am starting to hesitate to accept that answer.

Reply
0 Kudos
daphnissov
Immortal
Immortal

Well, as identified in your thread here, your hash does not match the value which is posted by VMware. So regardless of whether this is the 100% exact cause or not, we know you have corruption or missing data somewhere in that file. As in Monopoly, do not pass go and do not collect $200, because if you have corruption then nothing else really matters until that's resolved.

breakr
Contributor
Contributor

Since then I have managed to get the newer ISO for 6.7... and it got deployed without issues. So there is now evidence that the issue WAS indeed the corrupt ISO.

Reply
0 Kudos
invisibledev
Contributor
Contributor

• Step1 – Extract the required .ova file and there will be .ovf and .mf files created post extraction.

• Step2 – Edit the .ovf file by changing vmx-18 (any number ) change to vmx-7 after opening it in the text mode and save the changes.

• Step3- Delete the .mf file.

• Step4- Open .ovf file with VMWare workstation.

• Step5- ide0 error not detected by VM’s, so Select ‘No’ while switching ON the machine on VM ware.

 

then you get another error ... click retry the problem will be solve with 100% .. thnx ...  

Muhammad Hafizur Rahman

Reply
0 Kudos