Host Win7, NTFS
Guest Linux 2.4
My Linux VM does not start, showing VERR_DISK_FULL error (see below)
I made another VM, attaching corrupted VDI to this VM. It does not start either, same error.
My VDI disk is dynamic. Probably it hit host disk full then working. And has been corrupted. Now host disk has 5 Gb free space, but I cant start VDI or any of two Vms with this disk attached to. How can I resque VDI content?
=============================================================================================
Cant open session for VM ALTLINUX-2.4.
VD: error VERR_DISK_FULL opening image file 'C:\Users\vul\VirtualBox VMs\ALTLINUX-2.4\ALTLINUX-2.4.vdi' (VERR_DISK_FULL).
Failed to open image 'C:\Users\vul\VirtualBox VMs\ALTLINUX-2.4\ALTLINUX-2.4.vdi' in read-write mode rc=VERR_DISK_FULL (VERR_DISK_FULL).
Failed to attach driver below us! Disk is full. (VERR_DISK_FULL).
PIIX3 cannot attach drive to the Primary Master (VERR_DISK_FULL).
Код ошибки: E_FAIL (0x80004005)
Компонент: Console
Интерфейс: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
dynamic VDI corrupted after hiting host disk full
-
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: dynamic VDI corrupted after hiting host disk full
Moving to "Windows Hosts".
Unlike VHD, a VDI cannot be corrupted by a host disk full condition. You will simply get a virtual error when the disk can't grow any more.
Also, there is no "tag" in the VDI to say that the host disk is full - the latter would be established by a check of the host, so if you still get the message then the host disk is still full, or so close to full that VBox regards starting the VM as risky. Make sure that you have plenty of free space in the partition the VDI is located on, and make sure that any deleted files are really and fully deleted, i.e. not still in the recycle can. Verify in disk properties that you have lots of free space.
And if you use snapshots, that is likely to be where the disk space went, and moving the base VDI from a snapshot chain to another VM would be a classic nooby error.
Unlike VHD, a VDI cannot be corrupted by a host disk full condition. You will simply get a virtual error when the disk can't grow any more.
Also, there is no "tag" in the VDI to say that the host disk is full - the latter would be established by a check of the host, so if you still get the message then the host disk is still full, or so close to full that VBox regards starting the VM as risky. Make sure that you have plenty of free space in the partition the VDI is located on, and make sure that any deleted files are really and fully deleted, i.e. not still in the recycle can. Verify in disk properties that you have lots of free space.
And if you use snapshots, that is likely to be where the disk space went, and moving the base VDI from a snapshot chain to another VM would be a classic nooby error.
Re: dynamic VDI corrupted after hiting host disk full
You are right, adding more free space helps. 5 Gb is not enought, 15 Gb ruled the problemUnlike VHD, a VDI cannot be corrupted by a host disk full condition. You will simply get a virtual error when the disk can't grow any more.