May 17, 20251 yr Hi - I'm rather new to this and trying to fumble my way through. I've decided my HAOS VM is most likely preventing my storage drives from spinning down. I purchased a 4TB SSD and am using it as a cache drive. My thought was I could put the HAOS VM on the cache drive so it's persistently active state wouldn't keep my drives spinning. However, it does not seem to have fixed the problem and I'm trying to troubleshoot. A few questions: 1. Does anyone know if this logic is solid? It should just utilize the cache if done right and leave the spinning disks idle right? Would the cache being pinged spin up the storage drives for some reason (and can I stop that)?. 2. Why I think HAOS VM is the problem: When I shut down the VM my drives do seem to behave appropriate and spin down based on the settings I've chosen. When the VM is active the drives never spin down (going on 1yr of no spin down now :(). 3. Did I actually move the HAOS VM to the Cache properly? I feel like I messed this up and must be doing something wrong here as I am a noob. Thanks in advance, I appreciate any help as I've been working on this but just don't have as much time as I used to to figure this stuff out. Setup is below but 1 4tb cache ssd, 1 12tb storage, 1 12tb parity.
May 17, 20251 yr Community Expert You want the domains and system shares to be all on a pool to allow array drives to be spun down. You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. We can then see which shares have files on the array. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.
May 17, 20251 yr Author Thank you for the guidance - I've attached the diagnostics here. diagnostics2025.zip
May 17, 20251 yr Community Expert Solution It looks like the ‘system’ share still has files on the array. Mover will never overwrite existing files so if any are duplicates this needs tidying manually and you need to decide which copy to keep (normally the newest). If not then mover should transfer them as long as you have the Docker and VM services disabled under settings while this is taking place.
May 17, 20251 yr Author Thank you so much for looking in to this for me. I'll follow your instructions! Thanks again.
May 18, 20251 yr Author Reporting back. I was able to find and see how the system share had docker and libvirt.img on both the cache and the array. I stopped the VM's, dockers, turned it off in settings, manually ran the mover, and then re-enabled VM's/docker, started them back up, and now the system and domains are only on the Cache, everything works as it did before (no data or functionality loss). All seemingly worked without issue and fixed my problem. Thank you itimpi! Side note: USB manager wouldn't let me shut down HAOS VM (it kept immediately restarting it), so I just unplugged my zigbee and z-wave dongles and then I was able to shut it down in unraid.
May 18, 20251 yr 2 hours ago, td123 said: : USB manager wouldn't let me shut down HAOS VM Oh yeah... That's what was causing my own inability to shut down HA's VM last summer (thanks again to SimonF for immediately suggesting I look there). Sneaky. It'd be nice if it didn't do this when manually shutting down the VM, but I have no idea i\f it's possible for that plugin to know that. Edited May 18, 20251 yr by Espressomatic
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.