Problem with Dell PS4100

Hello,

After you replaced the battery, ensure all cables are securely connected.

Check the event log: Look for any error messages or warnings that may provide insights into the cause of the critical status. Take note of any specific error codes or messages.

Please let me know how it looks after checking cable connections and event log.

@dwilliam62​ 

Hi Don,

here is the output from show mem:

_____________________________ Member Information ______________________________
Name: WinnerLife-EQL                   Status: online
TotalSpace: 15.98TB                    UsedSpace: 7.75TB
SnapSpace: 270MB                       Description:
Def-Gateway: 10.178.0.2                Serial-Number:
Disks: 12                                
Spares: 1                              Controllers: 2
CacheMode: write-thru                  Connections: 0
RaidStatus: ok                         RaidPercentage: 0.000%
LostBlocks: false                      HealthStatus: critical
LocateMember: disable                  Controller-Safe: disabled
Version: V10.0.3 (R469188)             Delay-Data-Move: disable
ChassisType: DELLSBB2u12 3.5           Accelerated RAID Capable: no
Pool: WinnerLifePool                   Raid-policy: raid6
              Product Family: PS4100
All-Disks-SED: no                      SectorSize: 512
Language-Kit-Version: de, es, fr, ja,  ExpandedSnapDataSize: N/A
  ko, zh                               CompressedSnapDataSize: N/A
CompressionSavings: N/A                Data-Reduction: no-capable-hardware
Raid-Rebuild-Delay-State: disabled     Raid-Expansion-Status: enabled
_______________________________________________________________________________

____________________________ Health Status Details ____________________________

Critical conditions::
Critical hardware component failure.

Warning conditions::
Lost blocks detected in a RAID set.
_______________________________________________________________________________

____________________________ Operations InProgress ____________________________

ID StartTime            Progress Operation Details

-- -------------------- -------- -----------------------------------------------

and here are the recent logs:

WinnerLife-Group> show recent

22188:32:WinnerLife-EQL:netmgtd:19-Aug-2024 16:24:16.530032:rcc_util.c:1026:INFO
:25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. Us
er privilege is group-admin.

22143:26:WinnerLife-EQL:netmgtd:19-Aug-2024 16:23:40.170026:rcc_task.c:455:INFO:
25.2.6:CLI: Account grpadmin logged out.

21718:4728:WinnerLife-EQL:MgmtExec:19-Aug-2024 16:17:38.500632:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

21533:4695:WinnerLife-EQL:MgmtExec:19-Aug-2024 16:14:51.510599:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

21211:4623:WinnerLife-EQL:MgmtExec:19-Aug-2024 16:10:13.520527:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

21028:4591:WinnerLife-EQL:MgmtExec:19-Aug-2024 16:07:26.530495:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

20261:22:WinnerLife-EQL:netmgtd:19-Aug-2024 15:56:32.740022:rcc_util.c:1026:INFO
:25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. Us
er privilege is group-admin.

20177:0:WinnerLife-EQL:login:19-Aug-2024 15:55:20.050000:login.c:729:INFO:46.2.0
:CLI: Login to account root using a serial connection succeeded.

20155:4395:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:55:02.550299:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

20147:16:WinnerLife-EQL:netmgtd:19-Aug-2024 15:55:02.060016:rcc_task.c:455:INFO:
25.2.6:CLI: Account grpadmin logged out.

19962:4362:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:52:15.560266:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

19750:4316:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:49:12.570220:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

19566:4282:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:46:25.570186:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

18471:4035:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:30:49.614035:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

18287:4003:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:28:02.614003:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

17737:3890:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:19:57.633890:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

17671:0:WinnerLife-EQL:logevent:19-Aug-2024 15:19:02.960000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17582:0:WinnerLife-EQL:logevent:19-Aug-2024 15:17:46.940000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17488:0:WinnerLife-EQL:logevent:19-Aug-2024 15:16:30.930000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17401:0:WinnerLife-EQL:logevent:19-Aug-2024 15:15:14.890000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17311:0:WinnerLife-EQL:logevent:19-Aug-2024 15:13:58.880000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17220:0:WinnerLife-EQL:logevent:19-Aug-2024 15:12:42.870000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17130:0:WinnerLife-EQL:logevent:19-Aug-2024 15:11:26.820000:logevent.cc:238:WARN
ING:47.3.0:'diag' or 'update' was unable to send output using e-mail.  SMTP retu
rned the following error: Error sending mail:  Operation timed out

17037:0:WinnerLife-EQL:logevent:19-Aug-2024 15:10:10.790000:logevent.cc:238:INFO
:35.2.2:Data collection has finished

16626:3655:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:04:05.673655:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

16518:3630:WinnerLife-EQL:MgmtExec:19-Aug-2024 15:02:33.673630:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

16335:3597:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:59:46.673597:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

16001:3533:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:54:45.693533:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

15891:3509:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:53:11.723509:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

15710:3478:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:50:24.703478:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

15599:3453:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:48:50.703453:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

15416:3421:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:46:03.703421:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

15073:3348:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:41:04.723348:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

14967:3325:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:39:32.783325:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

14780:3289:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:36:45.733289:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

14746:0:WinnerLife-EQL:logevent:19-Aug-2024 14:36:16.090000:logevent.cc:238:INFO
:35.2.2:Starting data collection

13595:9:WinnerLife-EQL:netmgtd:19-Aug-2024 14:19:53.870009:rcc_util.c:1026:INFO:
25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. Use
r privilege is group-admin.

13349:2966:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:16:27.772966:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

13169:2938:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:13:40.782938:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

13063:2915:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:12:08.782915:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

12876:2879:WinnerLife-EQL:MgmtExec:19-Aug-2024 14:09:21.792879:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

12070:0:WinnerLife-EQL:login:19-Aug-2024 13:57:51.370000:login.c:729:INFO:46.2.0
:CLI: Login to account root using a serial connection succeeded.

11583:0:WinnerLife-EQL:login:19-Aug-2024 13:50:56.300000:login.c:729:INFO:46.2.0
:CLI: Login to account root using a serial connection succeeded.

11341:2531:WinnerLife-EQL:MgmtExec:19-Aug-2024 13:47:29.832531:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

11159:2499:WinnerLife-EQL:MgmtExec:19-Aug-2024 13:44:42.842499:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

10840:2429:WinnerLife-EQL:MgmtExec:19-Aug-2024 13:40:06.852429:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

10653:2394:WinnerLife-EQL:MgmtExec:19-Aug-2024 13:37:19.862394:replica_site.cc:1
511:INFO:8.2.21:Replication to partner sn861070 is not in progress because of ne
twork connectivity issues between the partners. The operation will be retried.

9887:2220:WinnerLife-EQL:MgmtExec:19-Aug-2024 13:26:23.882220:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

9706:2190:WinnerLife-EQL:MgmtExec:19-Aug-2024 13:23:36.892190:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

7073:1593:WinnerLife-EQL:MgmtExec:19-Aug-2024 12:46:09.971593:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

6888:1559:WinnerLife-EQL:MgmtExec:19-Aug-2024 12:43:22.971559:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

6457:1464:WinnerLife-EQL:MgmtExec:19-Aug-2024 12:37:10.991464:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

6271:1428:WinnerLife-EQL:MgmtExec:19-Aug-2024 12:34:23.991428:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

5288:1206:WinnerLife-EQL:MgmtExec:19-Aug-2024 12:20:22.021206:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

5104:1174:WinnerLife-EQL:MgmtExec:19-Aug-2024 12:17:35.031174:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

3791:877:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:58:51.070877:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

3607:843:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:56:04.080843:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

3503:822:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:54:32.080822:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

3318:789:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:51:45.090789:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2436:600:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:38:58.110600:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2101:536:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:33:59.130536:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

1764:266:WinnerLife-EQL:SP:19-Aug-2024 11:29:09.970266:cache_driver.cc:1056:WARN
ING:28.3.17:Active control module cache is now in write-through mode. Array perf
ormance is degraded.

1763:265:WinnerLife-EQL:SP:19-Aug-2024 11:29:09.970265:emm.c:355:ERROR:28.4.85:C
ritical hardware component failure, as shown next.
        C2F power module voltage is too high.

1337:362:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:23:05.150362:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

1152:327:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:20:18.160327:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

1042:302:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:18:44.160302:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

932:0:WinnerLife-EQL:eqllogmgr:19-Aug-2024 11:17:19.180000:emailRequest.cc:534:W
ARNING:31.3.0:Tried to send e-mail event notification through SMTP server '195.2
6.152.150:25'. Failed with error 'Operation timed out'.

761:176:WinnerLife-EQL:MgmtExec:19-Aug-2024 11:15:57.170176:replica_site.cc:1511
:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netwo
rk connectivity issues between the partners. The operation will be retried.

532:27:WinnerLife-EQL:psgd:19-Aug-2024 11:15:02.640027:psgd_group.cc:18266:INFO:
18.2.0:Group member WinnerLife-EQL now active in the group.

263:100:WinnerLife-EQL:SP [secondary]:19-Aug-2024 11:14:26.500099:emm.c:355:ERRO
R:28.4.85:Critical hardware component failure, as shown next.
        C2F Subsystem is not operating.

262:99:WinnerLife-EQL:SP [secondary]:19-Aug-2024 11:14:26.500098:emm.c:2363:ERRO
R:28.4.47:Critical health conditions exist.
 Correct immediately before they affect array operation.
        Critical hardware component failure.
        There are 1 outstanding health conditions. Correct these conditions before they
 affect array operation.

126:120:WinnerLife-EQL:SP:19-Aug-2024 11:14:18.020120:badblks.c:567:WARNING:14.3
.0:0:There are 15239 bad block entries in RAID LUN 0.

125:119:WinnerLife-EQL:SP:19-Aug-2024 11:14:17.820119:emm.c:2363:WARNING:28.3.51
:Warning health conditions currently exist.
 Correct these conditions before they affect array operation.
        Lost blocks detected in a RAID set.
        There are 1 outstanding health conditions. Correct these conditions before they
 affect array operation.

124:118:WinnerLife-EQL:SP:19-Aug-2024 11:14:17.820118:events.c:119:ERROR:14.4.0:
0:Inserting bad block entries in RAID LUN 0.

257:94:WinnerLife-EQL:SP [secondary]:19-Aug-2024 11:14:10.610094:cord.c:710:INFO
:28.2.108:Control module in slot 0 with serial number CN-0XF5CG-77921-497-000N i
s designated as secondary.

91:90:WinnerLife-EQL:SP:19-Aug-2024 11:14:04.270090:cache_driver.cc:1058:INFO:28
.2.39:Active control module cache set to write-back mode.

253:0:WinnerLife-EQL:QRQ [secondary]:19-Aug-2024 11:13:58.620091:qrq.c:910:INFO:
9.2.0:PS Series Array Firmware Version: Storage Array Firmware V10.0.3 (R469188)

244:83:WinnerLife-EQL:SP [secondary]:19-Aug-2024 11:13:58.610083:ppool_nvram.c:3
80:WARNING:15.3.0:NVRAM contains valid data. This is a POWER FAILURE RECOVERY.

89:89:WinnerLife-EQL:SP:19-Aug-2024 11:13:48.260089:emm.c:1333:INFO:28.2.6:Enclo
sure serial number: CN-01N9TR-70821-614-14LJ-A01.

83:83:WinnerLife-EQL:SP:19-Aug-2024 11:13:46.610083:ppool_nvram.c:380:WARNING:15
.3.0:NVRAM contains valid data. This is a POWER FAILURE RECOVERY.

90:0:WinnerLife-EQL:QRQ:19-Aug-2024 11:13:37.000000:qrq.c:910:INFO:9.2.0:PS Seri
es Array Firmware Version: Storage Array Firmware V10.0.3 (R469188)

