Raspberry 3 keeps crashing on installation

Archive All-In-One Installer
1

Hi,

I am since a few days fighting with getting an installation up and running. I have restarted a number of times, tried two different SD cards and the problem remains.

Basically what I do is

  1. LDownload the raspbian jessie lite 2016-09-23. Apparently after this one can not SSH into a fresh installed raspbian installation. I guess it is safe, but then you need to connect a keyboard and display. Not a wise decision IMHO.

  2. Using Win32Diskimager creating drive for the Raspi

  3. SSH into the raspi using putty

  4. Download the latest updates with sudo apt-get update && sudo apt-get upgrade -y

  5. sudo raspi-config to change the time zone and location.

  6. Since there is a new kernel, sudo reboot and login again.

  7. Start the all in one installer,
    wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && bash hass_rpi_installer.sh

  8. when the installation crashes I do
    rm -rf fabric-home-assistant
    sudo apt-get install libffi-dev libssl-dev
    sudo pip install cryptography --force-reinstall

  9. and then I try again
    wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && bash hass_rpi_installer.sh

at some point I am getting a message that the system goes down for a reboot.
I have tried to run a tail -f /var/log messages or syslog and I am not getting anything useful to what could be causing the crash.

I have read that others have followed the procedure above and that it should work.

2

See the post and this thread for fixes on RPI3

3

I wish it had been that simple. After doing the above I get further, but then at some point it just decides to reboot.
Its not that the installation stops, the raspberry reboots.
Here is what I have in the log file

Dec 18 21:28:46 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 21:29:46 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 21:28:57 raspberrypi systemd[1]: Reloading.
Dec 18 21:29:00 raspberrypi systemd[1]: Reloading.
Dec 18 21:29:00 raspberrypi systemd[1]: Reloading.
Dec 18 21:29:00 raspberrypi systemd[1]: Starting LSB: mosquitto MQTT v3.1 message broker…
Dec 18 21:29:00 raspberrypi mosquitto[30946]: Starting network daemon:: mosquitto.
Dec 18 21:29:00 raspberrypi systemd[1]: Started LSB: mosquitto MQTT v3.1 message broker.
Dec 18 21:29:01 raspberrypi systemd[1]: Reloading.
Dec 18 21:30:56 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 21:31:56 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 21:31:00 raspberrypi systemd[1]: Reloading.
Dec 18 21:31:00 raspberrypi systemd[1]: Reloading.
Dec 18 21:44:52 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 21:45:52 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 21:56:07 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 21:57:07 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 22:06:25 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 22:07:25 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 22:07:25 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 22:08:25 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 22:08:57 raspberrypi rsyslogd-2007: action ‘action 17’ suspended, next retry is Sun Dec 18 22:09:57 2016 [try http://www.rsyslog.com/e/2007 ]
Dec 18 22:08:58 raspberrypi rsyslogd: [origin software=“rsyslogd” swVersion=“8.4.2” x-pid=“485” x-info=“http://www.rsyslog.com”] exiting on signal 15.

Broadcast message from pi@raspberrypi on pts/3 (Sun 2016-12-18 22:09:01 UTC):

The system is going down for reboot NOW!

4

I know it definitely works using the post linked and the latest version of Jessie (pixel)

Are you able to wipe your SD and start again?

Failing that I can post all the commands later today when I’m at my PC :slight_smile:

5

I have tried two different SD cards, and it is the same… I don’t think it is the SD card. I have tried the jessie lite, full installation, with or without sudo dist-get update/upgrade…

It is not working for me, and I don’t file any leads to why it reboots. That is to me also odd, it is a message that it needs to reboot, so it is not a full blown crash. It is somehow a controlled reboot

6

To be brutally honest I’m not sure what’s causing it as I’m just a Linux noob, but I have the entire working process written down.

I’ll post it up today at some point but likely to be a few hours yet

7

These are the commands I used to get Home Assistant up and running using a clean install of Jessie (Pixel). Once the Jessie image has deployed to SD card, boot up into the UI enable SSH, set password and hostname then reboot. Connect using Putty or some other SSH tool, I have also used Juice on android too.

pi@host:~ $ sudo apt-get update
pi@host:~ $ sudo apt-get upgrade
pi@host:~ $ sudo apt-get install build-essential libssl-dev libffi-dev python-dev
pi@host:~ $ sudo pip install cryptography
pi@host:~ $ wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && bash hass_rpi_installer.sh

Once the installation is complete you will need to fix the mqtt broker error in configuration.yaml (home/hass/.homeassistant/configuration,yaml) there is normally a duplicate that you will need to delete and then setup the original mqtt broker to either point to your local host IP or change it to a cloud mqtt broker.

Once you fixed the mqtt broker you can restart the Home Assistant service using the following command

pi@host:~ $ sudo systemctl restart home-assistant.service

If its still not working after that check the homeassistant.log for errors found in the same location as your confguration.yaml

Hope this helps you get it working :smiley: