Author Topic: Lost configuration and one DRU failure.. how to restore.. getting error 500 etc  (Read 937 times)

Offline markm75

  • Jr. Member
  • **
  • Posts: 66
  • Karma: +0/-0
    • View Profile
So I have 2 parity drives and 5 regular dru's in my system.

I tried at first to restore the db.. this worked except all the drive letters were different so the dru/ppu info was wrong and it wouldnt let me change things (locked).. so i deleted that config and the files on the root of C after stopping the service and started again.

This time following the suggestion here
http://wiki.flexraid.com/2012/03/24/how-do-i-restore-if-i-lose-both-my-os-drive-and-a-data-drive-and-dont-have-backups-of-my-raid-config/

I chose to import configuration and picked one of my two PPU drives  (typed in H:\ also tried H:).. (side note.. seems the files on these drives are dated 6/2016.. not sure why, i guess parity hadnt been saving for some time and i didnt realize it?)..

When I go to restore and click the button i get an error
"error 500 the call failed on the server" and some google site notations after this.. in the log i see things about RPC call failed or similar.

Is this the right procedure to restore things?  (then do the swap drive to get the drive letters changed)..

And then once the pool is back.. how do i then restore the DRU that is dead/vacant (replaced with a new drive)?
Do i follow the instructions here?
http://wiki.flexraid.com/2011/08/23/restoring-a-failed-dru-or-ppu/

Upon restarting i cant even get the login box to appear..

i get
com.google.gwt.user.client.rpc.statuscodeexception

Thanks in advance

« Last Edit: August 06, 2017, 05:08:57 pm by markm75 »

Offline markm75

  • Jr. Member
  • **
  • Posts: 66
  • Karma: +0/-0
    • View Profile
I got it to get the user login again but the restore is still failing.. here are some logs:

[2017-08-06 18:12:09,748] ERROR:
java.lang.RuntimeException
   at com.tchegbe.flexraid.main.a.n.importMeta(Unknown Source)
   at com.tchegbe.flexraid.main.a.n.importExpertMeta(Unknown Source)
   at com.tchegbe.flexraid.main.a.d.create(Unknown Source)
   at com.tchegbe.flexraid.main.a.D.create(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.flexraid.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)
Caused by: java.lang.NullPointerException
   ... 33 more
[2017-08-06 18:12:09,749] WARN : Exception while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.tchegbe.flexraid.client.bean.ActionStatus com.tchegbe.flexraid.client.rpc.RPCService.create(com.tchegbe.flexraid.client.model.AddNewConfigurationModel)' threw an unexpected exception: java.lang.RuntimeException
   at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(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.flexraid.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)
Caused by: java.lang.RuntimeException
   at com.tchegbe.flexraid.main.a.d.create(Unknown Source)
   at com.tchegbe.flexraid.main.a.D.create(Unknown Source)
   ... 29 more
Caused by: java.lang.RuntimeException
   at com.tchegbe.flexraid.main.a.n.importMeta(Unknown Source)
   at com.tchegbe.flexraid.main.a.n.importExpertMeta(Unknown Source)
   ... 31 more
Caused by: java.lang.NullPointerException
   ... 33 more

Offline markm75

  • Jr. Member
  • **
  • Posts: 66
  • Karma: +0/-0
    • View Profile
Another note.. i had a backup of the OS drive back in january, but for some reason the .db file on the root of this drive is dated 2014.. could there be an alternate location for the db file?

Since 2016, guessing.. i have been running build: 2.0 final [2014-08-16]
« Last Edit: August 06, 2017, 05:22:49 pm by markm75 »

Offline markm75

  • Jr. Member
  • **
  • Posts: 66
  • Karma: +0/-0
    • View Profile
At this point, using the 2014 db file.. i was able to get things going.. i still dont understand how in my image of my OS drive, i could not find a newer db file (image made this year), unless i was looking in the wrong place.

This old db was missing a drive in the dru listings.. i added it.. i swapped out drive letters in disk management to make them the same again.. i didnt start the pool (restart needed).. i decided to try to "recover" the DRU that is now a blank new drive, using one of the two parity drive letters in the restore option area..

Its now been 15 hours.. its still at 87% on pre-validation..  I'm not sure if this is normal for it to take this long.. nothing has started restoring yet.. again for some reason my parity drives both have files dated around 6-2016, so i may have lost a years worth of data if so.. because i was unaware the parity info hadnt been updating regularly.


Offline markm75

  • Jr. Member
  • **
  • Posts: 66
  • Karma: +0/-0
    • View Profile
I had completely forgotten about this thread from before.. http://forum.flexraid.com/index.php/topic,48876.0.html    around the same time as the parity data last written date in fact.

I had asked how many parity drives i need to cover all my data.. in doing so someone pointed out that i should have all of the parity drives the same size as the largest dru (so 8TB).. i think this meant that ALL of the parity drives need be 8TB? 

Looking at that thread it seems that I had 3 parity drives.. now i have two after the failure.. so my failed drive was a parity drive (4TB)..  I have added another 8TB as a dru.. looks like I am probably ok to cancel the restore (still unsure if this long duration on pre-validation is normal).. I think i should make the new 8TB the other parity drive if this is the case.