Page 1 of 5

3PAR 7400 controller error

Posted: Sun Feb 02, 2014 3:44 am
by steve_carlose
Hello guys.
I have a error in my 3PAR 7400 node1(controller 1)
it doesn't start and 2 HBA port is blocked.
any idea??? what can I do?
I'm in a bad situation.PLEASE help me guys.

the error code is:
fatal error: code15 , sub-code 0x0 (2). hw_node_hba: slot2
disable FSBC boot watchdog.

fatal error:code127 , sub-code 0xcb105(d1a9)
disable FSBC boot watchdog.

I think in controller 1 the inform OS is locked.

I'm looking forward to your reply.
Regards

Re: 3PAR 7400 controller error

Posted: Sun Feb 02, 2014 1:35 pm
by skumflum
Is the system still available for IO? If it is, then don’t panic and call HP :)

There is probably something wrong with the HBA card in that controller node.

Re: 3PAR 7400 controller error

Posted: Mon Feb 03, 2014 1:51 am
by steve_carlose
thanks for your reply.
I fix this problem but now I have a new problem.unfortunately the inform OS does not boot in the controller(in both of controller)
the log is:
booting from device0 ,AHCI0 invalid boot sector.
fatal error code39, sub-code 0X10 (0).
AHCI0 MBR doesn't have a valid partition table
disable FSBC boot watchdog


what's that?what can I do? anyyyy idea?

Regards

Re: 3PAR 7400 controller error

Posted: Mon Feb 03, 2014 4:20 am
by skumflum
OK, so let me get this right, you fixed the problem and now it will not boot? What exactly did you do?
I will not pretend to know exactly what is going on, I am by no means an expert. If this only were one controller, I would say that something happened to the internal flash drive but since it affects two controller nodes, it is unlikely that the issue is hardware related.

Do you have a valid support agreement with HP? If you do, I would stop touching things immediately and call HP :)

Re: 3PAR 7400 controller error

Posted: Mon Feb 03, 2014 9:09 am
by steve_carlose
Thanks for your reply.
Yes I have two controller and I have this error in both of them :((

Re: 3PAR 7400 controller error

Posted: Mon Feb 03, 2014 2:08 pm
by skumflum
Am I right in guessing that you are not running anything on your 3PAR yet? Otherwise, you would probably just PAID HP to fix this for you.

The story behind this is somewhat fuzzy to me… What did you do to break the inform OS? How did you fix the other problem?

I would guess that the file system on the Internal Drives became corrupted somehow, maybe due to excessive untimely power cycling? The OS maybe needs to be reinstalled but I do not think it is possible without assistance.

Re: 3PAR 7400 controller error

Posted: Mon Feb 03, 2014 4:50 pm
by Josh26
I would second that some more background around what has been done may be more helpful, but I'm confused about the support. You cannot buy these without support, and the earliest 7400's should still be covered by the default agreement.

Re: 3PAR 7400 controller error

Posted: Mon Feb 03, 2014 5:11 pm
by Cleanur
Agreed you cannot purchase a 7400 legitimately without support and the absolute minimum warranty is 3 years, so call HP with the serial number and if needed they will perform a node rescue and get you back up and running. This is a complex piece of kit, you can't just play around and hope things will start working.

Ahh just spotted this :-
steve_carlose
Hello Guys.
I'm looking for a "changing HP3PAR serial number procedure document"
where can I find it? any idea


Now why would you want to do that ?

Re: 3PAR 7400 controller error

Posted: Tue Feb 04, 2014 12:02 am
by Josh26
I just noticed this is the same person who asked about an OOB procedure - something that literally means you just bought a new "out of the box unit". That would mean a legitimately purchased unit is DEFINITELY covered by HP.

Re: 3PAR 7400 controller error

Posted: Tue Feb 04, 2014 1:17 am
by steve_carlose
1. Connect new node serially, While the new node is booting, enter the whack prompt by pressing Ctrl+w
2. Execute the unset sys_serial command.
3> Execute the ahci init command.
4> Execute the ide erase command.
Press Y to erase the IDE on the NEW NODE The console states that this can take over an hour, but on these solid state drives (SSDs), it should take less than one minute to complete.

after I execute this procedure in both controller unfortunately my inform OS doesn't boot and show that log I write above.