[SOLVED] FC4 refuses to mount file systems - how to fix?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as 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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have been running an FC4 server for a while, when I noticed the / (root) partition becoming full. I ssh-ed the server, deleted a few /var/log files, bringing it down to 98%. I then rebooted and since then the system will boot but will refuse to mount anything.
(cat /etc/fstab produces an error message notifying of not being able to run fstab-sync.)
During boot, the only error message I have been able to spot is this:
After which there are lots of failure to access all kind of system resource due to filesystem being read-only.
The bottom line is that, despite being able to boot the system, I am unable to fix anything because nothing is mounted and I cannot even check what went wrong, why this is happening, and what to write were in order to fix this.
Any help, tip, insight, idea, instructions would be greatly appreciated.
Last edited by lifemustgoon; 11-30-2011 at 12:56 PM.
just disable SELinux (edit /etc/selinux/config) and move on.
OK, I just tried to edit /etc/selinux/config (from "permissive" to "disabled") but the system is in such bad situation, it won't let me to write the file back because is everything (that managed to be mounted) is mounted as a read-only filesystem.
I could use a SysRescueCD to mount that /etc writable, but given that SELinux was set to "permissive" (i.e. warnings only), is that really the solution to the problem?
Correct. It is empty, except for a single comment line saying that "This file is edited by fstab-sync - see 'man fstab-sync' for details"
Originally Posted by acid_kewpie
what about under the rescue CD?
Under the rescue CD it comes up empty (and so does /etc/mtab).
I managed to use SysRescueCD to completely disable SELinux (via /etc/selinux/config) but the problem persists.
It seems that the core problem is being unable to mount the / filesystem writeable, and as a result /etc/fstab and/or /etc/mtab cannot be generated by the system, and then there is a chain-reaction in which everything is mounted read-only.
The question now is what causes this?
If I can fix the root cause, the system will proceed normally on itself.
But what is that root cause?
What makes a system decide to mount read-only?
How did that /etc/fstab (or /etc/mtab) disappear?
Last edited by lifemustgoon; 11-30-2011 at 02:30 PM.
well I'd look at having a stab at writing the fstab file again manually, shouldn't be too hard to get the system usable again. Not had much experience with fstab-sync, long gone now... I'd probably look to at least make a backup copy of your new fstab in case it does get pwned, maybe uninstall / delete the fstab-sync binary if that's too involved.
well I'd look at having a stab at writing the fstab file again manually, shouldn't be too hard to get the system usable again.
That did the trick. (fortunately, I had a backup copy of the working fstab lying around and all I had to do is copy it over)
Now the big mystery is why, and how, this happened.
I will probably never know because this incident convinced me that I should perform the upgrade sooner rather than later. The problem is that the guy who passed this system on to me, installed zillion services that make that server tick (wordpress, sitebar, cups, backup and other daemons), it would take me forever to re-build that functionality on a newly installed server.