An Error Occurred During The File System Check Vmware
Contents |
KB #: 04260 Last Updated: January 14, 2015 Issue An unexpected interruption in the operation of an ESX host or an underlying datastore in VMware can damage the root file systems of the Unidesk appliances
Run Fsck Manually Without A Or P Options
(CachePoint Appliances and the Management Appliance). This damage can prevent them from booting
Unexpected Inconsistency Run Fsck Manually Linux
automatically. When an operational interruption occurs, the startup process prompts the user to enter the root password in order to repair unexpected inconsistency run fsck manually redhat the damaged file system. If you open the vSphere console for the appliance, you see an error and prompt similar to the following: root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. (i.e., https://kb.vmware.com/kb/2004225 without -a or -p options) *** 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): Procedure When prompted to do so, enter the root password---the password that you choose when you installed the appliance (this password is different from the one you use to http://www.unidesk.com/support/kb/appliance-requests-file-system-check-fsck-when-recovering-host-or-storage-interruption log in to the Unidesk Management Console). The default root password is v9Yx*6uj. The root password should have been changed at installation/appliance creation. If not, use theinstructions on theInstallationtopicunderSecure the appliancesto log in andMake sure you've changed the Administrator and root passwords for each appliance after you have recovered. The system displays the following prompt (this prompt waitsfor a command, not part of the error message): (Repair filesystem) 1 # If you are running Unidesk 2.5 or earlier, enter the fsck -y / command at the Repair filesystem prompt to repair the file system. For example: (Repair filesystem) 1 # fsck -y / The fsck utility displays several messages during the repair process. If you are running Unidesk 2.6 or later, there are now two partitions on the boot disk, and you must run two commands: (Repair filesystem) 1 # fsck -y /dev/sda1 (Repair filesystem) 1 # fsck -y /dev/sda3 At the (Repair filesystem) prompt, enter reboot to restart the system. For example: (Repair fileysystem) 2 # reboot Ignore messages about read-only file systems. When the appliance restarts, it should return to normal operations. It's possible; however, that additional cleanup work is required. If the appliance does not seem to be operating normally, conta
Cisco Cisco Unified Communications Manager (CallManager) Troubleshoot Error during Cisco Unified Communications Manager Bootup Hierarchical Navigation HOME SUPPORT PRODUCT http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-50/111822-boot-error-00.html SUPPORT UNIFIED COMMUNICATIONS CISCO UNIFIED COMMUNICATIONS MANAGER (CALLMANAGER) TROUBLESHOOT AND ALERTS TROUBLESHOOTING TECHNOTES Troubleshoot Error during Cisco Unified Communications Manager Bootup Document ID: 111822 Updated: Mar 03, 2010 http://forums.fedoraforum.org/showthread.php?t=277866 Download PDF Print Feedback Related ProductsCisco Unified Communications Manager Version 5.0 Cisco Unified Communications Manager Version 7.1 Cisco Unified Communications Manager Version 7.0 Cisco Unified Communications an error Manager Version 6.0 Cisco Unified Communications Manager Version 6.1 Contents Introduction Prerequisites Requirements Components Used Conventions Error while Booting CUCM 5.x/6.x/7.x Solution Related InformationRelated Cisco Support Community Discussions Introduction During Cisco Unified Communications Manager bootup on the Cisco Media Convergence Server 7816, this error is received: *** An error occured during the file system check. *** Dropping an error occurred you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue): Also, the user is unable to login to Cisco Unified Communications Manager in some other situations. This document describes how to resolve these errors. Prerequisites Requirements There are no specific requirements for this document. Components Used The information in this document is based on the Cisco Unified Communications Manager 5.x/6.x/7.x. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Error while Booting CUCM 5.x/6.x/7.x The Cisco Unified Communications Manager server is unable to boot. When trying to reboot the server, this error message appears regarding inconsistencies in the file system: /common contains a f
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora [SOLVED] "Unexpected inconsistancy run fsck manually" at every boot. FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 21st March 2012, 03:52 PM meganoob Offline Registered User Join Date: Oct 2011 Posts: 10 "Unexpected inconsistancy run fsck manually" at every boot. I feel like my question is pretty basic, but hey, my name says it, i'm a noob, so here it is: after a hardware problem, my computer closed in an unproper way, so now, when I boot, I get this message saying Unexpected insconsistancy, run fsck manually. (I'll print the whole message later, but for now I'm at work, so I don't have it) I ran fsck -f /dev/sda5. (the disk on which my fedora system is) The only two errors that popped up were some dates that were in the future, so I said yes to everything. But every time I reboot, I still get that message. Why? Thanks in advance Meganoob P.S. I scanned through the web for someone with a similar problem, but in every thread I found, people were doing fine once they had ran fsck. meganoob View Public Profile Find all posts by meganoob #2 21st March 2012, 04:17 PM DBelton Online Administrator Join Date: Aug 2009 Posts: 8,111 Re: "Unexpected inconsistancy run fsck manually" at every boot. Your system clock is wrong (are you booting into Windows by chance? it can mess up the system clock if you have Fedora set to use UTC, and Windows using local time). Yo may need to run fsck on more than just the filesystem that your Fedora system is on as well. From the Fedora common bugs: Quote: If you set back your system time for more than one day into the past, Fedora will not boot on next system restart. It will complain about your disk mount time being too far in the future. Typically the error message looks like this (dracut shell): /dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) dracut Warning: e2fsck returned with 4 dracut Warning: /dev/mapper/VolGroup-lv_root: Superblock last mount time (Tue Oct 25 14