Red HatThis forum is for the discussion of Red Hat Linux.
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.
Distribution: Mostly RedHat. Also Suse, Ubuntu, PHLAK etc.
Posts: 149
Original Poster
Rep:
OK, was that sarcasm / trying to be funny and failing miserably / genuine irritation?
I'll refrain from calling you an a-hole since you tried helping me out, and because I didn't read what was on the screen.
Another reason I'll refrain from insulting you is because it still doesn't work and I could use some further assistance, message being:
mount: /dev/sda2 not mounted already, or bad option
<seriously now>
If you could help me out here I'd really appreciate it.
</seriously now>
ADDED: Come on OpenBySource, I didn't mean to offend you here or anything (sorry if I did, unintentional), just really need your help. When I run mount, it lists /dev/sda2 as rw, yet when I try to edit anything it sez read-only filesystem. I'm really stumped here!
Distribution: Mostly RedHat. Also Suse, Ubuntu, PHLAK etc.
Posts: 149
Original Poster
Rep:
That's a relief! I appreciate your help OpenBySource!
Well, I booted up using the GRUB section found here http://linuxgazette.net/107/tomar.html (I know the root password, problem is I just never get the chance to type it in)
When I ran runlevel, here's what I got: N 5
NOTE: I'm using VMWare GSX to do this, don't know if that's of any relevance
Interesting that you are in runlevel 5. Did you enter the password for a regular user to get to this point? Are you able to use "su -" or is it messed up because of the rename on the root account?
I'm not certain what effect renaming the root user would cause to a system. Many startup scripts and daemons usually run as root so it may upset the balance of the universe. Hopefully the person who renamed root didn't mess with any of the filesystem owners:groups otherwise there could be a real mess to clean up.
The article from linuxgazette is a good reference. I would first try booting up in single user mode. If that didn't work I would go with using a LiveCD to permit mounting of the root partition in rw mode and then edit /etc/passwd. With RedHat I know you can use the install CD's to go into rescue mode and solve the problem similar to using a LiveCD.
Distribution: Mostly RedHat. Also Suse, Ubuntu, PHLAK etc.
Posts: 149
Original Poster
Rep:
Hi Wmakowski, thanks for your advice!
No I wasn't able to su, login as root or any of that. Even after repairing the passwd file, problems still didn't want to dissappear.
I've now reinstalled everything from scratch, with one important difference: I now made the VMWare Disk as Undoable. Now if something goes wrong and I can't figure out what the problem was, I simply reboot and say "Discard changes". Presto, system's back online and ready to roll!
I know this thread is old but the problem still exists. The original poster was using GSX server which is a VMware product. I ran into the same problem on my ESX server with RHEL4 Update 4. So far one of the filesystems has gone read only twice now in a 10 days throwing my bugzilla/mysql/splunk installs into a spin. This is now a known and acked problem by VMware as of this post (Oct 30,2007).
The problem is fixed by using the patch instructions provided at the following URL:
Thanks for this thread I managed to use it after failing to get my head around all the options for mount on the man pages. Please note that it looks that where everyone on this thread has typed or copied...
mount -o remount, rw X /
There is a space between the comma and the rw the comma is to separate option from -o. This will fail saying that you must specify the file type and return 32 (mount failure)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.