October 25, 20205 yr 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.
October 25, 20205 yr Fyi, a 512 Meg flash drive can be used in the array rather than burning a hard drive for this.
October 27, 20205 yr Author 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.
October 31, 20205 yr +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.
November 6, 20205 yr I could use this feature as well, just for a machine that runs vm's and no shares.
Archived
This topic is now archived and is closed to further replies.