sulogin: root account is locked, starting shell

[piglet]

I get this every time when I try and shut down.

New install of the raspbian image, apt-get updated and rpi-update. No other configuration changes made other than installing links2 and rpi-update + required git.

On issuing "sudo shutdown -f now" I get the message noted in the subject, and the pi is left with root logged in: root@raspberrypi.

Do you know how to fix it? I'm not going to ask Jim....

TIA

[azeam]

"-f" is not a valid option as far as I know. Do you get the same error with

Code: Select all

sudo shutdown -h now

[techpaul]

Why not use the aliases

sudo halt
sudo reboot

[mcgyver83]

Hi all, after installing xbmc following this guide http://www.raspberrypi.org/phpBB3/viewt ... 66&t=12455 I fall down in the piglet situation: sudo reboot, sudo shutdown -r now don't reboot the raspberry. The subject message appear..any hints?

[rishad]

I had the same problem today. In the messages it says run 'fsck' manually
Try
> fsck

This solved my problem

Thanks

[JamesTWatson21]

these commands worked for me, I kept shorting out the raspberry pi, and it kept hard rebooting causing the file-system to get corrupt.

Code: Select all

sudo umount /boot
sudo fsck.fat -a /dev/mmcblk0p1
sudo fsck.fat -a /dev/mmcblk0p8
sudo reboot

[IgorGanapolsky]

"-f" is not a valid option as far as I know. Do you get the same error with

Code: Select all

sudo shutdown -h now

This doesn't solve anything for me. Just a blank blue screen.

[IgorGanapolsky]

Why not use the aliases

sudo halt
sudo reboot

sudo halt just puts in a blue screen. What is it supposed to do?

[IgorGanapolsky]

I had the same problem today. In the messages it says run 'fsck' manually
Try
> fsck

This solved my problem

Thanks

I get an error:
/dev/mmcblk0p2 is mounted
e2fsck: Cannot continue, aborting

[Rev02]

I had the same problem mine was to do with drive mounting. I had a drive set to automatically mount and when it wasn't plugged in, it caused my pi to go in to safe mode all i had to do was plug the drive in at boot. Hope this helps anyone else.

[Szabi]

If you have changed the /etc/fstab file then change it back as it was before. Since you messed up boot location. That caused for me the booting issue.

[monand]

And how can I change the file if I can not have access?

I'm new with raspberry pi.

Thank you in advance,