How frustrating...! That is so annoying!

Well I guess at least we know that it's not corrupt now...

I wonder what the problem might be. When I tested last night I wasn't actually using VirtualBox (I was using KVM). So I'm about to fire it up in VirtualBox (on Windows) to see what happens then...