Jump to content
Covecube Inc.

Digitoxin

Members
  • Content Count

    9
  • Joined

  • Last visited

  1. It is not. I plugged in several drives. The scanner was not scanning any of them. I was not able to eject any of them until I stopped the scanner service.
  2. Whenever I attach an external hard drive to my server, Stablebit Scanner prevents the ejection of the hard drive. I get the following error in the registry when I attempt to eject the drive. The application \Device\HarddiskVolume8\Program Files (x86)\StableBit\Scanner\Service\Scanner.Service.exe with process id 3116 stopped the removal or ejection for the device USB\VID_174C&PID_55AA\MSFT30123456789202. I have to stop the Stablebit Scanner service, eject the drive, and then restart the service. Update: I tested this with a 5 drive external enclosure which has individual power buttons for each drive. This issue only occurs with the first drive I power up. If I power up drive 1 and then drive 2, Stablebit scanner is only preventing me from ejecting drive 1. I can successfully eject drive 2. If I power up drive 2 first and then drive 1, drive 2 is now the drive locked by Stablebit scanner. Drive 1 can be ejected fine. Same with the other drives in the enclosure. The drive I power up first is the drive that I an unable to eject because of Stablebit scanner. The rest of the drives eject fine.
  3. Yes, I meant Event Viewer. Disk 8 is the Drive Pool drive. It looks like HarddiskVolume22 is a temporary virtual drive created during the backup process and the errors related to that can be ignored. I am concerned about the I/O operation errors though since they only occur when the backup job is running and always occur when the backup job is running.
  4. I am running DrivePool 2.2.3.1019 on Windows Server 2019 Standard and am having the following issue. I have a Windows Server Backup scheduled to run daily. It is only configured to backup the System state, recovery, and Drive C. It is not backing up anything on my DrivePool drive, nor is it backing up to my DrivePool drive. When the backup starts running, I get the following errors in the event log. Disk 8 is my DrivePool drive. This happens every day when the backup starts. Warning 5/22/2020 5:04:58 AM Disk 153 None The IO operation at logical block address 0x21 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:04:58 AM Disk 153 None The IO operation at logical block address 0x11 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:04:58 AM Disk 153 None The IO operation at logical block address 0x1 for Disk 8 (PDO name: \Device\0000003b) was retried. Error 5/22/2020 5:04:29 AM FilterManager 3 None Filter Manager failed to attach to volume '\Device\HarddiskVolume22'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C. Error 5/22/2020 5:04:29 AM FilterManager 3 None Filter Manager failed to attach to volume '\Device\HarddiskVolume22'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C. Warning 5/22/2020 5:00:19 AM Disk 153 None The IO operation at logical block address 0x21 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:19 AM Disk 153 None The IO operation at logical block address 0x11 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:19 AM Disk 153 None The IO operation at logical block address 0x1 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:13 AM Disk 153 None The IO operation at logical block address 0x21 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:13 AM Disk 153 None The IO operation at logical block address 0x11 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:13 AM Disk 153 None The IO operation at logical block address 0x1 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:07 AM Disk 153 None The IO operation at logical block address 0x21 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:07 AM Disk 153 None The IO operation at logical block address 0x11 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:07 AM Disk 153 None The IO operation at logical block address 0x1 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:01 AM Disk 153 None The IO operation at logical block address 0x21 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:01 AM Disk 153 None The IO operation at logical block address 0x11 for Disk 8 (PDO name: \Device\0000003b) was retried. Warning 5/22/2020 5:00:01 AM Disk 153 None The IO operation at logical block address 0x1 for Disk 8 (PDO name: \Device\0000003b) was retried.
  5. I just installed a CT250MX500SSD1 (Same SSD, but the 250 GB version) and am having the same issue.
  6. I just upgraded Drivepool to the latest beta (2.2.0.848). I am now getting the following error when starting the GUI. There was a problem running this application Error report file saved to: C:\ProgramData\StableBit DrivePool\UI\ErrorReports\ErrorReport_2017_09_17-03_12_57.8.saencryptedreport The GUI continues to run after I close the error dialog. I have attached the ErrorReport. Three separate errors were generated back to back. ErrorReports.zip
  7. Normally, Windows sorts files alphabetically when enumerating a directory from the command prompt. I have several tools and batch files I have created over the years to do various batch operations to all the files in a folder. Many of these tools rely on the fact that the operating system enumerates the folders alphabetically. With DrivePool, this is not the case. When enumerating a folder on a DrivePool volume, if the files in that folder span multiple drives, each individual drives files will be sorted alphabetically, but it will start over as it goes from drive to drive. Is this a bug or a limitation of DrivePool?
×
×
  • Create New...