Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

So, this is it. Everything is working as usual except the disk is read only and dont want to change back.

^_^! thanks.

root@NODE02:/tmp# df .
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda5            461490504 179502128 258545928  41% /

root@NODE02:/tmp# mount -o rw,remount /dev/sda5
mount: cannot remount block device /dev/sda5 read-write, is write-protected

root@NODE02:/tmp# touch helll
touch: cannot touch `helll': Read-only file system

It's not multipath. It's nothing special. Just a server with ubuntu 9.10.

makes no sense for me, does it?

----EDIT----

Selinux is not active.

There is no RAID. There are 2 discs, 500Gb each one. First one for OS and some homes. Second one for distributed FS, HPC high performance.

Dmesg was not updated since 2 days ago. Nothing on it's last lines related to disc or errors.

Rebooted, and no hard drive found. From bios the hard drive is dead, not responding even to name queries.

New hard drive is needed. thanks.

share|improve this question
    
Not selinux getting in the way? –  Jason Tan Feb 8 '11 at 14:58

3 Answers 3

up vote 2 down vote accepted

I'm afraid this is due to corruption on the filesystem or problems on the underlying hardware, since it's the root filesystem my recommendation is to boot the server again with a rescue disc (or in single user mode) and try to repair the disk through fsck.

  • Check what dmesg says to confirm the corruption
  • Run fsck to repair the hard drive, as soon as fsck is run reboot immediately to avoid any issues

Hola Marc,

Em temo que aixo es un sintoma de corrupcio al sistema de fitxers o de problemes del hardware subjacent, com es el / lo que et recomano es de rebotar el servidor amb un CD de rescat e intentar reparar el disc amb fsck.

  • Mira que diu la comanda dmesg nomes per corroborar que hi ha corrupcio
  • Executa fsck per reparar el teu disc, en quan acabi rebota inmediatament per preveure qualsevol altre tipus de problema

Bona sort!

share|improve this answer
    
How did you know I speak catalan? Did we met? –  marc.riera Feb 9 '11 at 12:51
    
It's just your name, I'm named Marc as well :) –  lynxman Feb 9 '11 at 13:11

I've seen this before when a RAID card went bad, and the ext3 journal file couldn't be written to. At that point, the kernel marked the root FS read-only and wouldn't allow it to go back.

Nothing was logged about this, because of course the /var FS was on the same disc, and also RO. dmesg, however, was pleased to tell us about the problem. So, can you do a dmesg and tell us about the output?

In our case, the only fix was to power-cycle to wake up the RAID card, then reboot from rescue media and fsck the file system.

share|improve this answer

i had this problem. compiled a kernel with error in. the recompiled to get rid of error. then remounts fine.

share|improve this answer

Your Answer

 
discard

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.