New install and can't get ssh service to start

Installation Home Assistant OS
1

Hi

Trying hass.io install for the first time on an old raspberry pi 1 b with a 4gb sd card.

Install seems to have worked and I can access the dashboard.

I am now trying to start the ssh server (through the dashboard I clicked install on the service).

No matter what I do I can’t seem to get the service to start,I’m getting the following error

fatal error: runtime: out of memory
runtime stack:
runtime.throw(0xf227ff, 0x16)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/panic.go:566 +0x78 fp=0xbef809bc sp=0xbef809b0
runtime.sysMap(0x8d59a000, 0x96d8000, 0x96c72001, 0x15e07e8)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mem_linux.go:227 +0x15c fp=0xbef809e4 sp=0xbef809bc
runtime.(*mheap).mapBits(0x15d1b20, 0x96d72000)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mbitmap.go:159 +0xdc fp=0xbef809fc sp=0xbef809e4
runtime.(*mheap).sysAlloc(0x15d1b20, 0x100000, 0x1)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/malloc.go:430 +0x160 fp=0xbef80a50 sp=0xbef809fc
runtime.(*mheap).grow(0x15d1b20, 0x8, 0x0)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mheap.go:726 +0x68 fp=0xbef80a84 sp=0xbef80a50
runtime.(*mheap).allocSpanLocked(0x15d1b20, 0x1, 0x0)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mheap.go:630 +0x634 fp=0xbef80ab4 sp=0xbef80a84
runtime.(*mheap).alloc_m(0x15d1b20, 0x1, 0x10, 0x35d00, 0x0)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mheap.go:515 +0x138 fp=0xbef80af0 sp=0xbef80ab4
runtime.(*mheap).alloc.func1()
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mheap.go:579 +0x40 fp=0xbef80b0c sp=0xbef80af0
runtime.systemstack(0xbef80b20)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/asm_arm.s:261 +0xa8 fp=0xbef80b10 sp=0xbef80b0c
runtime.(*mheap).alloc(0x15d1b20, 0x1, 0x10, 0x100, 0x295b4)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mheap.go:580 +0x58 fp=0xbef80b38 sp=0xbef80b10
runtime.(*mcentral).grow(0x15d2930, 0x0)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mcentral.go:210 +0xb0 fp=0xbef80b64 sp=0xbef80b38
runtime.(*mcentral).cacheSpan(0x15d2930, 0x235a4)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mcentral.go:91 +0x65c fp=0xbef80ba8 sp=0xbef80b64
runtime.(*mcache).refill(0x86a31000, 0x10, 0xbef80bd4)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/mcache.go:121 +0xd4 fp=0xbef80bbc sp=0xbef80ba8
runtime.(*mcache).nextFree.func1()
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/malloc.go:527 +0x28 fp=0xbef80bcc sp=0xbef80bbc
runtime.systemstack(0xbef80be8)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/asm_arm.s:261 +0xa8 fp=0xbef80bd0 sp=0xbef80bcc
runtime.(*mcache).nextFree(0x86a31000, 0x15ced10, 0x1046790, 0x15ce848, 0xbef80c00)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/malloc.go:528 +0x154 fp=0xbef80bf4 sp=0xbef80bd0
runtime.mallocgc(0xf0, 0xef4e60, 0x43401, 0x0)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/malloc.go:680 +0xca0 fp=0xbef80c94 sp=0xbef80bf4
runtime.newobject(0xef4e60, 0x1)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/malloc.go:807 +0x30 fp=0xbef80ca8 sp=0xbef80c94
runtime.malg(0x8000, 0x15ceda0)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/proc.go:2688 +0x20 fp=0xbef80cc4 sp=0xbef80ca8
runtime.mpreinit(0x15cf310)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/os_linux.go:251 +0x1c fp=0xbef80cd0 sp=0xbef80cc4
runtime.mcommoninit(0x15cf310)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/proc.go:507 +0x108 fp=0xbef80cf4 sp=0xbef80cd0
runtime.schedinit()
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/proc.go:441 +0x40 fp=0xbef80d18 sp=0xbef80cf4
runtime.rt0_go(0xbef80eb4, 0xb6edc000, 0xbef80eb4, 0x2, 0x834d4, 0x0, 0x0, 0x771f8292, 0x7f3cf9d6, 0xce840c, …)
/yocto/resin-board/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/go/src/runtime/asm_arm.s:61 +0x84 fp=0xbef80d58 sp=0xbef80d18
container_linux.go:263: starting container process caused “process_linux.go:254: getting pipe fds for pid 2830 caused “readlink /proc/2830/fd/1: no such file or directory””

