January 28, 201610 yr Hi Is it possible to format and use an SSD outside of the array/cache and use it for VMs, shares, dockers etc? Or do I still need to have at least one SSD/HDD part of an UNRAID array before I can use any of the functions such as creating a VM, share etc? I have 4 x 1TB SSDs but don't want to use the cache or array due to poor performance (im mainly going to use all drives for VMs).
January 28, 201610 yr Hi Is it possible to format and use an SSD outside of the array/cache and use it for VMs, shares, dockers etc? Or do I still need to have at least one SSD/HDD part of an UNRAID array before I can use any of the functions such as creating a VM, share etc? I have 4 x 1TB SSDs but don't want to use the cache or array due to poor performance (im mainly going to use all drives for VMs). I believe you need at least one data drive to start the array. Features like vm and docker only work in a running array. You could slap any old drive in the box to satisfy that requirement, our install one or even all your SSDs as data drives with no parity installed. Not recommending this as the perfect unRaid use case, but trying to answer the question.
January 28, 201610 yr Author thanks. I guess best use case is to mount the 4 x SSDs individual and create VMs on any of them? I just want to get best write/read performance from the drives and not fall victim to poor BTRFS/array performance.
January 28, 201610 yr thanks. I guess best use case is to mount the 4 x SSDs individual and create VMs on any of them? I just want to get best write/read performance from the drives and not fall victim to poor BTRFS/array performance. In theory, drives should perform at full speed if in a non-parity protected array. I think someone may have mentioned limitations in assigning SSDs as array devices, but don't remember why. I know you'd never want to preclear one, or let unRaid clear it, as it would take a lot of useful life from the SSD.
January 28, 201610 yr Author thanks. I guess best use case is to mount the 4 x SSDs individual and create VMs on any of them? I just want to get best write/read performance from the drives and not fall victim to poor BTRFS/array performance. In theory, drives should perform at full speed if in a non-parity protected array. I think someone may have mentioned limitations in assigning SSDs as array devices, but don't remember why. I know you'd never want to preclear one, or let unRaid clear it, as it would take a lot of useful life from the SSD. OK, so if I add the 4 x SSDs as DATA drives 1,2,3 & 4 - i can format them as XFS, start UNRAID and create VMs? I am really undecided what the optimum configuration is for UNRAID and VMs when using 4 x 1TB SSDs.
January 28, 201610 yr Hi Is it possible to format and use an SSD outside of the array/cache and use it for VMs, shares, dockers etc? Or do I still need to have at least one SSD/HDD part of an UNRAID array before I can use any of the functions such as creating a VM, share etc? I have 4 x 1TB SSDs but don't want to use the cache or array due to poor performance (im mainly going to use all drives for VMs). i use Unassigned Devices plug in to u can mount a disk out of the array , but u can just have large cache and only use cache
January 28, 201610 yr Author Hi Is it possible to format and use an SSD outside of the array/cache and use it for VMs, shares, dockers etc? Or do I still need to have at least one SSD/HDD part of an UNRAID array before I can use any of the functions such as creating a VM, share etc? I have 4 x 1TB SSDs but don't want to use the cache or array due to poor performance (im mainly going to use all drives for VMs). i use Unassigned Devices plug in to u can mount a disk out of the array , but u can just have large cache and only use cache sounds like a plan although I'm not sure of the consequence of using such a large cache other than the obvious (lack of backup). Which leads me to another question. Are there any decent backup products either consumer or enterprise that can backup the VMs (even when they're powered on)?
January 29, 201610 yr OK, so if I add the 4 x SSDs as DATA drives 1,2,3 & 4 - i can format them as XFS, start UNRAID and create VMs? I am really undecided what the optimum configuration is for UNRAID and VMs when using 4 x 1TB SSDs. Can advise on possible but only speculate on optimal. Adding SSDs in btrfs cache pool may have some advantage. You'd likely need a dummy disk in the array to use all 4 ssd disks like this. You'd lose half the capacity and have some protection. I wouldn't do it that way, but there are some good arguments that this would be "optimal". But if each is an autonomous (xfs) drive, I wouldn't expect any difference in performance having them in a parity-less array vs mounted outside the array. The issue is the array can't be empty and be started (never tried it with v6 but 99% sure this is true). IF you had a real media array like a normal user would have, I'd go with mounting outside. But if this is purely to leverage the platform for VM / Dockers, I'd likely opt to have the 4 SSDs in an unprotected array. Remember great is the enemy of good. I wouldn't stress too much. If you want to move array disks outside the array later, you can. Only the btrfs approach would limit your future options. Although even then, reformatting is always an option.
January 29, 201610 yr Community Expert thanks. I guess best use case is to mount the 4 x SSDs individual and create VMs on any of them? I just want to get best write/read performance from the drives and not fall victim to poor BTRFS/array performance. In theory, drives should perform at full speed if in a non-parity protected array. I think someone may have mentioned limitations in assigning SSDs as array devices, but don't remember why. I know you'd never want to preclear one, or let unRaid clear it, as it would take a lot of useful life from the SSD. I think it was because trim could invalidate parity.
January 30, 201610 yr I think it was because trim could invalidate parity. Which wouldn't matter for an unprotected array.
Archived
This topic is now archived and is closed to further replies.