Jump to content
Division-M Community
Anthony

Beta v3.0.0.0

Recommended Posts

Release v3.0.0.0 beta (2018-07-21)
[ n ] Added new "Pool Firewall" feature (note disabling the "List" option is currently not available). (DB-216)
[ n ] Added file enumeration cache feature (FEC), this is part of the new "Drive Idle' feature. (DB-218 & DB-220)
[ u ] Empty pools are purged on restart. (DB-202)
[ b ] Improved network share handling, including a number of network share bug fixes. (DB-203)
[ b ] Network nodes being restored after having been removed from a pool. (DB-213)
[ b ] A pool can fail to mount if a network share failed to connect. (DB-214)
[ u ] Some USB based removable drive were not being detected. (DB-215)
[ u ] Improved mount point checks and loading times. (DB-204)
[ u ] Hard limit on log file usage improved. (DB-219)
[ u ] Fixed a number of driver installation issues. (DB-223)
[ b ] Fixed several issues with balancing and landing zone clearing. (DB-217)
[ u ] Improved balancing performance. (DB-217)
[ u ] Thread deadlocking issue resolved, and improved thread marshalling for better performance. (DB-225)
[ b ] Fixed a number of server related bugs.
 
 
There are a number of new features and updates with v3, here are a couple of important tips
- If during testing you experience any odd file system issue (aka folders not refreshing, permission issues etc), first disable "Drive Idle" (under settings/performance), and if the issue persists, try removing any mount point firewall setting you have added.
- We have posted a "How to" on the Pool Firewall, you can access via support at https://support.division-m.com/hc/en-us/articles/360000366936
 
Important - We have had reports of the Drive Bender not starting after an install of the v3 beta. We are investigating this, but in the meantime, if uninstall any previous version of Drive Bender, reboot, then install the v3 beta, the v3 beta starts as expected.

 

Share this post


Link to post
Share on other sites
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).

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

Uninstalling and re-installing worked fine.

I know this is the normal method, but the installer didn't say anything, so assumed (!!) that it would work, it didn't ?

All good now though ?

Share this post


Link to post
Share on other sites

Thanks CBers... The installer will only force an uninstall if the core driver is out of date. v3 is using the same driver as v2.8.x, so I would expect a forced uninstall first.

So that leaves an issue with the installer and the service starting, we'll check it out. In the meantime, I note the issue in the original post.

Share this post


Link to post
Share on other sites

i got this message if I open the drive bender client..

I uninstalled and reinstalled 3.0, but still happen

 

Quote

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei DriveBenderWindowsV2.Controls.PoolContainer.set_PoolId(String value)
   bei DriveBenderWindowsV2.MainForm.tmrLoad_Tick(Object sender, EventArgs e)
   bei System.Windows.Forms.Timer.OnTick(EventArgs e)
   bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3132.0 built by: NET472REL1LAST.
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll.
----------------------------------------
DriveBenderManager
    Assembly-Version: 3.0.0.0.
    Win32-Version: 3.0.0.0.
    CodeBase: file:///C:/Program%20Files/Division-M/Drive%20Bender/DriveBenderManager.exe.
----------------------------------------
System.Windows.Forms
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3151.0 built by: NET472REL1LAST_B.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Drawing
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
DriveBenderCommon
    Assembly-Version: 3.0.0.0.
    Win32-Version: 3.0.0.0.
    CodeBase: file:///C:/Program%20Files/Division-M/Drive%20Bender/DriveBenderCommon.DLL.
----------------------------------------
Telerik.WinControls.UI
    Assembly-Version: 2015.1.331.40.
    Win32-Version: 2015.1.331.40.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Telerik.WinControls.UI/v4.0_2015.1.331.40__5bb2a467cbec794e/Telerik.WinControls.UI.dll.
----------------------------------------
Telerik.WinControls
    Assembly-Version: 2015.1.331.40.
    Win32-Version: 2015.1.331.40.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Telerik.WinControls/v4.0_2015.1.331.40__5bb2a467cbec794e/Telerik.WinControls.dll.
----------------------------------------
System.Configuration
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Core
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3160.0 built by: NET472REL1LAST_C.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Xml
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
TelerikCommon
    Assembly-Version: 2015.1.331.40.
    Win32-Version: 2015.1.331.40.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/TelerikCommon/v4.0_2015.1.331.40__5bb2a467cbec794e/TelerikCommon.dll.
----------------------------------------
Microsoft.GeneratedCode
    Assembly-Version: 1.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
