root filesystem goes readonly

Linux and Unix-Like Linux
1

I see this when tried to create a dir using root

fstab entries are pretty normal
tried to remount with rw but it is still the same

block device /dev/sda2 is write-protected

---------- Post updated at 04:57 PM ---------- Previous update was at 03:51 PM ----------

fstab entry

LABEL=/                 /                       ext3    defaults        1 1

dmesg

ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
audit(1317999399.316:2): user pid=16747 uid=0 auid=4294967295 msg='avc:  0 AV en                 tries and 0/512 buckets used, longest chain length 0
'
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device sda2): ext3_remount: Abort forced by user
end_request: I/O error, dev fd0, sector 0

---------- Post updated at 04:58 PM ---------- Previous update was at 04:57 PM ----------

also treid

mount -o remount,rw /

---------- Post updated at 05:00 PM ---------- Previous update was at 04:58 PM ----------

release

Red Hat Enterprise Linux ES release 4 (Nahant Update 4)

uname -a

Linux hostname 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686 athlon i386 GNU/Linux
2

What is your disk device? Some flash devices have a 'read only' tab.

Also, check your dmesg. Disk errors can force a filesystem to go read-only.

3

If the disk was in rw mode and it suddently went ro, then I suspect you've hit this bug which is pretty common on RHEL4:

https://bugzilla.redhat.com/show_bug.cgi?id=197158

4

i checked the dmesg found a journal error which i dont rememmber :wall: now

---------- Post updated at 07:47 PM ---------- Previous update was at 07:46 PM ----------

oh thank you verdepollo

5

solved!!

no opion but rebooted and
ran fsck that fixed this :slight_smile: