Kali linux root account is locked

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

‘Cannot open access to console, the root account is locked.’ System won’t boot #1586

‘Cannot open access to console, the root account is locked.’ System won’t boot #1586

Comments

Describe the bug

Since a couple of days ago this message shows in every single boot, most of the times System won’t boot. No matter what boot option(from the given ones) I chose, system won’t boot. Pressing ‘Enter’ just repeats the message and will eventually cause system halt until I manually reboot. I cannot type any other input or command from there.
With some patience and reboots, system will randomly boot after a couple of ‘Enter’ and work ‘normally’.
I’m running DeepIn 15.11 x64 with recently(today) applied updates on a Dell Inspiron 3400 with 8th Gen Intel i5. System is installed on an WD Green M.2 SSD.
Any other info I’ll be happy to provide once the system randomly boots.

PS: Only change since the first boot with this problem is an USB Wireless mouse that I connected before system boot. Mouse was previosly used on the notebook, but always connected after system boot.

1. Problem reproduce frequency
   Every boot ever since first time. I’d upload a dd dump of my root partition if needed.
   Operating system :deepin
   Desktop environment :dde

To Reproduce

Screenshots

Enviroments:

Distro & Version

Related package version

Additional context

The text was updated successfully, but these errors were encountered:

Thanks for the answer. I’ll try it tonight and comment the results.
That aside, it’s not really good that this will happen from time to time randomly lol. If any developer wants or need more info, I’ll try to make a dump of current root partition status so they can replicate error, hopefully.

Same thing happening to my comp on every boot. Typically, the first one is unsuccessful, I press ‘Enter’ and the system halts on the ‘deepin’ logo. After multiple manual reboots (1 or 2 are most often enough), it will finally show the login screen, though still showing the message.

Do you have a Dell laptop too? Every month i have this problem.

Nope, Acer here. Started happening about ~8 months ago, mostly isn’t very problematic; though, last week, it wouldn’t boot for the whole day. I had to run chkdsk on my Windows partition and it finally seemed to fix the issue. Kinda weird

Well, I hope v20 solves this. Let’s wait.

Funnily enough, the ‘I won’t boot no matter what’ mode just came back 🤷🏼‍♀️ 5 boot tries and 30 mins in with no success so far

I’m mostly able to boot the system with a couple of ‘enter’s using safe mode in the boot opitons. It’s still a lot of random and I got used to sleep the pc through the week instead of shutting down.
I’ve just decided to re-install and now it boots normally, but it still ‘thinks’ there’s a mouse permanently connected. Also I get the same message with ‘unexpected device config size’ on every boot, although it starts normally.

@RMoroni I’ve never been able to do the chkdsk, device it’s locked while booted and I don’t know how to run it from grub(only accesible thing when on boot loop). Also yes, I insist on DeepIn only in hopes they fix this with version 20.

PS: Also, I have / and /home in different disks. I’ve tried formatting only / and the boot loop continued. I had to format both disks so it can boot ‘normally’ again.

On the linux line, got to the end of line and put this: ‘break=mount’ (separated by a space after the last option).

I have not found where to put this to get to console.

After press ‘e’, you’ll see this screen. You have the ‘linux’ line, then you put ‘break=mount’ in the end (press F10 to boot). I put this to force initramfs screen. on this screen you can check all your FS.

I got it now. I was able to do the checks and both finished almost instantly with no error(ofc since I re installed on sunday). Nothing else has changed, I still get the devices message and can’t enable ‘Disable touchpad when a mouse is present’ option because it will disable touchpad anyways.

Funnily enough, the ‘I won’t boot no matter what’ mode just came back 🤷🏼‍♀️ 5 boot tries and 30 mins in with no success so far

Did you try check your file systems? From other OS or initramfs.

Sometimes i have this problem, but i follow these steps to correct:

On the Grub screen, press ‘e’ to edit boot options.
On the linux line, got to the end of line and put this: ‘break=mount’ (separated by a space after the last option).
Press F10 to boot.
Then you will see the initramfs screen (that’s why the option ‘break=mount’).
Now run the file system check command: ‘fsck.ext4 dev/sdaX’ for your Deepin file systems (/, /home), except for EFI and Swap partition.
If some of the file systems return some problems (inconsistency or something like this), then the fsck will show you the option to correct, so you accept all the corrections (by press ‘y’ for each correction).
After check the file systems (and eventually correct some problems), write ‘exit’ and press Enter, so you will boot normally.

It always works for me, good luck for u!

To get Kali to boot into console mode:

(useful on slow and bad hardware such as ARM Raspberry Pi)
Just simply run the following commands:

1: root@kali: # systemctl get-default
2: root@kali: # systemctl set-default multi-user.target
3: root@kali:~# sudo reboot

After a reboot, Kali will start in consol mode everytime after this.

To revert these changes, all you have to do is use this command:

root@kali: # systemctl set-default graphical.target
root@kali: # sudo reboot

After a reboot, Kali will start normaly with GUI login screen everytime again.

Sometimes i have this problem, but i follow these steps to correct:
On the Grub screen, press ‘e’ to edit boot options.
On the linux line, got to the end of line and put this: ‘break=mount’ (separated by a space after the last option).
Press F10 to boot.
Then you will see the initramfs screen (that’s why the option ‘break=mount’).
Now run the file system check command: ‘fsck.ext4 dev/sdaX’ for your Deepin file systems (/, /home), except for EFI and Swap partition.
If some of the file systems return some problems (inconsistency or something like this), then the fsck will show you the option to correct, so you accept all the corrections (by press ‘y’ for each correction).
After check the file systems (and eventually correct some problems), write ‘exit’ and press Enter, so you will boot normally.
It always works for me, good luck for u!

By the time I read this I had already changed SO to Debian 9. At some point I started having a similar behaviour and I fixed this yesterday with those instructions 😀 I’ll probably be changing to DeepIn 20, because in the end, Debian has que same errors itself, as it seems.

Also, I added -y to fsck.ext4, because I had a long list of error to confirm.

Источник

Kali Linux

Система загрузиться не может и предлагает посмотреть ошибки загрузки в логах командами:
# journalctl -xe
или другими возможными командами.
Но доступ к консоли невозможен из-за залоченного аккаунта суперпользователя.

Нужно точно знать, по какой причине твоя система не грузится.
Возможно, не может примонтироваться какое-то блочное устройство, указанное в файле /etc/fstab. В этом случае, нужно подключить это недостающее блочное устройство или отредактировать файл из другой системы. Но это — не единственная вероятная причина. Просто проанализируй, что ты изменил в системе перед перезагрузкой.

Не помнишь ? В этом случае ничего тебе уже не поможет, только переустановка системы )

Lisamon

Member

Система загрузиться не может и предлагает посмотреть ошибки загрузки в логах командами:
# journalctl -xe
или другими возможными командами.
Но доступ к консоли невозможен из-за залоченного аккаунта суперпользователя.

Нужно точно знать, по какой причине твоя система не грузится.
Возможно, не может примонтироваться какое-то блочное устройство, указанное в файле /etc/fstab. В этом случае, нужно подключить это недостающее блочное устройство или отредактировать файл из другой системы. Но это — не единственная вероятная причина. Просто проанализируй, что ты изменил в системе перед перезагрузкой.

Не помнишь ? В этом случае ничего тебе уже не поможет, только переустановка системы )

Источник