HPE Storage Users Group

Hi all.
I have the following problem, after moving 3PAR 7200 to another location, I cannot start it.
In addition, the indication on the front panel has changed: on the main node it remained the same (00); on a box with 3.5 disks, instead of the previous number 01, it became number 02; on a box with 2.5 disks, instead of the previous number 02, it became number 01.
It seems that I connected the cables the same way as they were, I completed the system operation correctly. No error indicators light up. What could have happened?
But this is not the worst thing: the array does not start:

StoreServ cli% showsysmgr
Table of contents (TOC) quorum not reached.
TOCs found:
Invalid TOC: Name(3PAR) Sysid(18190) Gen(229173) Modified(2023-10-06 10:20:44 +03) Disk count(11/43)
Not enough TOCs of this generation to make quorum (60% needed).
56 disks were available to be examined for TOCs.

StoreServ cli% showsysmgr -d
Table of contents (TOC) quorum not reached.

TOCs found:
Invalid TOC: Name(3PAR) Sysid(18190) Gen(229173) Modified(2023-10-06 10:20:44 +03) Disk count(11/43)
Not enough TOCs of this generation to make quorum (60% needed).
5000C5005E8AED6C on 0:0:0 and 0:0:0
5000C5005E8BBCCC on 0:0:0 and 0:0:0
5000C5005E8ADA60 on 0:0:0 and 0:0:0
5000C50068C7C9B0 on 0:0:0 and 0:0:0
5000C50068BEC0E4 on 0:0:0 and 0:0:0
5000C50068BF53F8 on 0:0:0 and 0:0:0
5002538A06423521 on 0:0:0 and 0:0:0
5002538A06423701 on 0:0:0 and 0:0:0
5000CCA013225CD3 on 0:0:0 and 0:0:0
50011731007037F0 on 0:0:0 and 0:0:0
50011731007037F8 on 0:0:0 and 0:0:0
Invalid TOC: Name(3PAR) Sysid(18190) Gen(0) Modified(1970-01-01 03:00:00 MSK) Disk count(45/0)
Disks have no TOC present.
5000C5005E8B9AEC on 0:0:0 and 0:0:0
5000C5006824E22C on 0:0:0 and 0:0:0
5000C5005E8B7038 on 0:0:0 and 0:0:0
5000C50068CFA814 on 0:0:0 and 0:0:0
5000C5005E81D080 on 0:0:0 and 0:0:0
5000C5005E8B8BF8 on 0:0:0 and 0:0:0
5000C5005E8BA624 on 0:0:0 and 0:0:0
5000C5005E8B7E84 on 0:0:0 and 0:0:0
5000C50068CFC440 on 0:0:0 and 0:0:0
5000C5005E8B5D7C on 0:0:0 and 0:0:0
5000C5005E8BC504 on 0:0:0 and 0:0:0
5000C50068BEF8EC on 0:0:0 and 0:0:0
5000C50068C7C2DC on 0:0:0 and 0:0:0
5000C50068BEC0F0 on 0:0:0 and 0:0:0
5000C50068CF9C80 on 0:0:0 and 0:0:0
5002538A06423581 on 0:0:0 and 0:0:0
5000C50068AFC178 on 0:0:0 and 0:0:0
5002538A06423531 on 0:0:0 and 0:0:0
5002538A06423B81 on 0:0:0 and 0:0:0
5002538A0640C881 on 0:0:0 and 0:0:0
5000C50068BF25B8 on 0:0:0 and 0:0:0
5002538A06423561 on 0:0:0 and 0:0:0
5000C50068BEBDB0 on 0:0:0 and 0:0:0
5002538A06423501 on 0:0:0 and 0:0:0
5002538A06423511 on 0:0:0 and 0:0:0
5002538A0640C7F1 on 0:0:0 and 0:0:0
5002538A06423541 on 0:0:0 and 0:0:0
5001173100701F64 on 0:0:0 and 0:0:0
5001173100703684 on 0:0:0 and 0:0:0
5001173100703EB8 on 0:0:0 and 0:0:0
500117310070585C on 0:0:0 and 0:0:0
5000CCA01C6A98CB on 0:0:0 and 0:0:0
500117310070399C on 0:0:0 and 0:0:0
5000CCA01C6A98E3 on 0:0:0 and 0:0:0
5000CCA01C7B96A7 on 0:0:0 and 0:0:0
5000CCA01C6A93FB on 0:0:0 and 0:0:0
5000CCA01B8C7CDB on 0:0:0 and 0:0:0
5000CCA01C6A9453 on 0:0:0 and 0:0:0
5000CCA01C8BC98F on 0:0:0 and 0:0:0
5000CCA01C8BED07 on 0:0:0 and 0:0:0
5001173100702338 on 0:0:0 and 0:0:0
5000CCA01C8BBE8F on 0:0:0 and 0:0:0
5000CCA01C6A9477 on 0:0:0 and 0:0:0
5000CCA01C30322B on 0:0:0 and 0:0:0
5000CCA01C8B44AB on 0:0:0 and 0:0:0

