Ticket #2021 (closed defect: worksforme)
VDI corruption (or file size limitation?)
|Reported by:||thaytan||Owned by:|
|Host type:||Mac OS X|
I have an Ubuntu Hardy VM image that I've been using for a few months, running in an OS/X host. After a reboot of the laptop yesterday, the VM started refusing to boot - getting about halfway through the boot process, and then reporting a cascade of ATA errors, that I'd call 'faulty hard drive' errors, except that they're coming from a VDI file and the host disk is fine. The error output brings the host to its knees with IO, and I typically have to kill the VM, since I can't get it to respond sufficiently to power off.
Attaching a VBox log from when it happens. In the log, it's reporting VERR_EOF when trying to access certain sectors of the VDI. In case it's relevant, the VDI image is at 15.5GB of a 20GB allocation.
I've just tried compacting the VDI, which worked through the image without any warnings or errors, and that seems to have allowed it to boot. Some of the files in the filesystem seem to be corrupted though (filled with 0 bytes). I'm not sure how to diagnose it further.
- Status changed from new to closed
- Resolution set to worksforme