I have a very unusual date-related problem that has arisen on one of our Linux VMs.
We're using a VMWare VM as a desktop appliance in developing countries where there is no internet access - ie our master VM is copied onto each computer as an appliance, and after starting up the VM, users simply click a button to launch a browser with the application.
In one installation, however, the computer's clock was accidentally set to 2012 prior to installation of the VM. Once the error was noticed, the clock was corrected, but the VM then stopped working, giving the following error:
"Errors were found while checking the disk drive for /
F to attempt to fix the errors, I to ignore, S to skip mounting, or M for manual..."
If 'F' is chosen, the VM launches, but the error then reappears next time the VM is started. When the clock is changed back to 2012, this error disappears and the VM launches fine, but when the clock is returned to 2011, the VM returns the error message again!
I can't figure out how a clock setting could be affecting the VM's virtual hard disk integrity... Has anybody come across this bug before, or (even more importantly) figured out how to resolve it? (Our team had to drive out for half a day to install a new VM and migrate their data - we want to avoid that next time!)