Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

About dutchguy

  • Rank

Profile Information

  • Gender
    Not Telling
  1. I finally got it working after a lot of reinstalls. After completely removing 2.3.8 and then installing 2.3.9, it works fine now. Probably an upgrade problem?
  2. I just tried this version, but it does not work correctly: when I start up, my mount point cannot be created. In the event viewer, there are a lot of errors for vhyperdrive5: Log Name: Application Source: VHyperDrive5 Date: 18-8-2015 14:33:52 Event ID: 1 Task Category: None Level: Error Keywords: Classic User: N/A Computer: I7 Description: 2 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="VHyperDrive5" /> <EventID Qualifiers="0">1</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-08-18T12:33:52.000000000Z" /> <EventRecordID>2024</EventRecordID> <Channel>Application</Channel> <Computer>I7</Computer> <Security /> </System> <EventData> <Data>2</Data> <Binary>880300004665622020362032303135002E2E5C756D6F64655C636266736170695C636266736170692E6300</Binary> </EventData> </Event>
  3. I also have 16000 of these files in my folder (all have a date of yesterday and all were created in 2 minutes)
  4. You can just download it from this website: http://files.division-m.com/DriveBender%20v2040.exe
  5. It seems to me that DB would work fine for you. Now you always have to balance all the stuff you have on drives, with DB you don't have to do this anymore. Also if you want to backup stuff it is much easier since you only have one drive letter to refer to. I have two machines with DB, my main machine with 3x3TB drives and another (old) machine with a bunch of old drives. I have only one driver letter for both machines, so I can easily backup from my main machine to my other machine. Before it took ages to determine what stuff to put on what drives and also how to backup from one machine to the other.
  6. I just upgraded yesterday from Windows 8 RTM to Windows 8.1 RTM, DB kept on working fine.
  7. I'm using 2 PC's, both with a DB pool. One is my normal PC, the other one is a backup. The backup uses a few Green drives, but still I get speeds of around 80-90 MBps over the network (from one DB pool to the other pool).
  8. On the greens, the load cycle issue can be prevented by running wdidle3. Not sure about the Reds though. First hit on Google: http://www.anandtech.com/show/6157/western-digital-red-review-are-nasoptimized-hdds-worth-the-premium/2 Short: head parking is default disabled on Red drives.
  9. I really don't think there are any restrictions, I wouldn't worry about that. I'm using 3 WD red drives here and they are running fine.
  10. That's why I wrote that I have no duplication. Maybe it's Windows buffering?
  11. They are internal, so using SATA.
  12. I have 4 3TB disks (WD RED) in a DB pool (no duplication). I was wondering how it is possible I'm getting transfer speeds of 250MB/s when copying large MKV files? I think the drives never reach more than about 130-180MB/s?
  13. I already took this into account: 3 drives x 1.5 seconds = 4.5 seconds. Drivebender (3 drives) = 10 seconds. Besides, the process could take much shorter since the 3 drives could be accessed in parallel.
  14. Yes, I was using the latest version. If I get the properties of my mounts on c:\, I get the filecount (of 3 mounts) within 1 or 2 seconds, so about 3 to 6 seconds in total. If I get the properties of the drivebender drive, it takes about 10 seconds. This is only the first time, if I repeat the same, the mounts seem to be cached, so they are almost instantly, whereas the drivebender drive stays stable at 10 seconds (around 55000 files). Also when using a backup tool which has to read a drivebender drive over the network, scanning the directory structure takes a lot longer than it took on the bare drives.
  15. I also notice that scanning a mount point takes (a lot) longer than on a bare drive.
  • Create New...