Jump to content
Covecube Inc.

Question

Hello,

I recently started upgrading my 3TB & 4TB disks to 8TB disks and started 'removing' the smaller disks in the interface. It shows a popup : Duplicate later & force removal -> I check yes on both...

Continue 2 days it shows 46% as it kept migrating files off to the CloudDrives (Amazon Cloud Drive & Google Drive Unlimited).

  • I went and toggled off those disks in 'Drive Usage' -> no luck.
  • Attempt to disable Pool Duplication -> infinite loading bar.
  • Changed File placement rules to populate other disks first -> no luck.
  • Google Drive uploads with 463mbp/s so it goes decently fast;
  • Amazon Cloud Drive capped at 20mbps... and this seems to bottleneck the migration.
  • I don't need to migrate files to the cloud at the moment, as they are only used for 'duplication'... 

It looks like it is migrating 'duplicated' files to the cloud, instead of writing unduplicated data to the other disks for a fast removal.

Any way to speed up this process ? 

 

CloudDrive: 1.0.0.592 BETA

DrivePool: 2.2.0.651 BETA

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

If the process is ongoing, there should be a couple of buttons to the right of the pool condition bar, an "X" to cancel, and an ">>" to boost priority. 

 

 

however, this is still essentially a file copy. For a normal drive, tht would be roughly 4 hours per TB, under ideal circumstances. With a CloudDrive disk, it may be significantly longer, depending on your connection speed, the free space and size of the cache drives. 

 

 

Worst case here, if you want, you cloud "forcibly eject" the specific drive from the pool, and then copy it's contents to one of the other drives. 

 

This is definitely a more advanced bit, and requires much more "hands on", as you're essentially doing the disk removal manually (where as the UI automates it).

 

However, to do so requires installing one of the more recent StableBit DrivePool builds. 

http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.676_x64_BETA.exe

 

Also, check the disk in question, and look at the "PoolPart.xxxxx" folder. the "xxxxx" part is the pool part ID, and is needed for the next part. 

With the newer version, open up a command prompt, and run "dpcmd ignore-poolpart x: xxxxx" (where, "x:" is the pool drive, and the "xxxxx" is the Pool Part ID listed above).  This will disk from participation from the pool, causing it to show up as "missing" in the UI, where you'd want to remove it. 

 

From here, you can copy the contents of the PoolPart folder of that disk to whichever you want.  In this case, you could add the new disk to the pool, and copy the contents of the PoolPart folder on the old disk to the new Poolpart folder on the new disk. 

Share this post


Link to post
Share on other sites
  • 0

If the process is ongoing, there should be a couple of buttons to the right of the pool condition bar, an "X" to cancel, and an ">>" to boost priority. 

 

 

however, this is still essentially a file copy. For a normal drive, tht would be roughly 4 hours per TB, under ideal circumstances. With a CloudDrive disk, it may be significantly longer, depending on your connection speed, the free space and size of the cache drives. 

 

 

Worst case here, if you want, you cloud "forcibly eject" the specific drive from the pool, and then copy it's contents to one of the other drives. 

 

This is definitely a more advanced bit, and requires much more "hands on", as you're essentially doing the disk removal manually (where as the UI automates it).

 

However, to do so requires installing one of the more recent StableBit DrivePool builds. 

http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.676_x64_BETA.exe

 

Also, check the disk in question, and look at the "PoolPart.xxxxx" folder. the "xxxxx" part is the pool part ID, and is needed for the next part. 

With the newer version, open up a command prompt, and run "dpcmd ignore-poolpart x: xxxxx" (where, "x:" is the pool drive, and the "xxxxx" is the Pool Part ID listed above).  This will disk from participation from the pool, causing it to show up as "missing" in the UI, where you'd want to remove it. 

 

From here, you can copy the contents of the PoolPart folder of that disk to whichever you want.  In this case, you could add the new disk to the pool, and copy the contents of the PoolPart folder on the old disk to the new Poolpart folder on the new disk. 

 

Updated the DrivePool but receive:

 

PS C:\Users\Administrator> dpcmd ignore-poolpart Y: f61eddb3-5d7d-4a0b-9f8f-dcdbf0661d92
 
 
dpcmd - StableBit DrivePool command line interface
 
Version 2.2.0.676
 
Error: Incorrect function. (Exception from HRESULT: 0x80070001)

Tried Y: Y:\ "Y" "Y:" etc, no luck

Edited by Mirabis

Share this post


Link to post
Share on other sites
  • 0

To make absolutely clear, the Y: drive is your pool, and the "f61eddb3-5d7d-4a0b-9f8f-dcdbf0661d92" is the part after the "PoolPart." for the folder name, correct?

 

If so, could you enable logging and reproduce? 

http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

 

 

Also, try running "chkdsk x: /r", where "x:" is the pooled disk in question. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...