Getting thrown into read-only mode - not able to remount
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.
If the kernel and other software are up to date, then something is writing directly to the partition.
- Are you using VMWare with a partition (even if it's not the one having the problem)? When run in this mode the virtual systems and VMWare have direct access to the drive, and a bug can cause a bad write.
- Can you swap the drive controller card? I've seen the error correction logic fail silently, so bad writes occur with no other indication.
- It can also be a failure on the drive electronics, but if it passes SMART self-test, this is unlikely.
- Have you checked your drive, CPU and case temperatures? An overheating component can do bad things.
Interesting... the one about overheating seems to be the most probable to me.
The problem has occurred before (more than once) during heavy activity. It's possible that this heavy activity (disk, CPU or other) caused the temperature to rise above some threshold and this caused a bad write...
I've never checked for this type of thing before. Is there some utility I can use to monitor and log system temperatures?
If this turns out to be the problem, I guess I'll have to find some kind of cooling device...
The last value on the line is the current temperature.
If you want to check CPU and/or motherboard temperatures (and your hardware supports it), you need to install and configure the lmsensors utilities. Check your distribution software repositories; it's probably available pre-built.
Physically examine the fans and air ducts on the case and CPU. Vacuum any dust, and make sure all the fans are actually spinning.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.