Ticket #3025 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

Windows Host, Win XP Guest VHD corrupted after with 2.06 and 2.10

Reported by: dahcto Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 2.1.0 Keywords:
Cc: Guest type: Windows
Host type: Windows


Tried on VirtualBox 2.06 and VirtualBox 2.1. I converted a Virtual PC dyanmic .VHD to use with VirtualBox. Uninstalled VPC additions, reactivated, reinstalled VBox Additions. XP SP 2 to start. Ran Windows update and kept failing on SP3 (update or downloadable). Traced problem to VHD corruption. Found that files written to disk were getting corrupted. I kept going back to good copies and updating until there was a problem. The corruption issues seemed to appear when over 4GB (started at 2.8GB). I saw other issues with .VHD and 2.1 so went back to 2.06 an retried. Converted the .VHD to fixed and then to a .VDI, then back to dynamic. Ran through the update process again. Everything works fine as a .VDI. Installed SP3+ all updates. File size grew to 6GB+. Dynamic .VHD was corrupted at over 4GB until I changed to using a dynamic .VDI instead. Even downloading the SP3 (316MB) file or a small 5MB file corrupted the drive when it was in the failure mode.

Change History

comment:1 Changed 9 years ago by dahcto

I found the specific corruption data was "occasional" sectors filled with zeroes.

comment:2 Changed 9 years ago by CrpfBU

comment:3 Changed 9 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to duplicate

comment:4 Changed 9 years ago by nezroy

  • Status changed from closed to reopened
  • Resolution duplicate deleted

I'm still seeing this issue in 2.1.4. As soon as my VHD goes over 4GB, I get disk corruption like crazy in the VHD image. This is a Windows XP guest on a Windows Vista x64 host.

Decided to re-open this instead of since this one most accurately describes the exact issue I run into.

comment:5 Changed 9 years ago by nezroy

Just updated to 2.2.0 and so far no issues on a VHD >4GB, so maybe it's really fixed this time.

comment:6 Changed 9 years ago by sandervl73

  • Status changed from reopened to closed
  • Resolution set to fixed

Thanks for the feedback.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use