Is this just because the pi I’m using is too old/slow? Or can anyone suggest things I could do to try and fix this?

Thanks

2

Yeah, I think you need a bigger SD card. I don’t think the RPi1 is necessarily too old or slow. It will probably all depend on the complexity of your Home Assistsnt setup.

3

Thanks shred. I just got a brand new 16gb card and have the same issue.

When I examine the card using device manager (on a mac) it shows 5 partitions some as small as 13mb. Could it be the weird portioning?

I’m trying to work out how to wipe the card and start again but etcher wont let me override with a new image (maybe because it has a boot file?).

4

Are you installing Hass.io? What I did was use the Disk Utility to format the entire SD card. Make sure you set the format to FAT32 (I think it’s listed as MS-DOS).

5

I am having the same issue with a new install today, I got a 32Gig card, SSH starts but then stops right away. I used the SD format before imaging Hass.io.

6

Thanks for persevering with answering my question!

I’m using this image:
https://github.com/home-assistant/hassio-build/releases/download/1.1/resinos-hassio-1.1-raspberrypi.img.bz2

It was a brand new SD card - I simply used etcher to copy the image on to the card.

When I get home from work tonight I will have another go at wiping and re-imaging.

7

Hey Blue, I noticed on my SSH screen that when I try and start it, If I hit refresh on the log section it says setup user login or something along those lines. Does yours do that? also says it is starting version 3.2.2. but the version listed at the top is showing 2.8 or 2.2 can’t remember exactly.

8

I’m having the same issue. I just set up a new HASS.io build and I can’t get the Samba or SSH add-ons to start – they both report the same “fatal error: runtime: out of memory”.

It’s on a 16GB SD card, but on an older Raspberry Pi B with only 256MB of RAM.

Did you come up with any solution for this?

I did the install on a Model B Rev 2.0 (512MB) and moved the card to a Model B Rev 1.0 (256MB). Then this happened. I figured the hardware was close enough that it wouldn’t matter, but maybe it did.

9

Sorry for not updating earlier. I tried a clean install on another brand new card with no luck either.

I couldn’t get samba working either. Same problem.

I managed to get hassbian to install fine and work so it’s not the old pi or the sd card.

10

Thanks for replying.
Exact same thing with me. Did a fresh HASS.io install on a different card last night, and had the exact same result.

I guess the Docker containers used by HASS.io just need more RAM than what’s on the old Raspberry Pi boards (and/or maybe we just hit a weird bug). Surprised there aren’t more reports of this.
I was really looking forward to the convenience of hassio, but I’ll probably have to go back to one of the older install methods.
Guess maybe I need to consider buying a RPi3.

11

After hitting the memory error on two separate hassio installs, I tried setting it up with Hassbian, then again as a VirtualEnv on Raspbian. Hit (likely?) unrelated issues on both. Finally, I gave in an just bought a Raspberry Pi 3. Tried again with HASS.io last night, and it’s smooth as butter. I definitely notice a performance increase overall, too.

@dangeek - you mentioned on the latest podcast that you weren’t sure if HASS.io ran out of RAM on older systems. My 1st-gen RPi (Model B Rev. 1.0), has only 256MB of RAM (~180 usable, I think) and couldn’t handle more than 1 add-on without throwing memory errors.

1 Like
12

Same issue here. Just tried moving to Hass.io from a regular virtualenv install. Can’t start any addons. I have a Pi3 lying around, but wanted to keep that free for more intense workloads. This may have been a 256MB. I’ll try a 512MB one when I get home.

13

I swapped out the Pi I was using with a 512MB one. No issues after that. I happened to be using the first Pi I ever bought back when they first were released so it was the 256MB memory that was causing the issue.

1 Like