denywinarto

Whew, i don't know which one actually fixed it, but it suddenly showed up on my pool!
I did everything above until the poolpart.guid cannot be renamed, so i tried putting the drive offline and online DP said one of the disk is missing, thats when i noticed it's back on the pool. Many thanks Shane saved me from massive headache of copying 20tb files!
I almost reinstalled DP as well, i was too focused on finding the missing drive on the non-pooled Iist I didn't notice it's back on the pool
 

Try running the following in a command prompt run as administrator:
dpcmd refresh-all-poolparts And where poolpartPath is the full path of the poolpart folder of the missing drive:
dpcmd unignore-poolpart poolPartPath for example, dpcmd unignore-poolpart e:\poolpart.abcdefgh-abcd-abcd-abcd-abcdefgh1234 And where volumeid is that of the "missing" drive (you can use the command 'mountvol' to get a list of your volume identifiers):
dpcmd hint-poolpart volumeid for example, dpcmd hint-poolpart \\?\Volume{abcdefgh-abcd-abcd-abcd-abcdefgh1234}\ while poolparts and volumes happen to use the same format for their identifying string they are different objects If that doesn't help, you may try one or more of the following, in no particular order of preference:
repairing DrivePool (windows control panel, programs and features, select StableBit DrivePool, select Change, select Repair) uninstalling, rebooting and reinstalling DrivePool (may lose configuration but not duplication or content, and keep your license key handy just in case) resetting the pool (losing balancing/placement configuration, but not duplication or content):  Open up StableBit DrivePool's UI. Click on the "Gear" icon in the top, right-hand corner. Open the "Troubleshooting" menu, and select "Reset all settings..." Click on the "Reset" button. Alternatively, you may try manually reseeding the "missing" drive:
if - and only if - you already had and have real-time duplication enabled for the entire pool and you just want to get going again ASAP: remove the "missing" drive from DrivePool quick format it (just make sure it's the right drive that you're formatting!!!) re-add the "missing" drive, let drivepool handle re-propagating everything from your other drives in the background. otherwise: open the "missing" drive in Windows File Explorer (or other explorer of your choice) find the hidden poolpart.guid folder in the "missing" drive rename it from poolpart.guid to oldpart.guid (don't change the guid) remove the "missing" drive from DrivePool if the "missing" drive is now available to add again, proceed to: re-add the "missing" drive move all your folders and files (but not $recycle.bin, system volume information or .covefs) from the old oldpart.guid folder to the new poolpart.guid folder that's just been created tell the pool to re-measure once assured everything is showing up in the pool, you can delete the oldpart.guid folder. else if the "missing" drive is still not available to add again, proceed to: copy your folders and files (but not $recycle.bin, system volume information or .covefs) from the old oldpart.guid folder to the pool drive duplicates of your folders/files may exist on the pool, so let it merge existing folders but skip existing files you may need to add a fresh disk to the pool if you don't have enough space on the remaining disks in the pool check that everything is showing up in the pool if all looks good, quick format the "missing" drive and it should then show up as available to be re-added.

Yes, that's the pool drive letter. So if the hidden poolpart folder in the root of your bad drive is named "PoolPart.654e1b5c-05b8-44a2-8b6b-a0251f2ec7d6" then the command you would use to tag that particular poolpart to be ignored would be:
dpcmd ignore-poolpart n: PoolPart.654e1b5c-05b8-44a2-8b6b-a0251f2ec7d6

1. Manually move all files to the outside of the poolpart.xxx folder on the bad disk so that drivepool can't see them any more.
2. Remove the old disk from DrivePool (it will be instantly complete since the poolpart folder is empty).
3. Insert new disk (new different PoolPart.xxx is created).
4. Manually copy the files from the old disk to the new poolpart folder on the new disk.
I found out by doing this i didn't get BSOD compared to moving the disk using DP
Above is why i think the BSOD is related to drivepool, what i'm worried about if one my drives go bad then it would just throw random BSOD and screw up my OS

I pass through the HBA for Drivepool. I use Dell Perc H310 cards and the SMART data is all visible, as it should be because my Windows VM has direct access to the HBA.
 
edit: Wrong Chris I know, but hopefully helpful?  

Yeah i just figured it out myself, it didn't work even with registry imported,
This might take some time if i fill up all 60 drives someday..

Ah.  Mount point's don't really matter.  To DrivePool, or Windows really. 
So unless you're intending to mount the drive on the pool's path, there should be no issue. 

Only one?
 
That said, you want the "Drive Space Equalizer" balancer plugin.  That does what your expecting.
https://stablebit.com/DrivePool/Plugins
The "Volume Equalizer" only worries about data on the same disk, but different volumes/partitions.
 

Thanks for testing it Chris, managed to solve it with this 
 
http://fixmyitsystem.com/2013/12/QOS01.html?m=1
 
Looking forward for the new version then

So i can assume my problem will be fixed next version?
Also i have another question... does drivepool override smbbandwidthlimit?
I set the bandwidthlimit on win serv to 10MBps.. but copying from the share still gives me 30MBps

I have ubuntu server and i plan to install windows server 2012 on separate ssd using the same motherboard
Whats the fastest way to do this if i want to minimize downtime?
I plan to convert them all to NTFS first because ubuntu can still read NTFS..
Can drivepool read the result after that?

From an elevated command prompt, run this: 
netsh int tcp set global autotuninglevel=highlyrestricted This should help with the weird delay/lag issue. 
 
If not, then try this: 
http://wiki.covecube.com/StableBit_DrivePool_Q7420208
 
 
 
 
Server is using Server 2012R2, right? (signature says so).
 
If so, I think there is some weird combination going on here causing this issue.  
I've seen it myself.  Though, I can get it to occur on a non-pooled drive occasionally, so I dismissed it as network issues (which I've had on and off). 
 
However, there is an active ticket for this, because you're not the only one seeing it (I mean unless it's your ticket). 

Ok.. in progress now.. will post if there's any problem.. thanks for the input guys!

close but i would format in the latest version of windows you have or the windows dp box first
 
reading and formatting on another os might be fine but windows may or may not like it - why take the risk with your data - especially after waiting hours for a copy to finish to find - oops!