Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Our Sites

covecube.com 
community.covecube.com 
blog.covecube.com 
wiki.covecube.com 
bitflock.com 
stablebit.com 

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,

Strange problem: Pool working but not being reported correctly in the dashboard

edited April 2012 in DrivePool
Symptoms v1.0.6008:
  • Virtual pool drive exists in Windows explorer (F:\) is accessible (8.91 TB free of 22.7 TB) and shows as 'unknown" on the Hard Drives tab in the Dashboard
  • Server Folder "Pool" no longer exists and cannot be recreated as a shared Pool folder already exists
  • On the Pool tab no hard drives are shown to be a part of the pool.  When I try to add one to the pool I get an error "Cannot add the same disk to the pool twice"
  • On the "Stablebit Drivepool" tab, it reports Drive Pool is empty and that 6 drives are part of the pool.  Below it reports no folders on the pool.
  • All Data is still there and being shared.  I can access the data from the F:\ drive and from \\SERVER\Pool\ from the WHS and other computers
  • Default server share "Recorded TV"  I had moved to the pool is listed as missing. Can't re-add it because it reports that it already exists.
I have uninstalled Drivepool and re-installed with no changes to the symptoms above. 

I have also disabled sharing of the Pool and Recorded TV folders in Windows explorer which then allowed me to recreate them in the Server Folders tab of dashboard.  Now I can't move their locations back to the pool though as the F:\drive is not available.

Is there a way to recover from this other than copying all this data from the pool to somewhere else and then starting over by deleting the PoolPart folders and recreating the pool entirely?  There just seems to be a disconnect in what drivepool is doing and what it is reporting to the dashboard.  I expect that duplication is no longer working either since it doesn't think there are any folders in the pool.

Comments

  • Resident Guru
    Try the following steps: uninstall DrivePool, reboot, delete C:\ProgramData\StableBitDrivePool and reinstall DrivePool.

    What is it doing after this?
  • I tried your suggestion Shane and it did not have any effect.  I found out what caused this - I think.  I have a 9TB RAID-5 array that is my main storage on my WHS.  I added five 3TB USB HDDs which are what make up the DrivePool. The Raid-5 array is my E:\ drive and hosted all of my Server folders except for the Pool folder. The DrivePool was my F:\ drive. I had filled my Raid-5 and so I moved my Recorded TV folder over to the F:\ drive. None of this was a problem.  With the huge chunk of space now free on the Raid-5 E:\ drive I though I would add it to the pool too.  That's where it broke.  The E:\ drive added to the pool with no issue and the space reported was correct but after the next system restart is when all the symptoms occurred.  I ended up killing the stablebit service, renaming the Pool.Part folder on my E:\ drive manually (noting the name in case I needed to restore it) and rebooting.  When it came back up the pool was all back to only the five USB drives and everything was reporting normally.  This is how I am leaving it.

    I think I went wrong by adding a drive to the pool that hosted my shared server folders instead of moving the server folders to the Pool first then adding the drive.  I believe I read something about this in the forum somewhere but it slipped my mind.  Anyway, I am back up for now.
  • Resident Guru
    Ah. There's no problem with having a drive both host shared folders directly and be in the pool (I'm using that facility myself).

    I suspect the problem is an incompatibility between DrivePool and your machine's RAID-5 implementation.
Sign In or Register to comment.