82:82:WinnerLife-EQL:SP:19-Aug-2024 11:13:37.000000:mips_pss_init.c:363:INFO:28.
2.107:Control module in slot 1 with serial number CN-0XF5CG-77921-65A-0080 is de
signated as active.

2186:102:WinnerLife-EQL:SP [secondary]:19-Aug-2024 10:51:12.190101:emm.c:355:ERR
OR:28.4.85:Critical hardware component failure, as shown next.
        C2F power module voltage is too high.

2185:101:WinnerLife-EQL:SP [secondary]:19-Aug-2024 10:51:12.190100:emm.c:2363:ER
ROR:28.4.47:Critical health conditions exist.
 Correct immediately before they affect array operation.
        Critical hardware component failure.
        There are 1 outstanding health conditions. Correct these conditions before they
 affect array operation.

978:0:WinnerLife-EQL:eqllogmgr:19-Aug-2024 10:34:12.160000:emailRequest.cc:534:W
ARNING:31.3.0:Tried to send e-mail event notification through SMTP server '195.2
6.152.150:25'. Failed with error 'Operation timed out'.

808:187:WinnerLife-EQL:MgmtExec:19-Aug-2024 10:33:03.170187:replica_site.cc:1511
:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netwo
rk connectivity issues between the partners. The operation will be retried.

630:28:WinnerLife-EQL:psgd:19-Aug-2024 10:32:26.720028:psgd_group.cc:18266:INFO:
18.2.0:Group member WinnerLife-EQL now active in the group.

4697:1071:WinnerLife-EQL:MgmtExec:19-Aug-2024 10:21:12.011071:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

4517:1042:WinnerLife-EQL:MgmtExec:19-Aug-2024 10:18:25.021042:replica_site.cc:15
11:INFO:8.2.21:Replication to partner sn861070 is not in progress because of net
work connectivity issues between the partners. The operation will be retried.

3867:894:WinnerLife-EQL:MgmtExec:19-Aug-2024 10:09:08.040894:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

3683:861:WinnerLife-EQL:MgmtExec:19-Aug-2024 10:06:21.050861:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2915:687:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:55:25.070687:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2734:657:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:52:38.080657:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2623:631:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:51:04.080631:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2441:600:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:48:17.080600:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

2105:534:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:43:18.100534:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

1998:510:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:41:46.100510:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

1813:475:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:38:59.110475:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

1046:302:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:28:03.140302:replica_site.cc:151
1:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netw
ork connectivity issues between the partners. The operation will be retried.

961:0:WinnerLife-EQL:eqllogmgr:19-Aug-2024 09:27:00.140000:emailRequest.cc:534:W
ARNING:31.3.0:Tried to send e-mail event notification through SMTP server '195.2
6.152.150:25'. Failed with error 'Operation timed out'.

764:175:WinnerLife-EQL:MgmtExec:19-Aug-2024 09:25:16.140175:replica_site.cc:1511
:INFO:8.2.21:Replication to partner sn861070 is not in progress because of netwo
rk connectivity issues between the partners. The operation will be retried.

640:27:WinnerLife-EQL:psgd:19-Aug-2024 09:24:25.150027:psgd_group.cc:18266:INFO:
18.2.0:Group member WinnerLife-EQL now active in the group.

249:102:WinnerLife-EQL:SP [secondary]:19-Aug-2024 09:23:46.890095:emm.c:2363:ERR
OR:28.4.47:Critical health conditions exist.
 Correct immediately before they affect array operation.

247:100:WinnerLife-EQL:SP [secondary]:19-Aug-2024 09:23:46.890095:emm.c:2363:ERR
OR:28.4.47:Critical health conditions exist.
 Correct immediately before they affect array operation.

242:95:WinnerLife-EQL:SP [secondary]:19-Aug-2024 09:23:46.890095:cord.c:710:INFO
:28.2.108:Control module in slot 0 with serial number CN-0XF5CG-77921-497-000N i
s designated as secondary.

