Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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'.
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
.
.
.
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.