An Error Occurred During The File System Check Esx
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
Unexpected Inconsistency Run Fsck Manually Centos
systems of the Unidesk appliances (CachePoint Appliances and the Management Appliance). This unexpected inconsistency run fsck manually ubuntu damage can prevent them from booting automatically. When an operational interruption occurs, the startup process prompts the user to unexpected inconsistency run fsck manually redhat enter the root password in order to repair the damaged file system. If you open the vSphere console for the appliance, you see an error and prompt similar to the following: root: https://kb.vmware.com/kb/1017162 UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. (i.e., 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 http://www.unidesk.com/support/kb/appliance-requests-file-system-check-fsck-when-recovering-host-or-storage-interruption when you installed the appliance (this password is different from the one you use to 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
Tags Search LQ Wiki Search Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie [SOLVED] An error occurred during http://www.linuxquestions.org/questions/linux-newbie-8/an-error-occurred-during-the-file-system-check-system-unable-to-start-887514/ the file system check. System unable to start User Name Remember Me? Password Linux - Newbie This Linux forum is for members that are new to Linux. Just starting out and have a https://support.symantec.com/en_US/article.TECH96926.html question? If it is not in the man pages or the how-to's this is the place! Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as an error a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: an error occurred Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Search this Thread 06-21-2011, 06:15 AM #1 rohitchauhan Member Registered: Nov 2010 Distribution: RedHat Posts: 85 Rep: An error occurred during the file system check. System unable to start Hi friends, I am having a problem while starting the Linux (RHEL 5.3).The system is unable to start. Following message is shown on the screen. Please take a look Starting udev: [OK] Loading default keymap(us): [OK] Setting hostname rc [OK] Setting up Logical Volume Management:7logical volume(s) in volume group VolGroup00 now active [OK] Checking filesystems /dev/VolGroup00/LogVol00: clean, 26960/7864320 files, 867567/7864320 blocks /dev/VolGroup00/LogVol02: wxt3 recovery flag is clear, but journal has data. /dev/VolGroup00/LogVol02: run journal anyway /dev/VolGroup00/LogVol02: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY(i.e. , without a or p options) /dev/VolGroup00/LogVol04: clean, 86/.. files, 280/192 blocks /dev/VolGroup00/LogVol05: clean, 11/78 files, /. blocks /dev/VolGroup00/LogVol01: clean, 11/78 files, /. Blocks /boot: clean, ../ files, /. Blocks [FAILED] *** An
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Error: "Unexpected Inconsistency; Run fsck Manually" while booting a Symantec Messaging Gateway TECH96926 February 10th, 2014 http://www.symantec.com/docs/TECH96926 Support / Error: "Unexpected Inconsistency; Run fsck Manually" while booting a Symantec Messaging Gateway Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation While booting a SymantecMessaging Gateway, you see a message displayed on the console indicating an Unexpected Inconsistency on the Appliance. Symptoms The error is usually similar to this screenshot: Cause The hardware environment shows this error when the file system is corrupted. The virtual environment show this error when the backup is performed by using ESX server snapshots of the appliance. It is recommended to configure the backup from the web interface of the Symantec Messaging Gateway: Administration --> Host, Version, Backup. Several op