JasonC

Hmm my related, but separate threads are starting to blur together a lot more. Requested pic is in this thread: http://community.covecube.com/index.php?/topic/2595-not-all-disks-in-the-pool-being-used/ Maybe lock this thread and just continue in the other?

Drashna has pointed out in one of my other threads that the message that it would not install was probably incorrect. He is correct, it appears to have installed anyway. I'm going to try using it, although I admit a little consternation at it. It's a bit of an interesting order of events that must happen to allow it to install, but still display a bad version/won't install message. So in conclusion, House was right, everybody lies. Even the installer. Thanks

Disk list as requested Ah...you are correct...it did install anyway. I wasn't sure where to look at first. I guess I will have to see if it works ok for me. Thank you for that part!

It's probably my underlying OS, I bet I'm too current on server OSes and something doesn't work the way the installer expects. If I attach the pool disks to say, an Windows 8.1 installation, and move the license there, it should all just work?

...and ...sigh. apparently this is yet another DrivePool related thing that is going to give me installation problems. someone at Stablebit, can I force the install somehow? Obviously it's(the installer) too stupid to know what it's talking about.

My bad, should have checked the FAQ first. Found instructions there Hmmm...not quite my bad.... FAQ presumes the presence of a dashboard. I have no such thing, so....I guess I'm going for uninstall/reinstall non-beta version.

So in the process of checking them out, I've run into a problem. I have the beta version(support suggested it in an attempt to help me with a licensing issue). The SSD Optimizer doesn't recognize the beta as a valid version to install on. So I wonder if other plugins would have a similar issue.

So...the SSD Optimizer looks interesting to me, but apparently it doesn't recognize the beta version as a version it will install on. Is there a way I can I safely install the current non-beta now, without trashing the pool, so I can enable the plugin functionality?

None, as far as I know. I assume you mean plugins to DrivePool? I wasn't aware you could even have plugins. It's a vanilla installation, with disks added to a pool.

There are 10 disks my pool. 2 disks were pre-seeded. Data is now only apparently writing to 5 of the other disks in the pool. 3 of the disks in the pool are not getting written to, based on the graph of how much each disk is full. That doesn't seem to be in line with what I was expecting to have happen. Is that supposed to be that way? At first, I thought perhaps it was filling up other disks until the reached the same fill level as the pre-seeded disks, but since 3 of the disks are not being written to at all, that doesn't seem to be the case. Thanks

Well, that's what I was asking about. Having watched it for a while, I see balance the data out automatically seems to mean that the pre-seeded disks won't have writes on them until the other disks are caught up. Which brings me to my next question... There are 10 disks my pool. 2 disks were pre-seeded. Data is now only apparently writing to 5 of the other disks in the pool. 3 of the disks in the pool are not getting written to, based on the graph of how much each disk is full. That doesn't seem to be in line with what I was expecting to have happen. Is that supposed to be that way?

As I was migrating from a damaged StorageSpaces pool, I ended up pre-seeding a couple of disks before transferring all my disks to the DrivePool based disk. So I have a couple of disks that currently have the majority of the content on the pool. It's significant, so say, 2TB on each of a 4TB disk, but the total pool size is much larger. Should I explicitly tell it to perform a re-balance now, or let it just get to it when it gets to it? It sort of seemed like from the settings that an automatic rebalance wouldn't bother re-allocating until they were much more full, so I'm wondering if I should actually wait until then or get ahead of it. Thank you!

I'm curious, does anyone know if scanning a thin-provisioned disk will cause it to actually allocate it's maximum reported space? i.e. might not want to fully scan(or scan at all) such a disk? Thanks!

Ok, thank you! Support asked me to try the beta as well but I'm having the same result. It's not really the software itself so far, it's that I can't get past the activation step.

Is anyone actually deployed there? I'm trying to deploy it on a 2016 server but I can't get past the registration page. I've reached out to customer support but it's a bit slow, the back and forth. I wondered if anyone else had any issues, and how they got around it. Specifically, when I enter my key, the form goes blank but nothing seems to actually happen...

Hello, I've loosely followed DrivePool over the years, having been a WHS 2003 user for a long time back in the day. I ended up walking away from disk pooling for a while once disks became too large for WHS, until Storage Spaces arrived. I'm now 99% decided to leave Storage Spaces behind and switch to DrivePool, but I have a few quick questions I wasn't able to locate answers to easily in the forums: 1) I'm assuming that there are no problems using it in a (2016) Windows Domain given the Essentials support 2) Can I move pool disks between interfaces? Specifically, I'm in the process of migrating data right now, if I were to start a DrivePool pool with the first disk on USB, and later move that disk to a SATA interface (no slots available until I am able to pull failing disks), should this be an issue? It looks like not with the signature based disk ID, but I thought I'd ask. 3) There was a three, but I've forgotten it now. Thank you!