Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is how / should be mounted

/dev/md0 on / type ext3 (rw,errors=remount-ro)

but in fact, it is mounted read-only because of unknown reason so far for me.

cat /proc/mounts
/dev/md0 / ext3 ro,relatime,errors=remount-ro,data=ordered 0 0

:/var/log# echo aaa > /tmp/ddd
bash: /tmp/ddd: Read-only file system

As ext3 has errors=remount-ro flag, the possible reason is that the filesystem has errors. When I checked syslog/messages/dmesg I did not find any related information (no disk failures, filesystem errors etc.). This server does not have any iLo or so.

So what do you recommend, how to recover the root filesystem without working physically on the server.


:/var/log# mount -o remount,rw /
mount: cannot remount block device /dev/md0 read-write, is write-protected
share|improve this question
Ouch. Whatever you end up doing, first make sure you have proper backups! – Janne Pikkarainen Aug 20 '12 at 7:59

You will probably need to reboot. You might not have filesystem errors: remounting the filesystem read-only is intended to protect it against problems with the storage hardware: hba cards, cables, storage arrays and so on; and usually is an overreaction.

That said, the closer linux is to the disks, the more likely it is you have a real hardware problem.

share|improve this answer
Just rebooted it and waiting for fsck 5TB of data... – John Aug 20 '12 at 8:32

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.