Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  1. @Shane A really big thanks for this - as it made me realise I was thinking backwards. Of course you are right: if no new duplicated directories are placed in the pool after the new, third disk, is added, then duplicated files won't be moved to that new disk - makes sense, because they are already duplicated. So rather than move the duplicated files off of the failing disk, I should have moved the unduplicated files - Doh! HOWEVER, you were right: changing the rule to NOT put duplicated files on E: forced the balancer to start moving them to F and G - which stopped, when it thought it had
  2. @Shane A BIG thanks for such a fast response. 1. If you look here. Drive Pool is not even acknowledging the third (newest) drive as being a location for duplicated files. 2. See my UI - no re-balance here. 3. Thanks, for reporting that new disk checkbox is not sticky. 4. I don't have any additional plugins (only what came pre-installed as standard) so I'll try and force the duplicated files to move: Thanks!
  3. DrivePool V2.2.5.1237 I have one DrivePool virtual drive, that initially contained two identical (bought at the same time) 3TB Toshiba drives. Both 3TB drives (E and F) are completely (their entire partition) used in the pool. I run a simple policy/rule: An Unduplicated folder - where the files are balanced across both drives. A Duplicated folder - where files are duplicated across both drives. Everything was working great. About 1.5 years ago, I purchased a third identical 3TB drive (G) and added it to the pool - which balanced (I thought) and I didn't think any mo
  4. I have the same thing. I am running and it is throttling C: (which is not helpful...) because it says that the drive is over temp at 48C - when it thinks max temp is 44C (because that is the default max temp in scan control). The disk in question, is a Lexar 240 GB NS100, of which the manufacturer says that max temp is 70C. I have hooked the default max temp up to 55C - to clear the error and throttling, and I have submitted to Flock for analysis. I guess the DB that Scanner is reading from has incorrect values?
  5. Right, I have sussed it - and am now back up and everthing (including Drive Scanner) is working fine. I discovered that the Drive Scanner Service was throwing WMI Namespace errors which wmimgmt.msc was throwing up as: win32_operatingsystem: wmi invalid class Fixed by following steps 1 - 4 here: https://social.technet.microsoft.com/Forums/en-US/8ed26d46-9994-4052-a307-5b071805aea8/wmi-corrupt-how-to-reinstallrepair?forum=winservergen
  6. Yes, this is indicated as a known issue here: https://support.microsoft.com/en-gb/help/4471324/windows-10-update-kb4471324 - so I guess you might get additional support calls :-)
  7. Thanks Viktor - really appreciate you fast response. No, no other installs or changes other than the December Microsoft Malicious Software Tool update and MS AV signatures. So I told Drivepool and Cloud Drive to transfer the licence - and that worked, but Scanner complains that the background service failed to start. Checking event viewer, for Scanner, I have had these errors since install of KB4471324: Error report file saved to: C:\ProgramData\StableBit Scanner\Service\ErrorReports\ErrorReport_2018_12_13-10_02_51.0.saencryptedreport Exception: System
  8. Have just logged into W10 (prof) PC, after it has rebooted on install of KB4471324. Drivepool, Scanner and Cloud Drive now all give me an error dialogue that my "licence needs to be transferred to this computer". I don't want to hit the transfer button, because it is the same computer and same OS. The only difference being the install of this months MS Security Bulletin: KB4471324 How best should I proceed? Thanks, Woody.
  9. Team, I am current running (or was ...) PoolHD with one Drive Pool containing two physical disks. That Drive Pool contained two top level directories: "Duplicated" and "Non Duplicated" i.e. PoolHD balanced the non duplicated files across both disks and the duplicated files, duplicated across both disks. I have now upgraded to W10 and PoolHD no longer works - I expected this, as it is not supported in W10 - and I had always intended to migrate to DrivePool because Windows Storage Spaces requires the drives (that are to be added to a Storage Space) to be cleanly formatted, and of
  • Create New...