Jump to content
Covecube Inc.

Leaderboard


Popular Content

Showing content with the highest reputation since 08/23/20 in all areas

  1. 1 point
    OK - I found the issue (for me). MS Virus & Threat Protection has prevented Scanner from seeing the drives attached to my HBA. At this point I don't even know if any of the Scanner settings changes, including the one documented above, made any difference. I have seen the impact real-time protection has on even my new, pretty robust pc, and have made a habit of disabling the real-time protection. Windows, inexplicably, occasionally re-enables the feature. The result has been that when I made changes that may have resolved the issue with Scanner seeing SMART data on my drives, Windows has prevented me from seeing the correct result because it had re-enabled the real-time protection without my knowledge.. Anyway, in the image below you can see that Win has blocked the scanner service executable. I have add it, as well as the .native Scanner service, to the list of excluded programs and can confirm it has solved the issue following a reboot of my machine upon which Windows automatically re-enables real-time virus protection. I am now seeing all information on the drives on the HBA as I should. For the record my system is currently: OS Name Microsoft Windows 10 Pro Version 10.0.19041 Build 19041 Thanks to Spider99 for hanging in with me!
  2. 1 point
    hammerit

    WSL 2 support

    I tried to access my drivepool drive via WSL 2 and got this. Any solution? I'm using 2.3.0.1124 BETA. ➜ fludi cd /mnt/g ➜ g ls ls: reading directory '.': Input/output error Related thread: https://community.covecube.com/index.php?/topic/5207-wsl2-support-for-drive-mounting/#comment-31212
  3. 1 point
    Umfriend

    eXtreme bottlenecks

    Have you checked Event Viewer and what model is thus exactly? And if the data you want in the Pool is already on the disks you want to add to the Pool, then there is a much faster way of getting them in the Pool.
  4. 1 point
    Shane

    eXtreme bottlenecks

    In my experience Resource Monitor's reporting of read and write rates can lag behind what's actually happening, making it look like it's transferring more files at any given point than it really is - but that transfer graph is definitely a sign of hitting some kind of bottleneck. It's the sort of thing I'd expect to see from a large number of small files, a network drive over wireless, or a USB flash drive. Can you tell us more about what version of DrivePool you're using (the latest "stable" release is 2.2.3.1019), what drives are involved (HDD, SSD, other), how they're hooked up (SATA, USB, other) and if you've made any changes to the Manage Pool -> Performance options (default is to have only Read striping and Real-time duplication ticked)? Examining the Performance indicators of DrivePool (to see it, maximise the DrivePool UI and click the right-pointing triangle to the left of the word Performance) and the Performance tab of Task Manager when the bottlenecking is happening might also be useful. Hmm. You might also want to try something other than the built-in Windows copier to see if that helps, e.g. FastCopy ?
  5. 1 point
    Shane

    how to replace failing HDD

    Hi Querl28. There's a few different ways. Simplest is you install the replacement drive, tell DrivePool to add it to the pool and then tell DrivePool to remove the old one from the pool. DP tell you whether it successfully moved all the files on the old drive across (in which case you can then physically remove the old drive) or not (in which case you have to decide what to do about it). If you don't have spare ports to add the new drive before removing the old one, but you have enough free space on your other drives in the pool, then you can tell DP to remove the old drive from the pool before you install the new one. See also this support page on removing drives.
  6. 1 point
    malse

    WSL2 Support for drive mounting

    Hi im using Windows 10 2004 with WSL2. I have 3x drives: C:\ (SSD), E:\ (NVME), D:\ (Drivepool of 2x 4TB HDD) When the drives are mounted on Ubuntu, I can run ls -al and it shows all the files and folders on C and E drives. This is not possible on D When I run ls -al on D, it returns 0 results. But I can cd into the directories in D stragely enough. Is this an issue with drivepool being mounted? Seems like it is the only logical difference (aside from it being mechanical) between the other drives. They are all NTFS.

Announcements

×
×
  • Create New...