Still not possible to install hassio on a bootable USB-device?

curious · January 26, 2019, 8:01pm

I think I overlooked something

Is it still not possible to install hassio on a bootable USB-device ?
Installation stops after a while saying retry count exceeeded. start again.

If it shoould be possible, where to find a manual ?

Raspbian lite runs fine form my ssd

makai · February 5, 2019, 6:40am

Yes it is still not possible

Jrwolf · February 8, 2019, 1:58pm

There is some progress on it:

github.com/home-assistant/operating-system

Migrate from LABEL= to /dev/disk/by-label/*

home-assistant:dev ← berg:berg-systemd-deps

opened 07:19AM - 12 Jan 19 UTC

berg

+25 -5

Hey folks—this is my first patch against HassOS. First, let me just say that thi…s project is _wonderful,_ and while I'm a relative newcomer to it and to Home Assistant in general, working with Hass/Hassio/HassOS so far has been so much fun. I wanted to see if y'all would be willing to accept a patch like this one. I'm admittedly running HassOS in a slightly unsupported configuration (basically, with a `hassos-data` volume on an external storage device, not on my RPi's SD card). Unsurprisingly, this works quite well, *except* that maybe 50% of the time, my external volume isn't available until a few seconds after the `hassos-expand.service` unit wants to start. This, in turn, causes that unit to fail, and then any dependent units fail, like `mnt-data.mount`, leaving the system unable to start. Digging into the systemd source, my belief is that use of the `LABEL=` syntax [causes systemd](https://github.com/systemd/systemd/blob/ee0b9e721a368742ac6fa9c3d9a33e45dc3203a2/src/core/mount.c#L333) not to associate any block device dependencies with the mount, meaning that if a hotplug device isn't available, systemd won't wait for it. If we use `/dev/device/by-label/hassos-data`, say, all the dependencies should be wired up and everything should work. Because the `hassos-expand.service` depends on the filesystem not being mounted, I added an explicit dependency to this unit. I still need to do some (any?) extensive testing on this, but I'd love some feedback on the approach, and—despite the fact that I'm personally using it to run HassOS in a slightly off-label fashion—whether you'd accept it upstream, as it likely would improve the resiliency of the software in the face of wonky hardware even outside of my use-case. Anyway, thank you so much for even reading this PR, and thanks for all the work that you do on HA!

github.com/home-assistant/operating-system

Issues trying to take advantage of ability to move hassos-data filesystem to separate device

opened 06:22PM - 03 Feb 19 UTC

closed 06:39PM - 16 Apr 19 UTC

TonyApuzzo

wontfix

Seems that booting HassOS Dev 3.0 with a relocated hassos-data doesn't always wo…rk -- at least on my ODroid HC1, even after [PR#318](https://github.com/home-assistant/hassos/pull/318) Mentioning @berg since he is author of PR#318. I wasn't sure if it warranted a new issue, so I commented on the PR, but that was not the correct process, so I created this issue. For kernel logs and work so far see: * https://github.com/home-assistant/hassos/pull/318#issuecomment-460028839 * https://github.com/home-assistant/hassos/pull/318#issuecomment-460029474