VBoxManage --resize destoyed disk

This is for discussing general topics about how to use VirtualBox.
Post Reply
bepi58
Posts: 1
Joined: 8. Jun 2016, 22:42

VBoxManage --resize destoyed disk

Post by bepi58 »

I wanted to increase the size of my Windows 10 virtual disk:
VBoxManage modifyhd --resize 80000000000 2ef33a2c-82a8-4dbe-97e9-4297a2011a8b
When I wanted to restart my virtual machine I got an error message. I tried to solve it with:
VBoxManage closemedium disk 2ef33a2c-82a8-4dbe-97e9-4297a2011a8b
Got the message: "cannot be closed because it is still attached to 1 virtual machines"
So I de attached this disk and the closed it. Since the when I want to re attach this disk I get:
Die Plattenabbilddatei /home/henri/.VirtualBox/Machines/Windows-10/Windows-10.vdi konnte nicht geöffnet werden.

Could not get the storage format of the medium '/home/henri/.VirtualBox/Machines/Windows-10/Windows-10.vdi' (VERR_NOT_SUPPORTED).

Fehlercode:VBOX_E_IPRT_ERROR (0x80BB0005)
Komponente:Medium
Interface:IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee:IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC:VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

What can I do to fix the problem?
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VBoxManage --resize destoyed disk

Post by Perryg »

80,000,000,000MB ( what you entered ) is way too large. The largest available hard drive is only 4 TB so you can see your error. As for recovering you would need to use a backup ( if you created one ).

I am post correct instructions for you to use in the future. viewtopic.php?f=24&t=50661
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: VBoxManage --resize destoyed disk

Post by mpack »

And just to clarify: it is unlikely that VirtualBox destroyed the disk. What actually happened is that you made the drive so large that the guest BIOS or guest OS no longer supports it. We could have been more helpful about the latter if you had given details of the guest OS error.

I see that you identified the target VDI by UUID. Does that mean that the VDI in question is a snapshot? If that is the case then I don't know of any tool which can fix it, assuming you did this without making a backup. If you make a backup now then I guess it would do no harm to try the unofficial third party tool vidma (read the messages at beginning and end of the topic), but I doubt that developer had snapshots in mind.
Post Reply