Page 1 of 1

[Solved] Too many file or too large size so that cannot boot

Posted: 18. Sep 2015, 13:48
by X.L
Environment:
Host: Window 8.1 Profession with NTFS partition
VirtualBox: 5.0
Guest OS: Ubuntu 14.04 64bit with vdi image size set to 300GB

My Steps to crash this guest OS:
I tried to build Android 4.2 within this ubuntu but build keep been interrupted with something like:
The I/O cache encountered an error while updating data in medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.
After I put some other files within this virtual OS, it cannot boot up anymore :oops: :oops: with above error pop up. And the vdi file size is about 49854464KB.

Someone has some idea to make this guest OS back to alive? Thank you so much

Re: Too many file or too large size so that cannot boot

Posted: 18. Sep 2015, 15:44
by mpack
Do you have this file on a FAT formatted drive? FAT has a maximum file size of 4GB.

Otherwise, how much free space is on the host drive?

Re: Too many file or too large size so that cannot boot

Posted: 18. Sep 2015, 16:48
by X.L
The partition on host OS is NTFS originally, not formatted from FAT or FAT32. And there are more than 200GB spare space available.

Re: Too many file or too large size so that cannot boot

Posted: 18. Sep 2015, 17:26
by X.L
Another update:
After I use the CloneVDI.exe-2.10 to clone a new vdi image, I found out surprisingly that the image can boot but old image still can not. The image size are as below:
New one 49247812KB
Old one 49854464KB.

Is it 50GB is a dead line that been hard coded within VirtualBox somewhere? :cry:

Re: Too many file or too large size so that cannot boot

Posted: 18. Sep 2015, 17:35
by mpack
X.L wrote:Is it 50GB is a dead line that been hard coded within VirtualBox somewhere? :cry:
No, there is no such boundary.

More likely the original VDI is corrupted somehow.

Re: Too many file or too large size so that cannot boot

Posted: 19. Sep 2015, 01:47
by X.L
If the old image is corrupted, then maybe the clone operation really cue it. I donot know. Anyway, the tool CloneVDI really helps a lot. If without it, weeks of work are lost.