puulima

Thanks Carlo - makes sense. Did you stop the DrivePool service when copying into the new pool?

Well, I never got around to doing the above back in December...too much work/travel etc. So I'm now going to attempt this. But in thinking about it - since I don't plan to use the "old" DrivePool again on these drives or on the server they're coming from - can I just RENAME the "PoolPartxxx" folder to something generic like "Files" and then once those drives are added to the second server - and added to the DrivePool - then do the file moves? I'm assuming it's ok to rename the old PoolPartxxx folders on the drives being moved into the second server. Thanks!

I am trying to access the data on a drive form my DrivePool. I placed the drive in an external enclosure and fired it up - the drive is recognized by Windows fine and I can see the PoolPartxxxx folder - but when I try to open the folder I get a message: Window Title: "Location is not available" Window text: It lists the PoolPart folder name and then says "is not accessible" - the next line says "The Parameter is incorrect" So I googled and found nothing related to DrivePool with that error - some posts noted to run Chkdsk - but when I do that I get an error "The type of File system is RAW - CHKDSK is not available for RAW drives" So I'm thoroughly confused. Windows is NOT asking me to format or giving any other error - I just can't access the PoolPart folder? Help? I need to rename the PoolPart folder so I can add this drive to a different server and then migrate the data over. I don't want to end up with a second pool on the second server. ------- Update - I decided to connect the external drive to my PC using an eSATA cable (I was using USB) and the problem is gone! I don't understand what the difference is? I've used these external enclosures with DrivePool drives and USB or eSATA before with no issues. The Drive is a 4TB WD NAS variety - but don't think that would make a difference? I can open the PoolPartxxx folder now and get to the share folders/files fine... very odd. Anybody have any ideas why this would have happened with a USB cable?

Gotcha! I understand what you mean now. I had data on the second partition of the main drive (I shouldn't have added it to the pool initially) - so I'm waiting on DrivePool to finish migrating that data over to one of the other drives (the drives I'll be physically moving back to Server #1). Once that migration is done - I'll be moving the drives. I'll report back if any questions but sounds like it should go fairly smoothly. Thanks for the tips.

ok, so since I already have PoolPart folders on these disks - adding them to the original server will create a second pool - so sounds like I should FIRST - move all the data on those drives OUT of the PoolPart folders BEFORE I connect those drives to the original server so that doesn't happen. So technically - those drives become just like the ones used in this posting then? http://wiki.covecube.com/StableBit_DrivePool_Q4142489 Still not clear on your last statements above - I wasn't planning to REMOVE any disks on either server...was just going to move the disks from Server #2 over and add them to the original server pool and move the data into the original pool.

I had found that posting and it sounded like it might be what I need to do. So basically I already have the "PoolPArt" folders on Server #2 - but when I move those drives over to the first server and add them to that pool - DrivePool will create NEW "PoolPart" folders... So to clarify - once I STOP the DrivePool service and delete everything in C:\ProgramData\StableBitDrivePool. I then reboot the server - which should start the service again on the reboot - correct? The instructions in the post say to start the service again...will I need to if I reboot?

Couldn't find this topic in the forums...not sure what to search for? I have an existing Server with 8 x 2TB drives. I want to upgrade to larger drives (3's & 4's) so I setup a secondary server (had one kicking around) and installed 4 new (larger) drives, installed Drive Pool on server #2 and moved a ton of data from server #1 to server #2 - then I removed 2 drives from server #1. So can I pull the two empty/removed drives in server #1 and put in 2 of the new/larger ones from server #2 (with the moved data) and integrate them back into the existing pool on server #1? Of will Drive Pool not recognize them? (forcing me to move the data INTO the initial pool instead?). I'm guessing the Server folders on the drives from server#2 may not be recognized, but if I add them to the pool on server #1 - will it create a NEW set of Server Folders - and I can just move the files from one server pool folder set to the other? Obviously it would be great not to have to move the data across drives again - but I was thinking worse case - I pull the 2 removed drives from server#1 - put 2 new BLANK drives in and move (copy) data back from server #2 - but obviously that will take a lot more time. Thoughts? Thanks for your assistance... ADDED NOTE: Some of the folders on Server #2 are duplicated and some aren't - so wondering how that will impact whatever the best process is to merge these drives (data) into the Server #1 Pool?

Just to confirm - I should uninstall the old version from the Dashboard - then install the new version from windows?

I didn't find anything specifically outlining the best way to go about this. I'm assuming that I should upgrade - sounds like there may be some new features. So is the best way to do this uninstalling completely and re-installing the new version? Specifically - following these instructions? http://wiki.covecube.com/StableBit_DrivePool_Q8964978 Thanks for the advice...