topic Re: 3par with failed cpg and only one controller node in HPE 3PAR StoreServ Storage

3par with failed cpg and only one controller node

angyesther — Wed, 15 Jan 2025 11:00:42 GMT

Hi guys,

So, we have an old 3par with a failed node and a failed disk. It still works somehow but there's an issue that's been bugging me for a while. We had a storage growth issue so I migrated volumes and regained some space (thinvv), so I wanted to migrate (again) some data to full provisioning volumes but then I realized our cpg (R5) was still failed, it requests a compactcpg but the moment we try to run it we get the following error:

Error: LD tp-1-sd-0.21 is owned by node 0, but it should be owned by node 1. Regions can only be moved after this is fixed.

And we can't proceed, the system is supposed to have around 4TB free, but it won't let me create new volumes for lack of space.

This is the result of compactcpg:

cli% compactcpg -dr FC_r5
Compacting CPG FC_r5
Initial trim would reclaim 0 MB SA space, 0 MB SD space, and 0 MB USR space.
Would move 640 MB SA space, 1062656 MB SD space, and 0 MB USR space.
Final trim would reclaim 2048 MB SA space, 3614720 MB SD space, and 0 MB USR space.

The company won't buy a new controller node since it is an old storage. Is there a way I could bypass this issue and reclaim some space?

Best regards,

Angelica

Re: 3par with failed cpg and only one controller node

AnilKT — Wed, 15 Jan 2025 06:07:22 GMT

Hi angyesther,

Could you please let us know the HPE 3PAR model and OS version details you are using.

Also, please run the command showpd and give the output.

The compact operation may not work if you have a failed disk in the array.

Hope this helps.!

Regards

Anil

Re: 3par with failed cpg and only one controller node

angyesther — Thu, 16 Jan 2025 04:18:44 GMT

Hi AnilKT,

Yes, we also have a failed disk, we didn't change it because the servicemag couldn't run...

Here's the output:

3PAR cli% showpd
---Size(MB)---- ----Ports----
Id CagePos Type RPM State Total Free A B Capacity(GB)
0 0:0:0 FC 10 degraded 838656 0 ----- 0:0:1* 900
1 0:1:0 FC 10 degraded 838656 16384 ----- 0:0:1* 900
2 0:2:0 FC 10 degraded 838656 0 ----- 0:0:1* 900
3 0:3:0 FC 10 degraded 838656 15360 ----- 0:0:1* 900
4 0:4:0 FC 10 degraded 838656 0 ----- 0:0:1* 900
5 0:5:0 FC 10 degraded 838656 12288 ----- 0:0:1* 900
6 0:6:0 FC 10 degraded 838656 0 ----- 0:0:1* 900
7 0:7:0 FC 10 degraded 838656 12288 ----- 0:0:1* 900
8 0:8:0 FC 10 degraded 838656 0 ----- 0:0:1* 900
9 0:9:0 FC 10 degraded 838656 15360 ----- 0:0:1* 900
10 0:10:0 FC 10 degraded 838656 0 ----- 0:0:1* 900
11 0:11:0 FC 10 degraded 838656 592896 ----- 0:0:1- 900
-----------------------------------------------------------------------
12 total 10063872 664576
3PAR cli% showsys
---------------(MB)----------------
ID -Name-- ---Model---- -Serial- Nodes Master TotalCap AllocCap FreeCap FailedCap
45100 DIMABOX HP_3PAR 7200 **~~confidential info erased~~** 1 0 10063872 9153536 664576 245760
3PAR cli% showversion
Release version 3.2.1 (MU3)
Patches: P17,P18,P19,P23,P25

Component Name Version
CLI Server 3.2.1 (MU3)
CLI Client 3.2.1
System Manager 3.2.1 (P19)
Kernel 3.2.1 (MU3)
TPD Kernel Code 3.2.1 (P17)
TPD Kernel Patch 3.2.1 (P25)

Regards,

Angy

[Moderator edit: Erased the confidential info.]

Re: 3par with failed cpg and only one controller node

AnilKT — Thu, 16 Jan 2025 08:43:42 GMT

Hi angyesther,

The above output shows all the drives are in the degraded state.

Servicemag operation may not run as you have a failed disk in the array.

I would recommend you reach out the HPE technical support for more assistance on this.

Hope this helps.!

Regards

Anil

Query: 3par with failed cpg and only one controller node

support_s — Mon, 20 Jan 2025 08:16:19 GMT

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".