Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11573
  • Joined

  • Last visited

  • Days Won

    366

Posts posted by Christopher (Drashna)

  1. On 8/28/2021 at 1:57 PM, GameOver said:

    I have a similar issue but Explorer processes sit at 99% and wont close.  only way to change it is to manually force Explorer to close via task manager.  THis is entirely related to DrivePool as it doesn't happen without DrivePool installed

    Are you accessing the pool over the network, or directly? 

    And does this happen with any of the disks in that pool, as well? 

  2. StableBit DrivePool doesn't remove empty folders, for a number of reasons.   If you want, you can manually clean up the empty folders. 

    As for prevent rclone, if it can, have it check if the pool is writable first.  If there is a missing disk, the pool goes read only until the missing disk is resolved. 

  3. It's part of StableBit Cloud, not CloudDrive (sorry for the confusing naming).

    And yeah, you'd need to sign up for an account.

    Right now, it's still in beta, so it's completely free.  But we do plan on offering it as a subscription based service.  However, I do believe that we plan on having a free tier, though. 

  4. Yup, that looks normal.  

    Specifically, new files are placed on the disks with the most available free space.  So the 8 TB drives won't be used until the 14+ TB drives are filled enough to have the same amount of free space as the small drives. 

    That said, the "Drive Space Equalizer" balancer plugin can be installed and enabled, and this will forcibly rebalance the data so that all of the drives are being equally used. 
    StableBit DrivePool Balancer Plugins

  5. No, and that's intentional.  Having an option to do that would definitely lead to "why is all my data gone" type issues.   And people getting very upset about that. 

    And ideally, you want to move the data off of the pool.  So you can remove the disks from the pool, normally. 

    If you want to destroy the pool, that can be done manually, which is ideal since it's not a simple thing to do. 

    That said, you can use "dpcmd ignore-poolpart" on all of the disks and that will remove the pool. 

  6. It doesn't provide any storage, but uses existing storage you have with various providers.   Also, it doesn't expose the files on the providers, but rather creates a virtual drive that is stored on those providers. 

    That said, all of our software comes with a 30 day, fully featured trial period.  i'd definitely recommend checking out the software, even if it ends up not being for you. 

  7. well, you can run "dpcmd ignore-poolpart" to immediately eject a disk from the pool, and mark it as removed.  This prevents the drive from being used by the pool, and does NOT move the files off of it.  

    But yeah, just disconnecting the disk and then reconnecting the drive will cause it to show back up in the pool, if you didn't remove the hidden "PoolPart" folder. 

  8. You should be fine, here.   If you use the "duplicate data later" option, it will skip the duplicate date, and should remove the drive pretty much immediately.   

    Connect a new drive and add it to the pool, and it will reduplicate the data to the new drive. 

    The old drive will still have the data on it, so worst case, you have a spare set of the files, just in case. 

  9. Okay, Alex has taken a look at the API changes, and how we have things set up. 

     

    Quote

    As per the email: "Items that have a Drive API permission with type=domain or type=anyone, where withLink=true (v2) or allowFileDiscovery=false (v3), will be affected by this security update."

    This part being the key here.  The type we use is "sure", so StableBit CloudDrive should NOT be effected by this change. 

    The exception here may be with chunks that are shared.  They may become inaccessible after this change. 

  10. For replacing disks in the pool, it depends on how much free space you have.  But ideally, you want to remove the disk from the Pool using the "remove" option in the UI.  This will safely remove the drive from the pool, and you can then disconnect the drive and connect the new drive.  

     

    And yeah, if the drives are out of warranty, it may be a good idea to replace them.

    And removing the drives won't necessarily move the data to the gold drives.  That depends entirely on the setup of your pool(s). 

  11. will confirm that there shouldn't be any performance impact.   But that is a "it depends" sort of thing.  If you have antivirus software installed or certain disk tools, then they can cause an increasing impact, the more more layers there are.   But this should be minimal, as this is all handled in the kernel. 

  12. Well, I'm glad to hear that you were able to get it resolved, but sorry to hear about all the troubles. 

    The first error may have been fixed by this:
    https://wiki.covecube.com/StableBit_DrivePool_F3540

    The second error, "0x80070643", is definitely the "pending reboot" error code.  

     

    Also, just a heads up, WHS2011 and Windows Server 2008R2 (which it is based on) is outside of extended support for Microsoft. You likely won't get any automatic updates, past the official end of support date.  

×
×
  • Create New...