Author Topic: Operation Failure. Manage error Code=3 when trying to start pool  (Read 2248 times)

Offline Rand

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
So I just upgraded to u10r2 (from u8r2). I made sure I followed the uninstall directions before installing new version (stopped pool, uninstalled driver, stopped service, uninstalled flexraid, deleted remnant files etc.) After installing new version and rebooting (deleted browser cache for good measure) I tried starting my storage pool and got the following error:



Tried rebooting again, same thing. Tried uninstalling the pool driver and then reinstalling and got the same error. None of the pool settings have changed. Any ideas?



Edit: Just tried uninstalling and reinstalling again. Same problem. This is the log info I have:

Code: [Select]
[2012-10-03 12:27:05,555] INFO : Starting FlexRAID...
[2012-10-03 12:27:05,555] INFO : FlexRAID 2.0u10r2 final [Snapshot 1.4 stable / Storage Pool 1.0 RC / Real-Time 1.0 experimental]
[2012-10-03 12:27:05,556] INFO : Started: October 3, 2012 12:27:05 PM MDT
[2012-10-03 12:27:05,579] INFO : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
[2012-10-03 12:27:05,579] INFO : Quartz Scheduler v.1.8.4 created.
[2012-10-03 12:27:05,579] INFO : Registering Quartz shutdown hook.
[2012-10-03 12:27:05,579] INFO : Using thread monitor-based data access locking (synchronization).
[2012-10-03 12:27:05,609] INFO : Removed 0 Volatile Trigger(s).
[2012-10-03 12:27:05,609] INFO : Removed 0 Volatile Job(s).
[2012-10-03 12:27:05,610] INFO : JobStoreTX initialized.
[2012-10-03 12:27:05,610] INFO : Scheduler meta-data: Quartz Scheduler (v1.8.4) 'flexraid' with instanceId '1'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 3 threads.
  Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreTX' - which supports persistence. and is not clustered.

[2012-10-03 12:27:05,610] INFO : Quartz scheduler 'flexraid' initialized from default resource file in Quartz package: 'quartz.properties'
[2012-10-03 12:27:05,610] INFO : Quartz scheduler version: 1.8.4
[2012-10-03 12:27:05,673] INFO : Freed 0 triggers from 'acquired' / 'blocked' state.
[2012-10-03 12:27:05,674] INFO : Recovering 0 jobs that were in-progress at the time of the last shut-down.
[2012-10-03 12:27:05,674] INFO : Recovery complete.
[2012-10-03 12:27:05,675] INFO : Removed 0 'complete' triggers.
[2012-10-03 12:27:05,675] INFO : Removed 0 stale fired job entries.
[2012-10-03 12:27:05,675] INFO : Scheduler flexraid_$_1 started.
[2012-10-03 12:27:05,677] INFO : jetty-7.x.y-SNAPSHOT
[2012-10-03 12:27:05,681] INFO : started o.e.j.s.ServletContextHandler{/,null}
[2012-10-03 12:27:06,841] INFO : Started SocketConnector@0.0.0.0:8080 STARTING
[2012-10-03 12:27:39,625] WARN : /gwt/rpc
java.lang.RuntimeException: Login exception: unauthenticated user!
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
[2012-10-03 12:28:44,935] ERROR: Manage error! Code=3 Message=The system cannot find the path specified.

java.lang.RuntimeException: Manage error! Code=3 Message=The system cannot find the path specified.

at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)
at java.lang.Void.<unknown>(Unknown Source)



Edit: Tried in other browsers. No luck. Just tried reinstalling without UAC on, and for single user instead of all users. No luck.



Now it won't even let me uninstall because it gives me this error:



grrr...
Okay so I uninstalled using RevoUninstaller, tried reinstalling u8r2 again (which was working fine for me before all this) and now I'm getting the same error code 3 when trying to start the pool.  :'(



Just tried using the old Storage Pool driver. Same problem. For the record, all the drives I'm (was) using in the pool are healthy and seen in the Drive Manager. Running out of ideas, halp.
« Last Edit: October 03, 2012, 03:14:59 pm by Rand »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Operation Failure. Manage error Code=3 when trying to start pool
« Reply #1 on: October 04, 2012, 10:52:42 am »
Usually, a reboot would take care of uninstall issues.
If not:
1. Run
Code: [Select]
net stop "FlexRAID"
net stop "FlexRAID Disk Manager"

sc delete "FlexRAID Disk Manager"
sc delete FlexRAIDD
2. Reboot and delete the installation directory
3. Reboot and install desired release

Offline Rand

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Operation Failure. Manage error Code=3 when trying to start pool
« Reply #2 on: October 07, 2012, 08:27:53 am »
Welp. I tried the above steps to uninstall, reinstalled 10r2, and still got the "Manage Error! Code = 3 etc.." when trying to start the pool. As a last resort, I tried starting from scratch.. as in deleting my configuration and recreating it (including parity, ugh) and when it finally finished initializing I tried starting the pool aaaaaaaaannd STILL got the error. No idea what to try next. So frustrating because this was all working fine on previous version and now neither version will give me a working pool anymore.

Offline jrwalte

  • Newbie
  • *
  • Posts: 43
  • Karma: +0/-0
    • View Profile
Re: Operation Failure. Manage error Code=3 when trying to start pool
« Reply #3 on: October 07, 2012, 10:06:33 am »
You have a restore point from when you remember it working? Absolute worse case is reinstall os

Offline Rand

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Operation Failure. Manage error Code=3 when trying to start pool
« Reply #4 on: October 07, 2012, 10:08:04 am »
Unfortunately not. I'm running my OS on an SSD and opted not to run System Restore.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Operation Failure. Manage error Code=3 when trying to start pool
« Reply #5 on: October 07, 2012, 10:15:20 am »
You need to backtrace and properly uninstall some other software you might have installed in between.
Particularly, if you do/did have Drive Bender installed.

Offline Rand

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Operation Failure. Manage error Code=3 when trying to start pool
« Reply #6 on: October 07, 2012, 11:34:55 am »
Never used Drive Bender. The only other program I installed in the last week was an update for Media Player Classic. I still tried uninstalling other software that I thought might conflict like Hard Disk Sentinel, Google Drive etc (stuff that worked fine with FlexRaid before) but no go. Guess I'll just reformat sometime later this week when I have the time (and this time I'll use System Restore  ;))
« Last Edit: October 07, 2012, 11:51:31 am by Rand »