VBoxManage error: Details: code VBOX_E_FILE_ERROR (0x80bb0004)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
aubreyli
Posts: 2
Joined: 27. May 2019, 03:39

VBoxManage error: Details: code VBOX_E_FILE_ERROR (0x80bb0004)

Post by aubreyli »

I'm at version 6.0.8 r130520 (Qt5.6.2), I encountered the following error of one of my virtual machine,
c:\Program Files\Oracle\VirtualBox>VBoxManage.exe clonemedium "c:\Users\cli6\VirtualBox VMs\simics_debian\simics_debian.vdi" "c:\Users\cli6\VirtualBox VMs\simics_debian\simics_debian.raw" --format RAW
0%...10%...20%...30%...40%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Failed to clone medium
VBoxManage.exe: error: Could not create the clone medium 'C:\Users\cli6\VirtualBox VMs\simics_debian\simics_debian.raw' (VERR_IO_CRC)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCloneMedium(struct HandlerArg *)" at line 1023 of file VBoxManageDisk.cpp
What interesting is, another virtual machine works properly
c:\Program Files\Oracle\VirtualBox>VBoxManage.exe clonemedium "c:\Users\cli6\VirtualBox VMs\ubuntu\ubuntu.vdi" "c:\Users\cli6\VirtualBox VMs\ubuntu\ubuntu.img" --format RAW
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Clone medium created in format 'RAW'. UUID: d818594f-172a-4bd7-92dc-a10ea8aaa47a
The difference of these two VMs are:
- debian9 v.s. ubuntu 18.10
- debian9 boot from UEFI v.s. ubuntu 18.10 boot from legacy BIOS

I have enough free disk space on my drive C

Any suggestions are highly appreciated!
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VBoxManage error: Details: code VBOX_E_FILE_ERROR (0x80bb0004)

Post by socratis »

aubreyli wrote:I encountered the following error of one of my virtual machine
This is not an error with a Virtual Machine. You're seeing this error on your host when trying to convert a VDI to a raw image, not the same thing.

The error (VERR_IO_CRC) seems to be with the file itself, CRC error in the file. Something seems to be not right with your hardware. What does 'dmesg' have to say about it?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
aubreyli
Posts: 2
Joined: 27. May 2019, 03:39

Re: VBoxManage error: Details: code VBOX_E_FILE_ERROR (0x80bb0004)

Post by aubreyli »

socratis wrote:This is not an error with a Virtual Machine. You're seeing this error on your host when trying to convert a VDI to a raw image, not the same thing.
It is that one Virtual Machine image can be converted while the other can't, which makes me to think it's about Virtual Machine.
socratis wrote:The error (VERR_IO_CRC) seems to be with the file itself, CRC error in the file. Something seems to be not right with your hardware. What does 'dmesg' have to say about it?
My host is win10, how to obtain a similar log as 'dmesg'? I run chkdsk in read-only mode and it seems no error found.

Code: Select all

c:\Program Files\Oracle\VirtualBox>chkdsk
The type of the file system is NTFS.
Volume label is OSDisk.

WARNING!  /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
  495360 file records processed.
File verification completed.
  16169 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  688 reparse records processed.
  597910 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  688 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  51276 data files processed.
CHKDSK is verifying Usn Journal...
  34312592 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 347486207 KB total disk space.
 113663692 KB in 269199 files.
    166660 KB in 51277 indexes.
         0 KB in bad sectors.
    613207 KB in use by the system.
     65536 KB occupied by the log file.
 233042648 KB available on disk.

      4096 bytes in each allocation unit.
  86871551 total allocation units on disk.
  58260662 allocation units available on disk.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VBoxManage error: Details: code VBOX_E_FILE_ERROR (0x80bb0004)

Post by socratis »

You're right, you're on Windows hosts, not Linux! :o

How big is the VDI that you want to convert? Theoretical size, not the size that it occupies on your host. But again, the error is quite clear, something doesn't work during the conversion and it gives you a checksum error...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply