Leaderboard

I think I found where my issue was occurring, I am being bottle necked by the windows OS cache because I am running the OS off a SATA SSD. I need to move that over to part of the 970 EVO. I am going to attempt that OS reinstall move later and test again. Now the problem makes a lot more sense and is why the speeds looked great in benchmarks but did not manifest in real world file transfers.

I used this adapter cable for years & never had a problem. Before I bought my server case I had a regular old case. I had (3) 4 in 3 hot swap cages next to the server. I ran the sata cables out the back of my old case. I had a power supply sitting on the shelf by the cages which powered them. The cool thing was that I ran the power cables that usually go to the motherboard inside of the case from the second power supply. I had a adapter that would plug into the motherboard and the main power supply that the computer would plug into. The adapter had a couple of wires coming from it to a female connection. You would plug your second power supply into it. What would happen is that when you turn on your main computer the second power supply would come on. That way your computer will see all of your hard drives at once. Of course when you turned off your server both of the power supplies would turn off. Here is a link to that adapter. Let me know what you think. https://www.newegg.com/Product/Product.aspx?Item=9SIA85V3DG9612

Thanks - I'll set this all up once I can get my hands on a good sized SSD drive to use as my cache for the clouddrive.

Yup, we use volume IDs to track the disks, actually. However, there is some changes to how that's handled in the latest beta, so this may not be an issue in the future.

Actually, yes. That's part of what we want to do with StableBit Cloud. Good news! the latest beta has a concurrency limit, that you can configure. It defaults to 2 drives, right now. So this should help you out greatly! http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.1.1.1057_x64_BETA.exe

Yeah, the pooled drives have hidden "PoolPart" folders on each drive. Along with some super hidden data that ID's the pool. And duplication settings are stored the same way. But glad to hear that migration was dead simple!

That is also a scenario where de-registration/uninstall/re-install/re-registration can help. If you want to try it, here is how: To deactivate the license: go into "Scanner Settings..", navigate to the License tab, click View license details, then deactivate. Then do a manual uninstall of Stablebit Scanner. Re-download the latest version, to be sure your first copy wasn't bad in some way. I find cleaning out Windows temp files to be helpful, especially with botched or damaged installations. Tools like CCleaner, Wise Disk Cleaner/Wise Registry Cleaner, etc. Re-install, and then re-activate your copy with your activation key.

Ok solution is that you need to manually create the virtual drive in powershell after making the pool: 1) Create a storage pool in the GUI but hit cancel when it asks to create a storage space 2) Rename the pool to something to identify this raid set. 3) Run the following command in PowerShell (run with admin power) editing as needed: New-VirtualDisk -FriendlyName VirtualDriveName -StoragePoolFriendlyName NameOfPoolToUse -NumberOfColumns 2 -ResiliencySettingName simple -UseMaximumSize

Jaga, Christopher, Thank you, migration was very easy indeed, StableBit software picked pools up without any issues, these pools must have all required metadata inside I believe.

I braved it and has worked fine. Did an inplace upgrade from 2016 to 2019 desktop experience and can read and write to drivepool fine...

Well, for moving the pool over to new drives, you could just copy from one pool to another. No need to share the poolpart folders. In fact.... by doing that, you may end up making more work for yourself. (eg, duplication)

To be blunt, when talking about storage, it's a good idea to take things with a grain of salt. There are a lot of misconceptions and myths that get perpetuated, even by smart and experienced people. Worse, is that some things may have been true at one point, but technology and the like improved, but people still believe what once held true. That said, StableBit Scanner polls SMART data once a minute, by default. And you can configure that interval, if you want. As for the stuff mentioned, unless you have a bad drive (either failing, or poorly designed), I don't think that this is actually an issue on modern drives, and the issues mentioned are an exaggeration.

If you're going that route, you'll want to consider your old pool architecture (how many drives, what size, etc) compared to the new one. If you have the same number of drives, the migration still isn't too hard: Deactivate the licenses, uninstall the software Share each hidden Poolpart-xxxxx folder (from each of the old pool's drives) on the network (i.e. OldPool-E, OldPool-F, etc) Install Drivepool on the new machine, create a new pool using your new drives, then stop the Drivepool service (optional). Access each network drive-share you created on the old machine, and copy it's contents into each hidden Poolpart-xxxxx folder in the new pool. Each drive in the Pool has one on it. Start up Drivepool on the new machine (restart the service first if you stopped it), and tell it to re-measure the pool so it can see all the content you copied in. If you have a different number of drives, that's okay too. You'll have to copy the files from the old network drive-shares into the new Poolpart-xxxxx folders on each new drive, and then re-measure (first) and re-balance (second) on the new machine. If your new drives are large enough, you can copy multiple old Poolpart-xxxxx folder contents into the same Poolpart-xxxx folder on the new pool. Basically you are manually populating the new pool's drives with the old files via network copy, then telling Drivepool to "go see what's there" (re-measure), and "spread it all out evenly" (re-balance). You may want to use the Disk Space Equalizer plugin for Drivepool, to evenly spread out the newly copied files in the new pool. Install it, open Drivepool, toggle the plugin on once, let it run, then toggle it off. It won't matter if Drivepool/Scanner are deactivated/uninstalled on the old machine, since all you're doing is manually accessing the hidden Poolpart-xxxxx folder that it leaves on all pooled drives. DP doesn't need to be running, activated, or even installed on the old machine for that, just the new one. One thing of note: to keep the same folder structure your old pool had, you want to copy the folders/files from inside the old Poolpart-xxxxx folders exactly as they were. If you put files or folders into different locations from where they used to be, the pool won't look the same. The exception of course is copying two drives' worth of Poolpart-xxxxx contents into just one Poolpart-xxxxx on a new pool drive. The folder/file hierarchy inside the hidden Poolpart folders is important.

If you're asking about Drivepool and Scanner, they are very easy to migrate. You will need to deactivate the license in each piece of software before uninstalling it, so you can reactivate on the new system. Click the gear icon (upper right) in each, then Manage License. For the pool - simply shut down, migrate the physical drives to the new one, boot up and install Drivepool. It will see the prior pool drives, and re-create a new pool using them automatically. Then just reactivate both pieces of software on the new system using the activation key(s) you own. Click the gear icon (upper right) in each, then Manage License. If you are also using Clouddrive: Detach the drives, deactivate the license, install on new system, activate the license or trial and attach the drives. (per a quote from Christopher)

Nope, different protocol. But trust me when I say that NVMe health is FAR superior to SMART. Awesome. As for protocol: http://blog.covecube.com/2018/05/stablebit-scanner-2-5-2-3175-beta/ That has a picture of it.

This is what it's supposed to do: But if it's working now, then that's fine.