After correcting the date and time of the hypervisor to the current date and time this problem should be resolved. According to the vendor this issue occurs when the date and time on the Hypervisor Host is wrong. The first message was very strange since the machine was freshly deployed from an OVF. dev/sda1 has gone x days without being checked After a file system check is forced the machine stops with an error UNEXPECTED INCONSISTENCY followed by fsck / terminated with status 4. According to the machine 255 days where passed without the disk being checked. On initial boot of a freshly deployed (Ubuntu) Linux appliance on VMware vSphere 5 the machine stopped working because of an inconsistent disk.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |