'Read-only file system' problem
 

hi.

i am having trouble connecting via ssh/scp into my PC (Mandrake 10.0):

when i try to transfer a file via scp it gives this error:
'Read-only file system'

i am still able to ssh into the machine. after successfully logging in i get this error:
/usr/X11R6/bin/xauth: error in locking authority file /home/myhome/.Xauthority
i can't seem to be able to cp/rm/mv files anymore. it always complains that it's
a 'Read-only file system'.

the same happens when i become 'root'!!!

any ideas/suggestions?

marc

A quick solution might be to copy to another location or rename your /home/myhome/.Xauthority file then try to ssh/scp again and see what happens.

unfortunately that doesn't work.
cp/mv/rm ... nothing works (neither as user nor as root)!
it always complains that i only have read access.

i should also mention that i don't have physical access to
the machine at the moment. i'm debugging remotely.

marc

Is /home a separate partition from /? You should probably try (as root):

mount -o remount,rw <partition with /home>

If the filesystem is mounted read only, then not even root will be able to write to it.

i tried (as root):
mount -o remount,rw /dev/hda6

and get:
mount: block device /dev/hda6 is write-protected, mounting read-only


when i do 'dmesg' i get tons of these messages:
EXT3-fs error (device hda6) in start_transaction: Journal has aborted
EXT3-fs error (device hda6) in start_transaction: Journal has aborted
EXT3-fs error (device hda6) in start_transaction: Journal has aborted
.
.
.

is my harddisk broken?

marc

I'm having the same problem when logging in with ssh. :confused:

---------------------
dmesg says:
EXT3-fs error (device sda11) in start_transaction: Readonly filesystem.
---------------------

I can't do anything which requires writing. This happens only with 'remote controlling'.
I'm using Debian Sarge. Installed with netinstall image.

Buehler: Your hard disk ain't broken :)


edit:
wtf
/etc/fstab includes this
/dev/sda11 / ext3 defaults,rrors=remount-ro 0 1

This wasn't in fstab few days ago. Before I first time connected with ssh :rolleyes:

The same thing on Fedora Core 4
 

I had similar problem few days ago on fresh Fedora Core 4. Using default installation, it formatted disk using LVM. Then after 5-10 hours of uptime, it simply remounted root (/) fs as readonly and remound did the same as mentioned here - nothing. Only reboot helped. Didn't solved it at all, instead (not because of only this) reinstalled whole system, but choosen manual partitioning, and formatted it as normal ext3 volumes, not encapsulated in LVM... since then the problem didn't apperar at all...

Try this
 

mount -w /dev/<filesystem> (ie ad0, ad0a)