FedoraThis forum is for the discussion of the Fedora Project.
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 have come into a vicious circle which I don't know how to get myself out of. My original problem was that I don't know the root password for my fedora 6 installation. I was then told that I could solve this by going to grub boot menu, choose fedora, press e, go to the kernel line, press e, and type ' 1' and then boot. However, when I do this I get an error message, after a while, which says something like:
"extended attribute block 787451 has reference count 948 should be 946. Run fsck without -a and -p"
(This problem also occurs if I try to boot my computer in the normal way now.) However, to be able to run fsck I need the root password, which I didn't have.
At the moment I don't have access to the installation cd either since I'm abroad and that is left at home .
If someone has any ideas of how I can solve this, I would be extremely happy... I'm far from a computer genius so if you have a possible solution I would be happy if you could describe it step by step .
Might I suggest using "sudo" - supplying it's installed? You need to make sure your user is listed with the desired permissions in /etc/sudoers (which needs root access)...which makes me think you might need a secondary box to backup your data, blow away the current installation and re-install.
Maybe Fedora does something nice, like automatically add new users to /etc/sudoers; it never hurts to try.
It looks like you were trying to boot into single-user mode, which should give you the equivalent of root access. When you get to the grub screen, press "e" to edit the line indicating the Fedora kernel you're booting, and then press "e" a second time to edit the line that begins with the word "kernel". You should be able to append "s" or "single" to the end of the line and then press "b" to boot into single-user mode.
press "e" to edit the line indicating the Fedora kernel you're booting, and then press "e" a second time to edit the line that begins with the word "kernel". You should be able to append "s" or "single" to the end of the line and then press "b" to boot into single-user mode.
Do you have to re-change the line without these letters after changing the root password?
If fscking happens on Fedora like it does on Slackware (eg when filesystem is discovered to be borked upon booting) How about booting the system, logging into your user account, and then shutting the machine off with the power button (simulated power failure)!? Perhaps rather unorthodox, but when that 'happens' to me, the filesystem(s) gets fscked during next boot.
Beyond that, an earlier suggestion of using a LiveCD is the best idea yet IMHO.
Sasha
PS - It's unclear, but if the machine will now not boot up at all, then disregard this post (and get a liveCD )
Last edited by GrapefruiTgirl; 05-29-2008 at 07:33 AM.
If fscking happens on Fedora like it does on Slackware (eg when filesystem is discovered to be borked upon booting) How about booting the system, logging into your user account, and then shutting the machine off with the power button (simulated power failure)!? Perhaps rather unorthodox, but when that 'happens' to me, the filesystem(s) gets fscked during next boot.
Beyond that, an earlier suggestion of using a LiveCD is the best idea yet IMHO.
Sasha
PS - It's unclear, but if the machine will now not boot up at all, then disregard this post (and get a liveCD )
OK...call me dumb I know I know...but what does FSCKd mean? The hard disk will repair itself?? I see this term tossed around all the time but I am not quite sure exactly what it means yet...
FSCK is also often substituted for a similarly spelled vulgarity. This is most likely due to it being needed with things are messed up with the filesystems (i.e. "They are fsck'd up"). That is really more of a computer slang though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.