|Read-Only FIle System|
Tried to improve performance, instead goofed everything up
| 3:52 pm on Sep 12, 2006 (gmt 0)|
I'm running Kubuntu on one of my machines. I tried the speed improvements listed here [ubuntuforums.org], but I must have done something wrong because when I rebooted, it took forever and finally just booted into the command line interface. When I try to edit the files back to their original state, I'm told I can't do it because of a read-only file system.
I can boot into Recovery Mode okay, but the problem persists - no editing allowed.
I'm told I should boot from an Ubuntu Live CD and run fsck on the hard drive I normally boot from, which in the Live CD environment will (I guess) be unmounted. Supposedly, there's a good chance this will fix the problem.
Unfortunately, I have no idea how to run fsck on an unmounted drive, nor would I know which flags to use, etc., in order to get it to do what it needs to do. I've tried to learn more about it, but the documentation I've found so far is way above my head and assumes a greater level of hardware and file system knowledge than I have.
So, could anyone tell me exactly what to type in order to run fsck with the proper options on the unmounted hard drive from the Ubuntu Live CD? When mounted, the hard drive is hda1.
Thanks for any help or ideas!
| 11:59 am on Sep 13, 2006 (gmt 0)|
Try mount -o remount,rw /dev/... for the specific partition when it is booted in read-only mode. This will try to remount the partition in read-write mode. If this succeeds, you can edit the configuration files.
| 8:12 pm on Sep 13, 2006 (gmt 0)|
Thanks, I'll try that. However, since I have to go through something of a rigamarole to run this box with a monitor, keyboard, etc., I'd appreciate it if someone could provide some answers about fsck, too, just in case I have to resort to that (which I hope I don't - your advice seems much simpler).