Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  1. 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?
  2. 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
  3. 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 :-)
  4. 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.Management.ManagementException: Invalid namespace at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObjectSearcher.Initialize() at System.Management.ManagementObjectSearcher.Get() at ScannerServiceLib.Disks.#bFc() at ScannerServiceLib.Disks.Create() at ScannerServiceLib.Main._Closure$__.#qpf() at CoveUtil.ReportingAction.Run(Action TheDangerousAction, Func`2 ErrorReportExceptionFilter) and accompanying it: Error report file saved to: C:\ProgramData\StableBit Scanner\Service\ErrorReports\ErrorReport_2018_12_13-10_02_54.8.saencryptedreport Exception: CoveTroubleshooting.Reporter+ReporterLogException: {reporter_exception} at CoveTroubleshooting.Reporter.ThrowLogReportN(Exception TheException, Object[] TheParams) at CoveUtil.ErrorReporting..(Exception ) This device is an HP ProLiant Microserver N40L which has Realtek sound. However, ever since KB4471324 W10 can no longer detect the Realtek chip and I guess that Drivepool and Cloud drive were therefore seeing this server as a different/new device from a licencing perspective. As an aside, Emby also crashes - so KB4471324 is looking like the biggest culprit :-)
  5. 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.
  6. 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 course, I can't do that, because the drives contain data. Now, just like DrivePool, PoolHD stores the files in standard NTFS directories - and even gives advice on how to migrate from DrivePool to PoolHD by changing directory names to match the DrivePool naming conventions. Before purchasing DrivePool, I have downloaded a trial and have created a new Pool, but DrivePool will only add physical disks to the DrivePool pool, that have not previously been in a PoolHD pool. i.e. DrivePool doesn't see the two physical disks that were part of a PoolHD pool, even though both the drives effectively only contain a standard NTFS file structure and PoolHD is uninstalled. Remembering that I effectively have two physical drives that contain two top level directories - one which balances the contents of that directory across both drives and the other (the duplicated directory) that has identical content on both drives, how can I add them to a DrivePool pool? [Note: I guess that the secret is in the naming of some directories in the root of each drive, that indicates to DrivePool that it should steer well clear, but these are only directory names, so quite happy to edit them as necessary.] Thanks in advance, Woody.
  • Create New...