I recently had a problem with a dedicated server (LINUX) where the file system went read-only.

Recent modifications include installation of fcgid using PHP 5,2 on certain <VirtualHost> accounts.

The system wide PHP is PHP 5.3

I have explored the logs and not been able to find anything that would cause alarm.

Any help/advice would be greatly appreciated.


Usually, if the kernel decides to make one of your filesystems read only, it means that it has detected some critical problem on the filesystem. Often this is caused by a harddisk which is starting to break down and causes IO errors.

Check your dmesg output, by entering sudo dmesg. I think there should be some information about the reasons why the kernel would make your filesystem read only.

  • Thank you for your advice I am looking now. A quick scan of dmesg output doesn't seem to show anything alarming. after a fsck the system seems to be running fine. – CodeCryptor Feb 16 '13 at 16:26
  • Usually this message would include the device name, like for example /dev/sda1. So maybe you could grep for it like dmesg | grep /dev/sda1 – replay Feb 16 '13 at 16:30
  • Did I understand your issue correctly that the filesystem suddenly went read-only while the server was running? Or did it restart and then become read-only? That would be a different case. – replay Feb 16 '13 at 16:31
  • root@cdn1:~# dmesg | grep /dev/sda [ 4.129159] Adding 15624992k swap on /dev/sda2. Priority:-1 extents:1 across:15624992k – CodeCryptor Feb 16 '13 at 16:32
  • adding swap is not a critical error – CodeCryptor Feb 16 '13 at 16:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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