I need someone who has a lot of linux experience to help me.

My filesystem became read only even though I did not change anything.

So I tried
#mount -o remount,rw /
mount: block device /dev/hda1 is write-protected, mounting read-only

The following says that filesystem is wear/write but for some reason
it's still read-only.
#mount -l
/dev/hda1 on / type ext3 (rw) []
none on /proc type proc (rw)
/dev/hda5 on /usr type xfs (rw) []
/dev/hda6 on /var type xfs (rw) []
/dev/hda7 on /home type xfs (rw,usrquota) []
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
none on /tmp type tmpfs (rw)

I also got this but was told it's normal:
WARNING:  Kernel Errors Present
  end_request: I/O error, dev 03:06 (hda)...:  2Time(s)
  end_request: I/O error, dev 03:07 (hda)...:  5Time(s)
  hda: dma_intr: error=0x40 { Uncorrect...:  7Time(s)
  hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }...:  7Time(s)

Here's my system:
Linux server 2.4.25-040218 #1 SMP Wed Feb 18 17:59:29 CET 2004 i686
i686 i386 GNU/Linux


Please tell me how to fix the problem so that I can use the disk, make
it read and write.

The message "{ DriveReady SeekComplete Error }" appears to be
signaling a hardware error. I've had those kernel messages before with
a damaged hard disk. I've had it happen twice, in fact, once with an
IBM disk and once with a Seagate. On each occasion, I was able to run
the manufacturer's hard-disk utility to repair the damage. I still use
both disks daily, although they're somewhat flaky. If I want to boot
from one of them, for example, it usually takes multiple boot
attempts. I haven't noticed any corruption of my user files, however.

leapinglizard

It seems that the kernel sets the device in read-only mode because of
the errors it encounters.

You can try resetting it into read/write mode with the following command:

hdparm -r 0 /dev/hda1

And then try remounting it read/write again.

Vladimir

# hdparm -r 0 /dev/hda1

/dev/hda1:
 setting readonly to 0 (off)
 readonly     =  0 (off)

# mount -o remount,rw /
mount: block device /dev/hda1 is write-protected, mounting read-only

I guess that's not it..

Hmm. Try this:

blockdev --setrw /dev/hda1

And then try remounting.

Vladimir

Also, a reboot would surely solve this.

If you'd like to prevent this situation in the future, check your
/etc/fstab for an option like this: "errors=remount-ro". It's the
probable cause of your system marking the device read-only after
encountering an error.

But if your hardware is failing I would recommend backing up your data
and getting a new drive ASAP.

Vladimir

Thanks v but that didn't work.
Here is my fstab:
/dev/hda1	/		ext3    defaults        1 1
/dev/hda2	none		swap    sw 	        
/dev/hda5    /usr    	xfs     defaults        0 2
/dev/hda6    /var    	xfs     defaults        0 2
/dev/hda7	/home		xfs	defaults,usrquota	0 2
devpts		/dev/pts	devpts  gid=5,mode=620  0 0
none		/proc		proc    defaults        0 0
none		/tmp	tmpfs   defaults        0 0

I probably just need a new hard drive.

The "blockdev" command didn't do it? Then I'm afraid I'm out of clever ideas.

Your fstab doesn't have the option I mentioned, but it can also be
present in the superblock of the filesystem as a default. You can
check this like so:

tune2fs -l /dev/hda1

There should be a line beginning with "Errors behavior:".

Vladimir

No, error behavior is "Continue" so that's not it, Vladimir.

tune2fs -l /dev/hda1
tune2fs 1.32 (09-Nov-2002)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          8d055100-ac2d-4abb-a88e-c4e44a0a6065
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              66400
Block count:              132528
Reserved block count:     6626
Free blocks:              59121
Free inodes:              31335
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         13280
Inode blocks per group:   415
Last mount time:          Tue Dec 28 10:37:21 2004
Last write time:          Mon Jan  3 02:26:19 2005
Mount count:              0
Maximum mount count:      20
Last checked:             Mon Jan  3 02:26:19 2005
Check interval:           15552000 (6 months)
Next check after:         Sat Jul  2 03:26:19 2005
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal UUID:             <none>
Journal inode:            8
Journal device:           0x0000
First orphan inode:       0

I'm sorry I couldn't help you.

Vladimir

We may have to assume the HD is malfunctioning.
So depending upon your priorities ...

Try this:

boot from a floppy or CD  (make a bootable floppy if you do'nt have one)
then manually mount the HD and copy / recover your data. (that is what
you want , right?)  You can then experiment with reformatting /
re-installing with no penalties except your time.

Conversely, install a new / different  harddrive (physically
disconnect the cable on the old one) and install OS. Reconnect old HD
and mount it for recovery.

Sometimes its not worth the time to mess with bad hardware, recover
your data and move on !