Unreadable hard drive

[rodhzuniga]

Install a virtual machine with 30 gb, now does not start, and suddenly it works but without my data, and with only 1.5 GB, what do I do? I have important information.
Sorry for my writing, I do not speak English.

[socratis]

• Host: ...
• Guest: ...
• VirtualBox version: ...
• Error: ... (exactly)
• Right-click on the VM. Select Show Log. Save it. ZIP it. Attach it to your response, "Upload attachment" below this form.

[rodhzuniga]

Host: MAC OS Sierra
Guest: Windows XP 32 bits
VirtualBox: 5.0
Error: 0×80004005

[socratis]

I'm afraid that you need to be more specific. Details:
Your host can be: 10.12, 10.12.1, 10.12.2, 10.12.3, 10.12.4 developer.
Your guest can be: XP, XP SP1, XP SP2, XP SP3.
For example, your VirtualBox is not "5.0", it's "5.0.32".

But the most important is the error. This is just a number. I need the whole error, full error, not just the error code. Post a screenshot if you have to.

PS. If you can't speak English, post the question in your native language and we'll use Google translate.

[rodhzuniga]

Ok

Host: MAc OS Sierra 10.12.3 (16D32)
Guest: Windows XP SP3
Virtual Box 5.0.32 -112930
I've tried all recent versions, And I have not solved the problem.
My hard drive was 32 gb, now it does not want to start, I made a new machine and assigned that disk .vdi to the new machine, but only recognizes 1.6 gb

Code: NS_ERROR_FAILURE (0x80004005)
component: Medium
Interfaz: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}

Currently installing the disk in a new virtual machine, does not show error, works windows, but without the recent data, only the data from 3 years ago was the beginning.

[socratis]

Code: NS_ERROR_FAILURE (0x80004005)
component: Medium
Interfaz: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}

Was there anything else with that error? There must be. Can you include it? Can you please post a screenshot of the error?

Moving to "Using VirtualBox" from "OS X Hosts".

[rodhzuniga]

This happens when I assign the disk.vdi to the virtual machine

Fallo al abrir el archivo de imagen de disco /Users/macbookpro/VirtualBox Vms/Windows XP/WinxP.vdi.
Could not get the storage format of the medium '/Users/macbookpro/VirtualBox Vms/Windows XP/WinxP.vdi' (VERR_NOT_SUPPORTED).
Código Resultado: VBOX_E_IPRT_ERROR (0x80BB0005)
Componente: MediumWrap
Interfaz: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Receptor: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Receptor RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

[socratis]

It took several messages back and forth, but at least we have the whole error message. Open up Terminal and issue the command:

• VBoxManage showmediuminfo "/Users/macbookpro/VirtualBox Vms/Windows XP/WinxP.vdi"

A couple of things...

• Instead of "VirtualBox VMs" you have "VirtualBox Vms". Not something really important, but did you change it manually? Why?
• The VM is called "Windows XP" and the VDI is called "WinxP.vdi". Did you copy that VDI from somewhere else? Why is the name different?

PS. You can use Google Translate to translate my messages to Spanish: https://translate.google.com

[rodhzuniga]

The virtual machine stopped working alone, update Virtual Box and do not solve the problem. Clone the hard drive with "vboxmanage clonehd" and assign it the name 'WinxP.vdi', getting information from the hard drive with "vboxmanage showhdinfo" I get the same error.

I have already renamed the folder "VirtualBox VMs" and rename the disk from 'WinXp.vdi' to 'Windows XP.vdi' and the problem continues.

My hard drive was 30 Gb, now the original partition from which I got the clone, it only has 1.5 GB.

Thanks for your help.

vboxmanage showmediuminfo "Windows XP.vdi"
VBoxManage: error: Could not get the storage format of the medium '/Users/macbookpro/VirtualBox VMs/Windows XP/Windows XP.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp

[socratis]

1. I didn't ask you to rename the files or the directory. This can create more problems. I was simply asking why they had those names.
2. To me it seems that your VDI is corrupt. Do you have a backup?
3. Wait for user "mpack" to see if he has any more ideas. He knows VDIs.

[rodhzuniga]

If that seems, because the VDI Original, reduced its size, I read that in some forums have corrected it with a chkdsk for windows, in my case with mac I do not know the command.

[socratis]

No, that is not the problem in your case. You cannot get into Windows. 1.5 GB is too small to hold Windows. There is no Windows anymore. You cannot run 'chkdsk'.

There are two more commands I want you to try:

• VBoxManage internalcommands dumphdinfo "/Users/macbookpro/VirtualBox Vms/Windows XP/WinxP.vdi"
  VBoxManage internalcommands repairhd -dry-run "/Users/macbookpro/VirtualBox Vms/Windows XP/WinxP.vdi"

If you changed the directory and the file names, change the commands to match the renamed files.

Clone the hard drive with "vboxmanage clonehd" and assign it the name 'WinxP.vdi'

Do you still have the original file? The one you cloned? What's the size of the original?

[rodhzuniga]

Run the commands and these errors appear

vboxmanage internalcommands dumphdinfo "Windows XP.vdi"
VBoxManage: error: Format autodetect failed: VERR_NOT_SUPPORTED

vboxmanage internalcommands repairhd -dry-run "Windows XP.vdi"
VBoxManage: error: No file format specified and autodetect failed - please specify format: VERR_NOT_SUPPORTED

The original 30 GB file, now only 1.5 GB, when mounted on a new machine, starts but only with windows and without my data.