Jasper

Thanks. After giving it some thought I realized I had had this problem before and you told me to reset all settings. I'm in the process of doing that as I type. Hopefully this will once again fix it. I had to move the pool from the builtin LSI 2008 controller on the Supermicro X8DT6-F to a IBM Megaraid 1015 due to suspected flakiness after a MB swap. The 1015 is the same controller the pool was previously on and everything was perfect. Hopefully I'm back to where I was.

I think what's happening is DP is jumping the gun a little because by the time I open DP, all drives are present and accounted for. Is there a way to get DP to wait a few more seconds before declaring a drive MIA?

The "Missing" drive is nowhere to be found in DP so how can I remove it? Once the computer boots and I go into DP, all is normal, all proper drives are present and accounted for .

There isn't. This started when I temporarily hooked up a drive that was formally part of another pool. Now, every time the computer boots, DP says a drive is missing. How do I undo whatever I did? Thanks

Yep, you're right. Would have saved me a bunch of grief.

HD Sentinel said it was perfect before duplication and after duplication health was down to 26% and it had 101 bad sectors. I have no doubt that had I done a surface scan before dup the errors would have surfaced then. Duplication didn't cause the to fail, the flaws were already there. I almost hate to do a surface scan on a HD for fear of what it will reveal.

Thanks. The drive has been replaced and DP is redupping as I type. The drive that failed was a 5TB White Label drive. I have 2 of these and after this failure I did a surface scan on the other using HD Sentinel and it checked out perfect. So I guess WL drives are hit or miss. Glad to know recovery is as easy as it is.

Disaster has struck. I've just complete putting together a 10.2TB pool. Everything was rosy until Duplication finished this morning. I was shocked to discover that the largest drive in the pool, a 5TB WL drive, was in failure mode. According to HD Sentinel, health was at 26% and it had 101 bad sectors. I'm currently running a read surface scan (non destructive) and it's looking like Swiss cheese. Lots of hard to read sectors and it hasn't even hit the bad ones yet. At this point I don't trust the pool at all. I'd like to zero it out and start over again. Fortunately, all 10.2TB is safely backed up on another server so nothing is lost. So what's the best way to zero out a pool? I want to do a full format on the remaining drives also. Thanks

Thanks. No problem, just curious.

I'm currently duplicating my pool. The total size of the data is 10.2TB. Drivepool numbers are as follows - Duplicated = 13.4 Unduplicated = 3.62 Other = 8.15 Progress = 22.9% Does Drivepool use some sort of Chinese math?

Once again, thank you sir. Explorer is now much cleaner.

Currently they are mounted as drive letters. Can this be changes to folders without data loss? Thanks

Never mind, I found it.

Could someone tell me where the direct to disk setting is? Thanks

Thanks for the clarification.

Just update the BIOS on my SM X8DT6-F and after booting back up DP told me I needed to transfer my license to the "New Machine". I proceeded it transfered normally and I;m back up and running. But it would be nice to know what triggers the anti piracy "features" in DP and other Covercube products. PS - Absolutely nothing changed in this server except the BIOS. I'd also like to add some forum weirdness. I tried to submit this thread and it told me I did not have permission. After backing up it showed me as not logged in even tho I was when I hit the submit button. Something is rotten.

Great. Thanks.

Will it mess thi8ngs up if I do? Thanks

My main system, based on a FX 8350 draws more juice than that, slightly over 300w.

Think I'll leave BI where it's at. The new server pulls almost 300w when running and it doesn't have all the HDs in it yet so I think I'll run it on an as needed basis. the BI server has a 25w Athlon 5350 so it's going to be cheaper to operate 24/7.

I rebooted the server and the rest of the drives showed up. I was able to create a new pool. So everything appears to be back to normal. Also, I was having a problem with drives going off line when the server was rebooted. These drives did not correspond to the drives missing from DP. That too seems to have cleared up also. I know one thing, I'll never move a Drivepool drive to another box without reformatting it first. If I had actually wanted to transfer the data over along with the HDs it probably would have turned out just fine but I had already restored the data from a backup. Now I have to transfer 8.5 TB all over again.

I've learned the hard way never to put drives in a computer that were previously part of a pool. Things get real goofy. I removed an above mentioned drive from the pool and then Drivepool was telling me that it was having trouble removing a totally different drive, one I did not tell it to remove. Sensing a serious problem I decided to reformat all the drives and start over from scratch. Well now all the drives that were previously part of the pool legitimately are MIA. DP is not showing a pool as existing and the only drives showing up are the one that were never part of the legit pool (but were members of a defunct pool. (Hope I'm making sense. Anyway, I just want to SET DP back to square one and start all over again. What's the best way to proceed?

Yep, Blue Iris will bog down in a hurry. Right now it's on a dedicated low power server based on a AM1 and it took quite a bit of tweaking to get it running reasonably well. I had to cut the frame rates and update intervals way down just to get BI to fully load. Right now I'm not running the program on the server, just the service and then remoteing in. I'm thinking this new server should be able to handle the load and then some but if I do move BI over I'll have to run it 24/7 and I'm not so sure I want to do this. Decisions decisions.

Thanks to eBay I was able to assemble the following parts for surprisingly little. 1. Supermicro SC846E16-R1200B 24 Bay 4U Chassis with 2x 1200Watt 80plus Gold PSU. 2. Supermicro X8DT6-F Motherboard 3. 2x Intel Xeon x5570 cpu's. 4. 32gb Hynix DDR3 Server Ram (4 x 8gb) 5. Supermicro passive heatsinks (brand new in the box) I loaded Win Server 2012 R2 Datacenter (already had) and installed 17.5TB worth of HD's (already had). More to be added later. Everything I got from eBay could have passed for new and it all works flawlessly. I decided to go with Drivepool versus RAID / SS / other solutions for 2 reasons 1. Worst case senario all I can loose is a what's on the failed HD. The remainder of the pool leaves my data unmolested and accessible in any Windows computer (this is important to me). 2. I've been using it for quite some time now and it's proven to be totally reliable and simple (too simple but very good at what it does). I'll be using this server for the following - 1. Data Storage 2. Media Server 3. Backups. 4. Blue Iris Server Given the expandability of this system, it will probably outlive me. Yes, it's noisy and sucks up the juice but it won't be running 24/7 and it's not located in a people area so neither matters. Excluding the HD's and SW which I already had, The system cost me well under $1000. I'm happy.

Sorry for the lack of info. 1. OS = Windows Server 2012 R2 Datacenter 2. Version = 2.1.1.561 3. It WAS 2.08 TB. I think I know what might have happened. Some of the drives in the pool were previously in another pool that must have been dupped at one time. When I just went back and checked I got a dup mismatch warning with the option to delete older file parts. Dupped files are now down to 1.39mb.