56 disks were available to be examined for TOCs.

I'm 99.9% sure you've cabled it wrong when it sees all disk two times on the same port.

_________________
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.

I disconnected the cables from the main unit with two nodes and an additional two boxes of disks. Thus, I was left with a main block with two nodes and 24 disks that did not have any connections. This way I ruled out possible incorrect cabling. The situation has not changed much.

StoreServ cli% showsysmgr -d
Table of contents (TOC) quorum not reached.

TOCs found:
Invalid TOC: Name(3PAR) Sysid(18190) Gen(229173) Modified(2023-10-06 10:20:44 +03) Disk count(6/43)
Not enough TOCs of this generation to make quorum (60% needed).
5000C50068C7C9B0 on 0:0:0 and 0:0:0
5000C5005E8BBCCC on 0:0:0 and 0:0:0
5000C50068BF53F8 on 0:0:0 and 0:0:0
5000C5005E8AED6C on 0:0:0 and 0:0:0
5000C5005E8ADA60 on 0:0:0 and 0:0:0
5000C50068BEC0E4 on 0:0:0 and 0:0:0
Invalid TOC: Name(3PAR) Sysid(18190) Gen(0) Modified(1970-01-01 03:00:00 MSK) Disk count(18/0)
Disks have no TOC present.
5000C50068AFC178 on 0:0:0 and 0:0:0
5000C5005E81D080 on 0:0:0 and 0:0:0
5000C5005E8B9AEC on 0:0:0 and 0:0:0
5000C50068BEF8EC on 0:0:0 and 0:0:0
5000C5005E8B7E84 on 0:0:0 and 0:0:0
5000C5005E8B7038 on 0:0:0 and 0:0:0
5000C5005E8B8BF8 on 0:0:0 and 0:0:0
5000C5005E8BA624 on 0:0:0 and 0:0:0
5000C50068CFC440 on 0:0:0 and 0:0:0
5000C50068CFA814 on 0:0:0 and 0:0:0
5000C5005E8BC504 on 0:0:0 and 0:0:0
5000C50068CF9C80 on 0:0:0 and 0:0:0
5000C50068C7C2DC on 0:0:0 and 0:0:0
5000C50068BEC0F0 on 0:0:0 and 0:0:0
5000C5005E8B5D7C on 0:0:0 and 0:0:0
5000C5006824E22C on 0:0:0 and 0:0:0
5000C50068BEBDB0 on 0:0:0 and 0:0:0
5000C50068BF25B8 on 0:0:0 and 0:0:0

24 disks were available to be examined for TOCs.

Did you shut the system properly down before moving it?

Are both nodes up?

Assuming everything is cabled up correct and system is health, you could follow this:

https://community.hpe.com/t5/hpe-3par-s ... -p/6671944

If you do that when the system isn't healthy, it could go both ways.

_________________
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.

It seems to me that it is a good idea to change the numbering of the cases to the one that was in good condition before the shutdown. I can’t open this link, can someone tell me how to change the numbering using the small button on the front panel?

You can’t. That LEDs (and cage number) is controlled by the 3PAR OS.

_________________
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.