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 a Lunx newbie. My system is Redhat v9.0. Yesterday, I updated my system using the Redhat Network up2date app. Now I cannot login. I am positive I am using my correct password for root, but the system keeps giving me the message "Authentication Failed".
Any ideas? I vaguely remember hearing that there is a standalone account that can be used to bypass the standard login in cases where a user forgets his/her password. Maybe that would work? If so, can anyone tell me what that login is?
The only other alternative I can think of is to reformat the drive and start all over again. I have quite a bit of data and software downloads, as well as configuration, that I would prefer not to lose.
Follow these steps to reset your root password:
1) Reboot your computer.
2) When the grub bootloader appears on the screen select the entry for your linux system - it may be the only one.
3) Press the "e" key to edit the entry.
4) Select the line beggining with "kernel".
5) Press the "e" key again
6) Type " single" no quotes
7) Press enter
8) Press "b" to boot
9) When the prompt appears type "passwd" press enter
10) Enter a new password when prompted
11) Reboot by typing "shutdown -r now"
Thank you David, but I could not get the instructions to work. Here is what happens:
I follow the instructions and after I fullfill step #8, the system begins to boot and then it says "kernel panic: no init found. try passing init= option to the kernel"
I tried various combinations of passing the word "single" to the argument list, including init=single, but none worked. Is my system a lost cause?
David, thank you for your help. Yes, you are right, I had not noticed the space before the word "single". After I entered it properly, it let me change the root password, which I did. However, when I rebooted after that, it still gave me the message "authentication failed", I know I must have done something wrong, I just wish I knew what. If you happen to think of any other ideas, I would be very grateful.
Even of you cannot help me any further, I want to thank you for all your help - you have been very friendly and extremely helpful, unlike another Linux website - justlinux.com. When I posted the identical request for help on their forum, the moderator deleted my thread because, he said, I did not follow his protocol (I used the word "Help" in the subject line - apparently this is a very serious problem on his forum.) Anyway, it is nice to have a friendly person who is more interested in providing help than the words used to request help.
Thank you, and if you can think of some other ideas, I would appreciate it very much.
I ran the Up2date app and it connected to the Redhat network for the files to update. I do not recall which files were updated (there were quite a few), but I think the kernel was part of those. I also had installed some additional apps from the Linux CD - I think I added a couple of more text editors and some multimedia related apps.
Perhaps you could try following the procedure above until step 9 then make copies of:
/etc/passwd
/etc/shadow
/etc/group
Then create new files with just root entries:
/etc/passwd=
root:x:0:0:root:/root:/bin/bash
/etc/shadow=
root::12178:0:99999:7:::
/etc/group=
root:x:0:root
Make sure the permissions are set with:
chmod 644 /etc/shadow /etc/group /etc/passwd
chown root:root /etc/shadow /etc/group /etc/passwd
Then perform the reboot (step 11) after that login with user "root" and no password (just press enter at the prompt)
I just changed the root password again and then rather than reboot, I thought I would try loging in right from the command prompt, since I was already there. When it prompted me for the user I entered "root" and at the password prompt I entered the new password to which I had changed the system. It gave me the following message:
"Authentication service cannot retrieve authentication info"
I do not know whether this gives you a better idea of what might be wrong.
To my untrained mind it almost seems as though the password file might be corrupt (it cannot store passwords). Is there perhaps a way for me to delete and recreate the password file? Will that even help?
When I changed the password at the prompt, it said that all authentication tokens had been updated.
I just struggled with the Linux command line and I think I deleted and created the 3 files correctly. At least they appeared there when I did an "ls" listing. First I copied the original files into an _old version. Then I used "vi" to create a new version of each file with the text you provided. Since I am still not familiar with Linux, I hope I did it correctly. Anyway, after rebooting it gave me the login prompt and I entered "root". But it never gave me a password prompt, it just went back to a login prompt.
What do you think? Did I do something wrong with the 3 files?
I looked at the up2date log files, but I am afraid I cannot tell much from them. I did not see anything that stands out as an obvious error.
I wish to thank you for all your help. Obviously I must have done something to the system that will not allow me to login. I doubt Redhat did anything wrong with their up2date system. Even though I could not get back in (the system appears to run just fine, it is just that I cannot login), I learned a lot from your help and trying to get back in. I have made carefull notes of everything you told me and I will keep them for future reference. I did not expect to get such a crash course on the Linux command line. Thanks again.
Incidentally, should you think of anything that might help, please let me know. I will most likely wait a couple of days and then reinstall Linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.