HassOS 2.12, running on a Raspberry Pi 3 via SD card.
Supervisor logs:
19-09-30 01:16:10 INFO (SyncWorker_12) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-samba with version 8.1
19-09-30 01:16:11 INFO (SyncWorker_16) [hassio.docker.addon] Start Docker add-on hassioaddons/portainer-armv7 with version 0.7.5
19-09-30 01:16:14 INFO (SyncWorker_17) [hassio.docker.addon] Start Docker add-on hassioaddons/phlex-armv7 with version v1.1.0
19-09-30 01:16:15 INFO (SyncWorker_5) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-ssh with version 6.4
19-09-30 01:16:17 INFO (SyncWorker_13) [hassio.docker.addon] Start Docker add-on hassioaddons/tautulli with version 1.2.1
19-09-30 01:16:17 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<Addon.start() done, defined at /usr/src/hassio/hassio/addons/addon.py:462> exception=AddonsError()>
Traceback (most recent call last):
File "/usr/src/hassio/hassio/addons/addon.py", line 473, in start
await self.write_options()
File "/usr/src/hassio/hassio/addons/addon.py", line 371, in write_options
raise AddonsError()
hassio.exceptions.AddonsError
19-09-30 01:16:18 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<Addon.start() done, defined at /usr/src/hassio/hassio/addons/addon.py:462> exception=AddonsError()>
Traceback (most recent call last):
File "/usr/src/hassio/hassio/addons/addon.py", line 473, in start
await self.write_options()
File "/usr/src/hassio/hassio/addons/addon.py", line 371, in write_options
raise AddonsError()
hassio.exceptions.AddonsError
19-09-30 01:16:18 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_portainer
19-09-30 01:16:21 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_phlex
19-09-30 01:16:22 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_tautulli
19-09-30 01:16:23 INFO (SyncWorker_3) [hassio.docker.interface] Start homeassistant/raspberrypi3-homeassistant
19-09-30 01:16:25 INFO (MainThread) [hassio.api.security] /dns/info access from a0d7b954_portainer
19-09-30 01:17:04 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-09-30 01:17:04 INFO (MainThread) [hassio.addons] Phase 'application' start 2 add-ons
19-09-30 01:17:05 INFO (SyncWorker_8) [hassio.docker.interface] Clean addon_a0d7b954_nodered application
19-09-30 01:17:12 INFO (SyncWorker_9) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 3.5
19-09-30 01:17:13 INFO (SyncWorker_8) [hassio.docker.addon] Start Docker add-on hassioaddons/node-red-armv7 with version 4.2.1
19-09-30 01:17:16 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_nodered
19-09-30 01:17:18 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
19-09-30 01:17:18 INFO (MainThread) [hassio.core] Hass.io is up and running
19-09-30 01:17:22 INFO (MainThread) [hassio.api.security] /dns/info access from a0d7b954_nodered
19-09-30 01:17:23 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-09-30 01:17:23 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-09-30 01:17:41 INFO (MainThread) [hassio.store] Load add-ons from store: 61 all - 1 new - 0 remove
19-09-30 01:18:39 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-09-30 01:18:39 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-09-30 01:18:40 INFO (MainThread) [hassio.store] Load add-ons from store: 61 all - 0 new - 0 remove
19-09-30 01:21:48 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-09-30 01:21:48 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-09-30 01:21:49 INFO (MainThread) [hassio.store] Load add-ons from store: 61 all - 0 new - 0 remove
Description of problem:
I have a 2 TB hard drive containing documents from a previous Raspbian-based server, attached to a Raspberry Pi 3 via USB. I was planning on writing a custom addon to expose this as a NAS to my local network, as well as using it to backup snapshots in the event of an SD card failure. I'm familiar with the fact that there's a way to run the entire hassio installation from this drive, but I was hoping to avoid that so I don't need to play around with partitions on a drive already containing important data.
If I SSH into hass.io, access root and type lsblk, I can see that the Pi has identified my drive on /dev/sda1:
hassio > login
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
`-sda1 8:1 0 1.8T 0 part
mmcblk0 179:0 0 119.3G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part /mnt/boot
|-mmcblk0p2 179:2 0 24M 0 part
|-mmcblk0p3 179:3 0 256M 0 part /
|-mmcblk0p4 179:4 0 24M 0 part
|-mmcblk0p5 179:5 0 256M 0 part
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 96M 0 part /mnt/overlay
`-mmcblk0p8 179:8 0 118.6G 0 part /mnt/data
zram0 254:0 0 185.2M 0 disk [SWAP]
zram1 254:1 0 32M 0 disk /var
zram2 254:2 0 16M 0 disk /tmp
However, if I'm inside of the supervisor and I type hardware info, I don't see /dev/sda1 under disks:
Manually mounting /dev/sda1 somewhere doesn't make it accessible, either. Is this a bug or a feature? Is there a way to mount /dev/sda1 in a place where it's listed under hardware and addons can access it? Or should I do something like manually running Hassio inside of a Docker container using an OS like Raspbian?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Home Assistant release with the issue:
Hass.io version 189
Operating environment (HassOS/Generic):
HassOS 2.12, running on a Raspberry Pi 3 via SD card.
Supervisor logs:
Description of problem:
I have a 2 TB hard drive containing documents from a previous Raspbian-based server, attached to a Raspberry Pi 3 via USB. I was planning on writing a custom addon to expose this as a NAS to my local network, as well as using it to backup snapshots in the event of an SD card failure. I'm familiar with the fact that there's a way to run the entire hassio installation from this drive, but I was hoping to avoid that so I don't need to play around with partitions on a drive already containing important data.
If I SSH into hass.io, access root and type
lsblk
, I can see that the Pi has identified my drive on/dev/sda1
:However, if I'm inside of the supervisor and I type
hardware info
, I don't see/dev/sda1
under disks:Manually mounting
/dev/sda1
somewhere doesn't make it accessible, either. Is this a bug or a feature? Is there a way to mount/dev/sda1
in a place where it's listed under hardware and addons can access it? Or should I do something like manually running Hassio inside of a Docker container using an OS like Raspbian?