Power LED flashes, system doesn't reboot

[syberphunk]

Running Raspbian Jessie, and running:
apt-get upgrade
apt-get dist-upgrade
rpi-update

And installing the pidesktop-base-1.1.0.deb file, when I issue a 'sudo init 0' or 'sudo reboot' the raspberry pi shuts down cleanly, and then doesn't properly reboot, the power LED flashes once per second, the system attempts to boot, but instead remains with no display and the power LED flashing.

Uninstalling the pidesktop-base-1.1.0.deb file resolve the problem. Also, after installing the debian package it declares it is actually version 1.0.0.deb

This problem occurs when trying to shut down the pi desktop or rebooting.

[syberphunk]

Similar reported by user here: https://www.element14.com/community/docs/DOC-83477#comment-112924

[K2IE]

I also confirm the issue and the details.

[david-foo]

We note that this problem is a small probability event. It may be a issue with debian pi image itself.
I suggest to backup your data and then re-flash the image then install the deb packet again.

[K2IE]

@david-foo There are two confirmed reports here. Can you please confirm that this issue does not occur on your system and that it will reboot properly upon software command?

[david-foo]

@K2DLS Yes, the problem can not occurs on my device. After I input reboot command or click the reboot button on the UI , the LED change form on to blink, then the system go on and the LED keeps on again. This process takes about 10 seconds. The max waiting time is set to 30 seconds, that means if the rebooting process takes more than 30 seconds the MCU will cut off the power compulsively. This may cause this issue. But normally raspberry pi does not take 30 seconds to restart.

[syberphunk]

After a re-flash of the SSD with the latest Raspbian image, updating the packages and running rpi-update, and then installing the pi desktop package. This problem hasn't occured. However, I wouldn't want to have to wipe my entire raspberry pi install every time this problem appears.

[K2IE]

Same here. All working now but wondering what the root cause of the problem is?

[david-foo]

@K2DLS Thank you. I think this issue is not caused by the things we made on RaspberryPi, as you can see we have open the source code of the DEB packet. Maybe this is caused by RaspberryPi itself. I have met the same situation that Pi (without pi-desktop board and deb)can not boot up or can not reboot. Maybe we can go to Pi's forum to find info.

[bnetse]

This has occurred with my case too. Not always, but occasionally. I'm sure it occurred with the latest Raspian Stretch image. I currently have Jessie running and it has definitely happened with that.

I have spend far too long trying to setup this case to boot from a SSD and I still can't get satisfactory performance. It is very disappointing. I even cut a hole in the base of the case so I could get the SD card in and out. That's a terrible design flaw right there.

My case will not boot or reboot if it has anything plugged into the USB ports other than the loopback for the SSD. No keyboard, no mouse, no hub. Nothing!

Please advise me as to why?.

I have wasted so much time messing around with all the different methods for flashing the SSD (on the pi, on my mac, cloning a working SD, flashing an image, flashing an old image.. etc etc).
I'm not sure why I was trying it without peripherals, dumb luck I guess. All my previous attempts probably would have worked if I had just though to myself. "I know what will make it work, unplug the keyboard and mouse! then plug them back in again when its up and running". Yes. That is what I have to do. every. time.

Yes I have to boot bit programmed. Yes I have the deb packet installed. Yes my Pi Desktop boots from a SSD. Just not with anything plugged into its USB ports.

Anyone?

[bprobbins]

I experience one aspect of these problems: shutdown instead of reboot if I do a sudo reboot.
Latest Raspian stretch (as of today), monitor, usb hub with keyboard and mouse attached, 2.5a power, running desktop (but also occurs from cli). Installed pidesktop-base-1.1.0.deb today. SSD is 32GB msata in add on board supplied in PiDesktop kit. Everything else seems to run as advertised.
Last console message after reboot command before total shutdown is "random: crng init done"

Added a few weeks later: I have since found that for my problem, it was the msata device. Raspberry Pi foundation says "May not work on all drives." What I found was that a LITE-ON 32GB and a KingSpec 64GB msata would never reboot properly but I subsequently found that the following did work flawlessly: Samsung 850 250GB and MyDigitalSSD Superboot2 32GB and 128GB.

[marcelser]

@david-foo don't you think it is a problem of pidesktop-base package cause removing it fixes this. It's quite obvious that the package is somehow the culprit right? BTW: See also my other post in the issue of systemd, the pidesktop-base package creates a lot of other problems like "runlevel" showing "unknown" instead of "N 3" and systemd services not starting (resulting in "dead" state).

Also for the other problems: removing pidesktop-base solves all of this fuss

[phegedus83]

Is it possible to change max waiting time (30 sec)?

[david-foo]

@phegedus83 30 sec is fixed in the power-controll MCU which can not be changed by user.

[phegedus83]

@david-foo Thank you for your help. That's bad news. FSCK time is more than 30 sec and usb boot time is 45sec. It is possible to skip MCU process when I restart the raspberry without remove pidesktop-base-1.1.0.deb package? The shutdown process is useful.

[marcelser]

I put quite some time into the 1.1.0.deb package and actually found the error why for some the reboot doesn't work and the system doesn't enter proper multi-user state (preventing other scripts from starting).

The problem lies in the /lib/systemd/system/embest.service file. In the [Service] section the type of the service is defined as "Type=oneshot" but oneshot expects the program which is beeing started to end ,which the /usr/share/PiDesktop/python/restart.py doesn't do it runs in a loop forever. So the boot process hangs when the embest.service file is called and therefore the system doesn't enter proper multiuser state. Changing it to "Type=simple" which expects a daemon like program like the python script solves the problem and even a "sudo reboot" works properly. Also the subsequent multi-user services are started properly which was broken before the change. It should be really fixed and a 1.2.0.deb file created but it seems that nobody at element14 has the will or power to do that because their priorities are not focused on the Pi Desktop.