w3wilkes

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.

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.

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

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??

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

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.

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".

Installed with no problems. Pool came up without issue. Thanks!

In days gone by when I had a similar problem I just deleted everything from the client backup folder and started fresh.

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.

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

I agree on the support ticket, and please post what the answer is.

Problem fixed with info from DB development. I uninstalled 3.6.0.0a and then deleted the pool config from the registry. Then I installed 3.6.5.0 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 3.6.5.0 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 detail so that the issue can be corrected prior to the next release going live.

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.

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 3.6.5.0 on my WHS2011 I've rolled back to 3.6.0.0a which is working fine. And yes, I've opened a ticket