LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   cannot open access to console,the root account is locked (https://www.linuxquestions.org/questions/fedora-35/cannot-open-access-to-console-the-root-account-is-locked-4175727241/)

slayer21 07-22-2023 10:07 PM

cannot open access to console,the root account is locked
 
someone who can help.I get this message

cannot open access to console,the root account is locked

GentleThotSeaMonkey 07-23-2023 12:35 AM

A web search of that error returns numerous scenarios which may help you narrow it down, depending on when it occurs and which distro.

That will give you ideas for additional keywords, to help you isolate the problem.

Please do let us know what it turns out to be, and what additional info/clues helped you solve it.

yancek 07-23-2023 05:12 AM

Which release of Fedora are you using? What did you do to get that message? Recent releases lock the account by default and use sudo. See the link below.

https://lwn.net/Articles/879272/

syg00 07-23-2023 05:29 AM

This was such a monumental screw-up by the Fedora devs, they should have quit.

slayer21 07-23-2023 07:46 AM

Quote:

Originally Posted by yancek (Post 6443733)
Which release of Fedora are you using? What did you do to get that message? Recent releases lock the account by default and use sudo. See the link below.

https://lwn.net/Articles/879272/

fedora 37 I have, the problem was probably caused by a tool that was looking for vulnerabilities and in the terminal I was giving automated commands that I didn't know exactly what they were. the strange thing is that in the error it writes I don't see that I can type a command.

hazel 07-23-2023 08:22 AM

Can you use the console as yourself? If so, you can carry out diagnostics and perhaps fix things using sudo.

If not, you will have to boot from a rescue/installation image that will give you root access again.

slayer21 07-23-2023 08:51 AM

Quote:

Originally Posted by hazel (Post 6443758)
Can you use the console as yourself? If so, you can carry out diagnostics and perhaps fix things using sudo.

If not, you will have to boot from a rescue/installation image that will give you root access again.

How can I do this?What orders can I give, brother?

hazel 07-23-2023 08:59 AM

You haven't answered my question. Can you use the console as yourself? Can you log in as yourself and give simple commands like ls?

slayer21 07-23-2023 10:37 AM

Quote:

Originally Posted by hazel (Post 6443763)
You haven't answered my question. Can you use the console as yourself? Can you log in as yourself and give simple commands like ls?

but I don't see the ability to type a command.It says press enter to continue and press enter And it rewrites it every time you press it.Meanwhile after restarting windows because I'm running on my dualboot system, I get a black screen that says grub minimal bash-like and doesn't get into any mode

hazel 07-23-2023 10:48 AM

That "press enter to continue" usually occurs during boot when the kernel has loaded but can't find its initial root device. So you are not actually reaching a console at all.

In the second case you describe, you haven't even got as far as loading the kernel. You are stuck in the GRUB bootloader. The fact that the prompt says "grub" and not "grub rescue" shows that the bootloader has at least loaded its shell module and can receive commands, but can't find the kernel image that it needs to load next. I'm no expert on GRUB, but most of the other people here use it and they can tell you how to specify your kernel and initial root device.

slayer21 07-24-2023 12:31 AM

Quote:

Originally Posted by hazel (Post 6443781)
That "press enter to continue" usually occurs during boot when the kernel has loaded but can't find its initial root device. So you are not actually reaching a console at all.

In the second case you describe, you haven't even got as far as loading the kernel. You are stuck in the GRUB bootloader. The fact that the prompt says "grub" and not "grub rescue" shows that the bootloader has at least loaded its shell module and can receive commands, but can't find the kernel image that it needs to load next. I'm no expert on GRUB, but most of the other people here use it and they can tell you how to specify your kernel and initial root device.

and now what should i do for the first case?

hazel 07-24-2023 03:56 AM

Quote:

Originally Posted by slayer21 (Post 6443914)
and now what should i do for the first case?

Check the kernel messages that occur directly before that warning and post them here. Hopefully they should tell us what went wrong.

slayer21 07-24-2023 05:34 AM

Quote:

Originally Posted by hazel (Post 6443946)
Check the kernel messages that occur directly before that warning and post them here. Hopefully they should tell us what went wrong.

Thank you very much for helping me, you are a good man and life will give you all the good back.As for the case of the problem what command to write since as you can see from this photo it says press enter to continue and I can not write something.When I press enter I get the same message again

https://forums.fedoraforum.org/attac...4&d=1690081622

hazel 07-24-2023 06:01 AM

I am not a man, good or otherwise! As you would have seen if you had bothered to read my signature. What you need to do is to look at the lines immediately above this message and reproduce them here. Otherwise no one will know why the system wants you to abort the boot.

No Linux problem can ever be solved if insufficient information is given. If you want people here to help you, you must help us by providing as much information as possible.

michaelk 07-24-2023 06:49 AM

Maybe this will help.
https://docs.fedoraproject.org/en-US...ccount-locked/


All times are GMT -5. The time now is 12:27 PM.