Cicatrix Posted November 9, 2023 Share Posted November 9, 2023 Hello everyone, I am running Home Assistant as a VM and would like to run it from cache, so my array can spin down. The file activity plugin showed me, that the image is changed all the time, my disks keep spinning up. I set the domain-folder prim to HASS (VM-only cache pool) and sec. to the array, what am I doing wrong? Tank you guys. tower-diagnostics-20231109-1045.zip Quote Link to comment
itimpi Posted November 10, 2023 Share Posted November 10, 2023 Have you checked where any vdisks for the VM are located? According to the diagnostics it looks like they may be on disk1 or disk4 as that is where the ‘domains’ share currently has content. You also have the mover direction for that share set to be hass->array - if you want mover to transfer files to that pool it needs to be the other way around. 1 Quote Link to comment
Cicatrix Posted December 2, 2023 Author Share Posted December 2, 2023 On 11/10/2023 at 2:08 PM, itimpi said: Have you checked where any vdisks for the VM are located? According to the diagnostics it looks like they may be on disk1 or disk4 as that is where the ‘domains’ share currently has content. You also have the mover direction for that share set to be hass->array - if you want mover to transfer files to that pool it needs to be the other way around. Thank you for the reply and sorry for the the late answer. I was sick and had no time. I changed the settings to hass-> array for some shares, for some others cache-> array. Attached the newest diag. AppData seems to be on Cache and on Disk1, I don't know why. My biggest problem is, that for testing I turned VM-Manager and Docker off, but the discs kept spinning up. So there has to be another problem, but I can not find it. tower-diagnostics-20231202-0302.zip Quote Link to comment
Solution Cicatrix Posted December 19, 2023 Author Solution Share Posted December 19, 2023 Ok, it seems like the problem were old data on disk1. Maayybeeee the docker.img (I deleted it accidentally). After checking all data and recreating docker.img it seems to work for now. Quote Link to comment
Recommended Posts
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.