I wonder if going full SSD Pool is a good idea. While with HDDs it makes sense with SSDs it seems like it's more beneficial to RAID0 bunch of them and then copy everything to HDD only pool. Or abandon pool and go big array way (like 16 drives R60).
I would love to [sllooowwwwllllyyy] get rid myself of HDD ballast. Noisy, clunky and reliability is iffy with some and better with others. Problem is size and price. I can order 8x 4TB HDDs in a instant, you can't do that with SSDs unless you have Arab sheik as an uncle .
Right now went through some modifications as my Adaptec 71605 didn't initialized at all on my X99 board. After long wait finally changed it to 8405+Intel expander RES3FV288, only by name because it's re-branded Adaptec 82885T for (equivalent of) ~50USD less, which is nice. For now have mix setup with 2 arrays of HGST 3TBs and 5TBs + 4x4TB HGST drives configured into pool with triple duplication. 3&5 TB part will be removed in the near future and moved to old X58 system.
How fully SSD pool affect performance and life of SSD? Of course advantage of pool is obvious. No need to buy wholesale drives like in the case of RAID array, but will frequent duplication wear much faster NAND than for example R10 or 60? I know that SSDs get massive write hit when RAIDed into any redundant kind of array 10/5/6/50/60. Tested that first hand and really interested on the input of more knowledgeable folks than myself.
The only gripe I have with StableBit DrivePool is Scanner part. I reinstalled it again and with some tweaks finally got SMART of HDDs but not SSDs or NVMe 750s (for now only smartools returns any data). Still it takes days to scan anything (HDDs). For now disabled scanning the arrays because it's pointless. I would have to prevent any operations on both arrays for Scanner to work which is simply impossible. Prefer to configure controller to scrub drives on its own. Beginning to think that I should abandon that also on newly created pool. Controller reports SMART OK, without any dark-magic. When I order verification on a drive it just starts where ended previous day. SB Scanner just restarts and grinds surface for 12-15 hours and can't finish before workstation is powered down. At the moment it slowly crawling past 64.8% of first drive. It will never finish that today. Probably my last attempt with running Pool&Scanner together. Will see in next 5 hours or so if at least 1 drive is done.
Question
Hakuren
Hi guys. First post here.
I wonder if going full SSD Pool is a good idea. While with HDDs it makes sense with SSDs it seems like it's more beneficial to RAID0 bunch of them and then copy everything to HDD only pool. Or abandon pool and go big array way (like 16 drives R60).
I would love to [sllooowwwwllllyyy] get rid myself of HDD ballast. Noisy, clunky and reliability is iffy with some and better with others. Problem is size and price. I can order 8x 4TB HDDs in a instant, you can't do that with SSDs unless you have Arab sheik as an uncle .
Right now went through some modifications as my Adaptec 71605 didn't initialized at all on my X99 board. After long wait finally changed it to 8405+Intel expander RES3FV288, only by name because it's re-branded Adaptec 82885T for (equivalent of) ~50USD less, which is nice. For now have mix setup with 2 arrays of HGST 3TBs and 5TBs + 4x4TB HGST drives configured into pool with triple duplication. 3&5 TB part will be removed in the near future and moved to old X58 system.
How fully SSD pool affect performance and life of SSD? Of course advantage of pool is obvious. No need to buy wholesale drives like in the case of RAID array, but will frequent duplication wear much faster NAND than for example R10 or 60? I know that SSDs get massive write hit when RAIDed into any redundant kind of array 10/5/6/50/60. Tested that first hand and really interested on the input of more knowledgeable folks than myself.
The only gripe I have with StableBit DrivePool is Scanner part. I reinstalled it again and with some tweaks finally got SMART of HDDs but not SSDs or NVMe 750s (for now only smartools returns any data). Still it takes days to scan anything (HDDs). For now disabled scanning the arrays because it's pointless. I would have to prevent any operations on both arrays for Scanner to work which is simply impossible. Prefer to configure controller to scrub drives on its own. Beginning to think that I should abandon that also on newly created pool. Controller reports SMART OK, without any dark-magic. When I order verification on a drive it just starts where ended previous day. SB Scanner just restarts and grinds surface for 12-15 hours and can't finish before workstation is powered down. At the moment it slowly crawling past 64.8% of first drive. It will never finish that today. Probably my last attempt with running Pool&Scanner together. Will see in next 5 hours or so if at least 1 drive is done.
Link to comment
Share on other sites
2 answers to this question
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.