Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My Red Hat 7.3 system which was working fine until now,
hangs giving the following errors while booting.
a)Updating /etc/fstab failed to open /proc/partitions: No such file or
directory .
b)After this it gives a series of errors indicating files
cannot be created because file system is read-only.
I can login in "single user" mode.Also I checked
the /proc directory does have a "partitions" entry.
How should i debug further..
Thanks in advance for any help.
I'd change the first line to the partition it really is, something like
/dev/hda5 / ext3 defaults 1 1
Change the '/dev/hda5' with the right entry for your '/' partition. Use fdisk if unsure.
Just today I had a similar error... upon trying to restart apache, I got an error message saying it was unable to create a log file because the fle system was read-only. It turns out the entire partition had been made read-only. dmesg showed that there had been some kind of hardware error writing to the disk (I currently don't have access to the exact text) and so that device was switched to read-only mode. If anyone has any ideas on how to persue this I'd love to hear them. Otherwise I'll plod along as best I can and post any progress I make.
Boot from a boot disk or from installation cd (in 'rescue' mode). Run fsck on a partition there's the problem with. It should detect the error (and try to fix it).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.