cannot open access to console the root account is locked (parrot sec is)

AIM5657 · 09-11-2018, 11:47 AM

I upgraded my os restarted system but it took too long to switchoff, I ended up forcefully switching it off with the power button. When it restarted it keeps showing

Code:

You are in emergency mode
cannot open access to console the root access is locked
See sulogin(8) man page for more details
Press enter to continue

But when I hit enter it just shows the same message again I tried it in recovery mode and it does the same thing

Please how can I resolve this

rtmistler · 09-11-2018, 12:21 PM

You may have to use a live boot CD or USB in order to resolve this.

What distribution and version are you running?

Is this related? https://www.linuxquestions.org/quest...fs-4175636202/

AIM5657 · 09-11-2018, 11:25 PM

Thanks for the reply

Quote:

Originally Posted by rtmistler

You may have to use a live boot CD or USB in order to resolve this.

What distribution and version are you running?

Is this related? https://www.linuxquestions.org/quest...fs-4175636202/

I'm using Parrot security I have the live usb but please how do I use it to resolve the problem

brianL · 09-12-2018, 05:45 AM

Here's the sulogin man page:

https://linux.die.net/man/8/sulogin

0000ps · 09-26-2018, 05:37 PM

I have a similar problem, and sulogin won't help when I can't even enter single user mode. I suspect my problem is related to changing drives, (sdb is now sda), and perhaps it would resolve if I switch it back? I would try altering innitab, but the online man page says of innitab(5) "Description The /etc/inittab file was the configuration file used by the original System V init(8) daemon. The Upstart init(8) daemon does not use this file, and instead reads its configuration from files in /etc/init. See init(5) for more details." I'm a bit confused, and have no idea how I could alter init anyways. Could someone show me an example in nano (or vim, if necessary)? Are there specific forensic tools I could use from a live Parrot_Sec DVD?

And is this an issue I can blame on Systemd? I used to distro-hop easily before the widespread adoption of Systemd, now I get problems at boot time that are beyond my abilities to diagnose.