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,

StableBit DrivePool Service not running when server is rebooted.

edited March 2011 in DrivePool
dunno what happened but everytime i restart the server, the StableBit DrivePool Service  does not start. i checked through services.msc and i see that it set at AUTOMATIC and i have been manually starting it a couple of times already (every time i reboot_) 
whats happening? 
IS DRIVEPOOL nearing RTM as well?

sorry this is a repost.. posted on the wrong forum

Comments

  • Covecube
    There have been a number of reports of the service shutting down. Open a case @ stablebit.com/Contact so that we can troubleshot this. I'd like to see the event log, error reports, etc..

    DrivePool 1.0 will be released when it's feature complete. Here's a list of things left to do http://forum.covecube.com/discussion/13/features-from-drivepool-not-in-current-beta/.

    DrivePool will also have to be rock solid in terms of stability, so that's the immediate priority. I make no promises in terms of release dates because programming is inherently unpredictable. It will be released when it's ready in terms of the planned features and stability.

    However, I think we're looking at release in a few months. Right now it's bug fixes only, but development with ratchet up to full speed within days.
  • There have been a number of reports of the service shutting down. Open a case @ stablebit.com/Contact so that we can troubleshot this. I'd like to see the event log, error reports, etc..

    where do i find the log file? will send it as soon as i experience the same problem again.

    DrivePool 1.0 will be released when it's feature complete. Here's a list of things left to do http://forum.covecube.com/discussion/13/features-from-drivepool-not-in-current-beta/.

    DrivePool will also have to be rock solid in terms of stability, so that's the immediate priority. I make no promises in terms of release dates because programming is inherently unpredictable. It will be released when it's ready in terms of the planned features and stability.

    this i strongly agree! and how it should be. nothing less.

    However, I think we're looking at release in a few months. Right now it's bug fixes only, but development with ratchet up to full speed within days.

    take your time and more power to your team.
  • Covecube
    Go to http://stablebit.com/Contact and submit a message. This will open up a support case. I will instruct you on what to do there.
  • you are using vmware or hyper-v?
  • im using it LIVE on a DQ4CB intel board.
  • Covecube
    FYI, build 590 fixes a mount issue on reboot. Not sure this is what you were seeing. It's out now.
  • so i thought but still having same issues and worse. now, even after i deleted the files from C:\ProgramData\StableBitDrivePool\Service\Store and stop and restart stablebit service, i still do not see any of my hard drives for pooling, although after i restart the service i see that the files at C:\ProgramData\StableBitDrivePool\Service\Store re-appear.
    ive tried un-installing and re-insalling as well.. guess uninstalling and re-installing again wont hurt.
  • sorry way too early in the morning and i do not know what im doing... messed up my msgs... 
  • Covecube
    You may want to try stopping the service and checking the mount location @ C:\ServerPool\ServerFolders\ to make sure it's empty. You might have some files there.

    I don't think re-installing will help and deleting the Store folder will probably not help as well.

    It's tough to know what's going on without seeing the error reports.
  • everything was fine and dandy for a bit until i upgraded to new version and realized my pooled folders are gone. i did not see any error logs either.
  • turns out the service was not running again...
  • Covecube
    bapski,

    When you upgraded, did you reboot after uninstalling the old version?

    This time, did the service stop running right after a reboot, or right after you upgraded?
  • Covecube
    I've restarted a local test machine here with build 687 10 times and verified that the service starts up normally every time and that the pooled shares are visible. One thing I noticed is that the regular shares appear first then 10 seconds later the pooled shares show up, as the DrivePool service is started.
  • I have the same problem, reboot server and sb service is not running. I am on sb 718, WHS RTM and it's a new install, no previous version on this WHS.
  • edited April 2011 Resident Guru
    rmassey, anything else installed on the server besides DrivePool build 718?

    what happens if you downgrade to an earlier version (e.g. 652) then upgrade back to 718 - does the problem go away if and/or after a particular earlier version is installed?

    I have a clean WHS RC with DP 652 upgraded to 687, 692, then 718 and the DP service has always started (so far); will have to see what happens once I start over with the WHS RTM.
  • >>anything else installed on the server besides DrivePool build 718? 
    no previous versions of SB.  I have drive info and Advanced Admin Add-ins installed. 

    >>what happens if you downgrade to an earlier version (e.g. 652) then upgrade back to 718 
    Sorry, but not worth the trouble IMO, I'll just go start the service


  • Covecube
    The service is on a 30 second timeout and it appears that some servers are very busy during boot time and the service is timing out.

    Asynchronous service starting will be added, but for now you may want to set the service start type to Automatic (Delayed start) as a workaround.
  • Resident Guru
    Bumping this as have noticed this problem has returned since upgrading from 1584 to 1648; still occurring after upgrading to latest build 1671.

    Alex's advice to set the "Stablebit DrivePool Service" service start type to Automatic (Delayed Start) fixes it as before.
  • Covecube
    Shane,

    This should not be happening in M2.

    When this happens please submit logs:



    You don't need to flip the log switch, when you notice that the service is not running, just zip up the logs and upload them.

    Thanks,
Sign In or Register to comment.