Skip to main content

Timeline for Suse filesystem turns read-only

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
May 3, 2022 at 8:58 comment added U. Windl Anyway if a system is in such state, the best you can do is save (copy away) whatever you need from the system, and the reinstall it. Before doing so running a memory test (e.g. memtest86) is highly advised.
Jul 7, 2011 at 5:27 comment added Jas Yep, the disk seems to be the problem. Thanks for the help @Caleb, @alex.
Jul 7, 2011 at 5:26 vote accept Jas
Jul 6, 2011 at 18:22 comment added Caleb @Jas: I don't think there is much other sluth work you can do if you can't READ log files either which is what what seems to be happening. I would reboot this machine into a recovery disk of some kind and run a file system check, and also check for SMART messages or other indications of drive failure. Also turn OFF any backup systems that are not incremental because you may have seriously corrupt data already and you don't want to backup bad stuff over good.
Jul 6, 2011 at 15:58 comment added alex Then you have a failing disk drive most probably.
Jul 6, 2011 at 12:48 comment added Jas @alex - the error says : -bash: /bin/dmesg: Input/output error
Jul 6, 2011 at 12:39 comment added alex Invoking dmesg failed? That's really weird. What's the error message?
Jul 6, 2011 at 12:26 comment added Jas Hi Caleb... Neither me, nor my cat hit the alt+sysreq+u. Nor did I initiate the shutdown and aborting it. Like I said, I pretty much did nothing on the server for the past month (just occasionally stopping and starting a web service thru Apache Tomcat manager). Also, invoking dmesg failed. Can you tell me why is remounting the filesystem to r-w not recommended at this stage?
Jul 6, 2011 at 12:17 history answered Caleb CC BY-SA 3.0