Hi everyone,
I have a problem to open a vdi file. When i try to create a vm using this .vdi and i start it i get an error "Error Reading Disk; Press ctrl+alt-sup to restart".
What i have tried is:
- Add to other vm (windows) which works perfect. I can see the volumen, but it appear inconsistent and windows says i should format...not a good idea
- After that, from ubuntu, i tried to read de .vdi using kvm but i got, again, a message something like "corrupt file"....
- Then i read sometimes the header of the .vdi gets corrupt, so i opened with an hexadecimal-editor and the firsts 72 bytes looks right
Now i am close to give it up, please any idea i haven´t probe it´s wellcome
Thanks in advance,
ford
Error VDI File "Error reading disk"
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Error VDI File "Error reading disk"
Sounds like the VDI is corrupt. It may have been truncated by transporting it on a FAT32 formatted external drive. The only way you can be sure the disk is not corrupted is with an MD5 sum from the two hosts.
Incidentally, the proper way to move a VM is to copy the entire VM folder, not take the disk drive out and home. That would not have prevented this corruption, but it would avoid additional problems with setting up an identical VM. The other files in the VM folder only amount to a few meg at most - usually only measured in K - so there's no reason to not do it.
Incidentally, the proper way to move a VM is to copy the entire VM folder, not take the disk drive out and home. That would not have prevented this corruption, but it would avoid additional problems with setting up an identical VM. The other files in the VM folder only amount to a few meg at most - usually only measured in K - so there's no reason to not do it.
Re: Error VDI File "Error reading disk"
Thanks mpack,
You are right, i moved the vdi file to other volumen, so that should be the problem.
Next time i would be more carefully....
You are right, i moved the vdi file to other volumen, so that should be the problem.
Next time i would be more carefully....