Skip to content
New issue

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

reboot issue #50

Open
Tibalt opened this issue Sep 6, 2013 · 3 comments
Open

reboot issue #50

Tibalt opened this issue Sep 6, 2013 · 3 comments

Comments

@Tibalt
Copy link

Tibalt commented Sep 6, 2013

When I log on to the rasp with ssh and type "reboot"(using usb keyboard and hdmi output is also tested), the following text appears:
"Broadcast message from root@bsquask
(/dev/pts/0) at 0:07 ...

The system is going down for reboot NOW!"

and can not input anything in the terminal, which seems normal, but after a long time(10 mins at least), the rasp still can not reboot.

Another thing is there is actually no booting info feed to hdmi which is different from raspbian.

PS: it seems the /var/log/messages is cleared after repower. (I manually "logger hello", but that message disappears after repower.) /var/log seems is not a directory in tmpfs. Could anyone give me a hint?

@ghost
Copy link

ghost commented Sep 6, 2013

/var/log/ is a symbolic link to ../tmp/
/tmp/ is mounted as tmpfs so it won't survive reboots. If you want to change that just delete the symbolic link and create a directory log under /var/

For debugging purposes this is nice, but when running in 'production' I prefer using tmpfs to avoid wear and tear (and a full sdcard)

@Tibalt
Copy link
Author

Tibalt commented Sep 6, 2013

@limpens
Thanks.

@Tibalt
Copy link
Author

Tibalt commented Dec 4, 2013

"reboot --force" is the force solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant