HALP !!! I screwed up again

[Jasper]

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?

 

 

[Christopher (Drashna)]

That's ... odd.

 

Was this disk part of the existing pool previously, or part of a different pool?

 

If it was part of a different pool, then that really is odd, as it should be detected as such and create a secondary pool.

 

Could you grab the logs from the system?

http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Just steps #6-8.

 

After that, try rebooting the system. If that doesn't help, then do this:

http://wiki.covecube.com/StableBit_DrivePool_Q2299585B

[Jasper]

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.

[Christopher (Drashna)]

If that's the case, then it sounds like VDS screwed up somewhere.

If this happens again, could you do this:

http://wiki.covecube.com/StableBit_DrivePool_Service_Memory_Dump

And could you get the error reports from the system?

http://wiki.covecube.com/StableBit_DrivePool_2.x_Error_Reports

 

 

 

But again, this is odd. I switch disks between VMs all the time, and DrivePool works fine on all of them.