platt85 Posted October 25, 2020 Share Posted October 25, 2020 With 6.9 we now have the ability to use multiple cache pools. I transferred my data to a raid1 cache array. However, I still have to leave one hard drive in the main array in order to start the array which is needed to run dockers. This can be mitigated by allowing the array to start regardless of what drives you configured. This will also help those with unofficial zfs mounts. or Change docker & virtual machines to run at startup regardless of array running. This may cause other issues especially if your appdata, vm disks, etc are on the array, so i think the first recommendation would be best. Quote Link to comment
Squid Posted October 25, 2020 Share Posted October 25, 2020 Fyi, a 512 Meg flash drive can be used in the array rather than burning a hard drive for this. Quote Link to comment
platt85 Posted October 27, 2020 Author Share Posted October 27, 2020 On 10/25/2020 at 3:32 PM, Squid said: Fyi, a 512 Meg flash drive can be used in the array rather than burning a hard drive for this. Squid, you are my hero!!! Thank you for all your apps/help. I will look into that. Quote Link to comment
DougCube Posted October 30, 2020 Share Posted October 30, 2020 +1, useful feature Quote Link to comment
Armeros Posted October 31, 2020 Share Posted October 31, 2020 +1 I don't think the array could be started without actual hardware, because, well, you can't start an array without an array. but at least it should be possible to use other features without the array started. e.g. create vms using unsassigned_disks, or docker containers. Quote Link to comment
WEHA Posted November 6, 2020 Share Posted November 6, 2020 I could use this feature as well, just for a machine that runs vm's and no shares. 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.