Jump to content
Division-M Community

w3wilkes

Administrators
  • Content Count

    1,469
  • Joined

  • Last visited

  • Days Won

    131

w3wilkes last won the day on August 4

w3wilkes had the most liked content!

About w3wilkes

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Utah, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You will need a target drive to receive the data from the pool. The easiest way would be to have DB active so you can access your big "K" drive and then just copy from the big "K" drive to your target location.
  2. My "guess" is that it should be fine to re-label drives. For absolute certainty you can open a support ticket. Don't forget to release your license from the old computer so you can reactivate it on the new computer. https://support.division-m.com/hc/en-us/requests/new
  3. 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/
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. 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??
  9. 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
  10. 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.
  11. 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".
  12. Installed with no problems. Pool came up without issue. Thanks!
  13. In days gone by when I had a similar problem I just deleted everything from the client backup folder and started fresh.
  14. I'm up and running on 3.6.6.0b2. 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 3.6.5.0b1 that this newer release didn't like.
×
×
  • Create New...