ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

HBA issue.... Error 1026

 
Tom Bruce_1
Advisor

HBA issue.... Error 1026

Hi,

I have a G2 BL20P, 2 QLogic HBA's, 5GB of RAM, No internal disks, blade booting from SAN that I get an error only a certain time during the week. It always happens on Sunday mornings between 1-2 AM. I have seen other threads on this but mine, like I mentioned, is not a constant occurance. Any ideas on what is happening?
Here is the exact error:

The Driver has detected a path failure to Subsystem ID 50001FE15004B670. Dump Data 0 contains the Phys Path Info < Port | Bus | Target | Lun >. Dump Data 1 contains the Driver Status. Dump Data 2 contains the HBA Slot Number (ffffffff if unavailable). Dump Data 3 contains extended Driver Status.

0000: 0f 00 10 00 02 00 60 00 ......`.
0008: 00 00 00 00 02 04 00 c4 .......Ä
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 02 01 00 03 46 4f 44 00 ....FOD.
0030: ff ff ff ff 00 00 00 09 ÿÿÿÿ....

Shortly after this the path comes back.

THanks for any information you can provide.

Tom
4 REPLIES
Peter Godron
Honored Contributor

Re: HBA issue.... Error 1026

Tom,
if it that regular to pinpoint it must be either something scheduled overloading the system or the night cleaner is playing with the cables.
But seriously, check your scheduling system and if ncessary switch up the level of logging on the system.
Peter Godron
Honored Contributor

Re: HBA issue.... Error 1026

Tom,
please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#28
Not for my previouis answer, but in general.

0 points for more than 30 replies !
Tom Bruce_1
Advisor

Re: HBA issue.... Error 1026

There is nothing scheduled for the time frame on that server.... Not sure how much more logging I can turn on...

Any more ideas?

Thanks

Tom
Peter Godron
Honored Contributor

Re: HBA issue.... Error 1026

Tom,
is anything else using these disks in the SAN at that time.
To me it looks as if the SAN is busy at that time and fails to respond within the timeout period. Once the peak is over the disks start responding in time.