I ended up getting the original image to work today. HB just simply wouldn’t work before. Service started fine and there weren’t any odd errors. But all devices showed no response in the Home app. Reimaged to a different USB drive today and I got it working. Still interested in a hass.io image in the future though.
@pvizeli Hi, I see on resin-os gitter chat that you have been working on the development of this hass.io image.
Thanks for this; I just started on hass.io and was wondering if the options or settings involved in the creation of the image file itself have any influence on the possibility to boot from USB drive (or SSD via USB)? My RPI3 somehow likes to eat SD cards after a couple of reboots.
A Hassbian image or raspian/aio can boot fine from USB on my RPI3, but the hass.io resin-os image fails. Tried several USB drives, no luck. It just stalls during boot, even the boot logo is not shown.
The same image flashed to a SD card boots fine.
I have installed the image on SD card and have completed the hass.io installation and the Home Assitant page shows up.
After installing some add-ons, I made a image file of the SD card and flashed that to my USB drive but still no luck.
According to the github repository it should already be available in the firmware, see: https://github.com/resin-os/resinos/issues/283.
Could you take a look into this for making this available in a coming update of the image?
Thanks!
2 Likes
Same problem here. Can boot raspbian img from usb, but Hass.io just hangs…
It would be so great if anybody could sort this out, as I’ve found that I just sleep better knowing than my pi’s are running usb sticks 
2 Likes
Same - I have just gone through the same heartache, then found this thread.
After my second microsd failure I decided to use a usb case with a SSD drive to boot my Pi off and run HA. I etchered raspbian on there after enabling USB booting just to confirm booting from USB was working. No problems.
After etching hass.io onto the same drive, after power on I get no console. The Pi flickers a few lights and then calms down.
Would love to see this working.
1 Like
+1 Me too… burning down SD cards like there is no tomorrow…
Hi all!
I can boot hass.io from usb.
I made some changes in cmdline.txt and config.txt files.
There are two of each!
One couple on the resion-boot partition, and another on resin-rootA partition in resin-boot directory
I changed the “root” option in cmdline.txt
root=/dev/sda2
and I added the usb boot line to config.txt, at the end
program_usb_boot_mode=1
One another thing:
I enabled ssh access to resin os, explained here:
3 Likes
I’ve done this before with no luck. Was this after you had a working install on an SD card and then copied it to the USB drive? I have zero issues using USB drives with Raspbian but have never been able to get hass.io to boot even doing exactly as you said above. FWIW, that’s what I had to do after copying my existing HASS SD card to a USB stick.
Edit: let me try again. I’m almost certain I did this on all 4 files but I’ll try again. My next problem is getting my existing config working on hass.io but that’s for another thread lol
That is great news, will try as soon as I am near my RPI3 again. Thanks for sharing!
/edit
It is currently ‘Preparing Hass.io’, booted from USB drive with a fresh image and changes made as described above.
I could not get a (backup) image of my current SD card installation to work sadly, so we start over…
Thanks again Sanya, much appreciated!
-
I burned a raspbian lite to my SD card, and enable USB boot mode
-
I burned hassio rpi3 image to my USB stick
-
try to boot with only USB device -> no boot
-
boot from SD card with USB stick is plugged in -> rasbian started
-
I changed the cmdline.txt on SD card and USB stick
-
boot from SD card with USB stick is plugged in -> resin OS started (but docker has an error)
I used ssh to see logs:.............$ ssh root@pi -p 22222 root@hassio:~# docker ps Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? -
remove SD card and boot again -> resin OS and docker is running
-
wating
-
hass.io has an error: disk full
root@hassio:~# journalctl -f ... Aug 13 12:14:20 hassio dockerd[766]: 2017/08/13 14:14:20 [alert] 27#27: *2 write() to "/var/lib/nginx/logs/access.log" was incomplete: 117 of 215 while logging request, client: ::ffff:192.168.100.114, server: , request: "GET / HTTP/1.1", host: "hassio.local:8123", referrer: "http://hassio.local:8123/" Aug 13 12:15:02 hassio dockerd[766]: time="2017-08-13T12:15:02.567164650Z" level=error msg="Not continuing with pull after error: failed to register layer: Error processing tar file(exit status 1): write /usr/lib/perl5/core_perl/auto/Encode/JP/JP.so: no space left on device" ... -
shutdown with ssh
-
I used gparted to resize resin-data partition
-
boot from USB
-
wating
-
Home Assistant is now runnning
5 Likes
I got this also working. Thanks for the advices.
Here is what I did:
- flashed hass.io image to usb thumb drive
- used gparted to increase the resin-data partion (I added ~1GB more space)
2.1 modified the files like instructed - connected the usb drive to rpi and bootted it up
Some challenges with debug ssh access thou. When trying to connect, I get following error:
Disconnected: No supported authentication methods available (server sent: publickey)
I have created a public key with putty and copied (id_rsa.pub) that to the root of resin-boot partition.
Did you add your Private Key to be used by Putty as well? You have to add that in the left pane of putty under SSH - Auth.
Yes, I did. I will create new pair of keys and try it again.
I now see in your post that you copied the key file itself to the resin-boot partition. You have to create a file called ’ authorized_keys’ there and paste the key in it.
1 Like
Excuse me but does anyone take a Look to my post Hass.io Features proposal ?
The rebus a script poster to raspberry forum tha may help u
I have used this method sucessfully with hasbian but with hasio i get the following error
core-ssh:~/Adafruit-Pi-ExternalRoot-Helper# ./adafruit-pi-externalroot-helper -d /dev/sda
Target drive = /dev/sda
[error] Target /dev/sda must be existing device (use -d /dev/foo to specify)
tried sda1 as well but it doesnt seem to work. Anyone having any ideas?
Hi. I tried using gparted to increase resin-data (sda6) and it wouldn’t let me go beyond 1027Mb (from 1024) even though I had >11GB of unused space. Stuck now.
First you have to resize the main partition and after that you can increase the size of subpartitions. Some cases you have to even change the order of different subparttions but if remember right resin-data partition was the last subparttion. I hope this helps.
Are you sure that usb is mounted to sda? When I have multiple usb drives hooked to my rpi, every one is mounted to different path, like sdb, sdc, etc. This is just pure guessing…
Thanks but the other 5 partitions are all tiny so there is not much to steal from in order to make the data partition go from 1GB to say 2GB. I’m doing it with a gparted live USB drive under Windows.
Below is the file system of a Hassio image flashed to a 16GB thumb drive. Wondering if you can advise where you stole the space from?
