Jump to content
Covecube Inc.

Spider99

Members
  • Content Count

    537
  • Joined

  • Last visited

  • Days Won

    38

Spider99 last won the day on January 21

Spider99 had the most liked content!

About Spider99

  • Rank
    Advanced Member
  • Birthday 09/10/1964

Profile Information

  • Gender
    Male
  • Location
    UK

Recent Profile Visitors

809 profile views
  1. wow 56 usb drives looking at the wdf_violation its a "driver" related issue if the sas controller works ok without usb drives and vice versa then its probably a conflict between the drivers which is at fault - difficult to say - could be the usb controllers at fault - as i guess you are using more than one type off the motherboard as they usually come with a couple of different types dont think its that you are over doing it - just getting bitten by a bug - as they work when used separately however - the sas card is the way to go if you can add another with a sas expan
  2. When a NVME drive is being scanned it does not appear on DP dashboard two drives being scanned only one on DP dashboard - i waited a few mins for it to appear
  3. @gtaus remeasure time now less than 30 mins for 45TB of data
  4. the usb controller will be the bottleneck for 7200 rpm drives especially if they are newer models i tend to shuck my usb drives and a couple of WD Blacks i got recently can do 240MB/s plus once they have room to breath
  5. For me a remeasure is about 80-90mins for 45TB with a similar number of disks - the make up of the files on the disk will affect this greatly - lots of small files = slow i recently got rid of 500k of images - which accounted for a lot of the time above - but have not remeasured since with the HDD DP disks connected to a 9211 the speed is mainly affected by the files sizes/number, controller and HDD speed - cpu is only a very minor player in this
  6. Should be fine - i am in the process of moving/removing/replacing disks at the moment and DP does not care which sata port the disk is connected to only difference is that i dont use drive letters but mount points - so windows getting confused about drive letters is not something i see each disk has a unique poolpart - but as windows had a ghost drive which would have appeared with the same poolpart thats prob what caused DP to choke until you rebooted and it did its checks etc
  7. ok - thats a bit clearer will have a play and report back after some testing
  8. I have a new server that now boots considerably quicker than my old server - in just 5 seconds to the windows login screen as a consequence not all of the 20+ HDD i have - get a chance to mount in that time and DP then does a remeasure etc on every boot which i am trying to stop as its a long unnecessary process. So i would like to change the time that DP waits for the volumes to mount but its a bit confusing as there are three different options with "time" values CoveFs_WaitForVolumesOnMount (Default: "True") - Some volumes arrive late in the boot process so DrivePool will wait
  9. Drivepool Column Chooser on higher resolution displays appears off screen and is not accessible works fine on a 1920x1200 display not on a 4k display or 2560 x 1600 It does briefly appear while you resize the window of the bowser but disappears when you stop resizing the window so is not useable
  10. There is a inconsistency between how the disks are named between Scanner and DrivePool I would prefer the DP naming (mount point in this case) to the disk name used by scanner as its much easier to see which disk it is even better allow the user to define which parameter is used for the name of the disk in the dashboard as its easier to have the dashboard up to see "Generally" whats going on across pools etc Thanks
  11. chrome, win 10 and resolution anything above 1920 - happens on multiple machines its a scaling thing as pointed out in other threads
  12. two pc with scanner and dp on - the dashboard only has the combined results from both pc - you cant see them separately for each app - which is needed
  13. DP does not have a cache of files etc it provides the virtual disk to windows and it takes over from there having more memory will improve things to a degree as 8gb is very much on the low side for a server with potentially millions of files in a pool of that size the performance will depend on the cpu used, memory and the speed of the disks used i have a similar setup with 31 disks 7 ssds and 24 HDD and the speed is generally fine my media server (Emby) can scan the disks in a couple of minutes when checking for new additions etc - the initial scan is slow as it has t
  14. anything above 1920x1200 does not work i have two other displays 2560x1600 and 4k - they do not work
×
×
  • Create New...