Yes, everything can be updated.
1 Like
Hi, Iām on Synology DS718+ within 16GB RAM and I installed HA from hassos_ova-5.11_syn-patch.ova image on VMM, following the post #1 & Bearded Conti video
HA starts from VM and after login, it let me see some integrations and the Supervisor like possible integration, but when I try to configure it or just click on the left menu on the Supervisor label, I get only a blank window and nothing inside
Where did I made mistakes? Let me know for any further info
Thanks in advance for your kind help
Dear All,
Iām a new happy user of HA on Synology.
First, I thanks all of you made this possible to run Home Assistant Supervisor on the VMM.
Then, unfortunately, since I moved HA from Docker to VMM disks of my Synology DS are continuously running. When I stop the virtual machine, then they stop to run within the minute and the office becomes quiet!
My NAS is a DS1815+ with a RAM of 6GB, running DSM 6.2.4-25556.
The VM config is: 2 processors and 3 GB of RAM. I tried with 2GB without change.
In the NAS, there is one volume with 8 hard drives: 6 are used + 1 for hot spare + 1 SSD as cache.
There are 4TB free (~28%).
Now, while Iām writing the post, DSM RAM: 78% and CPU load is 16%.
Do you have any advice regarding this issue?
Many thanks
Try to restart VM - this should fix itself. Or you can connect to VM via terminal and try supervisor command after you login.
There is supervisor repair or supervisor restart - you can try bothā¦
Hi!
And what is the problem? Noise?
I have Syno tucked away in network cabinet and there is no noise.
You could move VMMās to SSDs to reduce noise but VMMās (if Iām not mistaken) need to write data as soon as it changes to prevent data loss, so youāll not get hibernate from them.
Check Synology forums on this - youāll get more answers there.
Hi,
Thanks for your reply.
Noise is a side effect. The problem is the loading of the NAS CPUs and the occupation of the disks.
When HA is not running, the NAS access to its disks from time to time. Iām used to that.
But when HA is running, the NAS is continuously accessing to disks (24/7). I fear for the life time of them (Red family from Western Digital).
There was no such problem with Docker (but not Home Assistant Supervised unfortunately).
So, Iām going to restart HA and try the commands you gave me in your previous reply. Of course, Iāll be back for a feedback.
Again thanks.
Take care
CPU load have nothing to do with disk access.
Yes, HA writes logs both in the text but also the recorder, you can probably turn both off. Donāt you worry so much about the lifetime of the disk. The datasheet talks about MTBF of 1ā000ā000 so your disks can spin for quite some timeā¦
This guy talks about āas everyone can tell you, spinning disks up and down constantly is bad for their healthā (the datasheet talks about 600ā000 spindowns here). But I suggest that you just accept that the disks will continue spinning at thatās nothing wrong with that.
To add on what Fredrick said - you will have more issues with them spinning down/up then constantly running. I have REDās spinning for 6+ years nowā¦
Itās like TV - leaving it running throughout the day is less damaging then turning it on/off 20 times a day.
Commands Iāve wrote were for other issue - Supervisor missing.
If you have an OLED tv it actually has burn-ins and wearouts. So there are always exceptions 
.
Thanks all for your answers but I fear my explanations are not correct.
Itās not a classic noise from a NAS who keeps its disks & fans spinning. My NAS is now old and Iām used to share my office with its Ā« sounds of life Ā». But since I installed and run HA, the noises are like what you hear in the fields during the ploughing season: tank tank tank tank-tank-tank-tank tank tankā¦
I stopped HA because I need to concentrate for my work and the NAS is so loud that it disturbs me.
Thatās not a normal behavior for me (my first hard drive was a 20MB disk in my Amiga 500 in 1991ā¦).
Unfortunately, I was not able to connect to HA and use supervisor commands neither change the log settings as Iām very new with HA and I donāt know how to proceed.
Thanks
Hi BeardedConti!
I did a mistake in the DHCP host name assignment because I changed the alias from homeassistant to HAVM (to save nvram on my RT-AX88U router) but I didnāt think about the ip/name resolutionā¦the Pi installation isnāt affected by host name change
Now everything works properly
My best thanks to Fredrik and You for your kind work!!
Hi there,
Iāve now also moved from the Docker based integration of Hass.io to this VM based.
Many thanks @fredrike for your dedication and superb work! Much appreciated.
The performance on my DS216+ II with 8GB RAM seems to be good.
However, Iāve one thing that I currently do not know how to solve. I am not talking about reverse proxy or so.
Previous, in the Docker environment, I could easily copy my LE SSL cert to the respective folder to be able to use it in HA for various things incl. AdGuard DoT (via my domain).
But, in the new VM environment, I do not know how to (automatically) let the DS copy my LE SSL cert from Host OS to the respective folder in the VM to be able to use it in the same way as before under Docker.
Are there any guides for the same or can anyone from here describe what to do (e.g. by providing a example script for the DSM task scheduler, if possible)?
Many thanks and BR
Stefan
You have two options. The āeasiestā is to enable the Samba share addon and mount hassio in DSM. The ābestā IMHO, is to use SSH as transport so using the SSH & Web Terminal addon. With generated keys and a scheduled task in DSM.
I can write up a guide for the latter, the hard part is to generate keys on DSM (if you are not familiar with Terminal and SSH).
The steps are:
- On DSM generate SSH keys with the command:
< /dev/zero ssh-keygen -q -N '' - Note the public key, the output from
cat ~/.ssh/id_rsa.pubi.e.% cat ~/.ssh/id_rsa.pub ssh-rsa AAAABBBCCC...== fredrike@DSM - In the configuration of Terminal and SSH add the authorized key i.e.
ssh: username: fredrikerl password: '' authorized_keys: - >- ssh-rsa AAAABBBCCC...== fredrike@DSM - Create a task from DSM that runs the following command as the user fredrike (note that
/volume1/Backupis a Shared Folder on Volume 1 in DSM).scp -r [email protected]:ssl /volume1/Backup/ssl_certs - Celebrate
1 Like
Many thanks for this guide. Did I get it right that I should first connect to DSM thru SSH (e.g. with Putty) and for example as āadminā user and then execute above quoted command?
By doing this, I always get some -ash: /dev/zero: Permission denied , even tried as ārootā.
Or was this step already wrong?
Thanks!
You forgot the <, the right command is < /dev/zero ssh-keygen -q -N '' or cat /dev/zero | ssh-keygen -q -N "" the same thing but the first is less writing. This command will generate the public and private key used in the last step.
Create a task from DSM that runs the following command as the user fredrike (note that
/volume1/Backupis a Shared Folder on Volume 1 in DSM).
scp -r [email protected]:ssl /volume1/Backup/ssl_certs
OK, did it like this, of course with own values set but doesnāt work.
At first I copy the privkey.pem and fullchain.pem from respective folder to a shared folder named āSSLā by a script (this works nicely) and then I run your script scp -r [email protected]:8123 /volume1/SSL in DSM task scheduler to move it to the HA VM but it does not work.
Also itās not that clear to me how this script shall do this job as no path for the files on the VM is defined and so on?
Thanks.
The : denotes folder (in my example the ssl folder).
If you like to use a custom port for ssh (the default is 22) use -p.
So the command for you would be (make sure you have created the admin user in the Terminal & SSH addon)
scp -r -p 22 [email protected]:/ssl /volume1/SSL
I suggest you to test it in Putty first.
Still not working unfortunately, tested in Putty - nothing had changed on HA VM in /ssl folder. But also no error msg in Putty after executing below commands.
The SSH port on my Host (DSM) is 303 and it has the IP .74 while the HA VM has .79.
So I tried with
scp -r -P303 [email protected]:/ssl /volume1/SSLand also with
scp -r -P303 [email protected]:/ssl /volume1/SSLPS: the āadminā user is configured in Terminal & SSH addon in HA as well as the correlated ssh-rsa key.
What are you trying to do? Note that -p is a small p and that the order defines from to
- Copy certs from hassio:
scp -r -p 22 [email protected]:/ssl /volume1/SSL - Copy certs TO hassio:
scp -r -p 22 /volume1/SSL [email protected]:/ssl
Note that the following config in the addon (replace with your generated public key).
OK, thanks. Indeed Iād like to copy from DSM to HA, so it would be the following command:
scp -r -p 22 /volume1/SSL [email protected]:/sslbut, this always results in:
for whatever reason. Iāve set the Terminal & SSH log_level to Debug but could not yet find the cause.
[08:03:20] INFO: Starting the Home Assistant STDIN service...
[services.d] done.
[08:03:21] INFO: Starting the ttyd daemon...
[08:03:21] INFO: Starting the SSH daemon...
debug1: sshd version OpenSSH_8.4, OpenSSL 1.1.1k 25 Mar 2021
debug1: private host key #0: ssh-rsa SHA256:*******
debug1: private host key #1: ssh-ed25519 SHA256:*******
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-D'
debug1: rexec_argv[2]='-e'
debug1: rexec_argv[3]='-d'
debug1: Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
[2021/04/30 08:03:21:3149] N: ttyd 1.6.3-3b174da (libwebsockets 4.1.4-v4.1.4)
[2021/04/30 08:03:21:3150] N: tty configuration:
[2021/04/30 08:03:21:3150] N: start command: tmux -u new -A -s homeassistant zsh -l
[2021/04/30 08:03:21:3150] N: close signal: SIGHUP (1)
[2021/04/30 08:03:21:3150] N: terminal type: xterm-256color
[2021/04/30 08:03:21:3151] N: LWS: 4.1.4-v4.1.4, loglevel 7
[2021/04/30 08:03:21:3151] N: NET CLI SRV H1 H2 WS IPV6-off
[2021/04/30 08:03:21:3169] N: /usr/lib/libwebsockets-evlib_uv.so
[2021/04/30 08:03:21:3466] N: Using foreign event loop...
[2021/04/30 08:03:21:3480] N: Listening on port: 64987
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: sshd version OpenSSH_8.4, OpenSSL 1.1.1k 25 Mar 2021
debug1: private host key #0: ssh-rsa SHA256:*********
debug1: private host key #1: ssh-ed25519 SHA256:*********
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.178.74 port 58386 on 192.168.178.79 port 22 rdomain ""
debug1: Local version string SSH-2.0-OpenSSH_8.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: permanently_set_uid: 22/22 [preauth]
debug1: ssh_sandbox_child: prctl(PR_SET_SECCOMP): Invalid argument [preauth]
debug1: list_hostkey_types: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-ed25519 [preauth]
debug1: SSH2_MSG_KEXINIT sent [preauth]
debug1: SSH2_MSG_KEXINIT received [preauth]
debug1: kex: algorithm: [email protected] [preauth]
debug1: kex: host key algorithm: ssh-ed25519 [preauth]
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none [preauth]
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none [preauth]
debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]
debug1: rekey out after 134217728 blocks [preauth]
debug1: SSH2_MSG_NEWKEYS sent [preauth]
debug1: Sending SSH2_MSG_EXT_INFO [preauth]
debug1: expecting SSH2_MSG_NEWKEYS [preauth]
debug1: SSH2_MSG_NEWKEYS received [preauth]
debug1: rekey in after 134217728 blocks [preauth]
debug1: KEX done [preauth]
debug1: userauth-request for user admin service ssh-connection method none [preauth]
debug1: attempt 0 failures 0 [preauth]
debug1: userauth-request for user admin service ssh-connection method publickey [preauth]
debug1: attempt 1 failures 0 [preauth]
debug1: userauth_pubkey: test pkalg rsa-sha2-512 pkblob RSA SHA256:************** [preauth]
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /etc/ssh/authorized_keys
debug1: fd 4 clearing O_NONBLOCK
debug1: /etc/ssh/authorized_keys:1: matching key found: RSA SHA256:*************
debug1: /etc/ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
Accepted key RSA SHA256:*********** found at /etc/ssh/authorized_keys:1
debug1: restore_uid: 0/0
Postponed publickey for admin from 192.168.178.74 port 58386 ssh2 [preauth]
Connection closed by authenticating user admin 192.168.178.74 port 58386 [preauth]
debug1: do_cleanup [preauth]
debug1: monitor_read_log: child log fd closed
debug1: do_cleanup
debug1: Killing privsep child 775
[2021/04/30 08:03:54:0838] N: received signal: SIGTERM (15), exiting...
[2021/04/30 08:03:54:0838] N: send ^C to force exit.
[08:03:54] INFO: STDIN service was stopped, restarting...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.