Jump to content

Keep certain VM's running without array started

30 posts in this topic Last Reply

Recommended Posts

Hmm.. I‘m sorry I have only „tested“ this behaviour with the power outage I had. I did not stop the array with the GUI or anything. I thought the array is offline during a parity check which is definitely not right.

I forgot I had my array in „auto start“.


Nevertheless, it would be really a good idea to be able to run VMs from unassigned devices or cache drives with the array offline.


Sorry again = (

Share this post

Link to post

Allowing access to array members (cache included) while the array is stopped is probably not going to happen, for various reasons Tom has stated before.




I see no real reason that we couldn't allow VM's that aren't on the array to operate. It's not like you couldn't set up a VM configuration where all the required elements were on a non array device, but it wouldn't be able to easily share those elements with the VM's currently configured. You would need a separate XML storage location, and an iso location for install media.


Maybe a GUI section for array limited VM's, and another for VM's on unassigned devices?


As soon as limetech actually takes control of UD instead of relying on dlandon to maintain it, I see no reason why we can't have 2 VM types. However, as long as limetech doesn't actively manage unassigned devices, it's probably not going to happen unless someone writes a plugin.

Share this post

Link to post

Unraid noob here, but it looks like this feature is something that I need as well.  Specifically, I have a Zerotier docker running that only uses the cache drive.  If I make a change on the server that requires stopping and starting the array then the docker shuts down and I lose access to the server.  I only have remote access to the server so this is a huge issue.

Share this post

Link to post

Unraid 6.8 supports WireGuard, which allows remote VPN access independent of the array status.

Share this post

Link to post


I'd also like to see the ability to start specific docker containers. If the data lives entirely on cache would be the condition to allow this. I.E. anything mapped to /mnt/user* would immediately disable this capability. 


I think RegEx could probably handle checking VM XML and Docker config for any reference to a non cache directory.

Share this post

Link to post

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.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.