144:142:WinnerLife-EQL:SP:19-Aug-2024 09:23:36.660142:cache_driver.cc:1056:WARNI
NG:28.3.17:Active control module cache is now in write-through mode. Array perfo
rmance is degraded.

143:141:WinnerLife-EQL:SP:19-Aug-2024 09:23:36.660141:emm.c:355:ERROR:28.4.85:Cr
itical hardware component failure, as shown next.
        C2F power module has insufficient hold time.

142:140:WinnerLife-EQL:SP:19-Aug-2024 09:23:36.660140:emm.c:2363:ERROR:28.4.47:C
ritical health conditions exist.
 Correct immediately before they affect array operation.
        Critical hardware component failure.
        There are 1 outstanding health conditions. Correct these conditions before they
 affect array operation.

238:0:WinnerLife-EQL:QRQ [secondary]:19-Aug-2024 09:23:32.010092:qrq.c:910:INFO:
9.2.0:PS Series Array Firmware Version: Storage Array Firmware V10.0.3 (R469188)

229:84:WinnerLife-EQL:SP [secondary]:19-Aug-2024 09:23:32.010084:ppool_nvram.c:3
80:WARNING:15.3.0:NVRAM contains valid data. This is a POWER FAILURE RECOVERY.

136:135:WinnerLife-EQL:SP:19-Aug-2024 09:23:14.810135:badblks.c:567:WARNING:14.3
.0:0:There are 15239 bad block entries in RAID LUN 0.

133:132:WinnerLife-EQL:SP:19-Aug-2024 09:23:14.610132:emm.c:2363:WARNING:28.3.51
:Warning health conditions currently exist.
 Correct these conditions before they affect array operation.
        Lost blocks detected in a RAID set.
        There are 1 outstanding health conditions. Correct these conditions before they
 affect array operation.

132:131:WinnerLife-EQL:SP:19-Aug-2024 09:23:14.610131:events.c:119:ERROR:14.4.0:
0:Inserting bad block entries in RAID LUN 0.

128:128:WinnerLife-EQL:SP:19-Aug-2024 09:23:13.260128:emm.c:1333:INFO:28.2.6:Enc
losure serial number: CN-01N9TR-70821-614-14LJ-A01.

83:83:WinnerLife-EQL:SP:19-Aug-2024 09:23:11.620083:ppool_nvram.c:380:WARNING:15
.3.0:NVRAM contains valid data. This is a POWER FAILURE RECOVERY.

129:0:WinnerLife-EQL:QRQ:19-Aug-2024 09:23:02.000000:qrq.c:910:INFO:9.2.0:PS Ser
ies Array Firmware Version: Storage Array Firmware V10.0.3 (R469188)

82:82:WinnerLife-EQL:SP:19-Aug-2024 09:23:02.000000:mips_pss_init.c:363:INFO:28.
2.107:Control module in slot 1 with serial number CN-0XF5CG-77921-65A-0080 is de
signated as active.

@ZenithRider​ 

I did power down the array to replace the battery.

@ZenithRider​ 

 Hello, 

 So you still have two issues.  1.)  The C2F (battery) module on the passive needs to be replaced also.  2.)  You have many lost blocks on your RAIDset  

143:141:WinnerLife-EQL:SP:19-Aug-2024 09:23:36.660141:emm.c:355:ERROR:28.4.85:Cr
itical hardware component failure, as shown next.
        C2F power module has insufficient hold time.

136:135:WinnerLife-EQL:SP:19-Aug-2024 09:23:14.810135:badblks.c:567:WARNING:14.3
.0:0:There are 15239 bad block entries in RAID LUN 0.

Did you shutdown the array first, or just power it off ? 

At the CLI run  GrpName>support exec "raidtool"

Please paste the output of that 

You will need to replace the C2F module on the passive CM as well.  You can remove that controller w/o shutting down the array.  If you are make sure you do a shutdown first.

 Regards,

Don 

#iworkfordell

@dwilliam62​ 

