Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by w3wilkes

  1. I would think the @ruralcricket approach should work and leave the contents on the original drive intact. One thing I'd do different is stop the drive bender service before I did the copy to prevent drive bender from possibly altering the contents of the drive being swapped out. And just to mention that if DB has removed your pool drives drive letters you will need to use Diskmgmt.msc to assign drive letters so you can do the copies. You might also want to open a ticket and refer to this thread and ask the developer if this will work. https://support.division-m.com/hc/en-us/requests/
  2. Just did this a couple of weeks ago. I did have to release my license and then re-establish it. Mine was a fresh install rather than a clone. As far as my pool went it made the transition just fine to the newly installed system drive.
  3. If you can't provide the logs the only choice I could see working would be to go to a regular drive and then copy the completed file into your pool.
  4. I thought you meant the drive was disconnected. So the pool did not have copies of the files that were on the disconnected drive (they weren't dup'd) when you did the repair and they were lost in the repair action? Like I said earlier, you can open a support ticket to see if the developer has a trick up his sleeve or you can do the 8TB copy over the next couple of days.
  5. When you say that you repaired the pool did that recover all the files that were on the removed drive? If so I would think you'd want to initialize the drive and add it back empty. If not you should open a ticket and ask for guidance from the developer. https://support.division-m.com/hc/en-us/requests/new
  6. Personal feeling is I've not really seen a performance difference between versions of DB, they're slower than JBOD copies. That being said you can open a support ticket and ask the question about stopping the copy / updating DB / restarting the copy. https://support.division-m.com/hc/en-us/requests/new I'm guessing you really wanted this in the DB section and not the Anvil section??
  7. Most modern systems have no trouble with drives larger than 2TB. On your 2 year ago problem with WHS 2011... MS released a hotfix a couple of years ago to provide support for UEFI / GPT formatted drives. This was never released through the standard Windows Update though and has to be installed manually. I've successfully been backing up and have also done Bare Metal Restores to Win10 PC's from my WHS2011 server. https://support.microsoft.com/en-us/help/2781270
  8. Glad to hear you got it running. I was going to suggest you delete the drive configuration from the registry and reboot. Drive bender will tell you it's rebuilding from drives.
  9. From either the Pool Management tab in WHS Server Folders or Drive Bender Manager after you've added the SSD to the pool click on the "Show detailed information and options for this drive" icon (furthest right from the drive) and in the dialog right under "File Placement" there's a drop down. Select "Landing Zone".
  10. Installed with no problems. Pool came up without issue. Thanks!
  11. In days gone by when I had a similar problem I just deleted everything from the client backup folder and started fresh.
  12. I'm up and running on Took a couple of tries. On the first try the pool did not come up and the DB Service failed. I then uninstalled and deleted my pool config from the registry then reinstalled and let the pool be recreated from the drives. This worked, but seems like there was something in the pool config created with the that this newer release didn't like.
  13. My guess is you're right, but to get the definitive answer you should open a ticket. https://support.division-m.com/hc/en-us/requests/new
  14. I agree on the support ticket, and please post what the answer is.
  15. Problem fixed with info from DB development. I uninstalled and then deleted the pool config from the registry. Then I installed and it realized that it had to look at my physical drives because there was no pool info in the registry. DB found my pool drives and asked if I wanted to restore the pool from the found drives. I said yes and the pool was restored successfully. Did one final reboot and all is good. Just remember that is beta and you might encounter problems if you try it. If you try this version and have problems, be sure to open a trouble ticket with all the
  16. What version of DB are you running (this is a good item to put in your forum signature)? I'm not clear on if you've actually had a drive failure or are you just asking how to proceed with the DB4 drive physically removed (which I guess would be viewed by DB as a drive failure)? If you haven't you should probably open a support ticket with as much detail as possible; https://support.division-m.com/hc/en-us/requests/new Hopefully the DB developer can provide direction on how to proceed.
  17. I was not able to install successfully! The DBservice would not stay started. DBManager showed 2 each of my DB drives 1 & 2 and also showed a drive DB3. My old pool had 3 drives labeled DB1, DB2 and DB3. My current pool has only 2 drives labeled DB1 & DB2. After a couple of tries and fails at on my WHS2011 I've rolled back to which is working fine. And yes, I've opened a ticket
  18. I did see the "ghost pool" (your drive X:) once a long time ago and like you I just got rid of it and all was good. Glad it went well for you.
  19. For item 3. You should be able to roll back without a problem, again, release the license from the Win2k19. On the other 2 questions. You should open a ticket and ask about your questions 1 and 2.
  20. Is this your first encounter with Drive Bender? You will find the manual for the product in the software install directory. It describes how to set up a pool. Parity is not a feature of Drive Bender. In a nutshell; Follow the instructions in the manual for adding your drives to the pool (they should be empty / formatted) Once the pool is created the 16 drives should appear as a single drive to File Explorer and the original drive letters should not be there for the native drives anymore. As you create directories on the new drive bender drive you should go into the Drive Bender
  21. Hopefully you've opened a ticket on your problem. https://support.division-m.com/hc/en-us/requests/new I use WHS2011 with drivebender and have my client computer backup folder in the DB pool and it works fine. I will say that I started with the client computer backup folder in the pool so I wonder if the problem might be related to moving the folder after you had been using it on a native drive.
  22. Did the drive fail or are you just upgrading the drive? Have you tried assigning the drive a letter and manually deleting the file. Then you might be able to get back to the DB drive removal process. Seems like there's a force option, but if the only copy of a file is on the drive being forced I think the file would be lost. You should probably open a support request and seek help from the developer. https://support.division-m.com/hc/en-us/requests/new
  23. This is the only report of this that I've seen since You should open a trouble ticket with Drive Bender support. https://support.division-m.com/hc/en-us/requests/new
  24. In your upgrading process did you drain each drive that was to be upgraded before you removed it from the pool? If not, the removed drive would be the same as a drive crash and should be handled that way to recover any primaries on the removed drive. I believe the process is defined in the manual which is located in the directory that you installed Drive Bender in, typically "C:\Program Files\Division-M\Drive Bender". There's also documentation on the Division-M website. https://support.division-m.com/hc/en-us/categories/201693583-Knowledge-Base-Drive-Bender If you need more help I
  25. I think you need to take ownership. Google is your friend, try this search "windows 10 take ownership drive" without quotes.
  • Create New...