Error Occurred During The File System Check
Contents |
Start-up General support questions Post Reply Print view Search Advanced search 9 posts • Page 1 of 1 Apoth30sis Posts: 11 Joined: 2012/03/07 23:28:15 error occurred during file system check linux [SOLVED] Error on Start-up Quote Postby Apoth30sis » 2012/03/19 05:45:25 Hello all, linux an error occurred during the file system check dropping you to a shell I had a power outage and my CentOS box crashed.This is as far as it gets on boot:Checking an error occurred during the file system check vmware filesystems_CentOS-.6.2-x86_:clean 227387/3238400files, 1841522/13107200 blocks/dev/sda1: Superblock last write time is in the future. (by less than a day, probably due to the hardware clock being incorrectly set). FIXED./dev/sda1: clean, 55/128016 files, an error occurred during directory enumeration 109513/512000 blocks/dev/mapper/vg_mediabox-lv_home: clean, 12484/26836992 files, 1955866/107336704 blocksfsck.ext4: No such or directory while trying to open /dev/sbg/dev/sbg:The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem(and not a swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck
An Error Occurred While Making The Requested Connection
with an alternate superblock: e2fsk -b 8194 *** An error occurred during the file system check.*** Dropping you into shell; the system will reboot*** when you leave the shell.*** Warning -- SELinux is active*** Disabling security enforcement for system recoveryGive root password for maintenance (or type Control D to continue)If I put the root password in for maintenance, the system just hangs. I am completely at a loss here. Any thoughts are appreciated. Top Apoth30sis Posts: 11 Joined: 2012/03/07 23:28:15 Re: Error on Start-up Quote Postby Apoth30sis » 2012/03/19 05:58:55 Correction, the system doesn't hang, it puts me into the shell, which makes more sense. Also important, /dev/sdg is a USB hard drive (ext4 formatted) which is not plugged into the system. It was plugged in when the system crashed. /dev/sda1 is the boot drive. Top TrevorH Forum Moderator Posts: 16831 Joined: 2009/09/24 10:40:56 Location: Brighton, UK Re: Error on Start-up Quote Postby TrevorH » 2012/03/19 09:52:10 Did you add it to /etc/fstab? If you did then it'll be trying to mount it even if it's not present
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red
Error Occurred During Initialization Of Vm
Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform Red an error occurred during the file system check centos Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red an error occurred during file system check redhat Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data http://www.centos.org/forums/viewtopic.php?t=2040 Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back https://access.redhat.com/solutions/390923 Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newslet
Today's Posts Advanced Search Find the answer to your Linux question: Entire Site Articles Downloads Forums Linux Hosting Forum Your Distro Red Hat / Fedora Linux Repair file http://www.linuxforums.org/forum/red-hat-fedora-linux/36988-repair-file-system.html system If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above http://serverfault.com/questions/619725/how-to-access-a-system-with-write-permission-after-file-system-check-fails to proceed. To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now error occurred supports the Tapatalk app for your mobile device. Page 1 of 3 1 2 3 Last Jump to page: Results 1 to 10 of 24 Thread: Repair file system Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Enjoy an ad free experience by logging in. Not a member yet? Register. 07-03-2005 error occurred during #1 zillah View Profile View Forum Posts Private Message View Articles Linux Newbie Join Date Nov 2002 Posts 139 Repair file system I have got 3 OSs on my laptop Latitude Dell D600 (Windows , FC3, Solaris 10) I have got no problem to boot in any of these 3 OSs. After while I tried to boot into linux I received this error message : Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): Repair file system1# After I spent one hour of googling I found this : ((If the system crashes (due to power outage etc...) then upon boot the system will check if the disk was unmounted cleanly. If not you may get the following message: Unexpected inconsistency; Run fsck Manually ... *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot Give root password for maintenance (or type Control-D for normal startup): At this point enter the root password then run fsck: (repair file system) 1# fsck -A -y ***** FILE SYSTEM WAS MODIFIED ***** (repair file system) 2# exit )) The link for above is this :
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to access a system with write permission after file system check fails? up vote -1 down vote favorite I created three new partitions, but after a reboot, the system is being dropped to a shell: /dev/mapper/group-newpartition: clean, 11/655360 files, 276620/2621440 blocks [FAILED] An error occurred during the file system check. Dropping you to a shell; the system will reboot Give root password for maintenance. I tried to fix the disk error with fsck(), but the result status code is 0x4. I tried to reverse what I changed in /etc/fstab so that the system didn't check the partition while booting. But the shell the system being dropped to was a read only file system. I tried to access through the single user mode, but the result was the same. How to fix the problem? centos shell boot hard-drive fsck share|improve this question edited Aug 12 '14 at 17:43 peterh 1 asked Aug 12 '14 at 1:31 Purres 49111 1 Why would you consider attempting to modify a seriously damaged disk that failed an fsck? –mdpc Aug 12 '14 at 2:02 This downvote because you asked a question, didn't even made it ready (see the end), and then disappeared without any reaction. You let others work for nothing. –peterh Aug 12 '14 at 8:38 I check the post when I am available online. I asked 16 hours ago. And revisit the post is the first thing I do this morning when I am before a computer. –Purres Aug 12 '14 at 17:51 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote The reason you are in read-only mode is that: a) Your file system was found to be damaged, then b) Your OS tried to fix it at boot, but failed, so c) Dropped you into a read-only shell so that you can extract and backup your files without modifying original file system hence preventing you from damaging it further. If I were you, I would try to fix the problem first. However, if you do insist, you can remount your filesystem with -o loop,rw like mount -t ext4 /dev/s