We didnt shutdown the array first we just powered off the 2 psu's could that cause the lost blocks? I will send you the output from support exec raidtool in the morning but i tried it already it has over 10000 lost blocks. 

Also we changed the coin cell battery too with the same kind of battery can that cause some trouble too?

Im a begginer so im still learning when this storage came out i was ten. 🙂

@ZenithRider​ 

Just powering off the array with a failed cache card might have  caused the lost blocks.   Whenever possible a shutdown should be done to force cache to disk. 

 Re: Coin cell battery isn't used as part of cache,  just for the clock 

 You will have to clear the lost blocks, which means there could be data impacted.

 Regards,

Don

#iworkfordell 

@dwilliam62​ 

Here's the output of support exec "raidtool" 

support exec raidtool
You are running a support command, which is normally restricted to PS Series Tec
hnical Support personnel. Do not use a support command without instruction from
Technical Support.
Driver Status: Ok
RAID LUN 0 Ok.
  *!! RAID LUN contains 15239 lost blocks. !!*
      (raidtool -W 0) clears blocks.
      (raidtool -w 0) lists blocks.
  11 Drives (0,2,4,6,8,1,3,5,7,9,10)
  RAID 6 (64KB sectPerSU)
  Capacity 17,617,013,637,120 bytes
Available Drives List: 11

I guess the next thing is raidtool -W 0 but is there any other way to save the files in the lost blocks?

Also whats the command for displaying the ip address? 

@ZenithRider​ 

Hello,  

 Those blocks are lost.  There is no way to associate them with a volume anymore.  The array is block storage not file, or filesystem aware.    The blocks could be in a snapshot or unallocated space, or a replica.   There is no way to know   To clear those blocks and remove that alert you will have to run  GrpName>support exec "raidtool -W 0"  

After that, at the hosts you should do a filesystem check of all your volumes 

 Re: IP   GrpName> mem sel MEMEBERNAME show eths

 Regards, 

Don

#iworkfordell

Hi again all,

So I waited for the battery module to arrive from dell and finally it did and i replaced that on the passive controller without turning off the storage i did it just by removing the passive controller and replacing the battery module. Also i cleared the lost blocks and that is okay now too.

After i replaced the battery module the previous error message disappeared but a new critical error appeared 28.4.47 and i found some solution here saying that i should just do a restart on the passive controller, so i did a restart on the passive controller and the now this is the error it says in the event log:

141:139:WinnerLife-EQL:SP:18-Sep-2024 13:11:28.250139:emm.c:355:ERROR:28.4.85:Cr
itical hardware component failure, as shown next.
        C2F Subsystem is not operating.

140:138:WinnerLife-EQL:SP:18-Sep-2024 13:11:28.250138:emm.c:2363:ERROR:28.4.47:C
ritical health conditions exist.
 Correct immediately before they affect array operation.
        Critical hardware component failure.
        There are 1 outstanding health conditions. Correct these conditions before they
 affect array operation.

The battery status is good on both controllers now but this critical error appeared.

Someone know how to fix this?

Hi,

When you have downtime, I’d suggest shutting the unit down, unplugging all the power, and leaving it off for a full 5 minutes. Make sure you securely seat and connect all the hardware components, including the new battery module. Sometimes, just reseating these components can fix hardware issues. Since you’ve already restarted the passive controller, consider restarting the active controller as well. However, ensure you have a maintenance window for this, as it might impact your storage availability.

@DELL-Erman O​ Hi Erman,

Thank you for the reply, i did what you suggested but i get the same outcome again, the error is 28.4.99 C2F SubSystem is not operating. 

I also did a restart on the active controller too but its the same.

Hi, 

Please check the firmware. I recommend updating the array firmware to a newer version if possible. If the issue persists, it might be related to a C2F daughterboard failure, but it’s hard to say for sure. At this point, I can’t think of anything other than a hardware issue.

@DELL-Erman O​ We changed the c2f daughterboards on both controllers so I doubt that but I will try with a firmware update. Thank you again.