1

I've got a Raspberry Pi. And lately I have the problem that I need to press enter when it's starting up.

The error is:

Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press enter to continue.

How can I view that man page? Or does anyone know a solution?

I found this question here, but that does not have an answer also.

  • Do you have a spare SD card? You could try setting up the same config to see if there's any issue. It could be worth doing a process of elimination to determine what's causing the issue. – BantuTech Feb 13 '18 at 12:27
  • How can I view that man page? Open a command line and type man sulogin or man 8 sulogin. Easier still, google for man sulogin , most of the man pages have been put on the web. Be warned they do change from time to time, so the command line is the better option. – Philip Couling Feb 13 '18 at 13:25
  • I doubt that will be useful though. Do you have any more context on the message? Which service was trying to start when it hit the error. Ie: what were the few lines before the message? – Philip Couling Feb 13 '18 at 13:27
  • @couling the message before this is: > Reached target Network – Refilon Feb 13 '18 at 15:27
1

I have limited skills in linux, but I found the following link very useful: Strange problem on startup - cannot open access to console.

In particular I took this sentence:

"The reason for this problem appearing seemingly out of the blue is fsck - the automated file system check, which runs on startup. During this check fsck may discover that something is wrong with some of your filesystems and interactive input is needed to confirm fixes. At this point it apparently attempts to launch the root shell via sulogin in order to ask for this input, sulogin then discovers that the root account has no password login privileges (i.e., its line in /etc/shadow has a * in the second field), and suggests to press "Enter" to continue."

Base on the explanation above (and taking a look at another cmdline.txt file from a different Rasberry that was working fine), before trying another thing, I added to the cmdline.txt file the following: fsck.repair=yes. Now my cmdline.txt looks similar to:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait splash plymouth.ignore-serial-consoles

That worked fine for me, but I recommend to make sure that doing that is not going to corrupt the system.

  • Please could you include a little more detail in your answer. It would be preferable to include all of the necessary information from the link in your answer, in case the link breaks in the future. (Trust me it happens!) – Darth Vader May 2 '18 at 13:37
0

There's insufficient information here to say what's broken. Something is broken during boot and it's trying to drop into an emergency console to let you fix it.

... then the emergency console is broken because the root account is locked. The messages you have included in your question are due to the to this, not the root cause which tries to drop you into the emergency console in the first place. See here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806852

So to fix this the best thing you can do is try to figure out what's breaking. It may help if you first unlock the root account and set a password on it.

Also check the lines in the console before your error, to see if there are any other errors reported.

0

OK I already faced this issue .. your SD card is broken, you should have a lot of injures message in dmesg related to memory disk problems .. just format another fresh one an retry.

  • 2
    I don't think this is correct. I can just continue when I press enter, and all works perfectly. So it is not broken :) – Refilon Feb 14 '18 at 13:47
0

I had the same problem and managed to fix it by "verifying" both boot and system partition with gparted on Linux.

Steps are:

  1. Open gparted, right click -> "unmount" partition for both partitions on SD card.
  2. Right click on partition -> "verify" also for both partitions
  3. Apply and that's it. You should be ready to go
0

Sudo nano /boot/cmdline.txt the file contains one line parameters separated by a space.

Either set parameter fsck.repair=no from fsck.repair=yes or add/insert on same line fsck.repair=no if fsck.repair parameter not in the file.

The prompt to press " enter to continue" will disappear at next boot.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.