Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Shane last won the day on May 16

Shane had the most liked content!

About Shane

Profile Information

  • Gender
    Not Telling
  • Location
  • Interests

Recent Profile Visitors

3627 profile views

Shane's Achievements

  1. It's good you didn't post your activation ID in the forum. That's mean to be kept private between you and StableBit. Even with a deactivated license, DrivePool will still be able to read files (now if it was still able to write to the pool, that'd be odd; maybe there's a grace period). On the new box where the media app can't "find" the file in the pool, can it "find" the file if you access it directly via whichever physical drive's hidden poolpart folder? Can you still copy the file from the pool to a non-pool drive with explorer? If not, can you still copy the file from the poolpart folder with explorer?
  2. When you say "Rebooted and DrivePool mounted the drive" do you mean the problem went away after the reboot? If so, it's possible something happened that caused the drive to briefly drop out but DrivePool wasn't able to reconnect (until the reboot)?
  3. That may indicate some other piece of software (or Windows) has an update pending. If not, for that level of technical assistance I'd suggest using the Contact form to open a support ticket.
  4. Unless directed otherwise by a File Placement rule or a balancer that can set file placement limits, DrivePool will always try to place incoming files on the drive with the most free space. To balance existing files across all the drives according to percentage used space, it looks like you need to do the following: Balancing -> Balancers: enable the "Disk Space Equalizer" balancer with its options set to "Equalize by the percent used". I'd also recommend making the "StableBit Scanner" balancer the highest priority if you're using that, and you can probably disable the "Volume Equalization" and "Drive Usage Limiter" balancers. Balancing -> Settings: turn on the Automatic balancing so that the (non-realtime, non-immediate) Balancers can do their thing. For now I'd suggest selecting "Balance immediately" with the "Not more often..." option unchecked.
  5. Removing a drive doesn't make the pool read-only during the removal. It does prevent removing other drives (they'll be queued for removal instead) and I believe it may prevent some other background/scheduled tasks, but one should still be able to read and write files normally to the pool. Only problem I can think of is if you're removing drive X and you've got a file placement rule that says files can only be put on X; I'd assume you'd have to change or disable that rule.
  6. Not that I know of. Perhaps make a feature request via the contact form?
  7. Non-real-time duplication is scheduled, so one disk at a time. When that runs is controlled by FileDuplication_DuplicateTime in the Settings.json file.
  8. As far as I can tell real-time tasks (e.g. real-time duplication) are as concurrent as they need to be (e.g. 2x duping = simultaneous writes to two disks, 10x duping = to ten disks, etc) while scheduled tasks (e.g. balancing, duplication checking, etc, including manually initiated tasks) are one disk at a time (at least for writes).
  9. If the main goal is to have the cloud storage act as an offsite backup that doesn't slow down the local storage, instead of a single pool with local and cloud disks I'd suggest separate pools for local and cloud with a backup tool updating the latter from the former. Edit: Otherwise, with only a single pool of mixed local and cloud drives, ensure the cloud drive local cache is set to expandable and is on a large enough disk to handle typical write volumes. Per the manual: "An expandable cache will try not to consume all of the disk space on the local cache drive. It will always try to keep at least 5 GB free. As the free space on the cache drive approaches 5 GB, in order to continue to maintain some free space on the local cache drive, writes to the cloud drive will get progressively slower."
  10. "?-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.
  11. After some more testing I can confirm cipher /w run on the pool only erases the free space on one drive in the pool before stopping, while filldisk run on the pool appears to leave anywhere from a few megabyes to over a gigabyte untouched on each of the disks in the pool. Filldisk also reacted similarly when run on individual drives via a mounted path (e.g. E:\Disks\MountedDrive) rather than via a drive letter, which is something to keep in mind if you use the former method to directly access your drives. Based on observing how DrivePool operated, I would recommend free space cleaning tools only be run directly on the individual drives. CyLog's Filldisk: Writes only zeroes, so three times faster than cipher /w. Doesn't remove the files it creates after it's aborted or finished, so you can effectively "pause" and you can see for yourself whether the free space is zero afterwards. In testing did not completely wipe the free space on drives accessed via mounted paths. May not scrub deleted files that are very small (1KB) due to how NTFS works. Microsoft's Cipher: Writes zeroes, then ones, then random bytes so more thorough but three times slower than filldisk. Leaves an empty EFSTMPWP folder on the target afterwards, so hard to check if it gets every last byte and there is a warning in the MS documentation about it potentially missing files of 1KB or less in size. Worked on mounted paths. SysInternals' SDelete: Like Cipher, but apparently has the 1KB file issue solved. TRIM: any SSD with TRIM functionality can do this automagically (and thoroughly). A windows command to manually trigger this is defrag volume /o - e.g. "defrag e: /o". If you are concerned about thieves scrounging through your Windows disks after stealing the machine, I'd recommend Bitlocker and a long passphrase.
  12. "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".
  13. The 12 Gb/s throughput for the Dell controllers mentioned on the datasheet is total per controller, so if you operated on multiple drives on the same controller simultaneously I'd expect it to be divided between the drives. Having refreshed my memory on PCIe's fiddly details so I can hopefully get this right, there's also limits on total lanes direct to the CPU and via the mainboard; e.g. the first slot(s) may get all 16 direct to the CPU(s) while the other slots may have to share a "bus" of 4 lanes through the chipset to the CPU. So even though you might have a whole bunch of individually x4, x8, x16 or whatever speed slots, everything after the first slot(s) is going to be sharing that bus to get anywhere else (note: the actual number of direct and bus lanes varies by platform). So you'd have to compare read speeds and copy speeds from each slot and between slots, because copying from slotA\drive1 to slotA\drive2 might be a different result from slotA\drive1 to slotB\drive1 from slotB\drive1 to slotC\drive1... and then do that all over again but with simultaneous transfers to see where, exactly, the physical bottlenecks are between everything. As far as drivepool goes, if C was your boot drive and D was your pool drive (with x2 real-time duplication) and that pool consisted of E and F, then you could see drivepool's duplication overhead by getting a big test file and first copying it from C to D, then from C to E, then simultaneously from C to E and C to F. If the drives that make your pool are spread across multiple slots, then you might(?) also see a speed difference between duplication within the drives on a slot and duplication across drives on separate slots. If you do, then consider whether it's worth it to you to use nested pools to take advantage of that. P.S. Applications can have issues with read-striping, particularly some file hashing/verification tools, so personally I'd either leave that turned off or test extensively to be sure.
  14. 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).
  15. Shane

    SMART errors

    Depending on the error, it might have been one that the drive's own firmware was capable of (eventually) repairing?
  • Create New...