reboot issue, hangs

[nuumio]

I'm using the newest ayufan ubuntu minimal as well. I see what you guys are saying ...

Code:

sudo systemctl reboot

appears to 'hang up' for me too. Bbut for some reason this appears to be shutting down the board completely, similar to

Code:

sudo shutdown now

Then I have to hard restart with the buttons or unplug/ plug in power supply. To be fair, I'm not well versed in all of the flavors of restarting from the command line, but for me

Code:

sudo shutdown -r now

works, as does

Code:

sudo reboot

So I'd be curious if either of those commands work for you guys also. Might save you from doing any of the bash configuration stuff that has been mentioned.

I just learned few days ago that systemctl reboot, reboot and shutdown -r now should all work exactly the same way in systemd based distros (including Ubuntu 18.04, I guess openmediavault too). Similarly poweroff and shutdown now should work the same way. See: https://unix.stackexchange.com/questions...014#196014

In Ubuntu those commands should look like this (at least they do in my systems):

Code:

$ ls -l $(which reboot poweroff shutdown systemctl)
-rwxr-xr-x 1 root root 170320 Jan  9 17:11 /bin/systemctl
lrwxrwxrwx 1 root root     14 Jan  9 17:11 /sbin/poweroff -> /bin/systemctl
lrwxrwxrwx 1 root root     14 Jan  9 17:11 /sbin/reboot -> /bin/systemctl
lrwxrwxrwx 1 root root     14 Jan  9 17:11 /sbin/shutdown -> /bin/systemctl

$ for a in $(which reboot poweroff shutdown systemctl); do dpkg -S $a; done
systemd-sysv: /sbin/reboot
systemd-sysv: /sbin/poweroff
systemd-sysv: /sbin/shutdown
systemd: /bin/systemctl

In that sense it's curious if those reboot commands work differently. systemd has a ton of man pages and I'm too lazy right now read read them so there may be a devil in somewhere in details. I remember having some problems with reboot myself too but haven't experienced them lately. Then again I haven't been rebooting by boards that often any more.

systemd debugging page has some useful tips to try if experiencing hang during poweroff and/or reboot. See https://freedesktop.org/wiki/Software/sy.../#index2h1
In a nutshell:

• Wait at least 5 minutes to distinguish a permanent hang from a broken service. Then try CTRL+ALT+DEL and see if systems reacts in any way.
  
• If it's permanently stuck try reboot -f or poweroff -f. If they don't work it's more likely to be a kernel, not systemd bug.
  
• If shutdown completes eventually try systemd debugging (see link above, be careful when modifying kernel command line parameters or you'll get non-booting system)
  

EDIT: About an hour later I figured out why I haven't experienced reboot problems as of late: I've running myRP64s with eMMC. I just tried rebooting with SD-card and it didn't work even once (tried about 10 times). I think it may have hanged once in shutdown but all other tries failed when trying to boot showing this in serial console:

Code:

pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
OUT
U-Boot SPL board init

U-Boot SPL 2017.09-rockchip-ayufan-1035-gd646df03ac (Oct 26 2018 - 08:36:09)
booted from SD
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

(full boot + reboot log pastebin: https://pastebin.com/4RPFk8FA)

Maybe people familiar with U-Boot can tell what's going on here.