Telerik.WinControls.ChartView
    Assembly-Version: 2015.1.331.40.
    Win32-Version: 2015.1.331.40.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Telerik.WinControls.ChartView/v4.0_2015.1.331.40__5bb2a467cbec794e/Telerik.WinControls.ChartView.dll.
----------------------------------------
RemObjects.SDK
    Assembly-Version: 9.2.103.1311.
    Win32-Version: 9.2.103.1311.
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/RemObjects.SDK/9.2.103.1311__3df3cad1b7aa5098/RemObjects.SDK.dll.
----------------------------------------
mscorlib.resources
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
Accessibility
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll.
----------------------------------------
System.Windows.Forms.resources
    Assembly-Version: 4.0.0.0.
    Win32-Version: 4.7.3056.0 built by: NET472REL1.
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.


 

 

Share this post


Link to post
Share on other sites
On 8/25/2018 at 5:16 AM, Schimi said:

i got this message if I open the drive bender client..

I uninstalled and reinstalled 3.0, but still happen

2

This is an issue that has been addressed in the next update which will be out in the next few days.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

We have had reports of the Drive Bender not starting after an install of the v3 beta.

Actually it switches drive letter on me from D to E and I think for a minute that Drive Bender has not started.

I have version 2.8 installed. I associate with Windows updates when I have thumb drive inserted which is normally my E: drive.

I am on the fast ring of windows 10 updates and have 1809 17746.1000

The fix is simple, just open the DB manager and switch the driver letters.

Hope this helps, TEd

 

Share this post


Link to post
Share on other sites

I was running 2.8.0 before successfully for some time and following a computer crash was unable to get my pool to start (the service would hang on a reboot). I'm on Windows 7 x64 and using FlexRAID transparent RAID to provide parity for my data drives. Uninstalled the software and installed 3.0.0 Beta. When the pool started it didn't retain any of my pooled drives so I had to recreate the pool from scratch (the landing zone was the only drive that was retained, for some reason). I have 21 drives in the pool, plus the landing zone, so this took a bit of time, which was irritating. From there the speed of the pool was extremely slow - clicking through a folder to view its contents took quite a while, and in some cases the pool got out of sync somehow (files would appear in the pool and disappear that existed on the individual disks). Eventually when I did a file system health check the computer ended up crashing again so I restarted. Upon restart the pool again had to be recreated (again, the landing zone shows as the only drive in the pool). I'm in the process of doing this now. Almost halfway done and the pool is noticeably snappier than it was when I had all 22 drives in there, but will see what behavior I get when all the drives are added. Definitely need to have the pool settings retained on computer crash or reboot, though - takes way too long to put the pool back together.

EDIT: Added all drives. For some reason on a few of my 3 TB or 4 TB drives step 7 (updating the pool with folders) takes substantially longer. Folder browsing is faster than it was but still slow. Many files that exist on the individual drives are not present on the pool. One drive has a file that ends in .$DRIVEBENDER but this doesn't show up in the pool. Looks like a copy of an existing file for some reason (duplication is turned off). Not very thrilled with the outcome - there are newer files that are on the drives that are obviously missing from the pool, and who knows how many files that I don't know about that are on the drives and missing from the pool. I don't see any help articles on how to fix this sort of situation.

EDIT 2: Looks like after I added all the drives I had to stop and restart the pool for the files to show up. Most (but annoyingly, not all) of the files did show up after I stopped and restarted the pool. No idea why there are certain files that still refuse to show up. I had previously tried to delete the folders that these files are in but the operation wasn't successful, so maybe that could be a contributing factor? Just seems odd since the files are still there and the folders are on all the drives as far as I can tell.

Share this post


Link to post
Share on other sites

I had 2 pools on my PC, but after offlining the temporary one, both went offline and I couldn't get either back.

I rebooted and tried to recover from the scan disks option, but DB said there were no pools found.

I even uninstalled DBv3 and installed v2. 7, but still nothing.

Currently attempting to recreate from scratch.

Share this post


Link to post
Share on other sites

hi, i've been using DB3 for about a week and unfortunately i'm going to go back to v2. i'm seeing slowness in rendering folders on the pooled drive in windows explorer that i didn't have in the prior version. let me know if i can provide more info

Share this post


Link to post
Share on other sites

Hi all,

Just a quick update on the next beta. We are still trying to nail down an issue with Drive Idle... we believe we have sorted the performance problem, however, there is still an issue with files not displaying on occasions. Problem difficult to sort, as it can take days before it shows up. Anyways... stay tuned!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...