HPE 3PAR StoreServ Storage

HP 3PAR StoreServ Storage - Node Rescue Fails after Replacing Node Disk

 
Venkatesh_SL
Advisor

HP 3PAR StoreServ Storage - Node Rescue Fails after Replacing Node Disk

HP 3PAR StoreServ Storage - Node Rescue Fails after Replacing Node Disk

Questions/Symptoms
SYMPTOM:There was failure on node disk and after replacement of disk, the node boots to 3PAR login prompt but unable to locate home directory and gives console menu.
3PAR(R) InForm(tm) OS 3.1.2.278 (none) ttyS0
(none) login: console
Password:

3PAR Console Menu (none) 3.1.2.278
1. Out Of The Box Procedure
2. Re-enter network configuration
3. Update the CBIOS
4. Enable or disable CLI error injections
5. Perform a Node-to-Node rescue
6. Set up the system to wipe and rerun ootb
7. Cancel a wipe
8. Perform a deinstallation
9. Update the system for recently added hardware (admithw)
10. Check system health (checkhealth)
11. Exit

When tried to perform node rescue by using option 5, it gives below error:
Could not open connection to CLI server process tpdtcl, it has not yet started or has failed.

Informed to perform node rescue from working node but failed again.
root@xxxxxxx-1 Tue Aug 13 01:56:41:~# startnoderescue –node 0
Node rescue from node 1 to node 0 started.
root@xxxxxxx-1 Tue Aug 13 01:57:43:~# showtask
4723 node_rescue node_0_rescue failed

Cause
CAUSE:It seems new node0 disk came with old OS and hence node rescue is failing.
Answer/Solution
FIX:Finally executed below command from problamatic node Whack> and it got booted and joined the cluster.
Whack>unset sys_serial
Whack>ahci init
Whack>ide erase
Whack>reset


I am an HPE Employee
If this helps you with your issue, please click the thumb to register a Kudo.
If it resolves the issue, please consider marking it as an Accepted Solution.

Accept or Kudo

3 REPLIES 3
Blago
Advisor

Re: HP 3PAR StoreServ Storage - Node Rescue Fails after Replacing Node Disk

If for some reason the node faild to be rescued again after the fix proposed by Venkatesh_SL. And the output is similar to this:

Booting from device 0, AHCI0Invalid boot sector.
Use "boot net install" to correct this.

*** Fatal error: Code 39, sub-code 0x10 (0).
AHCI0 MBR does not have a valid partition table
Disabled FSBC boot watchdog.

*** Fatal error: Code 39, sub-code 0x10 (0).

*** Fatal error: Code 39, sub-code 0x10 (0).

Go back to the Whack by pressing Ctrl+W and then:

Whack>ahci init

Whack>reset

 

Good Luck

 

 

If this helps you with your issue, please click the thumb to register a Kudo.
If it resolves the issue, please consider marking it as an Accepted Solution.
Torsten.
Acclaimed Contributor

Re: HP 3PAR StoreServ Storage - Node Rescue Fails after Replacing Node Disk

Well, version 3.1.2 is end-of-life since many years ...

You should consider to upgrade to a supported version, which is 3.2.2.MU6 for a 7000.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Blago
Advisor

Re: HP 3PAR StoreServ Storage - Node Rescue Fails after Replacing Node Disk

Hi, Torsten,

I totally agree that we should update to latest 3.2.2.MU6 . But we would need support contract to download it, no to mention that it is advised, the firmware upgrade process to be done by an HPE engineer.

We are going to consider it though.

Cheers

If this helps you with your issue, please click the thumb to register a Kudo.
If it resolves the issue, please consider marking it as an Accepted Solution.