Just recently, I happened to solve a VDI corruption that is VirtualBox refuses to use a previously attached VDI image after restart a VM. I searched for information about the VDI header structure and looked at the header block of the image. The header signature looked good but I found blocks are allocated more than its maximum size. If I modified the number of allocated blocks by hand, VirtualBox turned to be able to recognize it. I finally had to clone the modified image and reattach the new one to the VM in order to resume its normal operation. Is there any easier way to solve such a problem as fsck for filesystems?
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
