Unsolved

This post is more than 5 years old

3 Posts

15377

June 21st, 2007 05:00

PowerPath 5.0 on W2k3 - Unable to remove dead paths

I have a few Windows 2003 hosts connected to a Clariion CX-3 via iSCSI. There are some dead paths which I cannot remove. When I remove then through powermt, no error messages are shown but the paths are still there. When I remove them through PowerPath Admin I get a pop up message "Could not complete the requested operation", and a Windows Event Viewer message "EMC Power Path Error: EMCPowerPathAdmin could not remove path xxxx from the current configuration due to:"
Power Path Admin shows the disk number of this failed path as "Dev ???".

Any ideas?

2 Intern

 • 

131 Posts

June 21st, 2007 06:00

Rather than "powermt remove", try "powermt check", or "powermt check force" if that doesn't work.

3 Posts

June 21st, 2007 21:00

I have tried powermt check, remove and check force with the same results.

Even rebooting the production server does not help, the dead paths are still there.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 1st, 2007 07:00

search your system disk for powermt.custom ..rename it to something else and try running powermt check ..if that still does not remove it, reboot.

3 Posts

July 2nd, 2007 21:00

Thanks dynamox, but that did not work either. I found the powermt.custom file in C:\WINDOWS\system32\drivers\etc, renamed it and reran "powermt check dev=all". Same results. The path will not diappear.

I have rebooted and the path still comes back.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 3rd, 2007 10:00

hmm ..that's weird ..my last resort would be to re-install powerpath.

1 Rookie

 • 

74 Posts

November 18th, 2007 18:00

I have exactly the same problem. Am using version 4.6 though.
I don't even seem to have a powermt.custom file. Why would this be?

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

November 19th, 2007 12:00

powermt.custom file gets created whenever you run powermt save ..for example if you made setting changes within powerpath and want to save them..you would run powermt save. I have seen instances where i made changes on the storage side and i just could not force powerpath to reconfigure itself, so i was uninstall powerpath, re-install it ..and dead paths would not go away. So now if i cannot get powerpath to recognize changes elegantly (powermt config, powermt check ..etc) , i uninstall powerpath, remove powermt.custom and then reboot the system. Make sure to save the license key, i have had mixed luck where sometimes uninstall will remove the license key as well.

1 Rookie

 • 

74 Posts

November 19th, 2007 12:00

Uninstalled and upgraded to v5.1 and it seems to be fixed.
Thanks for the information :-)
No Events found!

Top