Jump to content

phhowe17

Members
  • Posts

    40
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by phhowe17

  1. 13 hours ago, Umfriend said:

    Assuming there is no duplication, wouldn't a single 2TB SSD suffice as a cache? Way simpler for a somewhat specific use case IMHO.

    Perhaps, I'm not sure that wouldn't be limited by my bus, I don't have an M.2 slot in this system.  I think I'll try some small SATA ssds and see if I have enough to do RAID 5 and have Drivepool use them as cache.  Otherwise I'll take Shane's suggestion and split up some of my existing HD into 500GB + remainder and mark the 500GB segments as "SSD"

    Most of the drive are on a LSI 9xxx-8i so are sharing that one controller.  Maybe adding another controller would help.

  2. I am using a file sync tool that can run multiple file copies at one time.  The problem I'm having is that DrivePool is picking the same physical disk for all four file write streams.  I have 10gb network cards between a server and it's backup and with parallel file copies to a single drive limits performance.

    The pool is generally will balanced before the copies start.  Using an SSD cache is not really a solution as often the total volume would exceed 500GB.

    Is there a way to force DrivePool to spread file operations across multiple disks?

  3. After some digging, it looks like searching the logs in C:\ProgramData\StableBit DrivePool\Service\Logs\Service for Error moving" will find the file names.

     

    C:\ProgramData\StableBit DrivePool\Service\Logs\Service>find /i "Error moving" *.log

    13:20:41.2: Warning: 0 : [RemoveDriveFromPool] Error moving file from \\?\Volume{d92a9186-3303-4a0c-a481-ea38c7619713}\PoolPart.9c1fe6e2-37d0-4425-88c8-9fe5e99b8512\DL\somefile.txt to \\?\GLOBALROOT\Device\HarddiskVolume29\DL\somefile.txt. Continuing removal. (Data error (cyclic redundancy check))

     

    At the end of the drive removal you will also get a notice that the drive could not be removed due to files in use.

     

  4. I'm removing a drive that reported some uncorrectable errors.  I have the live GUI service log  displayed with drive removal logging "warnings" and am seeing:

    13:20:41.2: Warning: 0 : [RemoveDriveFromPool] Error moving file from \\?\Volume{d92a9186-3303-4a0c-a481-ea38c7619713}\PoolPart.9c1fe6e2-37d0-4425-88c8-9fe5e99b8512\DL\folder...\file.txt to \\?\GLOBALROOT\Device\HarddiskVolume29\DL\folder...\file.txt. Continuing removal. (Data error (cyclic redundancy check))

    1. Was the file migrated off the drive or left behind?

    2. How do I get a listing of files not moved?

  5. Sometimes when I drag a single file between two folders on the same pool, windows does a copy instead of a move.  Watching the DrivePool console shows that the file is being read and written to the same physical disk. This is also confirmed in task manager. (I have a new mostly empty disk in the pool).  Drag tool tip says "copy" and the progress dialog says coping 1 item. The original file remains in the source folder. So far I've only noticed this on files with really long path names e.g. 186 chars +  93 filename = 279 total characters.

    Looks like the windows path-file length limitation.

  6. I too am having this issue on Server 2012 R2. I installed - Security and Quality Rollup updates for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1, RT 8.1 and Server 2012 R2 (KB 4471989) on 12/15.

    Should I uninstall the .NET update or xfer the license. I have a two system license and I'd hate to have my other system loose it's license.

     

     

  7. I have a pool with 8 drives. I frequently am unzipping large archives or converting .RAR files to actual folders/files.  When I do this, frequently the output is being written back to the same disk, or just a single disk leaving the other 7 disks idle.  Is there a way to ensure that more than one disk is involved to speed things up?   I considered using a placement rule for .zip and .r0xx files, but that just puts those files on one drive but doesn't assure that the outputs will end up on a different disk.

  8. The Win10 box was an upgrade from Win7Pro.  The lodctr /r command failed saying "Error: Unable to rebuild performance counter setting from system backup store, error code is 2". However the lodctr /e:perfdisk command succeeded and resolved the problem.

     

    Thanks.

  9. I'm trialing the release (2.1.1.561) and current beta (2.2.0.651) versions of DrivePool on Windows 10 Pro.  The Disk Performance chart always reads "No disk activity on the pool" even during long file copies. I was expecting this to show currently active files per the documentation.

     

     

×
×
  • Create New...