Page 79 of 83

Re: CloneVDI tool - Discussion & Support

PostPosted: 19. Jun 2018, 17:29
by Turbodid
Thanks for the information

My problem is to migrate a vdi file from an older version

Does VBoxManage do it??

Re: CloneVDI tool - Discussion & Support

PostPosted: 19. Jun 2018, 20:53
by socratis
Turbodid wrote:My problem is to migrate a vdi file from an older version

What does that mean? What older version?

Re: CloneVDI tool - Discussion & Support

PostPosted: 19. Jun 2018, 21:40
by Turbodid
Older version of virtualbox

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 02:23
by socratis
VDIs don't really change in between VirtualBox versions. Do you mind telling us why you think you need to "migrate" the hard disk? In what sense? From what version? Please give us the whole plan, this is not Twitter, you could elaborate...

We may be veering off from the CloneVDI help here...

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 08:06
by Turbodid
Hello,

When I try to create a new machine with an existing disk I get the following error:

Echec de l'ouverture du fichier d'image de disque E:\VM\La poste - KAORA - Sysperiane\Clone de VM Divalto Démo - X.1 - V39-disk1.vdi.

Could not get the storage format of the medium 'E:\VM\La poste - KAORA - Sysperiane\Clone de VM Divalto D�mo - X.1 - V39-disk1.vdi' (VERR_NOT_SUPPORTED).

Code d'erreur : VBOX_E_IPRT_ERROR (0x80BB0005)
Composant : MediumWrap
Interface : IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Fonction appelée : IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}
Code retourné : VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)



So how to solve it?

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 09:29
by mpack
It looks like that VDI has been corrupted. You can try opening it with the GUI version of CloneVDI and see if the repair option is offered.

Where did this VDI come from, and what is drive E: ? Because another explanation of VERR_NOT_SUPPORTED is that the VDI has been truncated by being transported on a FAT formatted external drive.

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 14:02
by Turbodid
Where can I download the CloneVDI GUI?

Thanks

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 14:10
by socratis
At the very first post of this thread.

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 14:16
by mpack
Turbodid wrote:Where can I download the CloneVDI GUI

You already downloaded it. CloneVDI is a native Win32 GUI application. Just run it normally: not from the command line, and not using any command line arguments. It isn't clear to me why you did that in the first place.

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 18:10
by Turbodid
Bad news

see the 2 attached files

:x
error.png
error.png (62.65 KiB) Viewed 5401 times

Re: CloneVDI tool - Discussion & Support

PostPosted: 20. Jun 2018, 19:15
by mpack
Hmm. Word wrapping is poor in the first dialog on your host. I'll need to fix that.

"OS error 0" means that it reached end of file unexpectedly, i.e. the file is truncated - which matches my earlier suggestion.

mpack wrote:and what is drive E: ? Because another explanation of VERR_NOT_SUPPORTED is that the VDI has been truncated by being transported on a FAT formatted external drive.


I assume you are aware that FAT partitions (most external thumb drives are FAT formatted) cannot store files which are larger than 4GB, however there are lot of other possible reasons for why the file came to be truncated.

Re: CloneVDI tool - Discussion & Support

PostPosted: 21. Jun 2018, 10:37
by Turbodid
As you can see in the attached screenshot it is a NTFS partition.

Re: CloneVDI tool - Discussion & Support

PostPosted: 21. Jun 2018, 11:59
by mpack
See the final sentence of my previous post, especially the latter part of that sentence.

I'm afraid that I'm going to have to call a halt to this. This is the CloneVDI support topic. We have already established that you do not have a CloneVDI problem, you have a damaged (truncated) VDI. You can go elsewhere to discuss that, but there is really no point: a truncated VDI cannot be repaired: you need another copy of the original file.

Re: CloneVDI tool - Discussion & Support

PostPosted: 11. Jul 2018, 13:05
by cosmicvibes
Just wanted to say cheers to the original poster. 9 years on and this tool is still saving bacon. Run fine under wine on Ubuntu 18.04. :D

Re: CloneVDI tool - Discussion & Support

PostPosted: 17. Aug 2018, 19:12
by ndt1896
mpack

This is amazing software. It is functional and intuitive in a rare way.

I have been pulling my hair out over a corrupted VDI file. Scouring the web, trying normal disk recovery utilities in windows/linux did not work out for me.

I made some progress by finding your posts like: this site topic =83565

(I registered just to shout out props so cant paste URLS yet, account needs to be a day old.)

Then I landed here and your software solved all my problems, successfully generating a new header for my corrupted file that worked.

I have downloaded the source code you posted and am excited to go through it. I'm interested if you have the cliff notes or napkin math you are doing to calculate the numbers when people give you a vdi file size and [corrupted] header?

Seriously, amazing work..