Jump to content
Division-M Community

TobiMan

Members
  • Content Count

    43
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by TobiMan


  1. Hi,

    since updating to Drivebender 3.2.0.0 I get the following error message:

    The Drive Bender server (HORST) has sent the following notification:
    The Pool firewall configuration failed with the following message: [FolderWALL (\\?\Volume{9f7a6270-51fd-416e-bc3d-e72c87b6fcc7}\)] - The folderwall rule(s), where NOT ABLE TO BE READ for rootpath: \\?\Volume{9f7a6270-51fd-416e-bc3d-e72c87b6fcc7}\ (D:\).
    There are no rules running, and all folders are unprotected!
     
    I've never applied any firewall rules, so I'm at a loss here what is causing the error. The drive base protection rule is applied, but that's by default I guess.
     
    Any hints how to solve this matter?
     
    Thanks
    Tobias

  2. On 11/1/2018 at 5:43 PM, TobiMan said:

    Unfortunately yes... accessing folders with greater content [files or subfolders] takes up to 2 minutes for the first time, access after that is faster, but still takes 1 minute or slightly more.

    I stand corrected... obviously DriveBender needs some time to cache the whole shebang. Works pretty cool, thanks  @Anthony. @fattipants2016give it a try!


  3. 19 hours ago, Anthony said:

    You are 100% correct!

    Are you seeing a performance issue?

    Unfortunately yes... accessing folders with greater content [files or subfolders] takes up to 2 minutes for the first time, access after that is faster, but still takes 1 minute or slightly more.


  4. From the BlogThe next feature is one we have called “Drive Idle”… over the years, a common concern with drive pooling is 1) power consumption and 2) drive wear and tear. Every time a pool is accessed, it can require many, if not all drives in the pool to spin up. In fact, this access is often a third-party app indexing the pool as a background task, again, often requiring the entire pool to spin up. Our Drive Idle technology is designed to prevent these spin ups, or, at the very least limit them. This feature should also improve pool performance and responsiveness.

    From my understanding, Drive Idle caches the location of the files and only spins up the necessary HDD for access, so other HDDs in the pool can remain spinned down. From my experiences, this feature still needs some tweaking concidering speed, but we are still in Beta, so no need for worries.


  5. I've realized that, when Drive Idle is enabled, opening a folder with many child folders [about 1.300 in my case] is very time consuming [about 1 minute]. I think that is not the desired behaviour, is there anything that I can do from my side to improve performance?

    Thanks
    Tobi


  6. 17 minutes ago, TobiMan said:

    Same issue here. Starting the service manually results in error 1067: the process was terminated unexpectedly [translated from German, I dont' know the exact error text in English).

    As CBers already suggested, uninstalling and reinstalling resolves the issue. Maybe installing over an existing installation does not work in all cases.


  7. 3 hours ago, CBers said:

    Just installed v3 over the top of v2.7, but on PC restart, the DB service won't start.

    Will uninstall and reinstall and see what happens.

    Same issue here. Starting the service manually results in error 1067: the process was terminated unexpectedly [translated from German, I dont' know the exact error text in English).


  8. 19 hours ago, JonnyManiac said:

    To fix the DLL issue if it has not been updated:

    - Stop any services that might be using the DriveBender volume such as backup software etc.
    - Using the Services management console in Windows Stop the ‘Drive Bender Service’. You might be promoted to Stop other dependent services which will be listed, click Yes and let them cleanly stop.
    - Once the service(s) is/are stopped you can update the DLL.

    Note of caution there are 2 versions of the DLL and Anthony had to determine what version I should use. There’s one in the lib\v5 and one in the lib\v6 directories which I assume relate to your OS version. With WHS2011 mine was the v5 one but this may not be correct for your OS. If you’re not sure - DON’T CHANGE IT!

    - Once you have updated the DLL (noting the above) you can reboot the server. All should then come up at boot and be using the replaced DLL.

    Thanks for sharing, I'll give it a try...!


  9. On 11.9.2017 at 9:21 PM, JonnyManiac said:


    Yep, was already running v2.6 before the upgrade. Given the DLL version in use is 2.5 I suspect that upgrade also didn't update the DLL.

    The version in the C:\Program Files\Division-M\Drive Bender\lib\v5 folder is the 2.7.0.0 version. It should be possible to copy it to the program folder proper without the service running but I don't know if it needs registering or is simply a resource file.

    I've logged a support call so I'll update this post when I hear back from them.

    I ran into the same issue but frankly didn't give it another thought, as Drive Bender is working. However, your're right. The dll version in the programs folder is still the older one. So thanks for pointing this out! If you've got a solution it would be nice if you would share it... :)


  10. Mhh... maybe it's a graphic issue? Some time ago the DB Client crashed upon start, because I adjusted the windows font size to be larger than 100%. Have you made some adjustments like that or are you using some eyecandy software?

     

    You could try starting the DriveBenderConsole.exe, which is on older version of the client, it should be in the same directory. If this works as expected, I would guess it's a graphical issue, be it with the DB Client or with your machine/OS.


  11. Don't know if you were replying to me or just posting your own experience =). But for me the WHS server sees the pool just perfectly and putting it off/online works.

     

    It's the network client I have installed in a Win 10 machine that only sees the drives not in the pool, and the pool itself is missing. Putting the pool offline on the WHS doesn't update the pool state on the Win 10 client.

    The client is running fine on my machine. As you have no problems to connect, it shouldn't be a firewall issue. Frankly I have no idea, sorry...


  12. Release v2.3.5.0 release (2015-06-01)

    The file balancing intervals could be set to a value that was not expected.

    SMART settings for individual drives was not taking effect.

    The SMART service and Windows tray application can use excessive CPU when the host machine comes out of sleep mode.

    Scheduled tasks can fail to load on start-up.

    The core driver is spamming the Windows event log.

    If the pool switches to fault tolerant mode, the duplicate file may not be displayed.

    On some occasions it is not possible to create a network mount point.

    Improved the efficiently of the pool health check.

    Fixed a font issue with the duplication manager.

    Windows 10 support.

×
×
  • Create New...