HP 3par 7400 problem with initialization

[MammaGutt]

If system is healthy, press 1.

[MichalK2]

Did I do the following? that's all right ? Or is there a mistake?

Code: Select all

3PAR Console Menu 1621379-1 3.2.2.709

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. Finish SP-to-Node rescue procedure
12. Exit
> 1


It appears your Cluster is in a proper manual startup state to proceed.
Removing VMs

  Welcome to the Out-Of-The-Box Experience 3.2.2.798

*****************************************************************************

*****************************************************************************
*                                                                           *
*   CAUTION!! CONTINUING WILL CAUSE COMPLETE AND IRRECOVERABLE DATA LOSS    *
*                                                                           *
*****************************************************************************
*****************************************************************************

You need to have the StoreServ network config information available.
This can be obtained from the Systems Assurance Document.


DO YOU WISH TO CONTINUE?  yes/no  ==> yes


Cluster has the following nodes:

Node 1


Enter < C > to continue or < Q > to quit  ==> C


Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
 1) Africa
 2) Americas
 3) Antarctica
 4) Arctic Ocean
 5) Asia
 6) Atlantic Ocean
 7) Australia
 8) Europe
 9) Indian Ocean
10) Pacific Ocean
11) none - I want to specify the time zone using the Posix TZ format.
#? 8^H^H^H
Please enter a number in range.
#? 8
Please select a country.
 1) Albania        18) Guernsey          35) Poland
 2) Andorra        19) Hungary          36) Portugal
 3) Austria        20) Ireland          37) Romania
 4) Belarus        21) Isle of Man       38) Russia
 5) Belgium        22) Italy          39) San Marino
 6) Bosnia & Herzegovina  23) Jersey          40) Serbia
 7) Britain (UK)     24) Latvia          41) Slovakia
 8) Bulgaria        25) Liechtenstein       42) Slovenia
 9) Croatia        26) Lithuania          43) Spain
10) Czech Republic     27) Luxembourg       44) Sweden
11) Denmark        28) Macedonia          45) Switzerland
12) Estonia        29) Malta          46) Turkey
13) Finland        30) Moldova          47) Ukraine
14) France        31) Monaco          48) Vatican City
15) Germany        32) Montenegro       49) Ã…land Islands
16) Gibraltar        33) Netherlands
17) Greece        34) Norway
#? 41

The following information has been given:

   Slovakia

Therefore TZ='Europe/Bratislava' will be used.
Local time is now:   Fri Mar  3 11:53:12 CET 2023.
Universal Time is now:   Fri Mar  3 10:53:12 UTC 2023.
Is the above information OK?
1) Yes
2) No
#? 1

You can make this change permanent for yourself by appending the line
   TZ='Europe/Bratislava'; export TZ
to the file '.profile' in your home directory; then log out and log in again.

Here is that TZ value again, this time on standard output so that you
can use the /usr/bin/tzselect command in shell scripts:

Updating all nodes to use timezone Europe/Bratislava...
Timezone set successfully.


Setting TOD on all nodes.

Current date according to the system: Fri Mar  3 11:53:24 CET 2023

Enter dates in MMDDhhmmYYYY format.  For example, 031822572002 would
be March 18, 2002 10:57 PM.

Enter the correct date and time, or just press enter to accept
the date shown above.  ==> 030311572023
Fri Mar  3 11:57:00 CET 2023


Is this the desired date? (y/n) y




Enter the StoreServ system name ==> Storage2

Cluster will be initialized with the name < Storage2 >


IS THIS THE CORRECT NAME?  yes/change  ==> yes


Cluster is being initialized with the name < Storage2 > ...Please Wait...


Please verify your InForm OS versions are correct.

Release version 3.2.2.709 (MU6)
Patches:  P99,P107,P119,P131,P135,P139,P149,P154,P160,P162,P165,P166,P168

Component Name                   Version                         
CLI Server                       3.2.2.809 (P165)                
CLI Client                       3.2.2.809                       
System Manager                   3.2.2.809 (P165)                
Kernel                           3.2.2.709 (MU6)                 
TPD Kernel Code                  3.2.2.709 (MU6)                 
TPD Kernel Patch                 3.2.2.809 (P165)                


Enter < C > to continue or < Q > to quit  ==> X^H^H


Enter < C > to continue or < Q > to quit  ==> C

Examining the port states...
All ports are in acceptable states.

Examining state of new disks...

Found < 24 > HCBRE0900GBAS10K disks

Cluster has < 24 > total disks in < 24 > magazines.
 < 24 > are degraded.

Now would be the time to fix any disk problems.


Enter < C > to continue, < R > to retry, or < Q > to quit  ==> C



Ensuring all ports are properly connected before continuing... Please Wait...


Found one or more discrepancies when examining cage connections:

Component ---------Description---------- Qty
Cabling   Missing node for cabling check   1

-Identifier- -- ------------------Description-------------------
node0        -- No cabling data for node0. Check status of node0


Please verify whether the output above is as expected.


Enter < C > to continue, < R > to retry, or < Q > to quit  ==> C


Examining drive cage firmware... Please wait a moment...
1 cage requires firmware upgrades.
This will require approximately 10-20 minutes.

Enter y to proceed with this action, or n to skip it.
y

2023-03-03 11:57:55 CET
Skipping cage cage0 cpuA already up to date at rev 409b
Cage cage0 cpuB is invalid.
Skipping upgrade for cage cage0 cpuB.
Waiting for cage0 to finish coming back...


All disks have current firmware.

Issuing admitpd... Please wait a moment...
admitpd completed with the following results...

Found < 24 > HCBRE0900GBAS10K disks

Cluster has < 24 > total disks in < 24 > magazines.
 < 24 > are degraded.

Not all of the disks are in a valid state.


Enter < C > to continue or < Q > to quit  ==> C



At this point, it is recommended that the OOTB stress test be started.  This
will run heavy I/O on the PDs for 1 hour following 1 hour of chunklet
initialization.  The stress test will stop in approximately 2 hours and 15
minutes.  Chunklet initialization may continue even after the stress test
completes.  Failures will show up as slow disk events.


Do you want to start the test (y/n)? ==> y
Starting system stress test...
Unable to proceed because the system is not connected to any disks.

Admin volume could not be properly created!

Exiting Out-Of-The-Box Experience...


3PAR Console Menu 1621379-1 3.2.2.709

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. Finish SP-to-Node rescue procedure
12. Exit
> 1

The system is currently running.  It needs to be in manual startup state for ootb to run.
If you are attempting to handle hardware upgrades, use the admithw CLI command instead.

Exiting Out-Of-The-Box Experience...


3PAR Console Menu 1621379-1 3.2.2.709

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. Finish SP-to-Node rescue procedure
12. Exit
> 

[MammaGutt]

Well, that output clearly states you do not have a healthy system. You only have node 1. Node 0 is missing. System is not healthy, system will not initialize.