virtualbox.org

Hi VirtualBox Experts!

I have been struggling with a damaged guest for some time now, and have begun building a replacement. I still hope to recover my files but have to move on. However...

In the course of troubleshooting the corrupt pre-header for my Ubuntu guest, I ran CHKDSK. Ohhhh myyy. I few google searches later I decided to run SFC /SCANNOW. Ouch. Apparently, Windows Update has been trying unsuccessfully to install a few packages since 5/19. Every night on shutdown. The majority of the logfile from SFC relates the unsuccessful attempts to install these packages. After that, the tail of the log shows a series of errors ("Ignoring duplicate ownership for..." and "Move File: Source = ..." and "Could not reproject corrupted file") involving hundreds of files.

Why am I posting this here? Well, I can't really see if Windows Update, or the file corruption, actually impacted my virtualbox guest. I've tried searching the file for keywords and have had no luck. I'll append the logfile here, and the results from CHKDSK, in the hope that someone can see where the damage occurred. Thanks in advance.

Regards,
Bob

EDIT: The whole logfile is (apparently) too large to attach, so I am zipping a subfile with entries dated 6/8...

I'm not sure what it is that you're asking us to look at? Host or guest file corruption is a matter between you and your respective host and guest operating systems. It would only be something for us to look at if you were suggesting that VirtualBox somehow caused the corruption - and I'm quite sure someone else would have noticed, and mentioned it by now, if that was the case.

I also don't recognize the log files - they are not from VirtualBox.

The virtualbox log is at the top of the attachment labeled "proteus_chkdsk_log_150608.txt"... I added the chkdsk results after that.

What I am looking for is a way to recover my damaged ubuntu guest, or at least getting the files off of it. In the course of researching the solution to that, I ran into what may be the source of the corruption, but I don't see any references to directory "c:\VirtualBox VMs" in the sfc logfile. I'm struggling to understand both events happening at the same time, yet having separate causes. It's more likely that they had a common cause, but I can't see any reference to vbox in the scan log.

Oh, I see. Well the VirtualBox part of the log is very short and you've already told us what it told you: you have host OS filesystem corruption. If you like you can use a hex editor such as FrHed to save off the first (say) 64kb of the VDI file, zip it and attach it here, and I should be able to tell if the VDI is potentially recoverable. Use "Open partially..." in FrHed, since of course the VDI is going to be far to big for system memory.

Speaking of which, it would also be useful to know how big the file is now.