Hi,
Yesterday I’ve made upgrade my openhabian to 2.1 using openhabian-config (I had openhab in 2.1 snapshoot) and after I’ve made upgrade linux also using openhabian-config.
Process was smooth but when I restarted after few minutes I’ve got message on console “gpio mem device opened…” and system stoped and my display turned to black
I’ve found information about https://github.com/openhab/openhabian/issues/147 but I think it is not this case. To be honest I do not understand information “installed using ua-netinst”, in my case I’ve installed using openhabian image, next I’ve instaled openhabian snapshot (using apt-get) and after I’ve upgraded openhabian/linux using openhabian-config.
Yes it is completely frozen and I cannot access it using ssh and keyboard/monitor connected directly to Rpi.
I have version Rpi v.2. In afternoon I try to record and share movie how it is look like.
I can try to reinstall from openhabian 1.3 but to be honest I prefer use existing installation (I have backup before upgrade of course) because in the same Rpi I have InfluexDB, Telgraph and many scripts.
BTW I have Razberry adapter connected to my Rpi.
Up to openHABian release 1.2, there used to be 2 ways to install the image:
a) The “regular/full” image (openhabianpi-raspbian-[…].img.xz)
and the
b) The “minimal” image using the unattended netinstaller (ua-netinstall) (openhabianpi-ua-netinst-[…].img)
Since release 1.3, @ThomDietrich provides only the “regular” build.
For troubleshooting…I don’t have many ideas…
you could try to enable single user mode and look at the output of dmesg
I’ve used rather ‘full image’.
It is not a problem with SSH, as I wrote display is turn off - and system does not respond. During afternoon I try to make once again migration from 2.0 to 2.1 and after I try to make system upgrade.
If it fail I reinstall everything
Single User mode is not about SSH. It’s about runlevels
Hit shift when starting up.
Hit “e” to edit config.
Tab over to cmdline.txt,
Add to the end of the line, init=/bin/sh
Hit ok, then Esc to boot…
it will boot you as root, single user.
check logs and dmesg output
edit: If the above doesn’t work, try:
edit /boot/cmdline.txt from another PC
add a space and a 1 at the end of cmdline.txt, right after the rootwait parameter
i´ve the same problem since upgrading to OH2.1. I´m not using the ua-netinst, i ´ve installed the “full-img”.
SSH, openhab, homegear and everything freezes.
Any news on this?
Same for me - after approx. one day, the installation is unreachable anymore via web/app. I can access the RPi via SSH, but it’s slow as hell - really, extremely slow. I checked the processes using “top” and it was almost idle…