(i.e., without -a or -p options) fsck exited with status code 4 The root filesystem on /dev/sda6 requires a manual fsck. RUN fsck MANUALLY (i.e., without -a or -p options) fsck exited with.
This issue is seen shortly after powering on a Virtual Machine running in Appliance Virtualization Platform (AVP) or in VMware. This might be a new deployment of an Avaya Appliance OVA or an existing system that is failing to boot up due to this error;/dev/sda6: Superblock last mount time (Tue Jun 30 18:, now = Sun Nov 9 09:) is in the future./dev/sda6: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. (i.e., without -a or -p options) FAILED. An error occurred during the file system check. Dropping you to a shell; the system will reboot. when you leave the shell.Give root password for maintenance (or type Control-D to continue): Avaya Aura Utility Services V7.0 for VMware.US-7.0.0.0.0.12-e55-01Avaya Aura Branch Session Manager V7.0 for VMware. The cause in this case was that the date and time in the AVP Host or VMware Host was very far off the current date and time.
![Without Without](/uploads/1/2/5/3/125376290/736271230.jpg)
If AVP Host / VMware Host was not configured with an NTP server then it will try and pull the date and time from the local hardware date and time, which in this case was very far behind the current date and time. That introduced the error where the Virtual Machine(s) failed to start.There are a few ways to check the current date and time on your AVP Host / VMware Host.
It can either be done from the command line through a PuTTy session directly to the Host or through the VMware vSphere Client. Further screen-shots in this article will give you examples of where you can check the time. The first place you could adjust the time would be the BIOS of the Hardware the AVP Host / VMware Host is running on. As the server starts you can press F9 to access Setup Examaple of HP ProLiant G8 below.Then locate the Date and Time configuration and Enter to edit the Date and Time.The next place you could change the time would be to configure NTP on the AVP Host during Installation you could specify details of the NTP Server. The two fields related to NTP Server can be seen in the screen-shot below.If NTP was not configured during the installation you could change the ' Time Configuration' in the AVP Host / VMware Host as shown below. The screen-shot below was taken from vCenter vSphere Web Client.
The VMware vSphere thick Client will have similar configuration for NTP, in case the Host is not part of vCenter.In the screen-shot below you can see that there was no NTP Server configured and also that the ' NTP Service Status' is Stopped. Before making changes to the AVP Host / VMware Host ensure that there are no running systems on there that could be affected by changes in the host. In the example below you can see that all the Virtual Machines on this Host are in a Stopped state.Edit the time configuration and also 'Start' the 'NTP Service Status'.
This may be enough to allow you to now start your Virtual Machines, however if they still do not want to start you may need to restart the VMware host.