Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Reputation Activity

  1. Like
    Shane got a reaction from BIFFTAZ in Is it ok to use space on HDD outside of pool?   
    That's ok to do, won't cause any harm.
  2. Like
    Shane reacted to dan66215 in Unable to remove clouddrive(s) from a drivepool because I lost write access   
    I also got a little brave/creative/foolish and had the thought that maybe I could kick off the duplication process on P manually via command line since the GUI wouldn't come up and it wasn't duplicating on it's own from the nightly job.

    So I did a dpcmd check-pool-fileparts P:\ 1 which completed successfully. When I checked F in clouddrive, the usage has increased and there's 1TB+ queued. So it looks like it's duplicating. That's one good thing so far!


  3. Like
    Shane reacted to MikeRotch in File distribution not optimal. How to see which file(s) are affected?   
    Applied some more Google-Fu and found this command
    GWMI -namespace root\cimv2 -class win32_volume | FL -property DriveLetter, DeviceID which gave me different GUIDs than from diskpart.  I was able to match the volume from the logs to the GUIDs provided by that command.  I think I have corrected the permissions from https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/ 
    and will try a balancing pass.
    Thanks again,
  4. Like
    Shane reacted to dan66215 in Unable to remove clouddrive(s) from a drivepool because I lost write access   
    The detach was successful. I had to do a reboot between the detach and the re-attach.  However when I re-attached F, the configuration screen came up, I selected another physical drive on which to put the cache. That was some time ago and it has not yet appeared in the GUI.  I believe it's adding it, but maybe very slowly, as the Clouddrive app is using about 40% of the CPU. The other detached clouddrives (formerly M & K) are visible in the GUI but have lost their drive letters.  Also the Drivepool GUI will not come up, though I have access to all the lettered drives via windows explorer and command prompt.
    I guess I'll give it overnight and hope that F: gets re-attached and that is the cause of the Drivepool GUI not responding.
  5. Like
    Shane got a reaction from Slaughty101 in Wrong SSD size report in DrivePool   
    I'd suggest opening a support ticket with StableBit.
  6. Like
    Shane reacted to Wendo in Drivepool not balancing   
    For anyone that finds this later. The system is now balancing for free space on each drive. 
    At this point the only thing I can assume was that because one drive was over 90% full it just completely broke balancing with the Drive Space Equalizer plugin, and that failure cascaded and broke balancing for all plugins. I had the Prevent Drive Overfill set to not go over 90%, but I'm wondering if any plugin will actually bring a drive under 90% usage (if that's what it's set too) once it's already gone over. All the text seems to imply it will just stop it going over 90%, nothing about recovering from such a situation.
    I disabled all plugins except the disk usage limiter and told it not to put any unduplicated data on DRIVE2. That ran successfully and got DRIVE2 under 90%, and after that and enabling the other plugins it started working exactly as I'd expected it to do so for the last year.
  7. Like
    Shane reacted to RetroG in Need to replace MediaSonic ProBox that died   
    regarding power:
    to use a PSU without a motherboard An "ATX Jumpstarter" AKA an ATX connector that connects Pin 14 to ground.
    you can also tie this to a power switch but it must be a latching type (most cases have push button style power buttons)

    if you want a little future expandability (and the ability to use less and longer cables) you can replace the SAS breakout brackets with a SAS expander. my personal pick would be the AEC-82885T (although that uses Mini-SAS HD connectors, 8643+8644).

    this would allow you to use SATA disks using longer cables (SATA cables use a lower signaling voltage) and allow you to connect just one SAS cable to each JBOD. (yes, you are connecting 8 disks using one 4 lane 6Gb or 12Gb link, but it's barely noticeable for spinning drives)
  8. Like
    Shane reacted to Damionix in Help with using Sans Digital EliteSTOR ES316X6+B with WorkStation (Dell Precision 7920)   
    Thank You so much for you response. I wish it came earlier. But I did get it done and configured and so far all has been working great. 
  9. Like
    Shane reacted to RetroG in Help with using Sans Digital EliteSTOR ES316X6+B with WorkStation (Dell Precision 7920)   
    it's an IT mode controller, it will work fine, even with 4Kn and TRIM. provided the expander in the JBOD is sane it should literally be plug and play. (I use a custom built jbod this way, on my windows desktop)

    but for cables... electrically they are both identical, the shape of the connector is the only difference. you can buy cables that go from 8644 to 8088 too. and honestly I would just go with the 9300, the 9200 series is quite ancient now and the price difference isn't much at all.. and provides an easy upgrade path if you want to someday install a better expander or a jbod that supports 12Gb/s (which you can daisychain the elitestore off of). the only gotcha is that the 9300 is going to run warmer.

    TLDR SAS hardware is insanely flexible, if you can think of it it'll probably work.
  10. Like
    Shane got a reaction from Shooter3k in Drivepool balancing   
    The only ways I can think of to do that would be to #1, have a pool exclusively for just those drives and that folder (whether by itself or as part of a bigger pool), #2 use File Placement and allow only that folder to use those drives (and I'm not sure if the disk space balancing algorithm is smart enough to figure out what you want from that), or #3 turn off automatic balancing and manually spread the files in that folder across the poolparts of those disks yourself.
  11. Like
    Shane reacted to Christopher (Drashna) in Scanner does not save progress when switching drives?   
    To add to this, yes, the progress is saved.  The "scanning" percentage is based on what needs to be scanned currently, not on the whole disk.  Which can be misleading.
    That said, you can see how the drive is tracked here: 
    https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Scanning Panel#Sector Map
    And you may note that each sector has a date when it was last scanned.  Each region is tracked, and different regions on the same disk can and will have different dates and times.   Over time, this should actually help the software to "learn" when to scan the drives, by picking times when they are much less likely to be throttled. 
  12. Thanks
    Shane got a reaction from ZagD in Can I use Drivepool inside a VM?   
    FWIW when I ran DrivePool in a MS Hyper-V VM a few times late last year, to mess with various pool setups, it worked without issue.
  13. Like
    Shane reacted to FONMaster in reinstalling, but installer says reboot pending.   
    Mission accomplished! Thanks for the steer, Shane!
  14. Like
    Shane reacted to RoadHazard386 in Making files visible on OneDrive Personal   
    Never mind. 😉 To accomplish my particular task, I don't actually need to make the files visible in Windows File Explorer, I just need to tweak OneDrive's settings to de-select the "OneDrive\Apps\StableBit Cloud Drive" folder. Now OneDrive will stop syncing it to each and every PC with OneDrive installed. 
    To free up the space it's already wasted, I then select the same folder in Windows File Explorer, right-click it, and choose "free up space." 
  15. Like
    Shane got a reaction from Shooter3k in Change settings.json to allow more concurrent disks?   
    Not that I know of. Perhaps make a feature request via the contact form?
  16. Like
    Shane reacted to Alex in How to access your cloud drive data after May 15 2024 using your own API key   
    This post will outline the steps necessary to create your own Google Drive API key for use with StableBit CloudDrive. With this API key you will be able to access your Google Drive based cloud drives after May 15 2024 for data recovery purposes.
    Let's start by visiting https://console.cloud.google.com/apis/dashboard
    You will need to agree to the Terms of Service, if prompted.

    If you're prompted to create a new project at this point, then do so. The name of the project does not matter, so you can simply use the default.


    Enter Google Drive API and press enter.

    Select Google Drive API from the results list.

    Click ENABLE.
    Next, navigate to: https://console.cloud.google.com/apis/credentials/consent (OAuth consent screen)

    Choose External and click CREATE.

    Next, fill in the required information on this page, including the app name (pick any name) and your email addresses.
    Once you're done click SAVE AND CONTINUE.

    On the next page click ADD OR REMOVE SCOPES.

    Type in Google Drive API in the filter (enter) and check Google Drive API - .../auth/drive
    Then click UPDATE.

    Now you will be prompted to add email addresses that correspond to Google accounts. You can enter up to 100 email addresses here. You will want to enter all of your Google account email addresses that have any StableBit CloudDrive cloud drives stored in their Google Drives.

    Click ADD USERS and add as many users as necessary.

    Once all of the users have been added, click SAVE AND CONTINUE.

    Here you can review all of the information that you've entered. Click BACK TO DASHBOARD when you're done.
    Next, you will need to visit: https://console.cloud.google.com/apis/credentials (Credentials)

    Click CREATE CREDENTIALS and select OAuth client ID.

    You can simply leave the default name and click CREATE.

    You will now be presented with your Client ID and Client Secret. Save both of these to a safe place.
    Finally, we will configure StableBit CloudDrive to use the credentials that you've been given.
    Open C:\ProgramData\StableBit CloudDrive\ProviderSettings.json in a text editor such as Notepad.
    Find the snippet of JSON text that looks like this:
    "GoogleDrive": { "ClientId": null, "ClientSecret": null } Replace the null values with the credentials that you were given by Google surrounded by double quotes.
    So for example, like this:
    "GoogleDrive": { "ClientId": "MyGoogleClientId-1234", "ClientSecret": "MyPrivateClientSecret-4321" } Save the ProviderSettings.json file and restart your computer. Or, if you have no cloud drives mounted currently, then you can simply restart the StableBit CloudDrive system service.
    Once everything restarts you should now be able to connect to your Google Drive cloud drives from the New Drive tab within StableBit CloudDrive as usual. Just click Connect... and follow the instructions given.
  17. Like
    Shane got a reaction from igobythisname in Remove error "Not enough space on the disk"   
    "?-did i go about this correctly? (i know)i have been impatient to let it duplicate/rebalance while i'm trying to complete my drives swap"
    "?-why did it give me the not enough space error when i added a new 18tb?"
    I might guess that if you had "duplicate files later" checked then it may not have had time to do that after the first 10tb was removed and before the second 10tb was removed, so it had to duplicate 2x10tb when at that point it only had 1x18 to go to? And/or did you have any File Placement rules that might've interfered? Only other thing I can think of is something interrupting the enclosure and DrivePool thought that meant not enough space.
    "?-why does the 2nd 10tb only read in my Sabrent enclosure but not when I install it in my tower?"
    No idea; DrivePool shouldn't have any problem with a poolpart drive being moved to a different slot (assuming DP was shut down before moving it and started up after moving it). When you say it didn't show up, do you mean "it didn't show up in DrivePool" or do you mean "it didn't show up at all, e.g. not in Windows Disk Management"? Because the latter would indicate a non-DP problem.
  18. Like
    Shane reacted to igobythisname in Remove error "Not enough space on the disk"   
    i see what you mean about the 2x10tb only have 1x18tb to go to.. the 2nd 10tb successfully removed, yay!
    as for the drive not showing up in my tower-it was not showing up in BIOS or Disk Management; turns out it was the 3.3v pin on a shucked WD white label that was the issue.. i covered up the power pin with tape and all is well now. thank you so much for your response.
    now i'm in the process of removing the 18tbs and 10tbs and reformatting them, so i can increase the allocation unit size from 4KB to 64KB
  19. Like
    Shane got a reaction from bobloadmire in Optimizing SSD cache with drive pool, trying to keep most recent files in cache for faster reads.   
    "1. Can I specify to keep the most recent files in the SSD cache for faster reads, while also duplicating them to archive disks during the nightly schedule?"
    No; files can be placed by file and folder name, not by file age. You could try requesting it via the contact form? Not sure whether it'd work better as a plug-in or a placement rule (maybe the latter as an option when pattern matching, e.g. "downloads\*.*" + "newer than 7 days" = "keep on drives A, B, D").
    "2. can I specify some folders to always be on the SSD cache?"
    Yes; you can use Manage Pool -> Balancing -> File Placement feature to do this. You would also need to tick "Balancing plug-ins respect file placement rules" and un-tick "Unless the drive is being emptied" in Manage Pool -> Balancing -> Settings. If you're using the Scanner balancing plug-in, you should also tick "File placement rules respect real-time file placement limits set by the balancing plug-ins".
  20. Thanks
    Shane got a reaction from inedibleoatmeal in Writing zeros to free space in pool   
    If you mean Microsoft's cipher /w, It's safe in the sense that it won't harm a pool. However, it will not zero/random all of the free space in a pool that occupies multiple disks unless you run it on each of those disks directly rather than the pool (as cipher /w operates via writing to a temporary file until the target disk is full, and drivepool will return "full" once that file fills the first disk to which it is being written in the pool).
    You might wish to try something like CyLog's FillDisk instead (that writes smaller and smaller files until the target is full), though disclaimer I have not extensively tested FillDisk with DrivePool (and in any case both programs may still leave very small amounts of data on the target).
  21. Sad
    Shane reacted to fleggett1 in Drive question.   
    I heard back from Gillware.  They want $1200 AND another drive that's at least 20 TB.  And they can only "guarantee" that they'll be able to recover around 80% of the disk.
    JFC.  It's like they think the drive has been at the bottom of the sea for the past year.  I was thinking $400 tops.
    I may never again go anywhere near diskpart.  If I had known things were going to be this expensive, I would've tried using something like EaseUS first, on my own.
  22. Like
    Shane reacted to fleggett1 in Drive question.   
    I'm still restoring the pool, which'll take another couple of days (no word yet from Gillware), but I got off my duff and took the Sabrent apart.  I have to say that it's really impressive on the inside, with almost everything some manner of metal.  Only the front doors and a handful of other parts are plastic.  Unpopulated, Sabrent says that it weighs 17.8 lbs, so it would definitely kill you if someone dropped it on your head, even drive-less.
    The PSU is a very cute 3.5" x 5" x 1.25" device that should be up to the task since it only has to have enough oomph for 10 drives along with the two 120mm "Runda" RS1225L 12L fans.  As you can see from the label, it's a 399.6W "Mean Well" EPP-400-12 unit when cooled adequately.  Since a normal 3.5 drive only consumes around 9.5W at load, that's only 95W needed for the drives, with the rest for the fans and the supporting PCB.
    So, assuming the PSU isn't outright lying, I don't think that's the issue.  I checked mine for obvious problems, like expanding or leaking caps, but didn't see anything.  The caps themselves look to be of pretty decent quality and the bottom circuit board appears clean.  The unit has what looks to be a rheostat, but I have no idea what it controls.
    If I had to take a very wild guess, I would say there's something amiss with the backplane, as that seems to be a common source of consternation with low(er)-grade server-style boxes, like the Norco.  It is interesting that I only started seeing drive dropouts once I had populated all ten bays, so maybe it works fine with only 8 or 9 bays running.
    So far, the two Terras are running just fine.  I'm praying to all sorts of gods that it remains so.

  23. Like
    Shane reacted to Martixingwei in Google drive not supported after may 2024? Why?   
    I believe currently the only way is to download everything to local and use the converter tool come with CloudDrive to convert it to other mountable format.
  24. Like
    Shane reacted to fleggett1 in Drive question.   
    Oh, hrrmmm, interesting.  It looks like FreeFileSync did the job, but its UI looks like it was done by a madman, so I might try Robocopy next time.  That fileclasses link is EXTREMELY helpful.
    A bit more on the pool reconstruction front.  I really needed more than six drive bays to work with, so I bloodied a credit card and bought another Terra.  FFS mirrored everything on the old pool to the three new Seagates seemingly fine.  Oh, but before that, the Seagates long formatted successfully, so I'm considering them good to go.
    I'm currently long formatting three of the old pool drives, which'll take another 24 hours.  Once that's done, I'll fire-up the second Terra with old pool drives and copy everything over from them to the drives that I'm in the process of long formatting (presuming they pass).
    Gillware has the drive.  I stressed to my contact that the drive should be fine electronically and mechanically, so they shouldn't have to take it apart.  I'm HOPING this will lower the cost of the recovery substantially.  You would think restoring everything from a simple diskpart clean should be a cakewalk for a professional recovery service, but we'll see.
    Incidentally, I was looking over Terramaster's line of products and they are all-in on NAS devices, with their flagship product supporting 24 drives.  I wish they would offer a 10- or even 8-bay DAS box, but then you're back to needing a beefy PSU.  I still intend to take apart the Sabrent assuming it's not a nightmare to do so.
    That's currently all the news that's fit to print.  More to come!
  25. Like
    Shane got a reaction from Mav1986 in Google drive not supported after may 2024? Why?   
    Once you've obtained your own API key from Google, the file to edit is C:\ProgramData\StableBit CloudDrive\ProviderSettings.json
    I also suggest making a backup copy of that file before you make any changes to it.
    You may then need to restart clouddrive. Per Christopher's post, "The safest option would be to detach the drive, change API keys, and re-attach. However, you *should* be able to just re-authorize the drive after changing the API keys."
    I suspect 350 Mbps is the best you'll get. 
  • Create New...