Jump to content
Division-M Community

All Activity

This stream auto-updates     

  1. Earlier
  2. 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/new
  3. Here is what I'd do. 1. Install the new drive (say N:) and create a temporary folder at the root (e.g. n:\drv_copy). 2. copy the contents of the small drive's pool folder into the n:\drv_copy folder. Verify an accurate copy (I'd use something that could compare file hashes) 3. stop the drive bender service. 4. note the name of the small drive's pool folder and rename n:\drv_copy to that name. 5. shut down and remove the small drive. 6. when you restart, drive bender should see the new drive as the old drive in the pool.
  4. If your pool has enough space, then you can remove a drive and DriveBender will move all of the files off of it to the other drives in the pool. If you adding new drives to increase the pool size, then I assume you don't have the space to do that, in which case the only option is to swap the drive out. You could force remove the drive, as though it had died, add the new drive to the pool, then once you had sanitised the old drive, copy the contents of that drive back to the pool.
  5. Hi all, I have a pool with 5 drives in it that I use for backup purposes. I want to swap out two of these drives with larger drives. But I remember that last time I swapped a drive using the Drive Bender "swap drive" function, it basically moved (not copied) everything from the old drive to the new one. So at the end of the process I was left with the new drive as part of the pool, and the old drive as an empty drive. Is there a way to change this functionality so that it copies (not moves) everything from the old drive to the new? There's nothing wrong with the old drives, I'm just upgrading them for capacity reasons, so if I can keep everything on them and just store them in a closet as a disaster backup, I'd prefer to do that.
  6. On a clean install, once you start DriveBender, It will see the disks that you previously had in a pool and ask if you want it recreated. You say YES and it'll do it. Nothing needs copying from an old install. I've done this many times over the years.
  7. Hey so with a clean install did drive bender just re-establish the pool, or did you have to carry over any info from a previous windows install? (I still have access to the old install so I can copy over the mounts folder for instance or the whole Division-M folder. )
  8. yep thanks support helped me: i was able to add the drive back to the pool, and DB was clever enough just to merge the files back
  9. 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.
  10. If it's the boot/system drive you want to clone, there shouldn't be any issues with DB. I've done it a few times through the years, even installing a fresh new OS. DB was able to find and mount my pool drives, no problem.
  11. I need to replace my hard drive with an ssd. Are their any potential issues with DB if I do this?
  12. Cos I don't need to know the answer to this question, anymore...
  13. Update: Had a response to try uninstall DB, re-install, and reboot... try again. To this end, again, no luck. My testing steps and response back below: So, i did try that, a few times while i was on build 20161. It would seem the issue started on build 20150 of Win10 2004. Before build 20150 we were on the MN (Manganese branch) ... now we are on the Iron branch. I also did a fresh install of Win10 ... build 20150, did all updates and drivers... installed DB... rebooted... DB came up fine, shut down, attached all my drives, powered up, DB found the pool, and started to remount... after an hour, nothing was going on. Rebooted again, and the DB service was stuck in starting mode... Win10 was extremely sluggish, explorer.exe kept crashing. Deleted the pool, and rebooted. DB service was fine again. Attached a USB SSD, tried to build a fresh new pool, and again, nothing happened. Trying anything in DB, would come up with a note of attempting mount point. Uninstalled DB, rebooted... updated Win10 to build 20161.. performed the same steps as above.. no luck again. Pulled out the SSD, and put my old SSD back with build 19635... all works as expected again. I installed DB on my normal daily PC, that is also running 20161. DB if fine until i try create a pool. Created a new pool, added a mount point, it remained on Creating Mount Point 0% for about 10 minutes... didnt progress. Cancelled the operation, and added a single blank SSD, which said completed. No new drive appeared in windows explorer (H:) Rebooted my pc, and system was basically unusable... explorer.exe kept crashing, i eventually got services up, and DB service was stuck starting. Tried net stop drivebender, service unresponsive due to starting or stopping. Eventually, managed to get to explorer, and grabbed the log files and attached them. Going to uninstall DB now... and await your response Have you tested on build 20161 or any Iron Branch Windows 20 2004??
  14. I have had a reply back from support, and have provided log files. Will let you know of the outcome! Cheers
  15. Keep us up to date with what the support team reply with please.
  16. Update - So, i decided to try StableBit Drive Pool on another pc with windows 10 (Iron Branch build 20161)... and that also doesn't work. Reading their forums, same issues with newer Iron Branch builds...... guess we will have to wait until a new DB version comes along, or MSFT fixes it! Another post on even Storage Spaces broken : https://mspoweruser.com/the-windows-10-may-2020-update-may-be-causing-major-hard-drive-management-issues/
  17. Just curious if anyone else has had this issue? Updated to Windows 10 build 20161, the pool wouldnt mount, DB service is stuck on starting... so i yanked my ssd out, put a spare ssd in installed a fresh build of Win10... installed DB, attached my drives, and it found a previous pool, offered to bring it online... i said ok. Nothing happened... Rebooted, and the DB service was stuck again. Deleted the mount point, and tried to create a new one. The DB service is running fine, but the Add mount point task is stuck on 0%... nothing happening. I have raised a ticket for this, but just wondering if anyone else has had this.. or knows how i can get my pool back.... this has happened to the last 2 builds of Win 10 insider... Worst case, i install the old ssd, and revert to previous build of Win10 that still worked. Edit: It must be an issue with the Iron Branch of Win10 then. old SSD has Manganese on it, build 19635 ... that works 100% fine. as soon as i hit the Iron branch... dead.
  18. You'll need to switch on advanced I/O logging for this particular case and then email the logs. All the details should be here: https://support.division-m.com/hc/en-us/articles/333757012755 Have you got an open support ticket? I expect you'll need one if not. To prepare you, these are the questions that were asked of me: What sort of file sizes are we talking about? Do you have enough free space on a/each drive(s) in the pool? Are you able to replicate this easily? How many drives do you have in the pool, and what is the free space on these drives?
  19. I can do that. How do I go about sharing them?
  20. 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.
  21. any update on this issue or anything that has helped fix it setting wise either in drivebender or the torrent client?
  22. 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.
  23. no I mean I physically disconnected to the drive, then repaired the pool. (I assume this removes all the files that are on that drive from the pool). I know I could copy the files from the drive back to the pool but it'll take nearly 2 days (8tb). If I can add it back, and DB will know that the files that exist in the pool folder structure on that drive should be re-inserted into the folder structure in the pool. My guess is that if I add the drive back and include the existing drive files the pool will then contain a new directory called "{815D69EA-ECD0-4339-9A0E-2BEE6AA2C0B9}" containing the files in the folder structure of the pool drive. .
  24. Just wanted to report back. I got help from someone over at the Snapraid forums. One of the users pointed me to this article to mount the drives into a folder. Then, I enabled the setting within Drive Bender for snapraid and everything worked great from there! https://docs.microsoft.com/en-us/windows-server/storage/disk-management/assign-a-mount-point-folder-path-to-a-drive
  25. 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
  1. Load more activity
  • Create New...