Author Topic: Error: Storage Pool handler initialization failure  (Read 457 times)

Offline meltek

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Error: Storage Pool handler initialization failure
« on: February 18, 2018, 06:17:18 pm »
Hi All,

I recently re-imaged my machine with windows server 2016 and re-installed Flexraid however getting the following error even after recreating my RAID.

I have tried the following
- Running UserMode CMD
- Re-installing FlexRAID
- Changing to fixed instead of removable by typing 'false' in removable property
- Restarted after each step


[2018-02-19 11:20:56,870] TRACE: Completing AutoRegistry options...
[2018-02-19 11:20:56,876] TRACE: Loading View definition...
[2018-02-19 11:20:56,876] INFO : Using Auto-View definition...
[2018-02-19 11:20:56,876] INFO : Building View Handler...
[2018-02-19 11:20:57,074] INFO : Mounting Storage Pool drive...
[2018-02-19 11:21:07,083] WARN : Active Storage Pool initialization failure... aborting!
[2018-02-19 11:21:07,083] ERROR: Storage Pool handler initialization failure!
java.io.IOException: Storage Pool handler initialization failure!
   at com.tchegbe.lib.io.view.g.a.b(Unknown Source)
   at com.tchegbe.lib.io.view.g.a.a(Unknown Source)
   at com.tchegbe.lib.io.a.b.v.a(Unknown Source)
   at com.tchegbe.lib.io.a.f.b(Unknown Source)
   at com.tchegbe.lib.io.a.f.a(Unknown Source)
   at com.tchegbe.flexraid.main.b.J.initStoragePool(Unknown Source)
   at com.tchegbe.flexraid.main.b.A.initStoragePool(Unknown Source)
   at com.google.gwt.user.server.rpc.RPC.<unknown>(Unknown Source)
   at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(Unknown Source)
   at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(Unknown Source)
   at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(Unknown Source)
   at javax.servlet.http.HttpServlet.service(Unknown Source)
   at javax.servlet.http.HttpServlet.service(Unknown Source)
   at org.eclipse.jetty.servlet.ServletHolder.handle(Unknown Source)
   at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Unknown Source)
   at com.tchegbe.lib.gwt.server.servlet.SecurityFilter.doFilter(Unknown Source)
   at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Unknown Source)
   at org.eclipse.jetty.servlet.ServletHandler.doHandle(Unknown Source)
   at org.eclipse.jetty.server.session.SessionHandler.doHandle(Unknown Source)
   at org.eclipse.jetty.server.handler.ContextHandler.doHandle(Unknown Source)
   at org.eclipse.jetty.servlet.ServletHandler.doScope(Unknown Source)
   at org.eclipse.jetty.server.session.SessionHandler.doScope(Unknown Source)
   at org.eclipse.jetty.server.handler.ContextHandler.doScope(Unknown Source)
   at org.eclipse.jetty.server.handler.ScopedHandler.handle(Unknown Source)
   at org.eclipse.jetty.server.handler.HandlerList.handle(Unknown Source)
   at org.eclipse.jetty.server.handler.HandlerWrapper.handle(Unknown Source)
   at org.eclipse.jetty.server.Server.handle(Unknown Source)
   at org.eclipse.jetty.server.HttpConnection.handleRequest(Unknown Source)
   at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(Unknown Source)
   at org.eclipse.jetty.http.HttpParser.parseNext(Unknown Source)
   at org.eclipse.jetty.http.HttpParser.parseAvailable(Unknown Source)
   at org.eclipse.jetty.server.BlockingHttpConnection.handle(Unknown Source)
   at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(Unknown Source)
   at org.eclipse.jetty.util.thread.QueuedThreadPool.<unknown>(Unknown Source)
   at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
[2018-02-19 11:21:07,083] TRACE: Checking and executing after pool start instructions..
[2018-02-19 11:21:07,083] TRACE:    => {"success": false, "status": null, "commandMessages": [{"messageCode": "errorExceptionMessage", "messageData": ["Storage Pool handler initialization failure!"]}], "serverMessages": null}

I am running 2.1 (2017.11.21)