Ive installed it on a DS920+ with 8gb of ram, after some lights setups 5 adons a few hacs integrations and like 15 devices. I have a ram consumption of 6-6.5gb and that from the second it turns on. When the vm is offline i have like 200mb ram usage, the vm chrashed one time while installing a template.
How many RAM did you assign for HA?
And⌠where do you read 6-6,5GB occupied? IN VM manager? There system always shows ram ASSIGNED to VM, not how much VM actually uses it, so thatâs not very usable info. For actual info how much HA consumer it go to HAâs settings - Hardware. However, if assigned ram is too small i guess it can happen that VM crashesâŚor, for that matter, if assigned ram is too big and too little is left for synoâs system to operate.
HA should have 4GB asigned (or more if you have it). It does run with 2GB, though. I have normally under 2GB occupied RAM, looking inside HA.
BTW⌠you can extend RAM beyond âmax allowedâ (and i think itâs a good idea). I have 20GB of ram installed (original 4 and additional 16GB module).
1 Like
So i checked in Ha Hardware and im unsing 0.6gb of 4 assigned.
So Thanks for the info with the VM Manager graph.
I strongly doubt that HA crashed because ram. It must be something else (bad addon⌠?)
I have latest Home Assistant image on Synology NAS virtual machine manager, basic setup, and now Iâm getting 400: Bad request, what could it be?
Ok, switched from an HP Esxi server to a synology DS423+ , purely cause of power consumptionâŚ
Installed extra 16GB ram, 1 additional nvme Samsung, to create an storage pool , for fast start of the VMMâs
Works quite good, only 1 issue I see sometimes, I have 2 USB sticks attached to the HAOS vmm, sometimes when I reboot the HAOS, the USB gets lost, in VMM I need to attach it again⌠Is this a known issue/behavior?
Hey @PatrickEhf or @fitim
I see in some old posts you also see the USB disappear sometimes on the VMM, do you guys have a solution for that?
I used to have that problem but not lately. That said I normally try to shutdown the VM before I reboot the NAS. Not sure if that helps or not
No problem here, too with BT USB adapter. But, as PapaLanc wrote, always either turn off VM properly or suspend it. In VM settings check if you have set for VM to âsuspendâ. that way VM will be properly shut down if Syno reboots by itself.
Oh, and having an UPS is a reeeeally a good idea here. Get a model which can be connected to Synoâs usb (you can connect USB hub into Syno to have more USB ports available). That way Syno will see UPS and will shut down properly (itself and VM) when/if battery will go empty when running on batteries.
iâve put 2 sticks on a hub and dont have this reboot issue. could be that having the extra hub makes the devices little bit sooner available (just guessing) and better mountable?
Hmm, not sure how an HUB can help for that? What HUB do you have attached? Is it connected to the front or back ? is it a powered on non powered hub ?
I think a hub wonât make any difference, except that youâll have more that one port (at the back) available. I like to have front USB free because i connect external HDD from time to time and make a backup on it, to have âofflineâ copy of important data (you never knowâŚin a case of failure, virus/ransomware attackâŚ)
Yeah, i only have the DS423+ for a few days, restored VM from an esxi, and i noticed that one of the USB sticks was unmounted after an HAOS reboot
It only happened once, cant reproduce anymore , but i hope its stable now
I also see other threads there sometimes after a week the USB got unmounted for some unknown reason , i hope this is not the case
Having big trouble since core > 2023.11.3. After some eventual successful reboot and backup attempts (to start from scratch in a new VM), my HA is currently down and is not accessible any more. Something very basic must have brought it down, but I cannot figure out what.
I ran HA on Synology since 2021 without bigger issues, except that booting after a shutdown took eternities (>1h). I upgraded recently to run HA in HTTPS mode (I think it was November 2023), to take advantage of ESPHome OTA update capabilities for D1-mini.
I have 10GB installed in my 218+. Because everything is super-slow, I assigned 2 cores and 3GB to each VM (which BTW did bot help to make it faster so far).
What I observed and tried out:
-
Restore a full backup in VirtualBox on my PC: (a) everything works flawlessly! (b) just update core (to 2024.2.5) and OS (to 11.5) in less then 10 minutes, including reboot.
-
Start from scratch in Synology VMM with the latest ova package. My plan was to add one after the other of the addons to hit the culprit. Worked initially well. I added some essential addons (Samba share,Studio Code Server). All good, until I rebooted the scratch environment. None of the add-ons show up, supervisor is not running
Reloading supervisor in the CLI makes no difference, although successfully completed
Looks like being the same issue like what @Morcegolas posted here Installation on Synology Virtual Machine Managager - #451 by Morcegolas -
I observe the same issue like @feron in Installation on Synology Virtual Machine Managager - #455 by feron that supervisor cannot login.
But as none of the addons is working, I cannot follow the advise from @Protoncek to add 172.30.32.1 to the trusted proxies
Installation on Synology Virtual Machine Managager - #456 by Protoncek
How can I edit the configuration.yaml if CLI is everything I have at hand?
My original environment is not running a docker version 25.x, which seems to cause a lot of issues too (nor does the new scratch installation).
ha > info
arch: and64
channel: stable
docker: 24.0.7
features :
...
hassos : "11.5"
homeassistant: 2024.2.1
hostname: ha-dsm
logging: info
machine: qemux86-64
operating_system: Home Assistant OS 11.5
state: running
supervisor: 2024.02.1
supported: true
supported_arch :
- amd64
- i386
timezone: Europe/Berlin
The log files I was I able to look at 3 weeks ago were full of timeouts. Which seems to be confirmed by an attempt to reload the supervisor in the original environment (after all, I prefer to get this up and running again first, before I think about making everything safer by moving or rebuilding everything in a new VM):
ha > supervisor reload
Post "http://supervisor/supervisor/reload": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
My system seems to be in a really bad state 
.
So of in anybody can point me to any post that can bring me onto the right track, please do so.
Hi guys, which network card model are you using? I have serious problems with both virtio and e1000.
Virtio is extremely slow and it often doesnât load the HA pages (I have to refresh several times); e1000 is faster, but itâs frequently unaccessible and it forces me to restart everythingâŚ
Iâm thinking of switching to a mini PC for HA, I canât get it to work on synology decently.
Anyone else find the recent updates messed up the synology VMM HAOS?
I now have 2 issues when using the latest updates:
- When I reboot, I have to type âbannerâ twice in the CLI in order for a âsetupâ problem to be resolved. Itâs never clear what the problem was or why this solves it.
- The VMM stopped recognizing the USB port on my NAS (which I use for audio out).
If I revert back to a backup a couple of months old the problems go away. Iâve tried to update 2 times with the same result.
i did not get past Operating System 12.2 yet, but sofar no issues. Rebooting i do very rarely (once or twice a month ). USB issues are also not common, but in the event they happen, a stick pull and put back or recconnect at VM config resolves them easily.
Hello
The installation went very well thanks to your advices but when I launch the VM, I have this error
Waiting for the Home Assistant CLI to be readyâŚ
[WARN] Home Assistant CLI not starting! Jump into emergency consoleâŚ
I have a DS1522+
I saw that some profiles are connecting by typing âloginâ. but itâs not working for me.
Any idea?
Type âbannerâ once. It will still be broken. Then type âbannerâ again. Donât ask me whatâs actually wrong. I keep saying something broke re synology in the last update.