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

[SebastianTR]

Hello.

I can't finish the Node Rescue process.

It is a 3PAR 72000 MU6.

I am installing a new node which is OK. It performs the entire process but fails due to "space" issues. I have made several node changes and this is the first time it has happened to me.

The IDE disk is the same as the other NODE (blue).

I have run all known processes from the WACK>

In short, I follow all the steps and execute:

whack>unset sys_serial

whack>ahci init

Whack>ide erase

whack>reset

Everything runs ok, but never joins the cluster and ends with this error

[ 45.018834] Total CM for this node is 4 GB
[ 45.018838] patrol_delay 4614 msecs
[ 45.018850] Starting eagle_cm_patrol_thread....
[ 45.018853] Num Srcs 14 Src Size 16384
[ 45.060562] Starting scan mir log thread 0x226b
[ 45.060564] Setting recovery log scan delay to 292 ms
init: Loading tpd kernel module: done.
init: Remapping interrupts
init: WARNING: irq name contains comma delimited list [aerdrv 0x70, aerdrv 0x70, aerdrv 0x70, aerdrv 0x70, aerdrv 0x70, aerdrv 0x70, aerdrv]
init: WARNING: irq name contains comma delimited list [nemoe 0x78, Eos intr]
init: Loading tpd kernel patch modules: Patch99 Patch110 Patch114 P119 Patch135 Patch138 Patch139 Patch142 Patch149 Patch160 Patch165
init: Configuring powerfail device /dev/pfail_storage: 801
init: done.
init: Initializing eanet0: done.
init: Rotating PM logs: done.
init: Rotating PR event logs: done.
init: Starting Process Manager: pm.
init: Rotating pr_sync_ide logs: done.
init: Starting PR Sync IDE: pr_sync_ide.
init: coreman: tpdinit run at epoch=1664819228sec with boot at epoch=1664819176sec
init: coreman: file system usage - /dev/sda7 - used=15227584KB (used-core=172KB) free=46257040KB total=61484624KB
init: coreman: space removal targets - freeMin=0KB freePct=0KB corePct=0KB targetToRemove=0KB targetToRemoveMinLow=0KB
init: coreman: exit - no free space requirements to satisfy
init: Launching tpd_cfg_tornado_dcncage script to work around 'Configures a Tornado Enclosures DP-1 port' issue
init: Running l
3PAR(R) InForm(tm) OS 3.2.2.709 1612423-1 ttyS0
1612XXX-1 login:

I can send the complete log. I don't see that it can be attached here.
I do not have current support from HPE.
I will greatly appreciate the help.

Thanks!!!!

[AnilKT]

Hi SebastianTR,
Hope you are doing good.

I clearly see that you are trying to add a new node to the cluster.

Could you please confirm both the nodes are having the Same OS version running,
if not, please sync the OS on both the nodes.

I observed that there is a DP-1 port issue as well, could you also please verify the SAS ports and Cables
are in a healthy state.

Kindly revert for further queries.

Hope this helps.

Regards
Anil

[SebastianTR]

Hi.

Thanks for your help. 

My Answers...

"I clearly see that you are trying to add a new node to the cluster."

Effectively. We are installing a completely new node. Empty IDE disk.

"Could you please confirm both the nodes are having the Same OS version running,"

They definitely do not have the same version. The node's disk is empty.
On the other hand, when we do the post-failure process again, we delete the IDE disk with the command

"if not, please sync the OS on both the nodes."

What would that procedure be? I understand that it is the Node Rescue. or not?

"I observed that there is a DP-1 port issue as well, could you also please verify the SAS ports and Cables
are in a healthy state."

The cables are ok.
We are doing the procedure with the SAS cables connected.
Would it be better to disconnect them for the node rescue procedure?

Thanks. 

Sebastian.

[Torsten.]

I cannot see an error and there is finally a login prompt.

So did the node join the cluster or not?

[SebastianTR · Accepted solution]

exact.does not join the cluster.
The problem has already been resolved.
7200 node was being used in a 3PAR 7200c.
all ok!

[Sunitha_Mod]

@SebastianTR

Hello Sebastian, 

Great! We are glad to know the problem has been resolved. 

[JakeHarnandez]

That does not solve the storage problem for me, unfortunately. Any other possible solutions that I could use?

Regards, Team Storaboxdirect

[sbhat09]

Hello @JakeHarnandez,

Can you please elaborate more on the issue you are facing?
It will be good if you can post it as a new discussion chain.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.