Jump to content

JustinH

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by JustinH

  1.  Just to add to this post. This solution of editing the BitLocker_PoolPartUnlockDetect json entry works for me, however it is important that you change the default value of the Override value for BitLocker_PoolPartUnlockDetect entry in both the CloudDrive AND and DrivePool json files. Change Override from null to false. These two json files should be located here:

    1. C:\ProgramData\StableBit CloudDrive\Service\Settings.json
    2. C:\ProgramData\StableBit DrivePool\Service\Settings.json

    Stop the two CloudDrive AND and DrivePool services and then edit the json files. Restart services.

    Change this entry. It is normally at the top of the JSON file.

     "BitLocker_PoolPartUnlockDetect": {
       "Default": true,
       "Override": null
     },

    to

     "BitLocker_PoolPartUnlockDetect": {
       "Default": true,
       "Override": false
     },

    More info here http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings

  2. Just to add to this post. This solution works for me, however, it is important that you change the default value of the Override value for BitLocker_PoolPartUnlockDetect entry in both the CloudDrive AND and DrivePool json files. Change Override from null to false. These two json files should be located here:

    1. C:\ProgramData\StableBit CloudDrive\Service\Settings.json
    2. C:\ProgramData\StableBit DrivePool\Service\Settings.json

    Stop the two CloudDrive AND and DrivePool services and then edit the json files. Restart services.

    Change this entry. It is normally at the top of the JSON file.

     "BitLocker_PoolPartUnlockDetect": {
       "Default": true,
       "Override": null
     },

    to

     "BitLocker_PoolPartUnlockDetect": {
       "Default": true,
       "Override": false
     },

     

  3. However the drivepool drive is available and seems to be running fine and the 3 underlying disks are all OK with chkdsk.

    One last thing is that the drivepool drive  does not appear in Stablebit Scanner. I have reset Drive Scanner and still does not appear.

    File explorer reports as the correct size (approx 22TB) but dispart and the Disk Management MMC have it as just 2TB approx.

    This is running on Windows Server 2019.

    Any solutions? This is a huge drive (3 x 8TB disks make it up) so would rather not have to start again particularly when it appears to be working fine in other respects.

  4. But I think it is very unlikely a ransomeware gang would write specific code for StabelBit users.  Simply not worth their time.

    I am sure they do the 80:20 rule and StabeleBit is a lot less than 20 when it comes to % of their target audience using it.

    I have submitted an RFE via the contact for,

  5. I have a trial of StableBit and also noticed that my external USB drives did not sleep at all. As you say the drives are being activated/polled every 5 seconds or so. It is very annoying and just wastes electricity etc.

    Covecube should really try and get on top of this issue and at least provide a KB article on how to tackle this issue.

    The bitlocker setting has been disabled.

  6. I'm really enjoying this suite of software which I am playing around with at the moment (on 30 day trial). Currently I copy much of my local data to cloud storage using something called Air Explorer, and therefore I am comparing it to StableBit CloudDrive. One fairly significant weakness is that any ransomware would just encrypt all my cloud storage as well as local, because they are just drive letters with StableBit.

    I know you can make a drive "Read Only" but as this is not available at the command line or via a schedule, I can not integrate with with my backup software.

    Is there any solution to this?

×
×
  • Create New...