Hitachi Proprietary DW850/DW900/DW1000

Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.

TRBL00-00

TROUBLESHOOTING
SECTION

TRBL00-00
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-10

Contents
1. Overview of TRBL..................................................................................................................TRBL01-10
1.1 Flow of Troubleshooting ..................................................................................................TRBL01-10
1.2 Checking Customer Report and Storage System Status ................................................TRBL01-20

2. Isolation of Failed Part ...........................................................................................................TRBL02-10

2.1 Flow of failed part isolation .............................................................................................TRBL02-10
2.1.1 Failures at the Time of Start-Up ..............................................................................TRBL02-40
2.1.2 Failures at the Time of Planned Shutdown (PS OFF) .............................................TRBL02-60
2.1.3 Detecting Storage System Failures by a Server .....................................................TRBL02-90
2.1.4 Lighting up ALARM (red) of Storage System LED ................................................TRBL02-120
2.1.5 Blinking WARNING (amber) of Storage System LED ...........................................TRBL02-190
2.1.6 Lighting up WARNING (amber) of Storage System LED ......................................TRBL02-200
2.1.7 Blinking or lighting up of CTL ALM LED (red) on CTL ...........................................TRBL02-210
2.1.8 Blinking CTL WARN LED (amber) of CTL (CBSS/CBSL) .....................................TRBL02-230
2.1.9 Lighting up FAN STATUS LED (red) of FAN (CBLH).............................................TRBL02-240
2.1.10 Turning off POWER LED of the Storage System LED ........................................TRBL02-250
2.2 Failure During Operation by Service Personnel ............................................................TRBL02-260
2.2.1 Error Recovery Procedure when Removing/Inserting CTL ...................................TRBL02-260
2.2.2 Failures Have Occurred when Installing Drive/DB ................................................TRBL02-320
[Link] Installation Failure of Drive/DB ......................................................................TRBL02-320
[Link] LED of ENC Turns On after Installing DB ......................................................TRBL02-360
2.2.3 Error Recovery Procedure during CHB/DKB replacement ....................................TRBL02-370
2.2.4 Error Recovery Procedure during BKM/BKMF/Battery/CFM
replacement and LANB blockade.........................................................................TRBL02-410
2.2.5 Error Recovery Procedure during LANB replacement ..........................................TRBL02-420
2.2.6 Recovery procedure when LDEV formatting failed ...............................................TRBL02-430
2.2.7 Recovery from the incorrect setting when adding Cache Memories .....................TRBL02-450
2.2.8 Recovery Procedure when Change the IP Address failed ....................................TRBL02-480
2.2.9 Correspondence at the time of the mode setting failure of System Option ...........TRBL02-500
2.2.10 Firmware version mismatching ............................................................................TRBL02-510
2.2.11 Recovery Procedure for Failure During DKB Installation ....................................TRBL02-520
2.2.12 Recovery Procedure for the System Lock during a Setting Change ...................TRBL02-530
2.2.13 Error Recovery When Adding Cache Memories/Cache Flash Memories............TRBL02-540
2.2.14 Error Recovery When Removing Cache Memories/Cache Flash Memories ......TRBL02-560
2.2.15 Transmission Failure and Timeout Occur Repeatedly After MPC Reboot...........TRBL02-580
2.2.16 Recovery Procedure when ALM LED (red) on Drive/DBPS/ENC is not
Turned off .............................................................................................................TRBL02-590
2.2.17 Recovery Procedure at SFP Replacement .........................................................TRBL02-610
2.2.18 Recovery Procedure when Procedure for Small Form-Factor
Pluggable (SFP) Data Transfer Rate Change fails ..............................................TRBL02-620
2.2.19 Error Recovery When Cache Memories/FANs Are Replaced .............................TRBL02-631
2.2.20 Actions when 00002-002145 Error is Displayed in the Web Server
Status Window .....................................................................................................TRBL02-632
TRBL00-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-20

2.2.21 Troubleshooting When the Error Message (32061-208063) Appears

in the Maintenance Utility window during Maintenance Work of
Controller Chassis/Controller Board.....................................................................TRBL02-633
2.2.22 Troubleshooting When Maintenance Work Cannot Be Completed
within Two Hours ..................................................................................................TRBL02-634
2.2.23 Troubleshooting When the Error Message (32061-208063) Appears
in the Maintenance Utility Window during a Maintenance Operation ...................TRBL02-635
2.2.24 Actions when 20123-107008 Error is Displayed in the Web Server
Status Window .....................................................................................................TRBL02-636
2.2.25 Procedure When Initialization of Duplicated Data Ended Abnormally .................TRBL02-638
2.3 Analyze by SIM Log ......................................................................................................TRBL02-640
2.4 Failures of Multiple Parts ..............................................................................................TRBL02-680
2.5 Checking Normality .......................................................................................................TRBL02-740
2.6 Troubleshooting When the Maintenance PC/SVP and GUM Cannot
Communicate with Each Other ....................................................................................TRBL02-770

3. Recovery Method of the Shared Platform Failure..................................................................TRBL03-10

3.1 SFP Module Failure Detection (SIM = 21a8xx, 21aaxx) .................................................TRBL03-10
3.2 Response to a FLASH DRIVE/ENCRYPTION PG LDEV FORMAT Failure
(SIM = 41000x) ..............................................................................................................TRBL03-20
3.3 Recovery procedure when DB power off was detected or when SAS/NVMe
port blockage occurred (SIM = ac50xx, cf12xx, cf22xx) ................................................TRBL03-30
3.4 Action When Time Synchronization Failed (SIM = 7ffa00) ............................................TRBL03-130
3.5 Recovery Procedure for LDEV Blockade due to Firmware Error (SIM = 3a0xyy).........TRBL03-140
3.6 Recovery Procedure for the Failure on the Occurrence of Unmatched
Memory Installation Capacity (SIM = ffe800)...............................................................TRBL03-150
3.7 Recovery procedure of SIM occurrence during battery charge (SIM = fe0000)............TRBL03-160
3.8 Action when Cache Write Through by battery factor is detected (SIM =
fe0100, fe0200) ...........................................................................................................TRBL03-170
3.9 Isolation and Recovery Procedure for Common SAS/NVMe Failure (SIM =
db0xxx, db1xxx, db2xxx, db3xxx, db4xxx, db5xxx, db6xxx, db7xxx, df6xxx,
df7xxx, df8xxx, df9xxx) ................................................................................................TRBL03-180
3.10 Recovery Procedure for LAN Error (SIM = 7d01xx,7d02xx) .......................................TRBL03-210
3.10.1 Recovery Procedure When an Internal LAN Failure Occurs (SIM =
7d01xx) (2U Controller Chassis) ..........................................................................TRBL03-210
3.10.2 Recovery Procedure When an Internal LAN Failure Occurs (SIM =
7d01xx) (4U Controller Chassis) ..........................................................................TRBL03-220
3.10.3 Recovery Procedure When a LAN Failure Occurs between CTL (SIM
= 7d02xx) (2U Controller Chassis) .......................................................................TRBL03-230
3.10.4 Recovery Procedure When a LAN Failure Occurs between CTL (SIM
= 7d02xx) (4U Controller Chassis) .......................................................................TRBL03-240
3.11 Recovery Procedure for the Failure on Both Sides of CACHE at the Time
of Starting (SIM = fff50x)..............................................................................................TRBL03-260
3.12 Recovery Procedure When Cache Correctable Error Is Detected (SIM =
fff0xx, fe05xx) ..............................................................................................................TRBL03-270

TRBL00-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.7.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-30

3.13 Recovery Procedure for LDEV Blockade (SIM = ef8xxx, ef9xxx, db8xxx,
db9xxx, dbaxxx, dbbxxx, dfaxxx, dfbxxx, 46cxxx, 46dxxx) ..........................................TRBL03-300
3.14 Response to the Occurrence of External Temperature Warning or Alarm
(SIM = af110x, af120x) ................................................................................................TRBL03-340
3.15 Response to the Detection of CPU Abnormal Temperature (SIM = af100x) ...............TRBL03-370
3.16 Response to the Detection of Invalid CEDT(SIM = 399f0x) ........................................TRBL03-380
3.17 Response to the Detection of Uninstalled CFM (SIM = aff20x) ..................................TRBL03-390
3.18 Response to the Occurrence of BKM or BKMF Warning (SIM = af400x) ...................TRBL03-400
3.19 Response to the Detection of Forced Volatilization Warning (SIM = fffe0x)................TRBL03-410
3.20 Response to the Occurrence of DKCPS Warning (SIM = af200x) ..............................TRBL03-420
3.21 Response to the Detection of Abnormal DBPS Input Voltage (SIM =
af60xx, af61xx, af62xx)................................................................................................TRBL03-440
3.22 Response to the Detection of Invalid CEMODE (SIM = 399e0x) ................................TRBL03-460
3.23 Recovery Procedure When CHK1B or CHK3 Threshold Over Occurs (SIM
= 3071xy, 3072xy) .......................................................................................................TRBL03-470
3.24 Recovery Procedure for Warning of Channel Board/Disk Board Type (SIM
RC = 3c9500) ..............................................................................................................TRBL03-480
3.25 Isolation Procedure for Failed Part in CACHE Volatilization (SIM = ffe700,
ffeb00, ffcd0x, ffcfyx, 610002)......................................................................................TRBL03-490
3.26 Isolation and Recovery Procedure for Drive Link Rate Error (SIM =
dbcxxx, dbdxxx, dbexxx, dbfxxx, dfcxxx, dfdxxx) ........................................................TRBL03-530
3.27 Drive failure recovery procedure .................................................................................TRBL03-550
3.27.1 In the case of normal termination (SIM RC = 452xxx, 462xxx, 4b8xxx,
4b9xxx, 4c8xxx, 4c9xxx) ......................................................................................TRBL03-570
3.27.2 In the case of termination with a warning (SIM RC = 455xxx, 465xxx,
4bexxx, 4bfxxx, 4cexxx, 4cfxxx) ...........................................................................TRBL03-580
3.27.3 In the case of termination owing to abortion (SIM RC = 454xxx,
464xxx, 4bcxxx, 4bdxxx, 4ccxxx, 4cdxxx) ............................................................TRBL03-600
3.27.4 In the case of abnormal termination (SIM RC = 453xxx, 463xxx,
4baxxx, 4bbxxx, 4caxxx, 4cbxxx) .........................................................................TRBL03-610
3.27.5 Correction access status .....................................................................................TRBL03-740
3.27.6 Parity group blockade ..........................................................................................TRBL03-750
3.27.7 Preventive maintenance ......................................................................................TRBL03-760
3.28 SVP Failure Recovery .................................................................................................TRBL03-770
3.28.1 Troubleshooting Storage Navigator .....................................................................TRBL03-790
[Link] Troubleshooting Related to Installation and Upgrade ..................................TRBL03-790
[Link] Troubleshooting Related to the Initial Setting Command of the SVP ..........TRBL03-820
[Link] Storage Device List Troubleshooting ...........................................................TRBL03-830
[Link] Troubleshooting of Storage Navigator other than the Above-Mentioned .....TRBL03-870
[Link] Background Service Log..............................................................................TRBL03-880
[Link] Checking Duplicated Ports and Using DLL Load Confirmation Tools ........TRBL03-1131
[Link] Troubleshooting Related to Jetty Periodic Reboot Function ......................TRBL03-1134
3.29 MPC Failure Recovery ..............................................................................................TRBL03-1140
3.29.1 When I cannot be connected from MPC to the GUM or Storage System .........TRBL03-1140
3.29.2 When the Set Network Location dialog is displayed .......................................TRBL03-1190

TRBL00-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-40

3.29.3 When the drive letter of the Maintenance PC is not displayed or is redundant .TRBL03-1190
3.29.4 When the installation folder of the Maintenance PC software (for
example, C:\Mapp) is deleted by mistake ..........................................................TRBL03-1190
3.29.5 When an Alert Message of an Antivirus Program is Displayed at the
Time of Maintenance PC Installation .................................................................TRBL03-1191
3.29.6 When There Is a Performance Problem of the Maintenance PC ......................TRBL03-1191
3.29.7 When the Alert Message Close programs to prevent information
loss Is Displayed ...............................................................................................TRBL03-1193
3.30 Event log of MPC/SVP ..............................................................................................TRBL03-1200
3.30.1 Reference procedure of the event log of MPC/SVP ..........................................TRBL03-1200
3.30.2 List of event ID of MPC/SVP .............................................................................TRBL03-1240
3.30.3 Actions for Windows Logs Related to Maintenance PC Software/SVP
Software .............................................................................................................TRBL03-1281
3.31 Procedure for Responding to the Used Endurance of Flash Drives, NVMe
Drives, and Flash Module Drives (FMDs) (SIM = 50axyy, 50bxyy, 50cxyy, 50dxyy) .TRBL03-1290
3.32 Recovery Procedure for CFM Patrol Check Error (SIM = ffccxy) ..............................TRBL03-1300
3.33 Recovery Procedure for CUDG Error (SIM = 760000)..............................................TRBL03-1320
3.34 Procedure for responding to the product program expiration (SIM = 7ff7xx) ............TRBL03-1330
3.35 Procedure for responding to an excess of the allowed capacity (SIM = 7ff8xx) .......TRBL03-1340
3.36 Procedure for responding to the prerequisite program product expiration
(SIM = 7ff9xx) ............................................................................................................TRBL03-1350
3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx,
effcxx, effdxx, effexx) .................................................................................................TRBL03-1360
3.37.1 Recovery Procedure when SAS Cable/NVMe Cable Connection Error
Occurs (SIM = effbxx, effdxx, effexx) .................................................................TRBL03-1360
3.37.2 Recovery Procefure when PCIe Cable Connection Error Occurs (SIM
= effcxx)..............................................................................................................TRBL03-1480
3.38 When Detecting Abnormal DB External Temperature (SIM = af7000, af7100) .........TRBL03-1540
3.39 Response to the Detection of Abnormal DKCPS Input Voltage (SIM =
af210x)(Use AC input voltage)...................................................................................TRBL03-1550
3.40 Response to the Occurrence of Battery Warning (SIM = fffa0x) ...............................TRBL03-1600
3.41 Recovery Procedure when a GUM Failure Occurs (SIM = aff1xx) ...........................TRBL03-1610
3.42 Recovery procedure when an alert notification failure occurs (SIM = 7d05xx) .........TRBL03-1630
3.43 Response to a loss of the GUM audit log and the warning issuance (unsent
audit log occurrence) (SIM = 7d03xx, 7d04xx) ..........................................................TRBL03-1660
3.44 Response when UPS warning occurs (SIM = aff0xx) ...............................................TRBL03-1670
3.45 Response to the Occurrence of DBPS Warning (SIM = af50xx, af51xx, af52xx) .....TRBL03-1680
3.46 Response to the Detection of Unmounted Channel Board (SIM = 3c9600) .............TRBL03-1700
3.47 Procedure for Responding to the Firmware Replacement Failure due to
Cache High Load (SIM = eb8xxx, eb9xxx, efexxx)....................................................TRBL03-1710
3.48 Recovery Procedure for the SAS PORT Temporary Failure (SIM = cf11xx) .............TRBL03-1720
3.49 Procedure for Responding to the Flash Module Drive Firmware Version
Warning (SIM = 50f000) ............................................................................................TRBL03-1740
3.50 Recovery Procedure When DKC Warning Occurs (SIM = 7d0900) ..........................TRBL03-1750
3.51 Recovery Procedure When an MP Error Occurs (SIM = 7d06xy).............................TRBL03-1760

TRBL00-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-50

3.52 Reclaiming the Control Pages Inside the DP-VOL....................................................TRBL03-1780

3.53 Recovery Procedure When SWPK is Blocked (SIM = 2154xx) ................................TRBL03-1790
3.54 Recovery Procedure When the Initial Installation Fails .............................................TRBL03-1800
3.55 Recovery Procedure When the Part Installation Error Occurs (SIM = ffd400) ..........TRBL03-1860
3.56 Recovery Procedure When Flash Module Drive Initialization Fails (SIM =
4c4xxx, 4c5xxx) .........................................................................................................TRBL03-1880
3.57 Recovery Procedure When the Panel Switch Warning (SIM = af4d0x) ....................TRBL03-1910
3.58 Recovery Procedure When Processor Is Blocked (SIM = 3073xx)...........................TRBL03-1920
3.59 Response to a Loss of the DKC Audit Log (SIM = 180000) ......................................TRBL03-1940
3.60 Recovery Procedure When CFM Failure Occurs (SIM = 30750x) ............................TRBL03-1950
3.61 Recovery Procedure for Differential Area Blocking (SIM = 4d1xyy) ..........................TRBL03-1960
3.62 Recovery Procedure for CTL Blocking (SIM = cf880x) .............................................TRBL03-1980
3.63 Recovery Procedure when the Configuration Backup Fails (SIM = 7d0bxx) ............TRBL03-1990
3.64 Response to the Detection of SWPK Temperature Warning (SIM = af46xx) ............TRBL03-2010
3.65 Response to the Occurrence of CHBBFAN Warning (SIM = af4c0x)........................TRBL03-2020
3.66 Response to the Occurrence of CHBBPS Warning (SIM = af4a0x) .........................TRBL03-2030
3.67 Response to the Detection of Abnormal CHBBPS Input Voltage (SIM = af4b0x) .....TRBL03-2050
3.68 Recovery Procedure When the CHBB Firmware Update Occurs (SIM =
afa0xx, afa1xx, afa2xx)..............................................................................................TRBL03-2070
3.69 Recovery Procedure When an Incorrect CFM Type or a Shortage of CFM
is detected (SIM = fe030x) ........................................................................................TRBL03-2080
3.70 Procedure for Version Downgrade from the Configuration Using HSAE Server .......TRBL03-2090
3.71 Recovery Procedure When the GUM Failure Occurs (SIM = 7d00xx)......................TRBL03-2100
3.72 Recovery Procedure When the SAS CTL Failure Is Detected (SIM = cf13xx) .........TRBL03-2120
3.73 Recovery Procedure for Cache Area Failure (SIM = fff40x) ......................................TRBL03-2130
3.74 Recovery Procedure When a CFM Failure Occurs in the CTL Other Than
the Failed CTL to Be Replaced .................................................................................TRBL03-2140
3.75 Recovery Procedure When a CFM Failure Occurs in the CTL Other Than
the CTL Removed for Maintenance (for VSP G130) .................................................TRBL03-2150
3.75.1 Recovery Procedure for a CFM Failure in CTL2 When CTL1 Is
Removed for Maintenance .................................................................................TRBL03-2151
3.75.2 Recovery Procedure for a CFM Failure in CTL1 When CTL2 Is
Removed for Maintenance .................................................................................TRBL03-2153
3.76 Recovery Procedure When Media Sanitization Ends (SIM = 4e4xxx,
4e6xxx, 4e8xxx).........................................................................................................TRBL03-2160
3.77 Recovery Procedure for Transmitted data abnormality between MP and
GUM (SIM = 14200x) ................................................................................................TRBL03-2170
3.78 Recovery Procedure for Multiple Errors of DKCPS/BKM in CBSN ...........................TRBL03-2180
3.79 Recovery Procedure for Environmental Microcomputer Warning (SIM = af300x) ....TRBL03-2240
3.80 Recovery Procedure for Channel Port Blockade (SIM = 2120xx) .............................TRBL03-2250
3.81 Recovery Procedure for Warning of Accelerator Fan Module (ACLF) type
(SIM = 3c9800) ..........................................................................................................TRBL03-2260
3.82 Recovery Procedure for ENC Error (SIM = af80xx, af81xx, af82xx) .........................TRBL03-2270
3.83 Recovery Procedure When an MP Patrol Check Error Occurs (SIM = 39b0xx) .......TRBL03-2280

TRBL00-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-60

4. Recovery from Open Platform Failure ...................................................................................TRBL04-10

4.1 Recovery Procedure for a Failure on Host Fibre Channel Interface ...............................TRBL04-10
4.1.1 Outline .....................................................................................................................TRBL04-10
[Link] Possible Failures and causes of them .............................................................TRBL04-10
[Link] Matters must be or desirable to be checked ....................................................TRBL04-20
4.1.2 Recovery Procedure When Device Is Not Recognized ...........................................TRBL04-50
4.1.3 Procedure for Checking Storage System Port Status .............................................TRBL04-80
4.1.4 Procedure for Checking Normalcy of the CHB ........................................................TRBL04-90
4.1.5 Procedure for Checking Status Information of LDEV ............................................TRBL04-100
4.1.6 Isolation Procedure for Fibre Channel Failure.......................................................TRBL04-110
4.1.7 Procedure for Checking Operation Mode of Port ..................................................TRBL04-151
4.2 Pinned track recovery ...................................................................................................TRBL04-160
4.2.1 Pinned Tracks ........................................................................................................TRBL04-160
4.2.2 Error Types ............................................................................................................TRBL04-170
[Link] ECC/LRC Error ..............................................................................................TRBL04-190
[Link] Write Error .....................................................................................................TRBL04-210
[Link] External VOL Write Error ...............................................................................TRBL04-220
[Link] External VOL Read Error ...............................................................................TRBL04-221
4.2.3 Procedure for Erasing Pinned Track .....................................................................TRBL04-230
[Link] HP-UX Procedure ..........................................................................................TRBL04-310
[Link] Procedure on Windows..................................................................................TRBL04-470
[Link] Procedure on Solaris .....................................................................................TRBL04-740
[Link] Procedure on AIX, Linux ................................................................................TRBL04-930
[Link] List of Pin Track Tool Directories .................................................................TRBL04-1080
[Link] ECC/LRC Error Recovery Processing of DP pool-VOL ...............................TRBL04-1090
[Link] Recovery from External VOL Write Error .....................................................TRBL04-1130
[Link] Recovery from External VOL Read Error.....................................................TRBL04-1150
[Link] Recovery Processing of the Device in the External Storage System ..........TRBL04-1170
[Link] Using Failed LBA Output Tool ....................................................................TRBL04-1200
4.3 Recovery Procedure for AL_PA Conflict (SIM = 2190xy) ............................................TRBL04-1240
4.4 Recovery Procedure for a Failure on Host iSCSI Interface ........................................TRBL04-1260
4.4.1 Outline .................................................................................................................TRBL04-1260
[Link] Possible Failures and causes of them .........................................................TRBL04-1260
[Link] Matters must be or desirable to be checked ................................................TRBL04-1270
4.4.2 Recovery Procedure When Device Is Not Recognized .......................................TRBL04-1280
4.4.3 Procedure for Checking Storage System Port Status .........................................TRBL04-1320
4.4.4 Procedure for Checking Normalcy of the CHB ....................................................TRBL04-1330
4.4.5 Procedure for Checking Status Information of LUN or LDEV for which
Namespace ID Is Set .........................................................................................TRBL04-1340
4.5 Recovery Procedure When Disconnection of Host Is Detected during iSCSI
Firmware Update (SIM = 3c97xx) ..............................................................................TRBL04-1350
4.6 Procedure When Open System Host Reservation Is Detected (SIM = ac9100) .........TRBL04-1360

TRBL00-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-70

5. ShadowImage Error Recovery...............................................................................................TRBL05-10

5.1 Recovery Procedure for ShadowImage Suspend Pair (SIM = 47dxyy, 7ff102, 47e700) TRBL05-10
5.2 ShadowImage Initialize procedure ..................................................................................TRBL05-50
5.3 Recovery Procedure for Pinned Track ............................................................................TRBL05-60

6. TrueCopy Error Recovery ......................................................................................................TRBL06-10

6.1 TrueCopy Error Recovery Procedure ..............................................................................TRBL06-10
6.1.1 Recovery for TrueCopy Error ..................................................................................TRBL06-20
6.1.2 TrueCopy Path Recovery Procedure .......................................................................TRBL06-90
6.1.3 TC Pair Recovery Operation .................................................................................TRBL06-100
6.1.4 Procedure when the host hangs............................................................................TRBL06-120
6.1.5 Recovery procedure when an error of TrueCopy pair operation occurs................TRBL06-120
6.1.6 Special note of pair recovery procedure when SIM=d4fy-yy is generated ............TRBL06-130
6.2 Pinned Track Recovery Procedure for TrueCopy .........................................................TRBL06-140
6.3 Recovery Action of Path Status Error ...........................................................................TRBL06-160
6.4 Failure Recovery Procedure and Planned Shutdown Procedure of the TC-
UR Configuration (Multi Target/Cascade) ....................................................................TRBL06-190
6.4.1 Failure Recovery Procedure of the TC-UR Configuration (Multi Target/Cascade) TRBL06-190
6.5 Failure Recovery Procedure and Planned Shutdown Procedure of the TC-
UR Delta Configuration (Multi Target)..........................................................................TRBL06-340
6.5.1 Failure Recovery Procedure of the TC-UR Delta Configuration (Multi Target) ......TRBL06-340
6.6 DKC Planned Shutdown Procedure of the TC-UR Configuration (Multi Target) ...........TRBL06-410
6.6.1 Planned Shutdown Procedure of the PDKC..........................................................TRBL06-410
6.6.2 Planned Shutdown Procedure of the LDKC ..........................................................TRBL06-440
6.6.3 Planned Shutdown Procedure of the RDKC .........................................................TRBL06-460
6.7 DKC Planned Shutdown Procedure of the TC-UR Configuration (Cascade)................TRBL06-480
6.7.1 Planned Shutdown Procedure of the PDKC..........................................................TRBL06-480
6.7.2 Planned Shutdown Procedure of the IDKC ...........................................................TRBL06-510
6.7.3 Planned Shutdown Procedure of the RDKC .........................................................TRBL06-540
6.8 DKC Planned Shutdown Procedure of the TC-UR Delta Configuration (Multi Target) ..TRBL06-560
6.8.1 Planned Shutdown Procedure of the PDKC..........................................................TRBL06-560
6.8.2 Planned Shutdown Procedure of the LDKC ..........................................................TRBL06-590
6.8.3 Planned Shutdown Procedure of the RDKC .........................................................TRBL06-610
6.9 Planned Shutdown Procedure of All DKCs in 3DC Configuration .................................TRBL06-630

7. Recovery from UR Failure .....................................................................................................TRBL07-10

7.1 Recovery Procedure for UR Failure ................................................................................TRBL07-10
7.2 Procedure for Recovering UR Pair .................................................................................TRBL07-80
7.3 Force Delete Pair Operation .........................................................................................TRBL07-110
7.4 Procedure for UR Pinned Track Recovery and Journal Volume Replacement .............TRBL07-130

TRBL00-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-80

7.5 Failure Recovery Procedure and Planned Shutdown Procedure of the UR-
UR delta Configuration ................................................................................................TRBL07-180
7.5.1 Failure Recovery Procedure of the UR-UR delta Configuration ............................TRBL07-180
7.5.2 DKC Planned Shutdown Procedure of the UR-UR delta Configuration ................TRBL07-410
[Link] Planned Shutdown Procedure of the PDKC ..................................................TRBL07-410
[Link] Planned Shutdown Procedure of the LDKC ..................................................TRBL07-470
[Link] Planned Shutdown Procedure of the IDKC ...................................................TRBL07-490
[Link] Planned Shutdown Procedure of the RDKC ..................................................TRBL07-520

8. Recovery from Thin Image/Thin Image Advanced Failure.....................................................TRBL08-10

8.1 Recovery Procedure for Thin Image/Thin Image Advanced Failure due to
SM Volatilization (SIM = 47ec00) ..................................................................................TRBL08-10
8.2 Recovery Procedure for Thin Image/Thin Image Advanced Failure (SIM =
4b3xyy, 7ff104) ..............................................................................................................TRBL08-20
8.3 Recovery Procedure for Pool Failure (SIM = 602xxx, 604xxx, 605xxx, 606xxx) ............TRBL08-40
8.4 Recovery Procedure for Pool Failure (SIM = 603000) ....................................................TRBL08-90
8.5 Recovery Procedure for Thin Image pool-VOL ECC/LRC Error ...................................TRBL08-100
8.6 Recovery Procedure for Thin Image/Thin Image Advanced Failure (SIM = 670000) ...TRBL08-110
8.7 Recovery Procedure for Thin Image pool-VOL Failure .................................................TRBL08-120
8.8 Recovery Procedure for Thin Image I/O Performance Degradation Alert (SIM
= 670100) ....................................................................................................................TRBL08-130

9. Recovery from Volume Migration Failure...............................................................................TRBL09-10

9.1 Recovery Procedure for Volume Migration Failure .........................................................TRBL09-20

10. Failure recovery of Dynamic Provisioning ...........................................................................TRBL10-10

10.1 Recovery Procedure for pool-VOL Blockade (When Two (Three in RAID6)
or More Are Blocked in the RAID Gr the pool-VOL Belongs) ........................................TRBL10-10
10.2 Recovery Procedure for Pool Failure (SIM = 623xxx)...................................................TRBL10-70
10.3 Recovery Procedure for Pool Failure (SIM = 624000) ................................................TRBL10-100
10.4 Recovery Procedure for Pool Failure (SIM = 62b000) ................................................TRBL10-110
10.5 Recovery Procedure for pool-VOL Blockade (SIM = 627xxx) .....................................TRBL10-120
10.6 Procedure for Releasing Protect Attribute of Data Retention Utility (SIM = 628000) ..TRBL10-140
10.7 Deleting Procedure for Pool at the time of pool-VOL Blockade (When
External Volume the pool-VOL Belongs Is Removed) .................................................TRBL10-150
10.8 Initialization Procedure for Pool ..................................................................................TRBL10-170
10.9 Recovery Procedure for Dynamic Provisioning by Turning Off the Power
and Volatilizing PS ON ................................................................................................TRBL10-190
10.10 Disabling Procedure for Accelerated Compression Setting of Parity Group .............TRBL10-210
10.11 Recovery Procedures from Failures on Pool Creation, Expansion, and Deletion .....TRBL10-230
10.12 Recovery Procedure When Automatic Pool Capacity Expansion Failed
due to a Pool-associated Factor (SIM = 632xxx) ........................................................TRBL10-320

TRBL00-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-90

11. External Storage System Maintenance................................................................................TRBL11-10

11.1 Maintenance of External Storage System .....................................................................TRBL11-10
11.1.1 Considerations When Performing Maintenance Work on External
Storage System......................................................................................................TRBL11-10
11.1.2 Maintenance (Isolation) Procedure for a Failure on External Storage
System (SIM = 21d0xx, 21d2xx, efd000, ef5xxx, ff5xxx) .......................................TRBL11-40
11.1.3 Procedure for Operating Storage Navigator ..........................................................TRBL11-50
11.2 Recovery Procedure for External Device Failure ..........................................................TRBL11-60
11.2.1 Recovery Procedure for Path Failure While Device is Blocked (SIM =
21d0xx, efd000) .....................................................................................................TRBL11-60
11.2.2 Recovery Procedure for Path Single Failure (SIM = 21d0xx) ................................TRBL11-80
11.2.3 Recovery Procedure for External storage system response delay (SIM
= 21d2xx) ............................................................................................................. TRBL11-110
11.2.4 Action When External Device and External Volume Are Not Recognized ...........TRBL11-120
11.3 Elimination Procedure for Pinned Data on External Storage System .........................TRBL11-140
11.4 Procedure for Operating External Device LBA Conversion Tool .................................TRBL11-160
11.5 Considerations When Performing Data Recovery on External Volume ......................TRBL11-270

12. Recovery from SNMP Failure ..............................................................................................TRBL12-10

12.1 Recovery Procedure for SNMP Test .............................................................................TRBL12-10
12.2 When Trap Cannot Be Received While Ping Reaches Manager PC
Prepared by Customer ..................................................................................................TRBL12-20
12.3 SNMP Trap Information.................................................................................................TRBL12-30

13. Failure recovery of Encryption License Key ........................................................................TRBL13-10

13.1 Recovery procedure when acquisition failure from key management server
(SIM = 661000, 661001)................................................................................................TRBL13-10
13.2 Recovery procedure for Encryption key threshold warning and depletion
(SIM = 660100, 660200)................................................................................................TRBL13-20
13.3 Recovery procedure of DKB failure when restoring Encryption Keys ...........................TRBL13-30

14. MP Blockade Reset Function ..............................................................................................TRBL14-10

15. Forced Outage and Restart of DKC/DB...............................................................................TRBL15-10

15.1 Non volatilization power-off and restarting procedure ...................................................TRBL15-20
15.2 Forced volatilization (full) power-off and restarting procedure 1-1 ................................TRBL15-80
15.3 Forced volatilization (full) power-off and restarting procedure 1-2 ..............................TRBL15-100
15.4 Forced volatilization (part) power-off and restarting procedure 2-1 ............................TRBL15-130
15.5 Forced volatilization (part) power-off and restarting procedure 2-2 ............................TRBL15-150

16. Recovery Procedure for GUM Information Recover Failure (SIM = 7d08xx) ......................TRBL16-10

17. Recovery Procedure for GUM Version Warning (SIM = 7d0axx).........................................TRBL17-10

TRBL00-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-100

18. Recovery from Global-active Device Functions Failure .......................................................TRBL18-10

18.1 Recovery Procedure for Global-active Device Functions Failure .................................TRBL18-10
18.1.1 Recovery Procedure at Failure Suspension of a GAD Pair (SIM = ddxyzz)..........TRBL18-20
18.1.2 Recovery Procedure at LDEV Block in the GAD Pair (SIM = 3a0xyy,
db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx, dfbxxx, ef8xxx, ef9xxx) .........................TRBL18-80
18.1.3 Procedure to Recover Data from Backup Data at LDEV Failure in the
GAD Environment ................................................................................................TRBL18-100
18.1.4 Recovery Procedure of the Pinned Track in the GAD Environment ....................TRBL18-120
18.1.5 Recovery Procedure at Quorum Disk Failure (SIM = def0xx) .............................TRBL18-150
18.1.6 Recover Path Failure Between a GAD Pair in the GAD Environment.................TRBL18-170
18.2 Recovery Procedure When a Failure Occurred While Creating/
Resynchronizing a GAD Pair .......................................................................................TRBL18-200
18.3 Failure Recovery Procedure and Maintenance Procedure of the GAD-UR
delta Configuration ......................................................................................................TRBL18-220
18.3.1 Failure Recovery Procedure of the GAD-UR delta Configuration .......................TRBL18-220
18.3.2 GAD-UR delta Configuration Maintenance Procedure ........................................TRBL18-350
[Link] Maintenance Procedure...............................................................................TRBL18-350
[Link] Planned Shutdown Procedure of the DKC of the GAD-UR delta
Configuration ...............................................................................................TRBL18-370

19. Recovery Procedure when the Maintenance Utility from Hitachi Device
Manager (Storage Navigator) Fails to Start or a Communication Error Occurs
between SVP and DKC..........................................................................................................TRBL19-10

20. dedupe and compression Error Recovery ...........................................................................TRBL20-10

20.1 Recovery Procedure for dedupe and compression Operation Error (SIM = 680001) ...TRBL20-10
20.2 Recovery Procedure for Operation Error in Deleting Capacity-Saving-
Enabled DP-VOLs (without blocking/formatting) (SIM = 680002) .................................TRBL20-50
20.3 Recovery Procedure when Operation Error of Deduplication System Data
Volume Automatic Deletion is Detected (SIM = 681xxx) ...............................................TRBL20-80
20.4 Recovery Procedure when Deduplication System Data Volumes are
Suspended (SIM = 682000) ..........................................................................................TRBL20-90
20.5 Procedure for Initializing All DP-VOLs for Which Capacity Saving
Is Enabled, Deduplication System Data Volumes (Fingerprint), and
Deduplication System Data Volumes (Data Store) in a Pool .......................................TRBL20-110
20.6 Recovery Procedure When an Operation Error Is Detected While the
Compression Acceleration Settings for Deduplication System Data
Volumes Are Changed (SIM = 689xxx) .......................................................................TRBL20-130
20.7 Recovery Procedure When the Compression Acceleration Settings for
Deduplication System Data Volumes Are Invalid after Duplicated Data Initialization ..TRBL20-140
20.8 Recovery Procedure When Access to Metadata for dedupe and
compression Fails (SIM = 68bxxx) ..............................................................................TRBL20-150
20.9 Recovery Procedure When Inline Deduplication Process by dedupe and
compression Is Delayed (SIM = 68a000) ....................................................................TRBL20-160

TRBL00-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL00-110

21. Dump Collection Troubleshooting ........................................................................................TRBL21-10

22. Procedure to Be Performed before Downgrading Firmware Version under the

Configuration that Uses Veeam Backup & Replication ..........................................................TRBL22-10

23. Recovery Procedure for Corruption of GUM Configuration Information (SIM 7d0d0x) ...TRBL23-10

24. Procedure When Warning Threshold for Cache Write Pending Rate Is
Exceeded (SIM = 493xyy)......................................................................................................TRBL24-10

25. Procedure When Overload of Cache Occurs (SIM = 491000) ............................................TRBL25-10

26. Procedure When Alert Settings Are Initialized due to a Failure At the Time of
CTL Replacement ..................................................................................................................TRBL26-10

27. Procedure for Checking the Snapshot Data Retention Period Setting for Thin
Image Advanced Pairs ...........................................................................................................TRBL27-10

28. Procedure for Disabling the Snapshot Data Retention Period Setting for Thin
Image Advanced Pairs ...........................................................................................................TRBL28-10

29. Procedure for Downgrading Firmware When the Configuration Includes a Thin
Image Advanced Pair for Which the Snapshot Data Retention Period Setting Is Enabled ....TRBL29-10

TRBL00-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL01-10

NOTICE: On the storage system with the Automatic Log Dump Collection enabled, the
automatic dump collection is performed on the SVP when specific SIMs are
generated. If you perform the maintenance work during the automatic dump
collection, the automatic dump collection might fail.
• If you can ask a customer to operate the SVP, ask the customer to check whether
the automatic log dump collection is being executed on the SVP screen before you
start the maintenance work. If the automatic dump collection is being executed,
wait for the automatic dump collection to complete or ask the customer to stop the
automatic dump collection. For how to check the dump collection state on the SVP
screen and how to stop the dump collection, see System Administrator Guide.
• If you can operate the SVP, check whether the automatic log dump collection is
being executed on the SVP screen before starting the maintenance work. If the
automatic dump collection is being executed, wait for the automatic dump collection
to complete or stop the automatic dump collection. For details, see MAINTENANCE
PC SECTION “11.14.3 Maintenance Work of Storage System with Automatic Log
Dump Collection Enabled”.
• If the SVP cannot be operated, start the maintenance work. If the automatic dump
collection is being executed, a log indicating a dump collection failure might be
output on the SVP of a customer.
For the Automatic Log Dump Collection, see MAINTENANCE PC SECTION 11.14
Automatic Log Dump Collection .

1. Overview of TRBL
1.1 Flow of Troubleshooting
Perform troubleshooting procedures according to the following cases if a failure notification is received.

1. If a failure notification is sent by the customer:

(1) Checking the customer report and the Storage System status (1.2 Checking Customer Report and
Storage System Status)
(2) Selecting how to perform troubleshooting and performing the recovery actions (2.1 Flow of failed
part isolation)
(3) Checking the normality (2.5 Checking Normality)
2. If a failure occurs during the additional installation, uninstallation, and preventive replacement:
Perform troubleshooting procedures in accordance with each recovery procedure in “2.2 Failure During
Operation by Service Personnel”.
3. If a failure occurs during the firmware update:
Perform troubleshooting procedures in FIRMWARE SECTION “4. Trouble Recovery Procedure in
Firmware Update”.

TRBL01-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL01-20

1.2 Checking Customer Report and Storage System Status

Check the customer report and the status of the Storage System according to the following check items to
identify how to perform troubleshooting first.
Check items Check results How to check
Checking the customer report
Did the server detect a Storage System failure? Check with the customer.
Did a failure occur at the time of the start-up of the
Storage System?
Did a failure occur at the time of the planned
shutdown?
Checking the LED status
Is the POWER LED on the Storage System off? For the LED position and LED
status, see LOCATION SECTION
“3.1 Switches and LEDs of
Controller Chassis”.
Is the CTL ALM LED (red) on the CTL blinking or For the LED position and LED
lit? status, see LOCATION SECTION
“3.2 Other Switches and LEDs”.
Is the ALARM LED (red) on the Storage System lit? For the LED position and LED
Is the WARNING LED (amber) on the Storage status, see LOCATION SECTION
System blinking? “3.1 Switches and LEDs of
Controller Chassis”.
Checking the alerts
Is SIM added? On the “Alerts” window of the
Maintenance Utility, check that
SIM has been added since the last
maintenance work. (*1)
Have failures occurred on multiple parts? (*2) From the [Hardware] menu of the
Maintenance Utility, select all of
chassis, and then check the graphic
on each chassis to see how many
parts the failure icon ( or )
indicates.
*1: • Starting the Maintenance Utility
The maintenance PC needs to be set up in advance. (See MAINTENANCE PC SECTION “1.2
Maintenance PC Setup Workflow”.)
Connect the Maintenance PC to the Storage System, and then start the Maintenance Utility. (See
MAINTENANCE PC SECTION “2.1 Workflow of Settings and Operations of the Maintenance
PC at Clientʼs Site”.)
• Operating the “Alerts” window
See MAINTENANCE PC SECTION “3.21 Alert Display”.
*2: If failures have occurred on multiple parts (part types), the corrective actions need to be taken on a
part with the highest priority first.
Before selecting how to perform troubleshooting, see “2.4 Failures of Multiple Parts” to check the
priority of corrective actions.

TRBL01-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-10

2. Isolation of Failed Part

Note
The correspondence to the document describing the code system, the text and troubleshooting of
the messages that occur during the maintenance work is displayed in MESSAGE SECTION
“1. Messages that Occur During Maintenance Work”.

2.1 Flow of failed part isolation

Select how to perform troubleshooting in accordance with the flowcharts on the next pages, and then perform
the recovery actions.
Each recovery action requires a different maintenance window. After checking the recovery action, open the
required maintenance window by referring to the following table, and then start the operations.

# How to perform troubleshooting Required maintenance window

1 When performing the recovery Continue to use the Maintenance Utility that has started for
actions according to ACC (other checking the alerts.
than “5xxxxxxx”)
2 When performing the recovery After logging out the Maintenance Utility, start the Maintenance
actions according to ACC PC software in accordance with MAINTENANCE PC SECTION
(“5xxxxxxx”) “ Maintenance work by Maintenance PC software “ in “2.1
3 When replacing the drive (*1) Workflow of Settings and Operations of the Maintenance PC at
4 When performing any recovery Clientʼs Site”.
actions other than specified in NOTE: When the Maintenance Utility starts with the Maintenance
items #1 through #3 PC software, the force execution option can be selected on
each operation window. For details, see MAINTENANCE
PC SECTION “11.8 Restrictions on Operations of
Maintenance Utility Started by Specifying IP Address of
CTL”.
* 1: Only when replacing an unblocked drive, use the “MPC” window for the confirmation procedure
before replacing the drive. (See REPLACEMENT SECTION “1.5.3 Procedure before PDEV
Replacement and Correction Copy” through “1.5.5 How to Search a Work ID to Replace a Drive”.)

TRBL02-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-20

START

Is the POWER Yes See “2.1.10 Turning off POWER LED

LED on the Storage System turned
of the Storage System LED”.
off?

No

Is the CTL ALM Yes See “2.1.7 Blinking or lighting up of

LED (red) on the CTL blinking or
CTL ALM LED (red) on CTL”.
lit?

No

Did the server detect a Yes See “2.1.3 Detecting Storage System
Storage System failure? Failures by a Server”.

No

Does the ALARM Yes See “2.1.4 Lighting up ALARM (red)

LED (red) on the Storage System
of Storage System LED”.
light up?

A No

Did a failure occur at the Yes See “2.1.1 Failures at the Time of
time of the start-up? Start-Up”.

No

Isolate whether the failure is related to the entire Storage System or

occurs under the specified conditions

1 2.5 Checking Normality

(TRBL02-30)

TRBL02-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-30

Did a failure Yes See “2.1.2 Failures at the Time of

occur at the time of the planned
Planned Shutdown (PS OFF)”.
shutdown?

No

Did a failure Yes See “2.2 Failure During Operation by

occur at the time of maintenance
Service Personnel”.
work?

No

Is the
WARNING LED (amber) Yes See “2.1.5 Blinking WARNING
on the Storage System (amber) of Storage System LED”.
Blinking?
No

Is SIM
added in the “Alerts” Yes
See “2.3 Analyze by SIM Log”.
window of Maintenance
Utility?
No

Isolate whether the failure occurs in an individual part

T.S.D. call
2.5 Checking Normality

TRBL02-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-40

2.1.1 Failures at the Time of Start-Up

START

Yes
All LED off?

No Check the PDU breakers

Does the ALARM LED Yes

light up?

No See 2.1.4 Lighting up ALARM

(red) of Storage System LED .
Does the Yes
WARNING LED light up or
Blink?
Open the Maintenance window of
No Maintenance PC.

Does the
READY LED on the Yes Did a
Storage System light communication error Yes
up? between MPC software and
No DKC occur?
1
Have (TRBL02-41) No
20 seconds Display the Alerts window of
passed since the main No Maintenance Utility to recover the
switch was turned on? Does the failure part. (See MPC03-1130.)
POWER LED light
in amber?
3
Yes (TRBL02-43) See 2.3 Analyze by SIM Log .

No Did 180
minutes elapse from PS ON?
(*1) See 2.1.4 Lighting up ALARM
(red) of Storage System LED .
Yes

4
(TRBL02-50)

*1: When you power on the storage system, the battery must be charged to 30 percent or above. If the
battery is fully discharged, it might take up to 90 minutes to power on the storage system.

TRBL02-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-41

Open the “Maintenance” window of

Maintenance PC.

Did a
communication error between Yes
MPC software and DKC
occur? Open the “Maintenance” window of
Maintenance PC from the CTL in the
No
other cluster.
Is the
status of the storage system Yes Did a
on Maintenance Utility still in “Power-on in Yes
communication error between
progress” after 20 minutes has
MPC software and DKC
passed?
occur?
No
No
Display the “Alerts” window of
Display the “Alerts” window of
Maintenance Utility to recover the
Maintenance Utility to recover the
failure part. (See MPC03-1130.)
failure part. (See MPC03-1130.)

See “2.3 Analyze by SIM Log”.

See “2.3 Analyze by SIM Log”.

Check the Maintenance

Perform steps 1 through 4 in PC settings. (*1)
MAINTENANCE PC SECTION “3.26 (See MPC01-10)
Resetting GUM”.

Execute LAN Check

(See DIAG04-210)

No
Normally ended?

Yes

2
END (TRBL02-42)

*1: See MAINTENANCE PC SECTION “2.3 Settings Other Than those of Maintenance PC Software
at Client's Site” and “2.4 Registering Storage Systems to Be Maintained in Storage Device List” to
check the Maintenance PC settings.

TRBL02-41
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-42

Is the
Storage System CBXSS/ Yes
CBXSL/CBSS/CBSL/
CBSN?
No
Replace the LANB
(See REP02-11-10.)

Execute LAN Check

(See DIAG04-210.)

No
Normally ended?

Yes

END

Replace the CTL

(See REP02-04-10.)

Execute LAN Check

(See DIAG04-210.)

No
Normally ended?

Collect dump
Yes (See MPC05-50.)

END T.S.D Call

TRBL02-42
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-43

Turn off the breaker of the Storage

System, and then turn it on.

Remove the CTL2.

(See REP02-04-10.)

Is the POWER LED No

turned off?
Turn on the main switch.
Yes
Install the removed CTL2.
(See REP02-04-10.) Is the Yes
POWER LED light changed to 5
green? (TRBL02-44)
Remove the CTL1.
(See REP02-04-10.) No

T.S.D Call
Is the POWER LED No
turned off?
Turn on the main switch.
Yes

Is the Yes
POWER LED light changed to 6
green? (TRBL02-44)
No

T.S.D Call

TRBL02-43
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-44

Does
the READY LED
of the storage system light up? Yes
For the approximate time required for the
LED to light up in green, see
INST01-05-10. Replace removed CTL2 with new one.
(See REP02-04-10.)

No

Yes
T.S.D Call Normally ended?

No

Perform the recovery procedure END

in (TRBL02-260).

Does
the READY LED
of the storage system light up? Yes
For the approximate time required for the
LED to light up in green, see
INST01-05-10. Replace removed CTL1 with new one.
(See REP02-04-10.)

No

Yes
T.S.D Call Normally ended?

No

Perform the recovery procedure END

in (TRBL02-260).

TRBL02-44
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-50

Open the “Maintenance” window of

Maintenance PC.

Did a
communication error between No
MPC software and DKC
occur?

Yes See “3.3 Recovery procedure when

DB power off was detected or when
PS OFF (*1)
SAS/NVMe port blockage occurred
(SIM = ac50xx, cf12xx, cf22xx)”.
Breaker OFF.

Check whether installation locations

and types of DIMMs and CFMs are
correct. (See DIMM: REP02-05-10,
CFM: REP02-10-10.)

Breaker ON.

PS ON

Did it start up No
normally?

Yes

END T.S.D Call

*1: If it does not change to the PS OFF status (POWER LED changes from green to amber) even after
waiting for about one minute, go to the next step

TRBL02-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-60

2.1.2 Failures at the Time of Planned Shutdown (PS OFF)

NOTE: • When SIM= af300x (environmental microcomputer warning) is reported, perform “3.79 Recovery
Procedure for Environmental Microcomputer Warning (SIM = af300x)”, and then power off the
storage system (planned shutdown).
• Reporting the SIM of Reference Code “SIM = 388f00” or “SIM = 389f00” might take 10 minutes
or more. Especially, if the emergency destage does not terminate, the reporting might take about
one hour.
• Even after the SIM of Reference Code “SIM = 388f00” or “SIM = 389f00” was reported, the
planned shutdown processing (PS OFF) might terminate normally.
• While mapping the external storage volume by the Universal Volume Manager function, if the
external storage performs the planned shutdown (PS OFF) first or the power failure occurs, the
Storage System might not turn off the power by the planned shutdown (PS OFF) (because the
Cache Write Pending data for the mapped external volume remains).
In this case, “SIM = 388f00” that indicates planned shutdown (PS OFF) impossible is reported. To
avoid the problem, perform the following procedure.
[Link] the external storage once.
[Link] the external storage by the Universal Volume Manager function in the Storage
System.
[Link] that the Storage System completed the planned shutdown and the READY LED on the
Controller Chassis turned off.
[Link] the planned shutdown (PS OFF) procedure of the external storage.
• In the case SIM = 62axxx is output for a pool that contains a virtual volume with capacity saving
enabled, PS OFF cannot be performed. Take the following procedure:
[Link] non-volatile PS off for the storage system (see “15.1 Non volatilization power-off and
restarting procedure”.
[Link] on the storage system (see INSTALLATION SECTION “1.5.1 Storage System Power
On”.
[Link] the user to take the actions as indicated in SIM = 62axxx.
[Link] off the storage system (see INSTALLATION SECTION “1.5.2 Storage System Power Off
(Planned Shutdown)”.

TRBL02-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-61

START

Does the POWER LED

light up in amber after the planned
shutdown operation (PS OFF)? Does either of the No
following also occur?
 The READY LED or ALARM LED lights up.
 The WARNING LED lights up or
blinks. Does the
No POWER LED still light up in
1 green after 60 minutes have passed since the
Yes planned shutdown operation (PS
(TRBL02-70) OFF)?

Yes
Open the “Maintenance Utility” window.

Yes Did a communication

error between MPC software and DKC
occur?

No

Collect the Auto Dump (see MPC05-50) 4

and contact the Technical Support Division. (TRBL02-80)

TRBL02-61
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-70

Is SSB
= 00a3 output in the same Yes
time zone as SIM is output? (See 3 (TRBL02-80)
MPC05-250.)

No
Does
Is Initial Installation a SIM log have only No
or Disruptive Installation or No Reference Code =
Disruptive De-installation procedure “af300x”?
in execution?
Yes
2
Yes
Can the No
Retry the procedure which is Initial “Maintenance Utility” window
Installation or Disruptive Installation be operated?
or Disruptive De-installation.
Yes T.S.D. call
Recover according to ACC
of the SIM, and retry PS OFF
Is storage operation.
system Initial Installation or No
Disruptive Installation or Disruptive
De-installation normally?
Collect Auto Dump (Normal).
(See MPC05-50.)
Yes
2
T.S.D. call

Does the SIM of No

Reference Code = “388f00” or 4
“389f00” exist?
(TRBL02-80)

Yes

Collect Auto Dump (Normal).

(See MPC05-50.)

T.S.D. call

TRBL02-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-80

3
(*1)

When the Storage System is connected to the UPS or the

server using the UPS connector, remove the connection
cable. (*2)

In accordance with “3.60 Recovery Procedure When CFM

Failure Occurs (SIM = 30750x)”, replace the abnormal CFM
so that all CFMs are in the normal state.

END

*1: Do not power off the Storage System until all CFMs become the normal state. If you power off the
Storage System while abnormal CFMs exist, the customer data might be lost.
*2: After completing all this recovery procedure, connect the removed connection cable to the UPS
connector again.

Yes
Is the site using UR?

If the operations (*3) that should be done before

No
PS OFF are not performed yet, perform them.

Is WRITE
PENDING DATA of the cache Yes
under decreasing?
See MPC06-10.

No

Have 20 minutes
past after the time that No
WRITE PENDING DATA of the cache
stopped decreasing?
See MPC06-10.
Is PS OFF
completed with POWER LED No
Yes 2
(amber) lit up? (See INST01-
Collect Auto Dump (Normal). 05-40.) (TRBL02-70)
(See MPC05-50.)
Yes
T.S.D. call END

*3: For the operations that should be done before PS OFF, see “Powering-off the primary or secondary
storage system” in Hitachi Universal Replicator User Guide.

TRBL02-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-90

2.1.3 Detecting Storage System Failures by a Server

START

Does the DKC Yes See “2.1.4 Lighting up ALARM

ALARM LED light up? (red) of Storage System LED”.

No

Does the
No
POWER LED of the DKC
light?
Is the
Yes AC breaker of the device No
connected with the DKC
on?
Yes
There is a possibility of a power Turn on the AC breaker of the
outage or a power failure in the DKC, and turn on the PS ON of
equipment. Confirm whether a the device.
power outage occured and there is
an abnormality in the equipment.

Has a power
outage occurred or is there No
an abnormality exists in the
equipment?

Yes

After removing the cause of the Execute the search of the DKCPS
power outage or the power failure failure.
in the equipment, turn on the PS (Refer to “3.20 Response to the
ON of the device. Occurrence of DKCPS Warning
(SIM = af200x)”.)
Has the job been No
abnormally ended?

Yes No Is there
repeatability?

Yes
Collect the command and trace
using the server.

1 (TRBL02-100)

TRBL02-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-100

Check SIM logs and ACC.

(Refer to the MAINTENANCE PC, SIM RC and ACC
(ACTION CODE) SECTIONs.)

Was the related Yes

SIM reported?
Execute troubleshooting in accordance
No
with “2.3 Analyze by SIM Log”
(TRBL02-640).

No Has the failure

been recovered?

Yes

END
Is there any failed CHL, connector, Yes
or cable? (See TRBL04-20.)
Replace the failed connector or cable.
No

No Has the failure

been recovered?

Yes

END
Are the system configuration No
information and the PCB jumper settings
correct?
Set the system configuration information
and the PCB jumper settings correctly.
Yes

No Has the failure

been recovered?

Yes
2
(TRBL02-110)
END

TRBL02-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-110

Is it possible to stop No
the system once? (*1)

Yes
Execute the PS off -> PS on.

Is a failure No
detected?

Yes
Reboot the system.
Troubleshoot the failed part using the
ACC of the detected failure.

Has the failure Yes

been recovered?

No
END

T.S.D Call

*1: Ask the customer whether he or she allows you to stop the storage system for investigation and
recovery.

TRBL02-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-120

2.1.4 Lighting up ALARM (red) of Storage System LED

START

Is I/O operation Yes

available from host computer?

Open the Maintenance window of

No Maintenance PC.
Open the Maintenance window of
Maintenance PC.
Did a
Yes communication error
1 between MPC software and
Did a
(TRBL02-130) DKC occur?
communication error No
between MPC software and No
DKC occur? Are
both the
Yes
4 following true?
SIM = cf88xx is reported.
Check the IP addresses of the SIM = fff7xx, 2130xx, 2140xx, or No
management port, maintenance port, ff21xx is reported for the parts installed
and internal network, and then write in the other CTL than the CTL
them down. (See MPC03-510) specified by SIM =
cf88xx.
Collect Dump/Log.
(See MPC05-50, MPC05-250) Yes

Is the READY LED of No

9 the storage system off?
(TRBL02-121) Check the IP addresses of the
Yes management port, maintenance port,
and internal network, and then write
Perform the power-off procedure.
them down. (See MPC03-510)
Remove the parts specified by action
codes of SIM = fff7xx, 2130xx,
2140xx, or ff21xx. A
(TRBL02-20)
Perform the power-on procedure.

Is the
READY LED of the No
storage system turned
on?
Yes T.S.D. call
Install new maintenance parts instead
of the removed parts.

Open the Maintenance Utility

window and check whether there are
other blocked parts. If any, replace
them with maintenance parts.

END

TRBL02-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-121

Is storage
system power down
available? (obtain customers No
permission and check
usage status) (*1)
T.S.D. call

Yes
Check and take a note of the states of
lights of the LEDs on all Controller
Boards, Channel Boards, Disk
Boards, and Controller Chassis that
are installed. (See LOC03-10)

PS OFF

Is storage Yes
system powered OFF 6
normally? (TRBL02-140)

No
Open the Maintenance window of
Maintenance PC.

Did a
communication error Yes
between MPC software and 8
DKC occur? (TRBL02-150)

No

Status of CACHE of Yes

CTL1 is normal?

No Status of CACHE of Yes

CTL2 is normal?

No 5
(TRBL02-140)

T.S.D. call

*1: Ask the customer whether he or she allows you to stop the storage system for investigation and recovery.

TRBL02-121
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-130

Close the “Maintenance Utility”

window.

Reboot MPC.

Check the LAN cables between

the DKC and the MPC.

Is the
communication error between Yes
MPC software and DKC
eliminated?

No
Replace the PC.
(then install the latest Firmware)

Is the
communication error between Yes
MPC software and DKC
eliminated?

No

4
(TRBL02-120) See “2.3 Analyze by SIM Log”.

TRBL02-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-140

Breaker OFF.

Wait for 1 minutes.

Does the BACKUP Yes

STS LED on the Controller Board
light up?

No (blinking or go out) No
Does the lighting continue for
three minutes or more?

Is the BACKUP STS Yes (*1) Yes

LED on the Controller Board
blinking?

No (light up or go out)

Breaker ON.

Wait for 30 seconds

The POWER LED on Yes

the Controller Chassis lights up in
green?

No
6

PS ON

2 (TRBL02-160)

*1: The blinking duration time of the BACKUP STS LED varies depending on the Storage System
models.
VSP G130: 10 minutes
VSP G350, VSP F350: 10 minutes
VSP G370, VSP F370: 20 minutes
VSP G700, VSP F700: 20 minutes
VSP G900, VSP F900: 20 minutes
VSP E590, VSP E790: 10 minutes
VSP E990, VSP E1090: 20 minutes

TRBL02-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-150

Remove the power cables only from the controller

chassis to disconnect the power. (See LOC02-20)

Wait for 1 minutes.

Does the
BACKUP STS LED on the Yes
Controller Board
light up?
No (blinking or go out) Does the lighting continue for No
three minutes or more?

Is the
BACKUP STS LED on the Yes (*2) Yes
Controller Board
blinking?
No (light up or go out)

Replace the controller board and cache memories offline at the same time referring to the following procedure. (*3)
Perform it for the both Controller Boards.
• CBXSS/CBXSL: REPLACEMENT SECTION “2.4.3 Replacing a Controller Board for CBXSS/CBXSL”, Step 4. “CBXSS/
CBXSL Controller Board Replacement Processing” only
• CBSS/CBSL: REPLACEMENT SECTION “2.4.1 Replacing a Controller Board for CBSS/CBSL”, Step 4. “CBSS/CBSL
Controller Board Replacement Processing” only
• CBLH: REPLACEMENT SECTION “2.4.2 Replacing a Controller Board for CBLH”, Step 4. “CBLH Controller Board
Replacement Processing” only
• CBSN: REPLACEMENT SECTION “2.4.4 Replacing a Controller Board for CBSN”, Step 4. “CBSN Controller Board
Replacement Processing” only

Connect the power cables to the controller chassis.

(See LOC02-20)

Set the IP address of the internal network that you have written
Set the Storage System to PS ON.
down in advance to the internal network in accordance with
the MAINTENANCE PC SECTION “3.6.1 Network Setting”.
Wait for 30 seconds (Select the check box for “Forcibly run without safety checks”,
and then perform the maintenance work. The checkbox is
displayed only when Maintenance Utility is started from the
“Web Console” window or the “MPC” window. To check the
Is the READY LED lit green on Yes
checkbox, start Maintenance Utility from the “Web Console”
the controller chassis? window or the “MPC” window.)

No Update the GUM firmware in accordance with the FIRMWARE

SECTION “3.3.1 Updating Firmware of the Storage System”.
Use the installation media for the SVP, which comes with the
Storage System and is owned by the customer.

[Check of normality] (TRBL02-300)

T.S.D. call END

TRBL02-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-151

*2: The blinking duration time of the BACKUP STS LED varies depending on the Storage System
models.
VSP G130: 10 minutes
VSP G350, VSP F350: 10 minutes
VSP G370, VSP F370: 20 minutes
VSP G700, VSP F700: 20 minutes
VSP G900, VSP F900: 20 minutes
VSP E590, VSP E790: 10 minutes
VSP E990, VSP E1090: 20 minutes
*3: Ignore the item (1) for checking the ALM LED, Step 4 in the procedures to refer to.
Furthermore, in the item (6) for CBSS/CBSL and (3) for CBLH, mount all the new cache
memories in the same positions on a new controller board instead of “all the Cache Memories
(including dust covers if any) mounted on the extracted Controller Board”.

TRBL02-151
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-160

Wait for the amount of time listed below:

VSP G130, G350, G370, F350, F370: 16 minutes
VSP G700, F700: 24 minutes
VSP G900, F900: 33 minutes
VSP E590: 16 minutes
VSP E790: 24 minutes
VSP E990: 33 minutes
VSP E1090: 39 minutes

Does the DKC ALARM No

LED light up?
Open “Maintenance Utility” window
Yes check whether a blocked part exists or
Open the “Maintenance” window of not. Replace a blocked part if it exist.
Maintenance PC.

Did a END
communication error No
between MPC software and
DKC occur?

Yes
Collect Dump/Log. Recover blocked MP.
(See MPC05-50, MPC05-250) (See MPC05-1240)

PS OFF
END

Is storage system Yes

powered off normally?

No
Open the “Maintenance” window of
Maintenance PC.

Did a
communication error Yes
between MPC software and
DKC occur?

No T.S.D. call

Status of “CACHE of Yes

CTL1” is normal?

No Status of “CACHE of Yes

CTL2” is normal?

No
7
T.S.D. call (TRBL02-170)

TRBL02-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-170

Breaker OFF.

Wait for 1 minutes.

Does the BACKUP

Yes
STS LED on the Controller Board
light up?

No No
Does the lighting continue for
three minutes or more?

Is the BACKUP STS Yes (*4) Yes

LED on the Controller Board
blinking?

No (light up or go out)

Is the DIMM/CFM Yes

3
installed correctly?
(TRBL02-180)
No

Install the DIMM/CFM correctly

(See DIMM: REP02-05-10,
CFM: REP02-10-10.)

Breaker ON.

PS ON.

2
(TRBL02-160)
*4: The blinking duration time of the BACKUP STS LED varies depending on the Storage System
models.
VSP G130: 10 minutes
VSP G350, VSP F350: 10 minutes
VSP G370, VSP F370: 20 minutes
VSP G700, VSP F700: 20 minutes
VSP G900, VSP F900: 20 minutes
VSP E590, VSP E790: 10 minutes
VSP E990, VSP E1090: 20 minutes

TRBL02-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-180

Did
the ALARM LED light Yes
up during the replacement of the
Controller Board?

No Remove the replaced Controller

Board.
Do the
“RefCode = fff4” (cache area Yes
blocking SIM) or “RefCode = ffe2” (Shared Remove the Parts found
Memory area blocking SIM) exist in PKC. (See ACC02-10.)
on the SIM log?
Breaker ON.
No
Remove one CHB/DKB/LANB. (The PS ON.
Maintenance PC operation is not
necessary.) (*5)
No Does the ALARM
LED light up?
Breaker ON.
Yes
Replace removed CTL with new
PS ON.
one. (See REP02-04-10) PS OFF.

Does the DKC No

ALARM LED light up?
Replace removed CHB/DKB/
Yes LANB with new one
Open the “Maintenance” window of (See REP01-06-80, REP01-06-90)
Maintenance PC. No Does the ALARM
LED light up?

Did END Yes

a communication error No
between MPC software and Replace the BKMF.
DKC occur? (See REP02-07-10)
Collect Dump/Log.
Yes (See MPC05-50, MPC05-250)
END
PS OFF.
Replace the blocked or failed
CHB/DKB/LANB with a
Insert the removed CHB/DKB/
maintenance part.
LANB and remove another CHB/
(See REP01-06-80, REP01-06-90)
DKB/LANB. (The Maintenance PC
operation is not necessary.) (*5)

END

No Have you executed

procedures for all CHB/DKB/
LANB?

Yes

T.S.D Call

TRBL02-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-181

*5: Perform removal, insertion, and removal of CHB, DKB, and LANB in the order shown below until
the failure part is identified.
• For CBLH1, CBLH2, CBLHN, and CBLMH4, two DKBs are installed per CTL:
CHB-1A  CHB-1B  …  CHB-1F  DKB-1G  DKB-1H
 CHB-2A  CHB-2B  …  CHB-2F  DKB-2G  DKB-2H
 LAN1  LAN2
• For CBLH2, CBLHN, and CBLMH4, four DKBs are installed per CTL:
CHB-1A  CHB-1B  …  CHB-1D  DKB-1E  …  DKB-1H
 CHB-2A  CHB-2B  …  CHB-2D  DKB-2E  …  DKB-1H
 LAN1  LAN2
• For CBLH1, CBLH2, CBLHN, and CBLMH4, no DKB is installed:
CHB-1A  CHB-1B  …  CHB-1H
 CHB-2A  CHB-2B  …  CHB-2H
 LAN1  LAN2
• For CBSS and CBSL:
CHB-1A  CHB-1B  CHB-2A  CHB-2B
• For CBXSS and CBXSL:
Do not perform removal or insertion but contact the Technical Support Division.
• For CBSN that contains no DKBs:
CHB-1A  CHB-1B  CHB-1C  CHB-2A  CHB-2B  CHB-2C
• For CBSN that contains DKBs:
CHB-1A  CHB-1C  DKB-1B  CHB-2A  CHB-2C  DKB-2B

TRBL02-181
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-190

2.1.5 Blinking WARNING (amber) of Storage System LED

START

Open the “Alerts” window of the

Maintenance Utility.
Refer to MAINTENANCE PC
SECTION “3.21 Alert Display”.

Did WARNING Yes See “2.1.6 Lighting up WARNING

of the Storage System LED light
(amber) of Storage System LED”.
up?

No

Did the
Storage System LED No
WARNING light up or go
out?
Yes

See “2.3 Analyze by SIM Log”.

TRBL02-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-200

2.1.6 Lighting up WARNING (amber) of Storage System LED

There are the parts that need to be maintained in the storage system. Follow the workflow shown below to
perform the maintenance work.

START

Open the “Alerts” window of the

Maintenance Utility.
(See MAINTENANCE PC SECTION
“3.21 Alert Display”.)

Is there a SIM without an Yes

action taken?
Perform the maintenance work
No according to the SIM in the “Alerts”
window. (See “2.3 Analyze by SIM Log”.)

Did the Storage System No

LED WARNING go out?

Yes

END T.S.D Call

TRBL02-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-210

2.1.7 Blinking or lighting up of CTL ALM LED (red) on CTL

START

Does the CTL

blink
ALM LED blink or light up? 1
(*1) (TRBL02-211)

light up
Replace the CTL
(See REP02-04-10)

Dose the CTL No

ALM LED go out?
Replace the Cache Memory
Yes (See REP02-05-10)

END
Dose the CTL No
ALM LED go out?

Yes T.S.D Call

END

*1: The LED might start blinking after 10 seconds of lighting. See the blinking patterns in the table for
determining maintenance procedure (TRBL02-213).

TRBL02-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-211

Determine the parts to be replaced and the priority according to

the table for determining maintenance procedure (TRBL02-213).

Yes
Blinking pattern #1? 2
(TRBL02-220)
No

Dose the CTL ALM LED Yes

blink during PS-ON or offline firmware 3
update? (TRBL02-212)

No
4

Yes
Blinking pattern #2?

No No Is SIM = “760000”
output?
Perform the maintenance work described in the table for determining
Yes
maintenance procedure.
NOTE: When replacing CFM, perform the CTL replacement
Perform the maintenance
procedure, remove the CTL from the chassis, replace the
work according to the ACC of
CFM only, and then reinstall the CTL to the chassis.
SIM = “760000”.
(Replace only the CFM. Do not replace CTL or other parts.)

Dose the CTL Yes [Check of normality]

ALM LED go off? (TRBL02-300)

No
END
Dose the
Yes
blinking pattern of the CTL ALM LED 1
change?

No
Perform the replacement work
Is the maintenance described in the table for
No work described in the table for determining maintenance procedure
determining maintenance procedure in order ( ①→②→…). Then, check
complete? the state of the CTL ALM LED and
go to the next step.
Yes

A
(TRBL02-261)

TRBL02-211
Hitachi Proprietary DW850/DW900/DW1000
Rev.5 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-212

Are the CTL ALM LEDs on No

both CTLs blinking?
If the approximate time for the READY
LED to light up (see Table 1-21
Yes Standard Lighting Time (INST01-05-
10)) has not passed after PS-ON, wait
until the time passes.

Yes Does the READY LED

(LOC03-10) remain off?

PS-OFF (*1)
No
Breaker OFF

Perform the cold replacement (*2) of the parts described in the

table for determining maintenance procedure.
When the blinking pattern of the CTL ALM LED is #2 and the
SIM = 760000 is output, replace only the DIMM indicated by
the ACC of the SIM with the maintenance part. 4
(TRBL02-211)
Breaker ON

PS-ON Perform the replacement work

described in the table for
determining maintenance procedure
Dose the CTL ALM Yes
in order ( ①→②→…) while the
LED go off?
storage system is powered off. Then,
END
No check the state of the CTL ALM
LED and go to the next step.
Dose the
Yes
blinking pattern of the CTL ALM 1
LED change? (TRBL02-211)
No

Is the maintenance
No work described in the table for
determining maintenance procedure
complete?

Yes

T.S.D Call

*1: If the storage system is not powered off (the light of the POWER LED does not change from green
to amber) when about 1 minute has passed, go to the next step.
*2: Replace the parts while the storage system is powered off.
TRBL02-212
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-213

Table 2-1 Table for determining maintenance procedure

# CTL ALM LED Blinking Pattern Maintenance Procedure
1 0.5 sec. ① Replace the CTL where the LED is blinking with a
On
maintenance part.

Off
0.5 sec.
→ Blinks in 1-second intervals.
2 10 sec. 2 sec. 10 sec. ① Replace all DIMMs installed in the CTL where the LED is
On
blinking.
NOTE: Before replacing DIMMs, check the DIMM types
Off and the number of installed DIMMs are correct. If
2 sec.
they are not correct, make them correct, and then
→ Blinks (On: 2 seconds, Off: 2 seconds)
once after 10 seconds of lighting. insert the CTL again.
② Replace the CTL where the LED is blinking with a
maintenance part.
3 10 sec. 2 sec. 10 sec. ① Replace the CFM installed in the CTL where the LED is
On blinking with a maintenance part. For CBLH1/CBLH2/
CBLHN/CBLMH4, replace only CFM-10 or CFM-20.
Off NOTE: Before replacing the CFM, check the CFM types
2 sec.
and the number of installed CFMs are correct. If
→ Blinks (On: 2 seconds, Off: 2 seconds)
2 times after 10 seconds of lighting. they are not correct, make them correct, and then
insert the CTL again.
② Replace the CTL where the LED is blinking with a
maintenance part.
③ Replace all DIMMs installed in the CTL where the LED is
blinking with maintenance parts.
4 10 sec. 2 sec. 10 sec. ① Replace the CTL where the LED is blinking with a
On
maintenance part.
② Replace all DIMMs installed in the CTL where the LED is
Off blinking with maintenance parts.
2 sec.
→ Blinks (On: 2 seconds, Off: 2 seconds)
3 times after 10 seconds of lighting.
5 10 sec. 2 sec. 10 sec. ① Replace the CTL where the LED is blinking with a
On
maintenance part.

Off
2 sec.
→ Blinks (On: 2 seconds, Off: 2 seconds)
4 times after 10 seconds of lighting.
(To be continued)

TRBL02-213
Hitachi Proprietary DW850/DW900/DW1000
Rev.7 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-220

(Continued from preceding page)

# CTL ALM LED Blinking Pattern Maintenance Procedure
6 10 sec. 2 sec. 10 sec. [During power-on or offline firmware update]
On
① Remove and install the CTL where the LED is blinking.
After completion of start-up of the storage system, perform
Off the Auto Dump (type: Normal) collection (see MPC05-
2 sec.
→ Blinks (On: 2 seconds, Off: 2 seconds) 50) even when the storage system is entirely normal and
5 times after 10 seconds of lighting. does not have any blocked parts, and contact the Technical
Support Division.
[Other than the above]
① Perform the dummy replacement of the CTL where the
LED is blinking. Then, regardless of success or failure of
the dummy replacement (regardless of whether the CTL is
restored or not), perform the Auto Dump (type: Normal)
collection (see MPC05-50), and contact the Technical
Support Division.

Replace the CTL

Did the CTL ALM No

LED go out?

Yes T.S.D Call

END

TRBL02-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-230

2.1.8 Blinking CTL WARN LED (amber) of CTL (CBSS/CBSL)

The blinking patterns of the CTL WARN LED are as follows:
• One blink (Blinks one time at 1.5 second intervals.)
• Two blinks (Blinks twice at 2.5 second intervals.)
• One and two blinks (Blinks one time in 1.5 seconds and then blinks twice in 2.5 seconds at 4 second
intervals.)

START

One blink and two Check

blinks repeat in order the blinking pattern blinks twice
of the CTL WARN
LED.
blinks once
FAN0 and FAN1 installed in FAN0 installed in the CTL FAN1 installed in the CTL
the CTL are abnormal. are abnormal. are abnormal.

Replace the FAN

(See REP02-06-10)

Did the CTL WARN No

LED go out?

Yes T.S.D Call

END

TRBL02-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-240

2.1.9 Lighting up FAN STATUS LED (red) of FAN (CBLH)

START

Replace the BKMF whose

FAN STATUS LED lights up.
(See REP02-07-10)

Is FAN
STATUS LED either of
the following? No
BKMF-10/-20: Tuned off
BKMF-11/12/13/-21/22/23: Lit
or blinking in green

Yes

END T.S.D Call

TRBL02-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-250

2.1.10 Turning off POWER LED of the Storage System LED

START

Is the
AC breaker of the device No Turn on the AC breaker of the DKC,
connected with the DKC and turn on the PS ON of the cevice.
on?
Yes
There is a possibility of a power outage
or a power failure in the equipment.
Confirm whether a power outage
occured and there is an abnormality in
the wquipment.

Has a power Execute the search of the DKCPS

outage occurred or is there No failure.(Refer to “3.20 Response to the
an abnormality exists in the Occurrence of DKCPS Warning (SIM =
equipment? af200x)”.)

Yes
After removing the cause of the power
outage or the power failure in the
equipment, turn on the PS ON of the
device.

END

TRBL02-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-260

2.2 Failure During Operation by Service Personnel

2.2.1 Error Recovery Procedure when Removing/Inserting CTL
The maintenance procedure when removing/inserting the CTL is as follows.
■ REPLACEMENT SECTION
2.4 Replacing a Controller Board
2.5 Replacing a Cache Memory (Perform the following procedure only when the failure is not resolved
even after the retry of DIMM replacement and the CTL is blocked)
2.6 Replacing a FAN (Perform the following procedure only when the CTL is blocked)
2.11 Replacing a LAN Board (Perform the following procedure only when the CTL is blocked)
2.8.4 Replacing a Battery for CBXSS/CBXSL (Perform the following procedure only when the CTL is
blocked)
2.10.3 Replacing a Cache Flash Memory for CBXSS/CBXSL (Perform the following procedure only
when the CTL is blocked)
■ INSTALLATION SECTION
3.7 Adding Cache Memory/Cache Flash Memory (Perform the following procedure only when the
failure is not resolved even after the additionally installed DIMM is replaced with the replacement part
and the CTL is blocked)
3.12 Replace Controller Board for CBSS/CBSL (Type Change) (Perform the following procedure only
when the CTL is blocked)
4.7 Removing Cache Memory (Perform the following procedure only when the CTL is blocked)

TRBL02-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-261

START

If there is any ACC for which action is

not taken, perform the maintenance work
according to the ACC.

Analyza the SSB and SIM

(See MPC05-250)

Yes Is SSB = 3560 output?

2
(See MPC05-250.)
(TRBL02-310)
No

Yes Is SSB = 359d

3
output?
(TRBL02-310)
No

Yes
Is there SIM?

No Failure isolation action

(See TRBL02-640)
Does the CTL ALM LED Yes
light up or blink?

From TRBL02-211 No Perform the maintenance work according

to “2.1.7 Blinking or lighting up of CTL
A ALM LED (red) on CTL”.

Does the DKC ALARM Yes

LED light up?

No
Click the [Refresh] button ( ) in the
“Maintenance Utility” window

Can you check No

“Maintenance Utility” window?

Perform the Recovery Procedure for LAN Error.

Yes (See TRBL03-210)

1
(TRBL02-270)

TRBL02-261
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-270

Is System
Unlocked displayed as No
system lock status in the upper right of 8
the Maintenance Utility
(TRBL02-311)
window?

Yes
9

Retry the CTL replacement by using

the same CTL. (*1)

Yes
Normally ended?

No
Retry the CTL replacement by using
a new CTL.

Yes
Normally ended?

No
Replace all DIMMs installed in the CTL with new
DIMMs and perform the CTL replacement again.

Yes
Normally ended?

No
Replace all CFMs installed in the CTL with new
CFMs and perform the CTL replacement again.

Yes
Normally ended?

No

Is
the Storage System Yes
CBXSS/CBXSL/CBSS/CBSL/ 11
CBXSN? (TRBL02-271)

No

T.S.D. call 6
(TRBL02-311)

*1: When removing and inserting the CTL, check that the installation of DIMM/CFM is the same as
that shown in the Maintenance Utility window. If it is different, install DIMM/CFM correctly.

TRBL02-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-271

11

Yes Is the FAN already

replaced?

No

Replace it with a new FAN and

perform the CTL replacement again.

Yes
Normally ended? 6
(TRBL02-311)
No

4
(TRBL02-280)

TRBL02-271
Hitachi Proprietary DW850/DW900/DW1000
Rev.10.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-280

T.S.D. call
Perform cold replacement (*2) of the other
Check and write down the IP addresses of CTL (use the parts as unchanged except for
the management port and the maintenance the Controller Board).
port for the internal network (MPC03-510).
Make sure to remove the failed replacement
Back up the configuration information CTL.
(MPC05-990).
While the other CTL is removed, set the
Storage System to PS ON.
Request the customer to allow PS OFF of
the Storage System. Does
Yes
the Ready LED of the Storage
Set the Storage System to PS OFF. System light?
No

Turn off the breaker of the Storage System,

and check that the DIMM and CFM are
properly installed in the inserted CTL.

While the other CTL is removed, turn on

the breaker of the Storage System and set
the Storage System to PS ON.

Does
Yes
the Ready LED of the Storage
System light?
No

Turn off the breaker of the Storage System,

replace the DIMM in the inserted CTL, and
turn on that breaker and Set the Storage
System to PS ON again while the other
CTL is removed.

Does
Yes
the Ready LED of the Storage
System light?
No
5
(TRBL02-290)
T.S.D. call

*2: Replace the parts in the PS OFF status.

TRBL02-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-290

5 Set the internal IP address written down beforehand to

the internal network by following MAINTENANCE PC
SECTION 3.6.1 Network Setting . (Check the checkbox
Is the of Forcibly run without safety checks before setting it.
status of the storage The checkbox is displayed only when Maintenance Utility
is started from the Web Console window or the MPC
system on Maintenance Utility Yes
window. To check the checkbox, start Maintenance Utility
still in Power-on in progress from the Web Console window or the MPC window.
after 20 minutes has The following error message is output because one CTL is
passed? removed, but continue the setting.
An error occurred in network settings for the controller
No board to which Maintenance Utility is not connected. If this
problem persists, contact customer support. (31862-200014) )
To reinstall the removed CTL in the Storage
System, perform CTL replacement for Perform reboot GUM procedure on Maintenance Utility. (See
removed CTL. ( ) MAINTENANCE PC SECTION 3.18 Reboot GUM.)

Perform Step 1 and Step 2 in the procedure described in

Yes MAINTENANCE PC SECTION 3.6.1 Network Setting to
Normally ended? check the IP address of the internal network.

No Is the IP
Retry the CTL replacement by using a new address of the internal network No
CTL. ( ) updated to the IP address written down
beforehand?
Yes
Normally ended? Yes
Is
No the status of the storage
Yes
Replace it with a new DIMM and perform system Warning on Maintenance
the CTL replacement again. ( ) Utility?
No
Yes
Normally ended? T.S.D. call

No
Replace it with a new CFM and perform the Connect the Maintenance PC to the cold replaced CTL,
and then set the date and time using Maintenance Utility
CTL replacement again. ( ) (see MAINTENANCE PC SECTION 3.5 Time Setting ).

Yes
Normally ended?
[Check of
Perform GUM firmware update on the
No normality]
cold replaced CTL. (*3).
(TRBL02-300)
T.S.D. call

*3: For GUM firmware update, see FIRMWARE SECTION 3.3.1 Updating Firmware of the Storage
System. Use the installation media for the SVP, which comes with the Storage System and is
owned by the customer.
However, wait for 15 minutes or longer after ( ) has been properly done, and then perform
GUM firmware update.
The time required for GUM firmware update is about 40 minutes.

TRBL02-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-300

[Check of normality]

Is there any
Yes
blocked parts in the Maintenance
Utility window?

No
Check whether any failed track and blocked LDEV exist in
accordance with MAINTENANCE PC SECTION “3.29 Checking
Existence of Pinned Track and Blocked LDEV”.

Does Pinned track exist? Yes

(MPC05-1170)
No

Is LDEV blocked? Yes

(MPC04-330)

No

Is SIM reported? Yes

(MPC05-250) (*4)

No

Is the GUM
firmware
version of the replaced CTL correct? No
Is the GUM firmware version of CTL1 the
same as that of CTL2? (*8)

Yes

Is SSB EC = 3475
issued 10 or more times in 10 minutes Yes
after completion of the replacement?
(*5)

No

END T.S.D. call

*4: The SIM = 7d08xx might be reported.

If the SIM = 7d08xx is reported, perform the recovery procedure according to “16. Recovery
Procedure for GUM Information Recover Failure (SIM = 7d08xx)”.
*5: Refer to MAINTENANCE PC SECTION “[1] SSB Log” in “5.3.1 Log Indication”.
*8: Refer to the NOTE in FIRMWARE SECTION “3. Display the “Firmware” window” (FIRM03-80).

TRBL02-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-310

Retry the CTL replacement by using a new CTL.

Is the CTL
No
replacement completed
normally?

Yes
10
(TRBL02-312)
END

No Is the model CBLH1/CBLH2/

CBLHN/CBLMH4/CBSN1/CBSN2?

Yes
Open Maintenance window

All MPs shown in (*6) are blocked Yes

and the other parts are not blocked.

No

All MPs shown in (*7) are blocked Yes

and the other parts are not blocked.
Replace CTL of the opposite cluster.
No

Is the CTL
No
replacement completed
normally?

Yes

T.S.D. call END

*6: MP (1) for each model

CBLH1 CBLH2 CBLHN CBSN1 CBSN2/CBLMH4
MP10-00~MP10-05 MP10-00~MP10-09 MP10-00~MP10-0D MP10-00~MP10-05 MP10-00~MP10-0F
MP20-00~MP20-05 MP20-00~MP20-09 MP20-00~MP20-0D MP20-00~MP20-05 MP20-00~MP20-0F
*7: MP (2) for each model
CBLH1 CBLH2 CBLHN CBSN1 CBSN2/CBLMH4
MP10-06~MP10-0B MP10-0A~MP10-13 MP10-0E~MP10-1B MP10-06~MP10-0B MP10-10~MP10-1F
MP20-06~MP20-0B MP20-0A~MP20-13 MP20-0E~MP20-1B MP20-06~MP20-0B MP20-10~MP20-1F

TRBL02-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.5 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-311

Is SSB EC =
3475 issued 10 or more times in No
10 minutes after completion of the
replacement? (*5)

Yes

On the other
Yes cluster, is the CTL replacement
with the maintenance part
complete?
No
On the other cluster, perform the CTL
replacement.

No
Normally ended?

Yes

Is SSB EC =
Yes 3475 issued 10 or more times in
10 minutes after completion of the
replacement? (*5)

No

T.S.D. call [Check of normality]

(TRBL02-300)

Has the
estimated time (see REP01- No
06-50) elapsed since you started the
replacement?
Wait until the estimated time elapses.
Yes

Release the system lock (TRBL02-530).

9
(TRBL02-270)
*5: Refer to MAINTENANCE PC SECTION “[1] SSB Log” in “5.3.1 Log Indication”.

TRBL02-311
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-312

10

Is the model
CBLH1, CBLH2, CBLHN, No
CBLMH4, CBSN1 or
CBSN2?

Yes

Is the
DKCMAIN firmware
version 88-07-03-x0/40 or later, 88- No
08-01-x0/40 or later, 88-08-02-x0/00 or later,
93-04-03-x0/00 or later, or 93-05-
03-x0/00 or later?

Yes
Set the System Option Mode 1251 to ON.

Perform the CTL replacement again.

Is the message (30762- No

208767) output?

Yes
Set the System Option Mode 1251 to OFF.

Check the status of each CTL with

Maintenance Utility.

Are
both of the
following met?
・The status of both CTLs is Warning. No
・The status of all parts including CFMs/
CHBs/DKBs/ PECBs is
Normal.

Yes
Replace the other CTL than the just replaced
one with a maintenance part.

Is the replacement No
successful?

Yes T.S.D. call

[Check of normality]
(TRBL02-300)

TRBL02-312
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-320

2.2.2 Failures Have Occurred when Installing Drive/DB

NOTICE: If drive installation processing fails, the drive status displayed in the Maintenance
Utility window might not match the LED lighting state of the drive.
If the ALM LED (red) on the drive is not lit when the drive status is displayed as
Blocked , block the drive with Maintenance Utility.

[Link] Installation Failure of Drive/DB

START

No
Did you install the DB? 2
(TRBL02-350)
Yes

Is the
message (32961-
Yes
208017) output in the
Maintenance Utility
window? (*1) Take a recovery action such
as connection check and part
No replacement according to the error
message, and then perform the
installation again.

Is the installation No
successful?

Yes

END

Is SIM
RC = effbxx
(NSW failure), effdxx Refer to “3.37 Recovery Procedure
Yes
(Expander error) or effexx (UNIT when Cable Connection Error Occurs (SIM
connection cable order = effbxx, effcxx, effdxx, effexx)”
error) output in the
SIM log?

No

1
(TRBL02-330)

*1: If the same part is indicated repeatedly and you have passed this route three times or more, go to
“No”.

TRBL02-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-330

Confirm the ENC equipment.

(Refer to (LOC02-60))
The abnormal termination has possible causes such as ENCs are not
installed or SAS cables/NVMe cables are not connected.
Confirm the connection of cables. Check that the ENCs are installed correctly. If not, install ENCs.
(Refer to (LOC05-10)) Check that SAS cables/NVMe cables are connected correctly. If not,
connect correctly them in accordance with the cable connection diagram.
Do the installation operation again.

Is DB installed No
3
successfully?
(TRBL02-340)
Yes

END

TRBL02-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-340

Replace the ENCs and SAS cables/

NVMe cables to be installed with the
maintenance parts. (*1)

Do the installation operation again.

Is DB installed Yes
successfully?

No
Replace the ENCs installed just
before the DB was installed or
DKBs. (*2) (*3) (See (REP02-16-10)
or (REP02-14-10))

Do the installation operation again.

Is DB installed Yes
successfully?

No END

T.S.D. call

*1: Replace the ENCs first, and then SAS cables/NVMe cables with the maintenance parts to identify
the failed parts.
*2: The connection source of the installed DB may be broken. Replace it with the maintenance part.
*3: For CBSS/CBSSE/CBSL/CBSLE/CBXSS/CBXSL, if the device installed just before the DB
was installed is a Controller Board, replace the Controller Board with a maintenance part. (See
REPLACEMENT SECTION “2.4 Replacing a Controller Board”.)

TRBL02-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-350

2 4

Have you
passed this route Yes
three times or more because the
same part is indicated
repeatedly?
T.S.D Call
No

Are all No
installation target drives
detected?
Remove undetected drives and insert
Yes them again.

No
Are the drives detected?

Remove undetected drives and

Yes install drives of maintenance parts as
replacement parts.

No
4 Are the drives detected?

Yes

11
(TRBL02-350A)

TRBL02-350
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-350A

11

Is there an error when Yes

detecting drives?
Resolve the problem of the part
No indicated by Maintenance Utility,
and then perform the installation
Confirm the Status of Drive by the
again.
Maintenance Utility window.

Is the installation No
4
successful?
(TRBL02-350)
Yes

Do the END
statuses of the
added drives include any of No
the following? Warning/Warning
(Port failed)/Failed/
Blocked
T.S.D Call

Yes

Are all target drives to Yes

10
be added blocked?
(TRBL02-355)
No

5
(TRBL02-351)

TRBL02-350A
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-351

5 6

Perform the following recovery

workflow for the drives that failed to
be added.

Are
multiple Drives that No
failed to be added in the
same DB?
• Drive replace 
Yes Recover the Drive that failed to be added by
following “Replacing a Drive” (REP02-03-10). (*1)
Perform the dummy replacement of the installed
drive in the above replacement procedure.

Is Drive blockade Yes

recovered?

No
• Drive replace 
Recover the Drive that failed to be added by
following “Replacing a Drive” (REP02-03-10). (*1)
Replace the drive with a spare part in the above
replacement procedure.

Is Drive blockade Yes

recovered?

No Are all drives No

that failed to be added
recovered?

7 Yes 6
(TRBL02-352)
END

*1: Before inserting Drives, check the Drive type names. (Refer to “Table List of Mountable Drive
Model Names” (INST03-03-20) and “Table Maintenance Parts List” (PARTS03-10).)
When SSB = A7A8 is output, it may be an unsupported Drive. Contact the Technical Support
Division.

TRBL02-351
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-352

Are the Drives

that failed to be added Yes
installed in the Chassis that
contains CTLs? • Controller Board replace 
Replace both Controller Boards that contain
No the Drives that failed to be added by following
• ENC replace  “Replacing a Controller Board” (REP02-04-10). (*1)
Replace both ENCs in the DB that contains the Perform the dummy replacement of the installed
drives that failed to be added by following “Replacing Controller Boards in the above replacement
an ENC” (REP02-16-10). (*1) procedure.
Perform the dummy replacement of the installed
ENC in the above replacement procedure.
Are the Yes
Controller Boards replaced
successfully?

ENC replace is No No
normally ended?

Yes T.S.D Call

• Drive replace 
Recover the Drive that failed to be added by
following “Replacing a Drive” (REP02-03-10). (*2)
Perform the dummy replacement of the installed
drive in the above replacement procedure.
*: If you have performed “Drive replace ”, use the
drive after the replace.

Is Drive blockade No
8
recovered?
(TRBL02-353)
Yes

Are all drives No

that failed to be added 6
recovered?
(TRBL02-351)
Yes

END

*1: For the drive number and the DB number, see THEORY OF OPERATION SECTION “4.1 DB
Number - C/R Number Matrix” “DB Number - R Number Matrix” and “DB Number - C Number
Matrix”.
*2: Before inserting Drives, check the Drive type names. (Refer to “Table List of Mountable Drive
Model Names” (INST03-03-20) and “Table Maintenance Parts List” (PARTS03-10).)
When SSB = A7A8 is output, it may be an unsupported Drive. Contact the Technical Support
Division.

TRBL02-352
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-353

Are the Drives

that failed to be added Yes
installed in the Chassis that
contains CTLs? • Controller Board replace 
Replace both Controller Boards that contain
No the Drives that failed to be added by following
• ENC replace  “Replacing a Controller Board” (REP02-04-10). (*1)
Replace both ENCs in the DB that contains the Replace the Controller Boards with maintenance
drives that failed to be added by following “Replacing parts.
an ENC” (REP02-16-10). (*1)
Replace the ENC with a spare part in the above
replacement procedure. Are the Yes
Controller Boards replaced
successfully?

ENC replace is No No
normally ended?

Yes T.S.D Call

• Drive replace 
Recover the Drive that failed to be added by
following “Replacing a Drive” (REP02-03-10). (*2)
Perform the dummy replacement of the installed
drive in the above replacement procedure.
*: If you have performed “Drive replace ”, use the
drive after the replace.

Is Drive blockade No
9
recovered?
(TRBL02-354)
Yes

Are all drives No

that failed to be added 6
recovered?
(TRBL02-351)
Yes

END

*1: For the drive number and the DB number, see THEORY OF OPERATION SECTION “4.1 DB
Number - C/R Number Matrix” “DB Number - R Number Matrix” and “DB Number - C Number
Matrix”.
*2: Before inserting Drives, check the Drive type names. (Refer to “Table List of Mountable Drive
Model Names” (INST03-03-20) and “Table Maintenance Parts List” (PARTS03-10).)
When SSB = A7A8 is output, it may be an unsupported Drive. Contact the Technical Support
Division.

TRBL02-353
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-354

Are the Drives

that failed to be added Yes
installed in the Chassis that
contains CTLs? • Controller Board replace 
Replace both Controller Boards that contain the Drives that failed to
No be added by following “Replacing a Controller Board”
• ENC replace  (REP02-04-10). (*1)
Replace both ENCs in the DB that contains the Perform the dummy replacement of the installed Controller Boards
drives that failed to be added by following “Replacing in the above replacement procedure.
an ENC” (REP02-16-10). (*1) *: Use the Controller Boards replaced in Controller Board replace .
Perform the dummy replacement of the installed
ENC in the above replacement procedure.
*: If you have performed “ENC replace ”, use the Are the Yes
drive after the replace. Controller Boards replaced
successfully?

No
ENC replace is No
normally ended?

Yes T.S.D Call

• Drive replace 
Recover the Drive that failed to be added by following “Replacing a
Drive” (REP02-03-10). (*2)
Perform the dummy replacement of the installed drive in the above
replacement procedure.
Even if you have already replaced the drive in the step “Drive
replace ”, replace the drive with a new spare part.

Is Drive blockade No
recovered?

Yes
T.S.D Call

Are all drives No

that failed to be added 6
recovered?
(TRBL02-351)
Yes

END

*1: For the drive number and the DB number, see THEORY OF OPERATION SECTION “4.1 DB
Number - C/R Number Matrix” “DB Number - R Number Matrix” and “DB Number - C Number
Matrix”.
*2: Before inserting Drives, check the Drive type names. (Refer to “Table List of Mountable Drive
Model Names” (INST03-03-20) and “Table Maintenance Parts List” (PARTS03-10).)
When SSB = A7A8 is output, it may be an unsupported Drive. Contact the Technical Support
Division.

TRBL02-354
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-355

10

Remove all target drives to be added.

Are all target drives No

removed successfully?

Yes T.S.D Call

Install all target drives again.

Are all target drives No

installed successfully?

Are all
Yes target drives to be
added blocked? No
END (Does the same problem
recur?)
2
Yes
(TRBL02-350)
T.S.D Call

TRBL02-355
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-360

[Link] LED of ENC Turns On after Installing DB

After a DB is installed, the LED on an ENC might light up in red.
In that case, perform dummy replacement of the ENC to restore it.
(See REPLACEMENT SECTION “2.16 Replacing an ENC”.)

TRBL02-360
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-370

2.2.3 Error Recovery Procedure during CHB/DKB replacement

Perform the appropriate recovery procedure according to case 1, 2, 3 or 4.

1. Blocking error occurrence

When an error message is output while blocking the CHB/DKB, the blockade processing has failed.
Perform the following recovery processing.

START

Open the “Maintenance Utility” window

(See MPC02-260)

Did the No
“Maintenance Utility” window
Open?
Perform the Recovery Procedure for
Yes LAN Error. (See TRBL03-210)

Is the PCB
No
CHB?
(See MPC03-1160.)

Yes

Is the paths of No
the PCB being replaced varied
offline?

Yes
Disconnect serial fibre cable of Perform “Vary Path offline” from
the CHB being replaced. host side.

Perform the “Replace” of the

CHB/DKB again.

Normal No
END?
Yes

END T.S.D Call

TRBL02-370
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-380

2. Restoring error occurrence

When an error message is output while blocking the CHB/DKB, the blockade processing has failed.
Perform the following recovery processing.

START

Is the message (30762- Yes

208186) displayed?
Ask user to create the maximum
No number of encryption keys (*1)

Yes No
Is SSB E/C = A7FE Normal end?
output? (See MPC05-250.)
Yes
No Replace the DKB to new one (*2)

TRBL02-390
No
Normal end?

Yes
T.S.D. call
Is the purpose
No of DKB Replacement a recovery
for initialization failure of encryption
environmental settings?

Yes
END Retry the initialization of encryption
environmental settings (*3)

*1: When creating encryption key on the Key Management Server, it may take approximately 60
minutes.
*2: When the DKB replacement was failed with using new part, it is not necessary for you to replace
the DKB to new one again.
*3: When you continue to use without initialization, Sparing may fail.
For initialization of encryption environmental settings, refer to “Encryption License Key User
Guide”.

TRBL02-380
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-390

3. In case of failures other than the blockade/recovery processing

START

Analyza the SIM

1
(See MPC05-250)

Yes
Is there SIM?

No Yes
Is it CUDG error? (*1)
Open the “Maintenance Utility”
window (refer to MPC02-260)
No

No
Did STATUS open?

Perform the Recovery Procedure for

Yes LAN Error. (See TRBL03-210)

Does the PCB

type displayed in the No
“Maintenance Utility” window
match the PCB type to
be replaced? Replace the PCB with the same type
of PCB.

Yes
Remove the PCB and replace it with
the same PCB again.

Yes
Normal end?

No

Replace the PCB with new one.

No
Normal end? 1

Yes

END

*1: Reference code : 760000. (See SIMRC02-120)

TRBL02-390
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-400

4. Case of the DKB/CHB type change operation

START

Open the “Maintenance Utility”

window (refer to MPC02-260)

Did the
No
“Maintenance Utility” window
Open?
Perform the Recovery Procedure for
Yes LAN Error. (See TRBL03-210)

Is type of DKB/CHB No
type after the changes? (*1)

Yes Perform the DKB/CHB type change

operation again.

Perform the Replace of the DKB/CHB.

*1: Check the type of CHB by following the procedure below.

1. Select [Maintenance Utility] - [Hardware] - [Other Hardware Maintenance…], and then select
[Controller Chassis] in the Maintenance Utility main window.
2. Click the [CHBs] tab in the “Controller Chassis” window, and check that the new CHB type is
displayed in the [Type] column of the CHB.

TRBL02-400
Hitachi Proprietary DW850/DW900/DW1000
Rev.7 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-410

2.2.4 Error Recovery Procedure during BKM/BKMF/Battery/CFM replacement and LANB

blockade

START

Analyza the SIM

1
(See MPC05-250)

Yes
Is there SIM?

Failure isolation action

No
(See TRBL02-640)

Did the CFM Yes

2
replacement fail?
(TRBL02-411)
No
3

Click the [Refresh] ( ) button in the

“Maintenance Utility” window.

Can you check

No
“Maintenance Utility” window?
Perform the Recovery Procedure for
Yes LAN Error. (See TRBL03-210)

Remove the replacement and replace it

with the same replacement again.

Yes
Normally ended?

No
Replace the replacement with new
one.

No
Normally ended? 1

Yes

END

TRBL02-410
Hitachi Proprietary DW850/DW900/DW1000
Rev.7 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-411

Analyza the SSB

(See MPC05-250)

Was SSB = 34ed output

No
around the same time as the CFM 3
replacement failed? (TRBL02-410)

Yes

Perform the CFM replacement again

by using the same CFM.

No
Normally ended?

Yes Perform the CFM replacement again

by using a new CFM.

Regardless of success or failure of the

CFM replacement (regardless of whether the
CFM is restored or not), perform the dump
collection (see MPC05-50), and contact the
Technical Support Division.

TRBL02-411
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-420

2.2.5 Error Recovery Procedure during LANB replacement

START

Analyza the SIM

1
(See MPC05-250)

Yes
Is there SIM?

(*1)
No Yes
Is it CUDG error?

No
Failure isolation action
(See TRBL02-640)

No
Is the CTL status normal?

Yes
Remove the replacement and replace it
with the same replacement again.

Yes
Normally ended?

No
Replace the replacement with new one.
Replace the replacement with new one.

No No
Normally ended? 1 Is the CTL status normal?

Yes
Yes

END END

*1: Reference code : 760000. (See SIMRC02-120)

TRBL02-420
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-430

2.2.6 Recovery procedure when LDEV formatting failed

If “Task Status” of the task formatted in the “Task” window of Storage Navigator is displayed as “Failed”
when terminating the LDEV format and if the LDEV formatted in “Logical Device Status” is displayed as
“Blocked”, recover the LDEV in the following procedure.

START

Has
Yes
SIM been created? (See
MPC05-250 )

No Has SIM = 410001 Yes

been created?

No

No Has SIM = 410002

been created?

Yes

Has the other SIM No

also been created?

Yes

Perform the recovery procedure

according to the ACC of the other
SIM created during the formatting
process.

Is SSB = 2cc7 No
output?

1 Yes
T.S.D. call
(TRBL02-440)
3
(TRBL02-431)

TRBL02-430
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-431

Did you retry LDEV Yes

formatting?

No Did you retry Yes

LDEV formatting twice or
more?

No T.S.D. call
Perform LDEV formatting (a) After 24 hours have passed since (a)
(MPC04-370). was done, perform LDEV formatting
(MPC04-370).

Did the LDEV format No

terminate abnormally?

Yes END

2
(TRBL02-430)

TRBL02-431
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-440

Has LDEV formatting Yes

been retried?

No Has LDEV been

formatted from [Logical Device No
Retry the LDEV formatting.
(See MPC04-370) Format] in the “Logical Devices”
window?

Yes

Has [Only
a Blockade Logical Device Yes
FORMAT with together] been executed?
(See MPC04-370)

T.S.D. call
No
Execute the [Only a Blockade
Logical Device FORMAT with
together]. (See MPC04-370)

Did the No
LDEV format terminate
abnormally?

Yes END

2
(TRBL02-430)

TRBL02-440
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-450

2.2.7 Recovery from the incorrect setting when adding Cache Memories
If you find an incorrect setting after the window operation of Cache Memory addition, recover it in
accordance with the following procedure.

START

Is the message “Add Cache Memories. Yes

First, … “ displayed?
Select cancel

No
END

Is the message “CTL1

(or CTL2) blockade is completed. In Yes
the maintenance manual procedure …”
displayed?
Pull out and insert the CTL on which
the CTL ALM LED is lit without
No installing the Cache Memories to be
added, and then select the [Recover]
button.

Yes
Did the recovery fail?

Select the [Close] button for the

No message.

Is the message “Cache 1

Yes
Memory addition is completed. …”
displayed? (TRBL02-460)

No Check Cache Memory status

T.S.D. call

END

TRBL02-450
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-460

Open the [CTL] tab in the

“Controller Chassis” window.

Is the CTL2 status other Yes

than Normal?

2
No
(TRBL02-470)

Is the CTL1 status other Yes

than Normal?
Perform dummy replacement of
No CTL1. (*1)

Is the dummy No
replacement completed
normally?

Yes T.S.D. call

Check that the number of Cache

Memories is the same as before
the addition by the [CTL] tab in
the “Controller Chassis” window.

Add the Cache Memories of

CTL2 again in the correct setting.

END

TRBL02-460
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-470

Is the CTL2 status other Yes

than Normal?
Perform dummy replacement of
No CTL2. (*1)

Is the dummy No
replacement completed
normally?

Yes T.S.D. call

Check that the number of Cache

Memories of CTL2 is the same
as before the addition by the
[CTLs] tab in the “Controller
Chassis” window.

Add the Cache Memories of

CTL2 again in the correct setting.

END

*1: If the added Cache Memories and CFMs exist, remove them.

TRBL02-470
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-480

2.2.8 Recovery Procedure when Change the IP Address failed

Network Settings failure

GUM reboot No
1
Failure?
(TRBL02-490)
Yes
From Maintenance Utility, reboot
GUM. (Refer to MAINTENANCE
PC SECTION “3.18 Reboot GUM”)

[GUM reboot] No
Success?
Execute “GUM reset with a
Yes [LAN-RST] switch”. (Refer to
MAINTENANCE PC SECTION
“3.26 Resetting GUM”)

Confirm that the network settings are

changed in the “Maintenance Utility”
window.

END

TRBL02-480
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-490

Execute “LAN Check”. Log out of the Maintenance

(See DIAG04-210.) Utility.

ALL MP No Execute Dummy replacement of

Abnormal? the connected CTL.

Yes No
ALL MP Normal?

Yes

Log out of the Maintenance

Utility.

Execute [Network Setting]

Change the internal network to
another IP address

[Network Setting] No
Success?

Yes

END T.S.D Call

TRBL02-490
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-500

2.2.9 Correspondence at the time of the mode setting failure of System Option
When “Operation was rejected by DKC.” and “Change Configuration was failed.” were displayed during the
mode setting execution of System Option, correspond it in the following procedure.

START

Is SSB
No
= 0x152F reported? T.S.D. call
(See MPC05-250.)

Yes
Did
QuickRestore or No No
Volume Migration operate during T.S.D. call
the mode setting?

Yes
Wait until QuickRestore or Volume
Migration is completed.

Perform the mode setting again.

(See MPC05-880.)

No
Did it succeed? T.S.D. call

Yes

END

TRBL02-500
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-510

2.2.10 Firmware version mismatching

NOTE: Firmware version might be highlighted (means mismatching with the current DKC
firmware (including acquisition/conversion error)) in the Version window opened
from the Maintenance window also when the firmware is not supported. In that
case, you do not have to perform the procedure shown below.
To check whether the firmware is supported or not, see description about storage
system models and firmware versions for MP FM list in Table 5- 18 Displayed
information in MAINTENANCE PC SECTION [Link] MP Ver.(Curt./FM).

START

Is there any other No

failure part?

Yes
Recover other failure part.

Perform the recovery procedure in

updating firmware. (FIRM04-40)

END

TRBL02-510
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-520

2.2.11 Recovery Procedure for Failure During DKB Installation

START

Is the PCB of the addition No

target correct?

Yes Replace with the

correct type of PCB.

Is the firmware of
the PCB targeted for addition
No
installed?
For DKB: DKB
For DKBN: DKBN
Remove the PCB and update the
firmware. Then, retry the procedure for
addition.
Yes

Is the message (30762- Yes

208186) displayed?

No

Is SSB E/C = A7FE output? Yes

(See MPC05-250.)
Ask user to create the maximum number of
No encryption keys. (*1)

No
Normal end?

Yes
Re-perform DKB install again. (*2), (*3)

No
Normal end?

T.S.D. call Yes

END

*1: When creating encryption key on the Key Management Server, it may take approximately 60
minutes.
*2: When the DKB replacement was failed with using new part, it is not necessary for you to replace
the DKB to new one again.
*3: If DKB is blocked, please dummy-replace the DKB.
TRBL02-520
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-530

2.2.12 Recovery Procedure for the System Lock during a Setting Change
When any of the following occurs while working on a setting change by Storage Navigator or others, the
system is locked and inoperable.

• When clicking the [×] button in the upper right of the window of the operating Web browser and closing
the window
• When restarting the client PC which uses the Web browser
• When shutting down the Maintenance PC or removing it from the storage system while more than one
asynchronous task (*) of Web Console is not complete (The second and later tasks are in the Waiting
status.)
*: Asynchronous tasks operated on Web Console include LDEV creation, LDEV formatting, LDEV
shredding, pool shrink, encryption editing, and parity consistency check. Asynchronous tasks are
executed without waiting for completion of other tasks.
• When a Web browser session times out during maintenance operation

Perform the recovery in the following procedure.

NOTE: If unlocking the system carelessly, it may become an unexpected status. Use this
procedure only when it is absolutely necessary.

START

Force release system lock

(Refer to MAINTENANCE PC
SECTION “3.17 Force Release
System Lock”)

Click the refresh button ( ) in the

window.

Is the system unlocking No

successful? (*1)

Yes

END T.S.D. call

*1: Confirm that “System Unlocked” is displayed on the Lock Release button ( ).

TRBL02-530
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-540

2.2.13 Error Recovery When Adding Cache Memories/Cache Flash Memories

Recover the failures in the following procedure when adding Cache Memories/Cache Flash Memories.

START

Did the Yes

Controller Board fail to
block?
Perform the maintenance in accordance
No with the message displayed in the
“Maintenance Utility” window.

Add Cache Memories/Cache Flash

Memories again.
Did the No
Controller Board fail to END
recover?
Yes

Do the blocked No
parts exist?

Yes

1 T.S.D. call
(TRBL02-550)

TRBL02-540
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-550

Is the
configuration of both CTLs No
matched in the “Maintenance
Utility window”?

Yes

Is the addition of the

Cache Memories/Cache Flash Memories No
completed in the “Maintenance Utility”
window? (*1) To return to the original Cache Memory/
Cache Flash Memory configuration,
Yes perform the dummy replacement of
the Controller Board to which Cache
Refer to the REPLACEMENT Memories/Cache Flash Memories were
SECTION (REP00-00) and replace the added according to REPLACEMENT
blocked parts. SECTION “2.4 Replacing a Controller
Board”. In the dummy replacement
procedure, remove the added Cache
Memories/Cache Flash Memories.

Refer to the REPLACEMENT

SECTION (REP00-00) and replace the
blocked parts.

Add Cache Memories/Cache Flash

Memories again.

Did you replace any of the CTLs, No

Cache Memories, or FANs?

Yes Refer to REPLACEMENT SECTION

“2.4 Replacing a Controller Board” and
END perform the dummy replacement.

*1: Select [Controller Chassis] in the “Maintenance Utility” window and click the [CTL] tab to check
the Cache Memory status.

TRBL02-550
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-560

2.2.14 Error Recovery When Removing Cache Memories/Cache Flash Memories

Recover the failures in the following procedure when removing Cache Memories/Cache Flash Memories.

START

After removing the Cache

Memories/Cache Flash Memories, is the No
Storage System configuration in the “Maintenance Utility”
window the same status as before the
removal? (*1)

Yes

Return the removed Cache Memories/

Cache Flash Memories to the original
conditions.

Refer to REPLACEMENT SECTION

“2.4 Replacing a Controller Board” and
perform the dummy replacement. (*2)

1
(TRBL02-570)

TRBL02-560
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-570

Is the configuration of both

No
CTLs matched in the “Maintenance Utility”
window?

Yes

Does the removal of the

Cache Memories/Cache Flash Memories Yes
completed in the “Maintenance Utility”
window?

No

Remove the Cache Memories/Cache Flash Memories

again. (*3)

END

*1: Select [Controller Chassis] in the “Maintenance Utility” window and click the [CTL] tab to check
the Cache Memory status.
*2: If the operation is suspended due to reboot of the maintenance PC, perform the dummy
replacement of both Controller Boards.
*3: The removal of Controller 1 may be completed depending on the detail of the removal failure. In
this case, if removing it again, Controller 2 starts the processing.

TRBL02-570
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-580

2.2.15 Transmission Failure and Timeout Occur Repeatedly After MPC Reboot
Though maintenance LAN and Maintenance PC Status are normal, Maintenance PC fail in processing
execution repeated. In this case, Maintenance PC might fail in a cause of abnormal state of management
LAN.

START

No
Is SVP connected?

Yes T.S.D call

Check the status of the management

LAN. For example, run ping to the
CTL from the command prompt on
SVP.

Is status
No
of Management LAN normal?
(*1)
Yes MPC might be fail in a cause of
abnormal state of Management LAN.
Please do repair the Management
LAN. (*2)

T.S.D call END

*1: Please check whether ping isnʼt slow in response.

*2: Ask the customer to perform the recovery operation according to the “Service Processor Technical
Reference”.

TRBL02-580
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-590

2.2.16 Recovery Procedure when ALM LED (red) on Drive/DBPS/ENC is not Turned off
Perform this recovery procedure in the following cases.
• When Drive Status is other than “Blocked” and “Failed”
• When PS Status or ENC Status is “Normal”

The ALM LED (red) on the Drive, PS or ENC might fail to go out due to the CTL, ENC, DKB or SAS PORT
blockade.

Turn off the LED in accordance with the following procedure.

Note that the PS described here is the DBS2/DBS/DBL/DB60/DBF/DBN power supply (DBPS).

START

Is the status
No
of the CTL, ENC and DKB all
“Normal”?
Perform the maintenance work of the
Yes CTL, ENC or DKB whose status is
not “Normal” in accordance with the
maintenance priority in “2.4 Failures
of Multiple Parts”.

Was the maintenance No

work successful?

Yes T.S.D call

Did the
No
target (*1) ALM LED (red) go
out?
Yes

1 END
(TRBL02-600)
*1: The target means a Drive in the status of other than “Blocked” and “Failed” and whose ALM LED
(red) lights up, or a PS or ENC whose ALM LED (red) lights up when the PS status or the ENC
status is “Normal”.

TRBL02-590
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-600

ENC Which is the target (*1) PS

part?

Restore the other ENC in the

same DB. Drive Is the other PS in the No
same DB “Normal”?
No Is the Drive [utilization] Recover the other PS in the
status DATA? Yes same DB.

Yes

Are other Drives No

in the same parity group
“Normal”?
Recover other Drives in the same
parity group.
Yes

Perform the dummy replacement of

the target (*1). (See REP02-03-10
for Drive, REP02-16-10 for ENC, or
REP02-15-10 for DBPS.)

Did the target (*1) No

ALM LED (red) go out?

Yes T.S.D call

END

*1: The target means a Drive in the status of other than “Blocked” and “Failed” and whose ALM LED
(red) lights up, or a PS or ENC whose ALM LED (red) lights up when the PS status or the ENC
status is “Normal”.

TRBL02-600
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-610

2.2.17 Recovery Procedure at SFP Replacement

START

Is the SIM = 21a8xx No

output at replacement?
Perform the replacement with the same SFP
Yes again.

Check the type of CHB with SFP to be

replaced using Maintenance Utility
Yes Has the replacement
succeeded?
END
Is the CHB type “32 G No No
Ready 4 Port FC”?

Yes
Display the “Port Status” window using Maintenance
Utility (MPC03-1160), and check the Data Transfer
Rate in the SFP Type column.

Is the Data Transfer Yes

Rate 32 Gbps?

No

Is the SFP with 32 Gbps No

mounted? (*1)

Yes
See INSTALLATION SECTION “3.9 Changing the Perform the replacement with the new SFP
Type of Small Form-Factor Pluggable (SFP)”, set again.
the data transfer rate to 32 Gbps, and perform the
replacement with the same SFP again.
Yes Has the replacement
succeeded?

No
END T.S.D call

*1: Check the record at the time of delivery, or remove the SFP and check the appearance. See
INST03-09-70, INST03-09-180, INST03-09-290.
TRBL02-610
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-620

2.2.18 Recovery Procedure when Procedure for Small Form-Factor Pluggable (SFP) Data
Transfer Rate Change fails

START

Display the “Port Status” window using Maintenance

Utility (MPC03-1160), and check the Data Transfer
Rate in the SFP Type column.

Is the changed
data transfer rate set in procedure No
for Changing the Type of SFP displayed in “Data 1
Transfer Rate”? (See INST03-09- (TRBL02-630)
10.)

Yes
2

Is the SFP already replaced with the one No

that has the new data transfer rate?

Yes
Replace the SFP with a maintenance part by following Replace the SFP with the one that has the new
the procedure in REPLACEMENT SECTION “2.13 data transfer rate by following the procedure in
Replacing a Small Form-Factor Pluggable (SFP)”. REPLACEMENT SECTION “2.13 Replacing a Small
Form-Factor Pluggable (SFP)”.

Is the SFP Status No

normal?

Yes

END T.S.D call

TRBL02-620
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-630

Perform the procedure for changing the SFP data

transfer rate again. (*1)

Is the procedure for

changing the SFP data transfer rate Yes
successfully completed? Is the SFP status
normal?
END
No
Display the “Port Status” window using Maintenance
Utility (MPC03-1160), and check the Data Transfer
Rate in the SFP Type column.

Is the changed
data transfer rate set in procedure No
for Changing the Type of SFP displayed in “Data
Transfer Rate”? (See INST03-09-
10.)

Yes

2 T.S.D call
(TRBL02-620)

*1: When an SFP with the changed data transfer rate is already inserted, perform dummy replacement
(Pull out the SFP and then insert it into the same port).

TRBL02-630
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-631

2.2.19 Error Recovery When Cache Memories/FANs Are Replaced

START

Refer to REPLACEMENT SECTION

“2.4 Replacing a Controller Board” and
perform the dummy replacement.

No
Normally ended?

Yes

END T.S.D call

TRBL02-631
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-632

2.2.20 Actions when 00002-002145 Error is Displayed in the Web Server Status Window
View the communication service log (see “[Link] Background Service Log” (TRBL03-1100)) to check
troubleshooting codes and coping methods.
If the problem persists, contact the Technical Support Division.

TRBL02-632
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-633

2.2.21 Troubleshooting When the Error Message (32061-208063) Appears in the

Maintenance Utility window during Maintenance Work of Controller Chassis/
Controller Board
When the error message (32061-208063) appears during maintenance work and [System Locked] does
not change to [System Unlocked] in the upper part of the “Maintenance Utility” window (by clicking the
refresh button in the window) within a period of time described in a section of the maintenance manual
for performing the maintenance work (other than TROUBLESHOOTING SECTION), perform the
troubleshooting corresponding to each maintenance work as shown in the table below.

Table 2-2 Maintenance work and troubleshooting page

Maintenance work Troubleshooting page
Maintenance requiring removal and installation of CTL TRBL02-260

NOTE: If you cannot solve the problem in the way shown in Table 2-2, perform “2.2.22
Troubleshooting When Maintenance Work Cannot Be Completed within Two Hours”.

TRBL02-633
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-634

2.2.22 Troubleshooting When Maintenance Work Cannot Be Completed within Two Hours
If maintenance work cannot be completed when more than two hours have passed, perform the following
troubleshooting steps.
If System Monitor of Maintenance Utility is started before maintenance work, the system lock might not be
released even after the maintenance work is completed. When the “System Monitor” window is running, close it.

START

Open Maintenance Utility window.

Is “System No
Locked” displayed as the system
lock status?
Perform “2.2.23 Troubleshooting Wait until the estimated time has
When the Error Message (32061- elapsed.
Yes
208063) Appears in the Maintenance
Utility Window during a
Maintenance Operation”.

Has
the estimated END
time (see the table in (*1)) No
elapsed since the maintenance
work was started?
(*3)

Yes

T.S.D. call

*1: The estimated time for maintenance is as follows:

No. Maintenance work Maximum time
1 Controller Board Replacement (*2) 4 hours
2 Adding Cache Memory/Cache Flash Memory 4 hours
3 Shared Memory (SM) Installation 8 hours
4 Removing Cache Memory 4 hours
5 Removing Shared Memory (SM) 8 hours
6 Other than above 2 hours
*2: Including a variety of replacement operations that can be selected by using the [Replace] button in
the [CTLs] tab in the “Controller Chassis” window.
*3: If System Monitor is running and the system lock is not released after the estimated time for
maintenance (*1) has passed, release the system lock forcibly according to “2.2.12 Recovery
Procedure for the System Lock during a Setting Change”. Then, perform “2.2.23 Troubleshooting
When the Error Message (32061-208063) Appears in the Maintenance Utility Window during a
Maintenance Operation”. (In the procedure 2.2.23, skip the operation to release the system lock
forcibly because it is already done in the procedure 2.2.12.)
TRBL02-634
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-635

2.2.23 Troubleshooting When the Error Message (32061-208063) Appears in the

Maintenance Utility Window during a Maintenance Operation
When the error message (32061-208063) appears in the Maintenance Utility window during a maintenance
operation, perform the following troubleshooting steps.

START

Is “System No
Locked” displayed as the system
lock status?
Release the system lock forcibly. See
(MPC03-1050).
Yes
Solve the problem according to
“2.2.22 Troubleshooting When
Maintenance Work Cannot Be No
Is SIM reported?
Completed within Two Hours”.

Yes
Solve the problem according to “2.3
Analyze by SIM Log”.

Check the normality according to

“2.5 Checking Normality”.

END

TRBL02-635
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-636

2.2.24 Actions when 20123-107008 Error is Displayed in the Web Server Status Window

START

Connect the Maintenance PC and

check the capacity of installed cache
memory and the Shared Memory
Function status. (*1)

Is it possible to check No
them?

Yes
Check whether the capacity of
installed cache memory is sufficient
for the shared memory currently
set. For the cache memory capacity
required for the Shared Memory
Function, see INSTALLATION
SECTION “3.1.1 Cache Capacity and
the Number of Required Options”.

Is
the capacity
of installed cache memory Yes
sufficient for the shared
memory?
T.S.D. call
No
Tell the customer that the capacity
of installed cache memory is not
sufficient for the shared memory
currently set and cache memory
needs to be added. Then, make sure
to add cache memory (INST03-
07-10) so that the cache memory
capacity is sufficient for the shared
memory capacity.

To remove cache memory and shared

memory, remove shared memory
(INST04-08-10) first, and then
remove cache memory (INST04-07-
10).

END

TRBL02-636
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-637

*1: How to check the set Shared Memory Function and cache memory capacity
1. Connecting a Maintenance PC
Connect the Maintenance PC and the Storage System.
• Connect the Maintenance PC and the Controller Board via LAN cable referring to
MAINTENANCE PC SECTION “2.2 Connecting Maintenance PC to Storage System”.
2. Starting Maintenance Utility
Start Maintenance Utility (refer to MAINTENANCE PC SECTION “2.7.3 Starting the
Maintenance Utility Window by Specifying IP Address of CTL”).
3. Checking the Shared Memory Function and cache memory configuration
(1) <Main Window>
Select the [Controller Chassis] tab in the main window.
(2) <Controller Chassis Window>
Click the [CTLs] tab in the “Controller Chassis” window to display the Cache Memory
status, its installed capacity, and the Shared Memory Function status.

TRBL02-637
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-638

2.2.25 Procedure When Initialization of Duplicated Data Ended Abnormally

The following is the procedure when initialization of duplicated data failed with either of the following errors
output.
• Error message (03405-208343) in Storage Navigator
• “An internal error occurred. (SSB1: 2ee7 SSB2:feec)” in error information of asynchronous commands in
CCI (Command Control Interface)
(Display the error information of asynchronous commands by running the “raidcom get command_status”
command.)

START

No
Is SSB = 2cc7 output?

Yes
Did
you retry Yes
initialization of duplicated
data?
Did you
No Yes
retry initialization of
duplicated data twice or
more?

No T.S.D. call

Click [Apply] in the “Initialize After 24 hours have passed since

Duplicated Data” window to retry. (a) (a) was done, click [Apply] in the
(*1) “Initialize Duplicated Data” window
to retry. (*1)

END

*1: For CCI, execute the [raidcom reset command_status] command to clear the error information of
asynchronous commands, and then run the [raidcom initialize pool] command.

TRBL02-638
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-640

2.3 Analyze by SIM Log

Not only when the SIM is automatically reported by the remote maintenance function, but when either of the
following occurs, take action according to the workflow shown below.
• In another trouble shooting workflow, you are instructed to perform the maintenance work according to the
SIM.
• Unrecovered SIMs remain in the “Alerts” tab in the main window of the Maintenance Utility.

START

Check the SIM in

the SIM RC SECTION. Is there the Yes
reference code of the SIM in the table
in TRBL02-650?

No
Refer to ACC (ACTION CODE) Execute the Recovery Procedure of the
SECTION (ACC00-00), confirm ACC reference code.
and prepare a necessary service part.

Execute REPLACEMENT SECTION

(“1.6 Parts Replacement Processing
List”) of the work ID.

TRBL02-640
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-650

Reference Code Recovery Procedure

21a8xx, 21aaxx 3.1 SFP Module Failure Detection (SIM = 21a8xx, 21aaxx)
410001, 410002 3.2 Response to a FLASH DRIVE/ENCRYPTION PG LDEV FORMAT Failure
(SIM = 41000x)
ac50xx, cf12xx, cf22xx 3.3 Recovery procedure when DB power off was detected or when SAS/NVMe
port blockage occurred (SIM = ac50xx, cf12xx, cf22xx)
7ffa00 3.4 Action When Time Synchronization Failed (SIM = 7ffa00)
3a0xyy 3.5 Recovery Procedure for LDEV Blockade due to Firmware Error (SIM =
3a0xyy)
ffe800 3.6 Recovery Procedure for the Failure on the Occurrence of Unmatched Memory
Installation Capacity (SIM = ffe800)
fe0000 3.7 Recovery procedure of SIM occurrence during battery charge (SIM = fe0000)
fe01xx, fe02xx 3.8 Action when Cache Write Through by battery factor is detected (SIM =
fe0100, fe0200)
db0xxx, db1xxx, db2xxx, 3.9 Isolation and Recovery Procedure for Common SAS/NVMe Failure (SIM =
db3xxx, db4xxx, db5xxx, db0xxx, db1xxx, db2xxx, db3xxx, db4xxx, db5xxx, db6xxx, db7xxx, df6xxx,
db6xxx, db7xxx, df6xxx, df7xxx, df8xxx, df9xxx)
df7xxx, df8xxx, df9xxx
7d01xx, 7d02xx 3.10 Recovery Procedure for LAN Error (SIM = 7d01xx,7d02xx)
fff50x 3.11 Recovery Procedure for the Failure on Both Sides of CACHE at the Time of
Starting (SIM = fff50x)
fff0xx, fe05xx 3.12 Recovery Procedure When Cache Correctable Error Is Detected (SIM =
fff0xx, fe05xx)
46cxxx, 46dxxx, ef8xxx, 3.13 Recovery Procedure for LDEV Blockade (SIM = ef8xxx, ef9xxx, db8xxx,
ef9xxx, db8xxx, db9xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx, dfbxxx, 46cxxx, 46dxxx)
dbaxxx, dbbxxx, dfaxxx,
dfbxxx, 46cxxx, 46dxxx
af110x, af120x 3.14 Response to the Occurrence of External Temperature Warning or Alarm (SIM
= af110x, af120x)
af100x 3.15 Response to the Detection of CPU Abnormal Temperature (SIM = af100x)
af420x 3.16 Response to the Detection of Invalid CEDT(SIM = 399f0x)
aff20x 3.17 Response to the Detection of Uninstalled CFM (SIM = aff20x)
af400x 3.18 Response to the Occurrence of BKM or BKMF Warning (SIM = af400x)
fffexx 3.19 Response to the Detection of Forced Volatilization Warning (SIM = fffe0x)
af200x 3.20 Response to the Occurrence of DKCPS Warning (SIM = af200x)
af60xx, af61xx, af62xx 3.21 Response to the Detection of Abnormal DBPS Input Voltage (SIM = af60xx,
af61xx, af62xx)
399e0x, 399f0x, af000x 3.22 Response to the Detection of Invalid CEMODE (SIM = 399e0x)
3071xy, 3072xy 3.23 Recovery Procedure When CHK1B or CHK3 Threshold Over Occurs (SIM =
3071xy, 3072xy)
3c9500 3.24 Recovery Procedure for Warning of Channel Board/Disk Board Type (SIM
RC = 3c9500)
ffe700, ffeb00, ffcd0x, 3.25 Isolation Procedure for Failed Part in CACHE Volatilization (SIM = ffe700,
ffcfxx, 610002 ffeb00, ffcd0x, ffcfyx, 610002)
dbcxxx, dbdxxx, dbexxx, 3.26 Isolation and Recovery Procedure for Drive Link Rate Error (SIM = dbcxxx,
dbfxxx, dfcxxx, dfdxxx dbdxxx, dbexxx, dbfxxx, dfcxxx, dfdxxx)
(To be continued)

TRBL02-650
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-660

(Continued from the preceding page)

Reference Code Recovery Procedure
452xxx, 462xxx, 455xxx, 3.27 Drive failure recovery procedure
465xxx, 454xxx, 464xxx,
453xxx, 463xxx, 4b8xxx,
4b9xxx, 4baxxx, 4bbxxx,
4bcxxx, 4bdxxx, 4bexxx,
4bfxxx, 4c8xxx, 4c9xxx,
4caxxx, 4cbxxx, 4ccxxx,
4cdxxx, 4cexxx, 4cfxxx,
eb6xxx, eb7xxx, efcxxx
50axyy, 50bxyy, 50cxyy, 3.31 Procedure for Responding to the Used Endurance of Flash Drives, NVMe
50dxyy Drives, and Flash Module Drives (FMDs) (SIM = 50axyy, 50bxyy, 50cxyy,
50dxyy)
ffccxy 3.32 Recovery Procedure for CFM Patrol Check Error (SIM = ffccxy)
760000 3.33 Recovery Procedure for CUDG Error (SIM = 760000)
7ff7xx 3.34 Procedure for responding to the product program expiration (SIM = 7ff7xx)
7ff8xx 3.35 Procedure for responding to an excess of the allowed capacity (SIM =
7ff8xx)
7ff9xx 3.36 Procedure for responding to the prerequisite program product expiration (SIM
= 7ff9xx)
effbxx, effcxx, effdxx, 3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx,
effexx effcxx, effdxx, effexx)
af7000, af7100 3.38 When Detecting Abnormal DB External Temperature (SIM = af7000, af7100)
af210x 3.39 Response to the Detection of Abnormal DKCPS Input Voltage (SIM =
af210x)(Use AC input voltage)
fffa0x 3.40 Response to the Occurrence of Battery Warning (SIM = fffa0x)
aff1xx 3.41 Recovery Procedure when a GUM Failure Occurs (SIM = aff1xx)
7d05xx 3.42 Recovery procedure when an alert notification failure occurs (SIM = 7d05xx)
7d03xx, 7d04xx 3.43 Response to a loss of the GUM audit log and the warning issuance (unsent
audit log occurrence) (SIM = 7d03xx, 7d04xx)
aff0xx 3.44 Response when UPS warning occurs (SIM = aff0xx)
af50xx, af51xx, af52xx 3.45 Response to the Occurrence of DBPS Warning (SIM = af50xx, af51xx,
af52xx)
3c9600 3.46 Response to the Detection of Unmounted Channel Board (SIM = 3c9600)
eb8xxx, eb9xxx, efexxx 3.47 Procedure for Responding to the Firmware Replacement Failure due to
Cache High Load (SIM = eb8xxx, eb9xxx, efexxx)
cf11xx 3.48 Recovery Procedure for the SAS PORT Temporary Failure (SIM = cf11xx)
50f000 3.49 Procedure for Responding to the Flash Module Drive Firmware Version
Warning (SIM = 50f000)
7d0900 3.50 Recovery Procedure When DKC Warning Occurs (SIM = 7d0900)
7d06xy 3.51 Recovery Procedure When an MP Error Occurs (SIM = 7d06xy)
2154xx 3.53 Recovery Procedure When SWPK is Blocked (SIM = 2154xx)
ffd400 3.55 Recovery Procedure When the Part Installation Error Occurs (SIM = ffd400)
4c4xxx, 4c5xxx 3.56 Recovery Procedure When Flash Module Drive Initialization Fails (SIM =
4c4xxx, 4c5xxx)
af4d0x 3.57 Recovery Procedure When the Panel Switch Warning (SIM = af4d0x)
3073xx 3.58 Recovery Procedure When Processor Is Blocked (SIM = 3073xx)
180000 3.59 Response to a Loss of the DKC Audit Log (SIM = 180000)
30750x 3.60 Recovery Procedure When CFM Failure Occurs (SIM = 30750x)
4d1xyy 3.61 Recovery Procedure for Differential Area Blocking (SIM = 4d1xyy)
cf880x 3.62 Recovery Procedure for CTL Blocking (SIM = cf880x)
7d0bxx 3.63 Recovery Procedure when the Configuration Backup Fails (SIM = 7d0bxx)
(To be continued)
TRBL02-660
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-670

(Continued from the preceding page)

Reference Code Recovery Procedure
af46xx 3.64 Response to the Detection of SWPK Temperature Warning (SIM = af46xx)
af4c0x 3.65 Response to the Occurrence of CHBBFAN Warning (SIM = af4c0x)
af4a0x 3.66 Response to the Occurrence of CHBBPS Warning (SIM = af4a0x)
af4b0x 3.67 Response to the Detection of Abnormal CHBBPS Input Voltage (SIM =
af4b0x)
afa0xx, afa1xx, afa2xx 3.68 Recovery Procedure When the CHBB Firmware Update Occurs (SIM =
afa0xx, afa1xx, afa2xx)
fe030x 3.69 Recovery Procedure When an Incorrect CFM Type or a Shortage of CFM is
detected (SIM = fe030x)
7d00xx 3.71 Recovery Procedure When the GUM Failure Occurs (SIM = 7d00xx)
cf13xx 3.72 Recovery Procedure When the SAS CTL Failure Is Detected (SIM = cf13xx)
fff40x 3.73 Recovery Procedure for Cache Area Failure (SIM = fff40x)
4e4xxx, 4e6xxx, 4e8xxx 3.76 Recovery Procedure When Media Sanitization Ends (SIM = 4e4xxx, 4e6xxx,
4e8xxx)
14200x 3.77 Recovery Procedure for Transmitted data abnormality between MP and GUM
(SIM = 14200x)
af300x 3.79 Recovery Procedure for Environmental Microcomputer Warning (SIM =
af300x)
2120xx 3.80 Recovery Procedure for Channel Port Blockade (SIM = 2120xx)
3c9800 3.81 Recovery Procedure for Warning of Accelerator Fan Module (ACLF) type
(SIM = 3c9800)
af80xx, af81xx, af82xx 3.82 Recovery Procedure for ENC Error (SIM = af80xx, af81xx, af82xx)
39b0xx 3.83 Recovery Procedure When an MP Patrol Check Error Occurs (SIM =
39b0xx)
2190xy 4.3 Recovery Procedure for AL_PA Conflict (SIM = 2190xy)
3c97xx 4.5 Recovery Procedure When Disconnection of Host Is Detected during iSCSI
Firmware Update (SIM = 3c97xx)
ac9100 4.6 Procedure When Open System Host Reservation Is Detected (SIM = ac9100)
47dxyy, 47e700, 4b0xyy, 5. ShadowImage Error Recovery
47e600, 4b2xyy, 47e500,
4b4xyy, 7ff102
d4xyyy, dbxyyy, d48yyy, 6. TrueCopy Error Recovery
d4eyyy, dbeyyy, d4dyyy,
dbdyyy, 2180xy
47ec00 8.1 Recovery Procedure for Thin Image/Thin Image Advanced Failure due to SM
Volatilization (SIM = 47ec00)
4b3xyy, 7ff104 8.2 Recovery Procedure for Thin Image/Thin Image Advanced Failure (SIM =
4b3xyy, 7ff104)
602xxx, 604xxx, 605xxx, 8.3 Recovery Procedure for Pool Failure (SIM = 602xxx, 604xxx, 605xxx,
606xxx 606xxx)
603000 8.4 Recovery Procedure for Pool Failure (SIM = 603000)
670000 8.6 Recovery Procedure for Thin Image/Thin Image Advanced Failure (SIM =
670000)
(To be continued)

TRBL02-670
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-671

(Continued from the preceding page)

Reference Code Recovery Procedure
670100 8.8 Recovery Procedure for Thin Image I/O Performance Degradation Alert (SIM
= 670100)
47fyxx, 7ff106 9. Recovery from Volume Migration Failure
623xxx 10.2 Recovery Procedure for Pool Failure (SIM = 623xxx)
624000 10.3 Recovery Procedure for Pool Failure (SIM = 624000)
62b000 10.4 Recovery Procedure for Pool Failure (SIM = 62b000)
627xxx 10.5 Recovery Procedure for pool-VOL Blockade (SIM = 627xxx)
628000 10.6 Procedure for Releasing Protect Attribute of Data Retention Utility (SIM =
628000)
632xxx 10.12 Recovery Procedure When Automatic Pool Capacity Expansion Failed due
to a Pool-associated Factor (SIM = 632xxx)
21d0xx, 21d2xx, efd000, 11.1.2 Maintenance (Isolation) Procedure for a Failure on External Storage
ef5xxx, ff5xxx System (SIM = 21d0xx, 21d2xx, efd000, ef5xxx, ff5xxx)
21d0xx, 21d2xx, efd000 11.2 Recovery Procedure for External Device Failure
660100, 660200, 661000, 13. Failure recovery of Encryption License Key
661001
7d07xx [Link]
7d08xx 16. Recovery Procedure for GUM Information Recover Failure (SIM = 7d08xx)
7d0axx 17. Recovery Procedure for GUM Version Warning (SIM = 7d0axx)
680001 20.1 Recovery Procedure for dedupe and compression Operation Error (SIM =
680001)
680002 20.2 Recovery Procedure for Operation Error in Deleting Capacity-Saving-
Enabled DP-VOLs (without blocking/formatting) (SIM = 680002)
68bxxx 20.8 Recovery Procedure When Access to Metadata for dedupe and compression
Fails (SIM = 68bxxx)
68a000 20.9 Recovery Procedure When Inline Deduplication Process by dedupe and
compression Is Delayed (SIM = 68a000)
7d0d0x 23. Recovery Procedure for Corruption of GUM Configuration Information (SIM
7d0d0x)
493xyy 24. Procedure When Warning Threshold for Cache Write Pending Rate Is
Exceeded (SIM = 493xyy)
491000 25. Procedure When Overload of Cache Occurs (SIM = 491000)
46axxx, 46bxxx Collect Normal type dumps, and then contact the Technical Support Division.

TRBL02-671
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-680

2.4 Failures of Multiple Parts

When failures have occurred in multiple parts and actions need to be taken during the system operation,
follow the priority described in this section and start from the higher priority regardless of the error levels.
[For VSP G130, G350, G370, G700, G900, VSP F350, F370, F700, F900, VSP E990, E1090]
Table 2-3 indicates that the smaller number in the Priority item has the higher priority.
However, if the following SIMs are reported, take action to recover these SIMs first.
• When the key acquisition failure (SIM = 661000, 661001) is reported, preferentially perform the operation
described in 13.1 Recovery procedure when acquisition failure from key management server
(SIM = 661000, 661001).
• When the DB power off (SIM = ac50xx) is reported, preferentially perform the operation described in 3.3
Recovery procedure when DB power off was detected or when SAS/NVMe port blockage occurred (SIM =
ac50xx, cf12xx, cf22xx).
• When the DKCPS warning (SIM = af200x) is reported, preferentially perform the operation described in
3.20 Response to the Occurrence of DKCPS Warning (SIM = af200x).
• When the DBPS warning (SIM = af50xx,af51xx,af52xx) is reported, preferentially perform the operation
described in 3.45 Response to the Occurrence of DBPS Warning (SIM = af50xx, af51xx, af52xx).
• When the CPU abnormal temperature (SIM = af10xx) is reported, perform 3.15 Response to the Detection
of CPU Abnormal Temperature (SIM = af100x).

Table 2-3 Priority Table (VSP G130, G350, G370, G700, G900, VSP F350, F370, F700,
F900, VSP E990, E1090)
priority action part maintenance work
1 CTL (*1) Replace
2 DKB Replace
3 SWPK Replace
4 PCP Replace
5 PECB/PCIe cable Replace
6 CHB Replace
7 ENC Replace
8 CFM Replace
9 BKM/BKMF Replace
10 ACLF Replace
11 LANB Replace
12 HDD Replace
13 LDEV Format or Restore
14 other hardware Replace
15 Firmware Update Firmware
*1: When all the following are met, be sure to perform 10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx) before replacing a CTL. If you perform maintenance work in the
wrong order, data may be lost.
• There is a pool in which DP-VOLs for which Capacity Saving is enabled exist.
• There are blocked pool-VOLs in the pool.
• The status of the CTL to be replaced is Normal or Warning.
TRBL02-680
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-681

[For VSP E590, E790]

Table 2-4 indicates that the smaller number in the Priority item has the higher priority.
However, if the following SIMs are reported, take action to recover these SIMs first.

• When the DB power off (SIM = ac50xx) is reported, preferentially perform the operation described in 3.3
Recovery procedure when DB power off was detected or when SAS/NVMe port blockage occurred (SIM =
ac50xx, cf12xx, cf22xx) .
• When two or more of the following SIMs are reported without a CTL failure, preferentially perform the
operation described in 3.78 Recovery Procedure for Multiple Errors of DKCPS/BKM in CBSN .
DKCPS warning (SIM = af200x)
DKCPS input voltage Abnormality (SIM = af210x)
BKM warning (SIM = af400x)
Battery warning (SIM = fffa0x)
• When the CPU abnormal temperature (SIM = af10xx) is reported, perform 3.15 Response to the Detection
of CPU Abnormal Temperature (SIM = af100x) .

Table 2-4 Priority Table (VSP E590, E790)

priority action part maintenance work
1 CTL (*1) (*2) Replace
2 DKCPS Replace
3 DKB Replace
4 CHB Replace
5 ENC Replace
6 CFM Replace
7 BKM Replace
8 LANB Replace
9 HDD Replace
10 LDEV Format or Restore
11 other hardware Replace
12 Firmware Update Firmware
*1: When all the following are met, be sure to perform 10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx) before replacing a CTL. If you perform maintenance work in the
wrong order, data may be lost.
• There is a pool in which DP-VOLs for which Capacity Saving is enabled exist.
• There are blocked pool-VOLs in the pool.
• The status of the CTL to be replaced is Normal or Warning.
*2: When a CTL is specified as a part targeted for maintenance action by the report of SIM = ff210x
(LANB blocking), assume that the CTL has the eighth priority for action.

TRBL02-681
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-690

When all the following are met, be sure to perform 10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx) before replacing a CTL. If you perform maintenance work in the wrong
order, data may be lost.
• There is a pool in which DP-VOLs for which Capacity Saving is enabled exist.
• There are blocked pool-VOLs in the pool.
• The status of the CTL to be replaced is Normal or Warning .

Maintenance priority flow

[For VSP G130, G350, G370, G700, G900, VSP F350, F370, F700, F900, VSP E990, E1090]

START

Check SIMs

Is there a SIM No
without an action taken?

Yes END
Check maintenance parts by ACC

Is the CTL/ Yes

ISW/HIE/X-path maintenance
required?
Is
No No there a pool in which
DP-VOLs for which Capacity Saving
is enabled exist? (*2)
6
(TRBL02-691) Yes

No Are there
blocked pool-VOLs in the pool?
(*3)
Yes

Is the
No status of the target
CTL for maintenance “Normal” or
“Warning”? (See MPC03-
1160.)
7
Yes
(TRBL02-691)
Perform “10.5 Recovery Procedure for pool-
VOL Blockade (SIM = 627xxx)”.

TRBL02-690
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-691

Are both of the

following met?
・SIM = 3075xx is reported. Yes
・CFMs are blocked in the other CTL
than the blocked CTL.
Replace the CFMs first
according to “3.60 Recovery
No Procedure When CFM Failure
Occurs (SIM = 30750x)”.

Is SIM = 21e0xx
(ACLF blockade) reported for two Yes
ACLFs installed in the blocked
CTL?
Perform the replacement of the CTL.
At the same time, replace both the
No ACLFs installed in the target CTL
with maintenance parts.
Replace the CTL

Did the maintenance No

work fail? (*1)

Yes
6

Is the DKB maintenance Yes

required?
Replace the DKB
No

Did the maintenance No

work fail? (*1)

Yes 2
(TRBL02-690)

1
(TRBL02-700)

TRBL02-691
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-700

Is the SWPK Yes

maintenance required?
Replace the SWPK
No
Did the
No
maintenance work fail?
(*1)
Yes

Is the PCP Yes

maintenance required?
Replace the PCP
No

Did the
No
maintenance work fail?
(*1)
Yes

Is the PECB/ Yes

PCIe cable maintenance
required?
Replace the PECB/PCIe cable
No
Did the
No
maintenance work fail?
(*1)
Yes

5 (TRBL02-710) (TRBL02-690) 2

TRBL02-700
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-710

Is the CHB maintenance Yes

required?
Replace the CHB
No

Did the maintenance No

work fail? (*1)

Yes
Is the ENC maintenance Yes
required?
Replace the ENC
No

Did the maintenance No

work fail? (*1)

Yes
Is the CFM maintenance Yes
required?
Replace the CFM
No

Did the maintenance No

work fail? (*1)

Yes
Is the BKM/BKMF Yes
maintenance required?
Replace the BKM/BKMF
No

Did the maintenance No

work fail? (*1)

Yes
Is the ACLF Yes
maintenance required?
Replace the ACLF
No

Did the maintenance No

work fail? (*1)
2
Yes
3 (TRBL02-720) (TRBL02-690)

TRBL02-710
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-720

Is the LANB Yes

maintenance required?
Replace the LANB
No

Did the maintenance No

work fail? (*1)

Yes

Are DP-VOLs
for which Capacity
Saving is enabled, Deduplication Yes
System Data Volumes (Fingerprint), or
Deduplication System Data
Volumes (Data store) Perform “10.5 Recovery Procedure
blocked? (*4) for pool-VOL Blockade (SIM =
627xxx)”.

No

Is the HDD Yes

maintenance required?
Replace the HDD
No

Yes Did the maintenance

work fail? (*1)

No
Recover the LDEV as needed

Did the maintenance No

work fail? (*1)

Yes

4 2
(TRBL02-730) (TRBL02-690)

TRBL02-720
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-730

Is the LDEV Yes

maintenance required?
Recover the LDEV
No

Did the maintenance No

work fail? (*1)

Yes

Is other Yes
hardware maintenance
required?
Replace the hardware pointed out by
No ACC

Did the maintenance No

work fail? (*1)

Yes

The firmware is faulty. Update the

firmware. (See FIRM03-10.)

2
(TRBL02-690)

*1: Including the case when the maintenance work is suspended.

*2: How to check for a pool in which DP-VOLs for which Capacity Saving is enabled exist:
In the “Logical Devices” window of Web Console, if [Compression] or [Deduplication and
Compression] is displayed in the [Capacity Saving] column of a DP-VOL, Capacity Saving is
enabled for the DP-VOL. See [Pool Name (ID)] of the DP-VOL.
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only the DP-VOLs for which Capacity Saving is enabled, specify the column value
for the filter. For more details about filtering, refer to “System Administrator Guide”.

TRBL02-730
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-730A

*3: How to check whether there are blocked pool-VOLs:

In the “Logical Devices” window of Web Console, if [Pool] is displayed in the [Attribute] column
of a volume, the volume is a pool-VOL. If “Blocked” is displayed in the [Status] column of the
pool-VOL, the pool-VOL is blocked. To identify the pool to which the pool-VOL belongs, see [Pool
Name (ID)].
*4: How to check the blockade state of DP-VOLs for which Capacity Saving is enabled, Deduplication
System Data Volumes (Fingerprint), and Deduplication System Data Volumes (Data store):
In the “Logical Devices” window in Web Console, if [Blocked] is displayed in the [Status] column,
the volumes are blocked. For the DP-VOLs for which Capacity Saving is enabled, “Compression”
or “Deduplication and Compression” is displayed in [Capacity Saving]. For the two types of
Deduplication System Data Volumes, “Deduplication System Data Volume (Fingerprint)” or
“Deduplication System Data Volume (Data store)” is displayed in [Attribute].
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only the DP-VOLs for which Capacity Saving is enabled, Deduplication System Data
Volumes (Fingerprint), and Deduplication System Data Volumes (Data store), specify the column
value for the filter. For more details about filtering, refer to “System Administrator Guide”.

TRBL02-730A
Hitachi Proprietary DW850/DW900/DW1000
Rev.10.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-731

When all the following are met, be sure to perform 10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx) before replacing a CTL. If you perform maintenance work in the wrong
order, data may be lost.
• There is a pool in which DP-VOLs for which Capacity Saving is enabled exist.
• There are blocked pool-VOLs in the pool.
• The status of the CTL to be replaced is Normal or Warning .

Maintenance priority flow

[For VSP E590, E790]

START

Check SIMs

Is there a SIM No
without an action taken?

Yes END
Check maintenance parts by ACC

Is the CTL/ Yes

ISW/HIE/X-path maintenance
required?
Is
No No there a pool in which
DP-VOLs for which Capacity Saving
is enabled exist? (*2)
6
(TRBL02-731A) Yes

No Are there
blocked pool-VOLs in the pool?
(*3)
Yes

Is the
No status of the target
CTL for maintenance “Normal” or
“Warning”? (See MPC03-
1160.)
7
Yes
(TRBL02-731A)
Perform “10.5 Recovery Procedure for pool-
VOL Blockade (SIM = 627xxx)”.

TRBL02-731
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-731A

Are both of the

following met?
・SIM = 3075xx is reported. Yes
・CFMs are blocked in the other CTL
than the blocked CTL.
Replace the CFMs first
according to “3.60 Recovery
No Procedure When CFM Failure
Replace the CTL Occurs (SIM = 30750x)”.

Did the maintenance No

work fail? (*1)

Yes
6

Is the DKCPS Yes

maintenance required?
Replace the DKCPS
No

Did the maintenance No

work fail? (*1)

Yes

Is the DKB maintenance Yes

required?
Replace the DKB
No

Did the maintenance No

work fail? (*1)

Yes

1 2
(TRBL02-732) (TRBL02-731)

TRBL02-731A
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-732

Is the CHB Yes

maintenance required?
Replace the CHB
No
Did the
No
maintenance work fail?
(*1)
Yes

Is the ENC Yes

maintenance required?
Replace the ENC
No
Did the No
maintenance work fail?
(*1)
Yes

Is the CFM Yes

maintenance required?
Replace the CFM
No

Did the
No
maintenance work fail?
(*1)
Yes

Is the BKM Yes

maintenance required?
Replace the BKM
No
Did the
No
maintenance work fail?
(*1)
Yes

3 (TRBL02-733) (TRBL02-731) 2

TRBL02-732
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-733

Are DP-VOLs
for which Capacity
Saving is enabled, Deduplication Yes
System Data Volumes (Fingerprint), or
Deduplication System Data
Volumes (Data store) Perform 10.5 Recovery Procedure
blocked? (*4) for pool-VOL Blockade (SIM =
627xxx) .

No

Is the LANB
maintenance required? Yes
(SIM=ff210x is reported.)
Replace the CTL.

No
No
Did the maintenance
work fail? (*1)

Yes

Is the HDD Yes

maintenance required?
Replace the HDD.
No

Yes Did the maintenance

work fail? (*1)

No
Recover the LDEV as needed.

Did the maintenance No

work fail? (*1)

Yes

4 2
(TRBL02-734) (TRBL02-731)

TRBL02-733
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-734

Is the LDEV Yes

maintenance required?
Recover the LDEV
No

Did the maintenance No

work fail? (*1)

Yes

Is other Yes
hardware maintenance
required?
Replace the hardware pointed out by
No ACC

Did the maintenance No

work fail? (*1)

Yes

The firmware is faulty. Update the

firmware. (See FIRM03-10.)

2
(TRBL02-731)

*1: Including the case when the maintenance work is suspended.

*2: How to check for a pool in which DP-VOLs for which Capacity Saving is enabled exist:
In the “Logical Devices” window of Web Console, if [Compression] or [Deduplication and
Compression] is displayed in the [Capacity Saving] column of a DP-VOL, Capacity Saving is
enabled for the DP-VOL. See [Pool Name (ID)] of the DP-VOL.
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only the DP-VOLs for which Capacity Saving is enabled, specify the column value
for the filter. For more details about filtering, refer to “System Administrator Guide”.

TRBL02-734
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-735

*3: How to check whether there are blocked pool-VOLs:

In the “Logical Devices” window of Web Console, if [Pool] is displayed in the [Attribute] column
of a volume, the volume is a pool-VOL. If “Blocked” is displayed in the [Status] column of the
pool-VOL, the pool-VOL is blocked. To identify the pool to which the pool-VOL belongs, see [Pool
Name (ID)].
*4: How to check the blockade state of DP-VOLs for which Capacity Saving is enabled, Deduplication
System Data Volumes (Fingerprint), and Deduplication System Data Volumes (Data store):
In the “Logical Devices” window in Web Console, if [Blocked] is displayed in the [Status] column,
the volumes are blocked. For the DP-VOLs for which Capacity Saving is enabled, “Compression”
or “Deduplication and Compression” is displayed in [Capacity Saving]. For the two types of
Deduplication System Data Volumes, “Deduplication System Data Volume (Fingerprint)” or
“Deduplication System Data Volume (Data store)” is displayed in [Attribute].
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only the DP-VOLs for which Capacity Saving is enabled, Deduplication System Data
Volumes (Fingerprint), and Deduplication System Data Volumes (Data store), specify the column
value for the filter. For more details about filtering, refer to “System Administrator Guide”.

TRBL02-735
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-740

2.5 Checking Normality

Check whether the Storage System is restored to the normal status in accordance with the following flow
after recovering from the failure.

START

Can you check the Storage No

System directly?
Open “Maintenance Utility” window.
Yes

Does the
POWER LED (green) on No No Is the connection to
the Storage System light “Maintenance Utility” normal?
up? (*1)

Yes Yes

Does the Is
READY LED (green) on No No the “Storage system
the Storage System light status” of the Storage System
up? (*1) “READY”? (*2)

Yes Yes

Does the No
WARNING LED on the Storage
System go out? (*1)

Perform “2.1 Flow of failed

Yes
part isolation” again.

1
(TRBL02-750)

*1: See LOCATION SECTION “3.1 Switches and LEDs of Controller Chassis”.
*2: See MAINTENANCE PC SECTION “11.3.3 Navigation Area”.

TRBL02-740
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-750

Check whether any failed track and

blocked LDEV exist in accordance with
MAINTENANCE PC SECTION “3.29
Checking Existence of Pinned Track and
Blocked LDEV”.

Is there
any LDEV whose Yes
status is displayed as “Blocked” in
the “Status” column?
(*3) Start the “MPC” window (See MPC02-
220.) and the “Web Console”window
No (See MPC02-190.).

Recover the LDEV blockade

(See TRBL03-300) (*4)

Are there any failed Yes

track?
Start the “MPC” window (See MPC02-
No 220.) and the “Web Console”window
(See MPC02-190.).

Recover the failed track according to the

failed track recovery procedure on “4.2.1
Pinned Tracks”.

2
(TRBL02-760)

*3: Unformatted LDEVs are out of the target. Furthermore, the customers might intentionally block the
LDEVs due to the LDEV formatting or shredding. If any blocked LDEV exists, ask the customers
whether the LDEV blockade needs to be recovered.
*4: A case that a contact to the Technical Support Division is necessary exists in “3.13 Recovery
Procedure for LDEV Blockade (SIM = ef8xxx, ef9xxx, db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx,
dfbxxx, 46cxxx, 46dxxx)”. When the LDEV blockade cannot be solved, be sure to contact the
Technical Support Division and follow the judgment.

TRBL02-750
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-760

Check SIMs

Is there a SIM without No

an action taken?
If Controller Board replacement is
Yes performed when the customer uses
SNMP v3 for failure monitoring (*1),
ask him or her to perform the following
See “2.3 Analyze by SIM Log”.
work.
• Restart of the SNMP manager (or
reregistration of target storage systems
for monitoring on the SNMP manager)
• Trap report test
• Appropriate management of unchecked
traps in the storage network

Checking the health is

completed

*1: See “NOTICE: What the customer needs to do after Controller Board replacement” in “2.4
Replacing a Controller Board” in REPLACEMENT SECTION.

TRBL02-760
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL02-770

2.6 Troubleshooting When the Maintenance PC/SVP and GUM Cannot Communicate with
Each Other
Perform the following recovery procedure when the Maintenance PC/SVP and GUM cannot communicate
with each other.

START

Can you
connect to the storage No
system from the Maintenance
PC?

Yes
Reboot the GUM on the Controller Reset the GUM on the Controller
Board that has a problem according Board that has a problem according
to MAINTENANCE PC SECTION to MAINTENANCE PC SECTION
“3.18 Reboot GUM”. “3.26 Resetting GUM”.

Can
you connect to Yes
the storage system from the
Maintenance PC/
SVP?
END
No

Troubleshoot according to
“3.29.1 When I cannot be connected
from MPC to the GUM or Storage
System”.

TRBL02-770
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-10

3. Recovery Method of the Shared Platform Failure

3.1 SFP Module Failure Detection (SIM = 21a8xx, 21aaxx)
The recovery procedure when an SFP module failure occurs is indicated.

START

Is it ana SFP No
wrong type? (SIM = 21a8xx)
(*1)

Yes SFP module

No
failure?
(SIM = 21aaxx) (*2)

Yes

Replace the SFP module in the

location pointed by SIM Action Code.
END

END

*1: SFP wrong type factors

• When a LongWave SFP is used in the ShortWave setting port and a ShortWave SFP is used in the
LongWave setting port.
• When an unsupported SFP transceiver is installed.
• When the information on the SFP is not recognized correctly.
*2: SFP module failure factors
• When SFP module hardware failure is occurred.
• When an unsupported SFP transceiver is installed.

TRBL03-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-20

3.2 Response to a FLASH DRIVE/ENCRYPTION PG LDEV FORMAT Failure (SIM = 41000x)

See “2.2.6 Recovery procedure when LDEV formatting failed”.

TRBL03-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-30

3.3 Recovery procedure when DB power off was detected or when SAS/NVMe port
blockage occurred (SIM = ac50xx, cf12xx, cf22xx)

• When replacing a part in the following recovery procedure, do not check the checkbox for
Forcibly run without safety checks without a direction given by the Technical Support Division.
If you do so, customer data might be lost.
If an error occurs in process of part replacement, collect dumps and contact the Technical
Support Division.
• The Error Code (30762-208171) might be displayed during the following recovery procedure.
Do not click [Yes] because customer data is lost.
Contact the Technical Support Division according to the workflow.

When DB power off detection (SIM = ac50xx), SAS port blockage (SIM = cf12xx), or NVMe port
blockage(SIM = cf22xx) occurs, perform recovery actions as follows. (*3)
Priorities of maintenance of parts indicated by ACC depend on the parts to be maintained. When both
SIM = ac50xx, cf12xx, cf22xx are output, perform maintenance in the following priority order.
When there is no applicable part in the parts indicated by ACC, perform maintenance for the part of the
second priority.

Maintenance parts ac50xx cf12xx or cf22xx

PDU breaker Switch ON 1 -
DBPS replacement 2 -
ENC replacement 6 3
DKB replacement 8 4
SAS cable/NVMe cable replacement (*1) 7 5
CTL replacement (*2) - 9

*1: When replacing SAS cables/NVMe cables, perform the dummy replacement of the ENCs to which
the cables are connected (see REP02-16-10).
*2: For VSP G130, VSP G350, VSP F350, VSP G370 VSP F370, VSP E590, VSP E790.
*3: When blocked parts cannot be identified, Warning might not be displayed in ENC and DBPS
locations in Maintenance Utility.

TRBL03-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-40

START

1
Is DB power off SIM = No
3
ac50xx reported?
(TRBL03-51)
Did you go
Yes
No through this route three
times or more without any change in
SIM, DKC state, etc.?

Yes
Are all SIMs of
DB power recovered SIM = Yes T.S.D. call
ac51xx paired with DB power off SIM =
ac50xx reported? (*1) (*2)
When power-off recovery SIM = ac51xx is
output, wait for time multiplying the number
No of SIMs = ac51xx by five minutes (*3)

Are the
following met? 3
The storage system is VSP G130, (TRBL03-51)
G350, G370, F350, or F370. Yes
SIM = ac5000 is output and SIM = ac5100
is not output on CBSS/CBSL/
CBXSS/CBXSL.

13
No (TRBL03-101)

2
(TRBL03-50)

*1: When DBPS replacement, PDU ON etc. is performed, check SIM after five minutes.
xx in SIM = ac50xx indicates the Drive box number (hexadecimal). When DB power is
recovered, SIM = ac51xx whose xx is the same as that of SIM = ac50xx is output.
*2: When all of SAS PORTS/NVMe PORTS connected to the Drive box in which DB power is not
recovered are blocked, even if power feeding to the Drive box in which DB is powered off is
recovered, SIM = ac51xx is not output. If the situation occurs, call T.S.D.
*3: When replacing PDU ON, DBPS and others, check SIMs after five minutes or more elapse. It
requires about five minutes to recover the LDEV after DB power-off recovery SIM is output.

TRBL03-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-50

Does the
AC IN LED light up on all Yes
DBPSs in all DBs installed in the
storage system? Is it
possible to forcibly
No power off and restart DKC/DB? No
(Customers approval and check of
usage state are required
(*4))
5
Yes
(TRBL03-71)
Perform forced power off and restart of DKC/DB
according to TRBL15-10. (Correct the connection
between the DKC and the distribution board) (*1)

3
(TRBL03-51)
Have all PDU breakers been Yes
turned on?
Replace the failed part (DBPS whose LED is
No not lit) according to SIM = ac50xx ACC. (*2)
(*3)
Confirm the connection between the DKC
and the distribution board.
See (THEORY04-09-10)
1
Is it (TRBL03-40)
possible to forcibly
power off and restart DKC/DB? No
(Customers approval and check of
usage state are required Turn on all PDU breakers.
(*4))
Yes
Wait for the following time.
Shut down the DKC/DB forcibly and restart The number of SIMs = ac50xx Five
it in accordance with Procedure No.1 of minutes (*3)
TRBL15-10. (*1)

3 1
(TRBL03-51) (TRBL03-40)

*1: If DKC/DB is forcibly powered off and rebooted, DB power interruption recovery SIM is not
output. Furthermore, the forcible power off is different from the normal power off procedure,
confirm with the Technical Support Division and perform the operation.
*2: If you cannot replace DPBS, call T.S.D.
*3: If PDU on, DBPS replacement and so on are executed, check SIM after waiting for more than
5 minutes.
xx in SIM = ac50xx indicates the Drive box number (hexadecimal). When DB power is
recovered, SIM = ac51xx whose xx is the same as that of SIM = ac50xx is output.
*4: Check whether the temporary stop of the storage system in the forcible power-off and restart
process affects the system and confirm that you can get the approval from the customer.
TRBL03-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-51

Does the
blocked SAS PORT of No
SIM = cf12xx (or blocked NVMe PORT 4
of SIM = cf22xx) occur?
(TRBL03-70)
(*1)

Yes

Is the SIM
= effexx which shares No
common xx with SIM = cf12xx (or SIM
= cf22xx) being output?
(*1), (*2) Yes
Are five ENCs
7
displayed in ACC?
Yes (TRBL03-100)
No

Is there
the ENC temporary
failure recovery of SIM = Yes
cf14xx around the blocked SAS PORT
of SIM = cf12xx (or blocked
NVMe PORT of SIM
= cf22xx)? Is xx
Check the connection order and dummy (SAS Port #) in
replace a failed part in accordance with SIM the blocked SAS PORT of
No
= effexx ACC. (*2) No SIM = cf12xx (or blocked NVMe
PORT of SIM = cf22xx) and ENC
9 temporary failure recovery
8 of SIM = cf14xx
identical?
(TRBL03-60)
Is the Error Code No
(30762-208171) displayed? Yes

Yes END (*3)

4
Select [NO] and cancel the maintenance. (TRBL03-70)

T.S.D. call

*1: The xx in cf12xx, cf22xx, effexx represents SAS Port number xx (hexadecimal) or NVMe Port
number xx (hexadecimal).
*2: For the detail of the connection order, see 3.37 Recovery Procedure when Cable Connection Error
Occurs (SIM = effbxx, effcxx, effdxx, effexx) .
*3: The ENC temporary failure recovery of SIM = cf14xx reports that the blocked SAS PORT of SIM
= cf12xx (or NVMe PORT of SIM = cf22xx) on the SAS Port#/NVMe Port# shown by xx due
to the ENC temporary failure has been recovered automatically. Therefore, no action is required
such as part replacement for the blocked SAS PORT of SIM = cf12xx (or NVMe PORT of SIM =
cf22xx). To user inquiries, inform them to that effect.
If any blocked SAS PORT of SIM = cf12xx (or NVMe PORT of SIM = cf22xx) with a different xx
exists, ask the service personnel for maintenance.
TRBL03-51
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-60

Replace failed parts specified by ACCs

of SIM = cf12xx (or SIM = cf22xx) with
maintenance parts in order. (*1) (*3)

Is the SAS port or No

NVMe port blockage resolved? (*2)
(*4)

Yes
Is blocking all of the ENCs/ No
DKBs specified by ACCs unsuccessful
9 (30762-208342)?
(TRBL03-51) Are all of
Yes the failed parts specified
by ACCs of SIM = cf12xx (or SIM No
= cf22xx) replaced with
maintenance parts?

Yes

T.S.D. call

*1: When the target of replacement is ENC, there are cases where multiple ENCs are displayed in
Maintenance Utility. In this case, instead of replacing all ENCs with maintenance parts, replace
only the first ENC indicated in ACC of SIM = cf12xx (or SIM = cf22xx) with maintenance parts.
However, the ENCs not to be replaced with maintenance parts need to be powered off.
Remove and insert those ENCs when replacing the first ENC with a maintenance part.
*2: You can check whether the blockage is resolved by using the Maintenance Utility.
Check that the status of the DKB equipped with the SAS port/NVMe port is Normal.
*3: When replacing SAS cables/NVMe cables, perform the dummy replacement of the ENCs to which
the cables are connected (see REP02-16-10).
*4: Due to a drive error on the path to the replaced parts, the message (30762-208343) indicating an
error in the restoration processing might be output.
When the SAS port/NVMe port related to the replaced parts is in the Normal status, go to Yes.

TRBL03-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-70

Is there any LDEV whose No

status is displayed as Blocked in the Status
column? (*1)

Yes
Recover the LDEV blockade
(Refer to TRBL03-300) (*2)

Is there any drive whose No

status is displayed as Blocked or Failed in
the Status column?

Yes
Replace the blocked drive. (*3)

Is there any drive

for which PDEV replacement failed No
or whose status is displayed as
Warning?

Yes
Replace the ENC in the DB in which the drive in the
Blocked , Failed , or Warning status is installed
or the CTL. (*4) (*5)

Is the Error Code (30762-208171) No

displayed?

Yes
Select [NO] and cancel the maintenance.

Is there any
No Replace the HDD
drive whose status is displayed
Micro-program.
as Blocked , Failed , or
(See FIRM03-10)
Warning?
Yes
Is the version in the HDD
Current list later than or equal to the No
version in the HDD CFM Version list?
T.S.D. call
(*6) (See MPC05-1130)

Yes

END

TRBL03-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-70A

*1: Unformatted LDEVs are out of the target.

*2: A case that a contact to the Technical Support Division is necessary exists in 3.13 Recovery
Procedure for LDEV Blockade (SIM = ef8xxx, ef9xxx, db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx,
dfbxxx, 46cxxx, 46dxxx) .
When the LDEV blockade cannot be solved, be sure to contact the Technical Support Division and
follow the judgment.
*3: Perform dummy replacement first. When the dummy replacement fails, a Drive failure due to the
power-off is considered. Perform replacement with a new drive.
*4: Perform the dummy replacement first. If the dummy replacement fails, replace the ENC or CTL
because there is a possibility of a failure of the ENC or CTL.
*5: Replace the ENC or CTL in the cluster (CL) to which the blocked part belongs.
Port 0 failed: Replace the ENC or CTL in CL#1.
Port 1 failed: Replace the ENC or CTL in CL#2.
Blocked: Replace the ENC or CTL in both CLs.
Failed: Replace the ENC or CTL in both CLs.
*6: For an HDD whose firmware version is displayed in the HDD Current list but not displayed in the
HDD CFM Version list, you do not need to check it.

TRBL03-70A
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-71

Perform maintenance work for the SIM =

ac50xx for which the corresponding SIM =
ac51xx is not output. (*1)

Is the SIM
= cf12xx (or SIM =
cf22xx) which targets a SAS No
Port (or NVMe Port) which connects to
chassis number xx of SIM =
ac50xx being output?
(*2) 6
(TRBL03-81)
Yes

Is the SIM
= effexx which shares No
common xx with SIM = cf12xx (or SIM
= cf22xx) being output?
(*3)
10
Yes (TRBL03-80)
Check the connection order and dummy
replace a failed part (ENC) in accordance
with SIM = effexx ACC. (*4), (*5)

11

Is the Error Code No

(30762-208171) displayed?

Yes 1
Select [NO] and cancel the maintenance. (TRBL03-40)

T.S.D. call

*1: If multiple power interruption SIMs = ac50xx, for which the corresponding power interruption
recovery SIMs = ac51xx are not output, are output, perform maintenance work in ascending order
of the unit number (xx).
*2: ac50xx represents chassis number xx (hexadecimal). The xx in cf12xx, cf22xx, effexx represents
SAS Port number (hexadecimal)/NVMe Port number (hexadecimal).
*3: For the detail of the connection order, see 3.37 Recovery Procedure when Cable Connection Error
Occurs (SIM = effbxx, effcxx, effdxx, effexx) .
*4: SIM = cf11xx, cf12xx, cf22xx which is related to not replaced SAS Port/NVMe Port may be
reported after the replacement.
*5: If the UNIT connection cable order error (SIM = effexx) is output after the replacement/dummy
replacement, see 3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx,
effcxx, effdxx, effexx) .

TRBL03-71
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-80

10

Replace failed parts specified by ACCs

of SIM = cf12xx (or SIM = cf22xx) with
maintenance parts in order. (*1) (*2) (*3)
(*5)

Is the SAS port or NVMe No

port blockage resolved? (*4)

Yes
Is blocking all of the ENCs/ No
DKBs specified by ACCs unsuccessful
11 (30762-208342)?
(TRBL03-71) Are all of
Yes the failed parts specified
by ACCs of SIM = cf12xx (or SIM No
= cf22xx) replaced with
maintenance parts?

Yes

T.S.D. call

*1: When the target of replacement is ENC, there are cases where multiple ENCs are displayed in
Maintenance Utility. In this case, instead of replacing all ENCs with maintenance parts, replace
only the first ENC indicated in ACC of SIM = cf12xx (or SIM = cf22xx) with maintenance parts.
However, the ENCs not to be replaced with maintenance parts need to be powered off.
Remove and insert those ENCs when replacing the first ENC with a maintenance part.
*2: SIM = cf11xx, cf12xx, cf22xx which is related to not replaced SAS Port/NVMe Port may be
reported after the replacement.
*3: If the UNIT connection cable order error (SIM = effexx) is output after the replacement/dummy
replacement, see 3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx,
effcxx, effdxx, effexx) .
*4: You can check whether the blockage is resolved by using the Maintenance Utility.
Check that the status of the DKB equipped with the SAS port/NVMe port is Normal.
*5: When replacing SAS cables/NVMe cables, perform the dummy replacement of the ENCs to which
the cables are connected (see REP02-16-10).

TRBL03-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-81

Is the SIM
= effexx which targets
SAS Port/NVMe Port connected No
to chassis number xx of SIM =
ac50xx being output?
(*1) 12
(TRBL03-90)
Yes

Check the connection order and dummy

replace a failed part (ENC) in accordance
with SIM = effexx ACC. (*2), (*3)

Is the Error Code (30762- No

208171) displayed?

Yes 1
(TRBL03-40)
Select [NO] and cancel the maintenance.

T.S.D. call

*1: ac50xx represents chassis number xx (hexadecimal). The xx in effexx represents SAS Port number
(hexadecimal)/NVMe Port number (hexadecimal). For the detail of the connection order, see 3.37
Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx, effcxx, effdxx, effexx) .
*2: SIM = cf11xx, cf12xx, cf22xx which is related to not replaced SAS Port/NVMe Port may be
reported after the replacement.
*3: If the UNIT connection cable order error (SIM = effexx) is output after the replacement/dummy
replacement, see 3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx,
effcxx, effdxx, effexx) .

TRBL03-81
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-90

12

Replace ENCs/cables/DKBs specified by

ACCs of SIM = ac50xx with maintenance
parts in order. If DBPSs are specified by
ACCs, do not replace them here. (*1) (*2) (*3)

Is the
replacement with
maintenance parts completed No
normally? (If it is completed normally, a
message indicating the completion
is displayed in the
window.)
Is blocking all of the ENCs/ No
Yes DKBs specified by ACCs unsuccessful
(30762-208342)?
1
(TRBL03-40) Yes Are all of the ENCs/cables/ No
DKBs specified by ACCs replaced with
maintenance parts?

Yes

T.S.D. call

*1: In the Content-SIM window of the SVP, multiple ACCs specifying ENCs/cables/DKBs in which
failures might have occurred are displayed. Replace the ENCs/cables/DKBs with maintenance
parts in order from the one displayed on the top of the list until the replacement with maintenance
parts is completed normally.
*2: SIM = cf11xx, cf12xx, cf22xx which is related to not replaced SAS Port/NVMe Port may be
reported after the replacement.
*3: If the UNIT connection cable order error (SIM = effexx) is output after the replacement/dummy
replacement, see 3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx,
effcxx, effdxx, effexx) .

TRBL03-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-100

See [1] SSB Log of 5.3.1 Log Indication in MAINTENANCE

PC SECTION, and specify the following values from the detailed
data of SSB = a4b1 output near the time as the SAS PORT
blockade (cf12xx) or NVMe PORT blockade (cf22xx). (*1)
XX: SAS Port#/NVMe Port# of a failed part
YY: EXP# of a failed part

See the Location correspondence table (*3) and replace the

following corresponding failed parts.
1. ENC [XX/YY]: replacement with a maintenance part
2. ENC (in the lower Drive Box)
[XX/YY-1]: dummy replacement

Is the SAS port or NVMe No

port blockage resolved? (*2)
See the Location correspondence table (*3)
Yes and replace the following corresponding
failed parts.
ENC (in the lower Drive Box) [XX/YY-1]:
replacement with a maintenance part

Is the SAS port or NVMe No

port blockage resolved? (*2)
See the Location correspondence table (*3)
Yes and replace the following corresponding
failed parts.
CABLE [between ENC and ENC (in the
lower Drive Box)]: replacement with a
maintenance part (*4)

Yes Is the SAS port or NVMe

port blockage resolved? (*2)

Is the Error Code (30762- No No

208171) displayed?

Yes 4

Select [NO] and cancel the maintenance. (TRBL03-70)

T.S.D. call

TRBL03-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-101

13

Shut down the DKC/DB forcibly and restart it in

accordance with Procedure No.1 of TRBL15-10.

Has the Storage System No

started?

Yes
T.S.D Call

Is there any LDEV whose No

status is displayed as Blocked in the Status
column? (*2)

Yes
Recover the LDEV blockade
(Refer to TRBL03-300) (*3)

Is there any PDEV No

whose status is displayed as Blocked in
the Status column?

Yes

Replace the PDEV blockade. (*4)

(Refer to REP02-03-10)

Replace the HDD Firmware.

Is the version in the HDD
No (See FIRM03-20)
Current list later than or equal to the
Use the installation media for the SVP,
version in the HDD CFM Version list?
which comes with the Storage System and
(See MPC05-1130)
is owned by the customer, or the installation
media for the Maintenance PC whose
Yes version is the same as or later than the
DKCMAIN firmware version installed in
the Storage System.
END

*1: If DKC/DB is forcibly powered off and rebooted, DB power interruption recovery SIM is not
output. Furthermore, the forcible power off is different from the normal power off procedure,
confirm with the Technical Support Division and perform the operation.
*2: Unformatted LDEVs are out of the target.
*3: A case that a contact to the Technical Support Division is necessary exists in 3.13 Recovery
Procedure for LDEV Blockade (SIM = ef8xxx, ef9xxx, db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx,
dfbxxx, 46cxxx, 46dxxx) .When the LDEV blockade cannot be solved, be sure to contact the
Technical Support Division and follow the judgment.
*4: Perform dummy replacement first. When the dummy replacement fails, a Drive failure due to the
power-off is considered. Perform replacement in a new Drive.

TRBL03-101
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-110

*1: SSB detailed information

+0x0 +0x4 +0x8 +0xC
00000000: 7404190b 00279f00 b1a40000 00aa2000
00000010: 00000000 00002e0d 00000000 00000004
00000020: 00000000 0000009f a4b1d84f 74920000
00000030: 00000000 0000ff9f 00000000 00000000
00000040: d84f7492 80eeeeee eeeeeeee eeeeeeee
00000050: 21120083 00000000 100000ee 00010000
00000060: 800f0021 ffffffff 01210503 00000000
00000070: 02010046 00XXYY00 10000000 00100302
XX: SAS Port#/NVMe Port# of a failed part
YY: EXP# of a failed part

*2: You can check whether the blockage is resolved by using the Maintenance Utility.
Check that the status of the DKB equipped with the SAS port/NVMe port is Normal.

*3: Location correspondence table

• VSP G130, G350
SAS PORT# EXP# ENC SAS PORT# EXP# ENC
xʻ00ʼ xʻ00ʼ CTL1 xʻ08ʼ xʻ00ʼ CTL2
xʻ01ʼ xʻ00ʼ 01-1 xʻ09ʼ xʻ00ʼ 01-2
xʻ01ʼ 02-1 xʻ01ʼ 02-2
xʻ02ʼ 03-1 xʻ02ʼ 03-2
xʻ03ʼ 04-1 xʻ03ʼ 04-2
xʻ04ʼ 05-1 xʻ04ʼ 05-2
xʻ05ʼ 06-1 xʻ05ʼ 06-2
xʻ06ʼ 07-1 xʻ06ʼ 07-2

• VSP G370
SAS PORT# EXP# ENC SAS PORT# EXP# ENC
xʻ00ʼ xʻ00ʼ CTL1 xʻ08ʼ xʻ00ʼ CTL2
xʻ01ʼ xʻ00ʼ 01-1 xʻ09ʼ xʻ00ʼ 01-2
xʻ01ʼ 02-1 xʻ01ʼ 02-2
xʻ02ʼ 03-1 xʻ02ʼ 03-2
xʻ03ʼ 04-1 xʻ03ʼ 04-2
xʻ04ʼ 05-1 xʻ04ʼ 05-2
xʻ05ʼ 06-1 xʻ05ʼ 06-2
xʻ06ʼ 07-1 xʻ06ʼ 07-2
xʻ07ʼ 08-1 xʻ07ʼ 08-2
xʻ08ʼ 09-1 xʻ08ʼ 09-2
xʻ09ʼ 10-1 xʻ09ʼ 10-2
xʻ0aʼ 11-1 xʻ0aʼ 11-2

TRBL03-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-120

• VSP G700
SAS PORT# EXP# ENC SAS PORT# EXP# ENC
xʻ00ʼ xʻ00ʼ 00-1 xʻ08ʼ xʻ00ʼ 00-2
xʻ01ʼ 02-1 xʻ01ʼ 02-2
xʻ02ʼ 04-1 xʻ02ʼ 04-2
xʻ03ʼ 06-1 xʻ03ʼ 06-2
xʻ04ʼ 08-1 xʻ04ʼ 08-2
xʻ05ʼ 10-1 xʻ05ʼ 10-2
xʻ06ʼ 12-1 xʻ06ʼ 12-2
xʻ07ʼ 14-1 xʻ07ʼ 14-2
xʻ08ʼ 16-1 xʻ08ʼ 16-2
xʻ09ʼ 18-1 xʻ09ʼ 18-2
xʻ0aʼ 20-1 xʻ0aʼ 20-2
xʻ0bʼ 22-1 xʻ0bʼ 22-2
xʻ01ʼ xʻ00ʼ 01-1 xʻ09ʼ xʻ00ʼ 01-2
xʻ01ʼ 03-1 xʻ01ʼ 03-2
xʻ02ʼ 05-1 xʻ02ʼ 05-2
xʻ03ʼ 07-1 xʻ03ʼ 07-2
xʻ04ʼ 09-1 xʻ04ʼ 09-2
xʻ05ʼ 11-1 xʻ05ʼ 11-2
xʻ06ʼ 13-1 xʻ06ʼ 13-2
xʻ07ʼ 15-1 xʻ07ʼ 15-2
xʻ08ʼ 17-1 xʻ08ʼ 17-2
xʻ09ʼ 19-1 xʻ09ʼ 19-2
xʻ0aʼ 21-1 xʻ0aʼ 21-2
xʻ0bʼ 23-1 xʻ0bʼ 23-2
xʻ02ʼ xʻ00ʼ 24-1 xʻ0Aʼ xʻ00ʼ 24-2
xʻ01ʼ 26-1 xʻ01ʼ 26-2
xʻ02ʼ 28-1 xʻ02ʼ 28-2
xʻ03ʼ 30-1 xʻ03ʼ 30-2
xʻ04ʼ 32-1 xʻ04ʼ 32-2
xʻ05ʼ 34-1 xʻ05ʼ 34-2
xʻ06ʼ 36-1 xʻ06ʼ 36-2
xʻ07ʼ 38-1 xʻ07ʼ 38-2
xʻ08ʼ 40-1 xʻ08ʼ 40-2
xʻ09ʼ 42-1 xʻ09ʼ 42-2
xʻ0aʼ 44-1 xʻ0aʼ 44-2
xʻ0bʼ 46-1 xʻ0bʼ 46-2
xʻ03ʼ xʻ00ʼ 25-1 xʻ0Bʼ xʻ00ʼ 25-2
xʻ01ʼ 27-1 xʻ01ʼ 27-2
xʻ02ʼ 29-1 xʻ02ʼ 29-2
xʻ03ʼ 31-1 xʻ03ʼ 31-2
xʻ04ʼ 33-1 xʻ04ʼ 33-2
xʻ05ʼ 35-1 xʻ05ʼ 35-2
xʻ06ʼ 37-1 xʻ06ʼ 37-2
xʻ07ʼ 39-1 xʻ07ʼ 39-2
xʻ08ʼ 41-1 xʻ08ʼ 41-2
xʻ09ʼ 43-1 xʻ09ʼ 43-2
xʻ0aʼ 45-1 xʻ0aʼ 45-2
xʻ0bʼ 47-1 xʻ0bʼ 47-2

TRBL03-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-121

• VSP G900
SAS PORT# EXP# ENC SAS PORT# EXP# ENC
xʻ00ʼ xʻ00ʼ 00-1 xʻ08ʼ xʻ00ʼ 00-2
xʻ01ʼ 04-1 xʻ01ʼ 04-2
xʻ02ʼ 08-1 xʻ02ʼ 08-2
xʻ03ʼ 12-1 xʻ03ʼ 12-2
xʻ04ʼ 16-1 xʻ04ʼ 16-2
xʻ05ʼ 20-1 xʻ05ʼ 20-2
xʻ01ʼ xʻ00ʼ 01-1 xʻ09ʼ xʻ00ʼ 01-2
xʻ01ʼ 05-1 xʻ01ʼ 05-2
xʻ02ʼ 09-1 xʻ02ʼ 09-2
xʻ03ʼ 13-1 xʻ03ʼ 13-2
xʻ04ʼ 17-1 xʻ04ʼ 17-2
xʻ05ʼ 21-1 xʻ05ʼ 21-2
xʻ02ʼ xʻ00ʼ 02-1 xʻ0Aʼ xʻ00ʼ 02-2
xʻ01ʼ 06-1 xʻ01ʼ 06-2
xʻ02ʼ 10-1 xʻ02ʼ 10-2
xʻ03ʼ 14-1 xʻ03ʼ 14-2
xʻ04ʼ 18-1 xʻ04ʼ 18-2
xʻ05ʼ 22-1 xʻ05ʼ 22-2
xʻ03ʼ xʻ00ʼ 03-1 xʻ0Bʼ xʻ00ʼ 03-2
xʻ01ʼ 07-1 xʻ01ʼ 07-2
xʻ02ʼ 11-1 xʻ02ʼ 11-2
xʻ03ʼ 15-1 xʻ03ʼ 15-2
xʻ04ʼ 19-1 xʻ04ʼ 19-2
xʻ05ʼ 23-1 xʻ05ʼ 23-2
xʻ04ʼ xʻ00ʼ 24-1 xʻ0Cʼ xʻ00ʼ 24-2
xʻ01ʼ 28-1 xʻ01ʼ 28-2
xʻ02ʼ 32-1 xʻ02ʼ 32-2
xʻ03ʼ 36-1 xʻ03ʼ 36-2
xʻ04ʼ 40-1 xʻ04ʼ 40-2
xʻ05ʼ 44-1 xʻ05ʼ 44-2
xʻ05ʼ xʻ00ʼ 25-1 xʻ0Dʼ xʻ00ʼ 25-2
xʻ01ʼ 29-1 xʻ01ʼ 29-2
xʻ02ʼ 33-1 xʻ02ʼ 33-2
xʻ03ʼ 37-1 xʻ03ʼ 37-2
xʻ04ʼ 41-1 xʻ04ʼ 41-2
xʻ05ʼ 45-1 xʻ05ʼ 45-2
xʻ06ʼ xʻ00ʼ 26-1 xʻ0Eʼ xʻ00ʼ 26-2
xʻ01ʼ 30-1 xʻ01ʼ 30-2
xʻ02ʼ 34-1 xʻ02ʼ 34-2
xʻ03ʼ 38-1 xʻ03ʼ 38-2
xʻ04ʼ 42-1 xʻ04ʼ 42-2
xʻ05ʼ 46-1 xʻ05ʼ 46-2
xʻ07ʼ xʻ00ʼ 27-1 xʻ0Fʼ xʻ00ʼ 27-2
xʻ01ʼ 31-1 xʻ01ʼ 31-2
xʻ02ʼ 35-1 xʻ02ʼ 35-2
xʻ03ʼ 39-1 xʻ03ʼ 39-2
xʻ04ʼ 43-1 xʻ04ʼ 43-2
xʻ05ʼ 47-1 xʻ05ʼ 47-2

TRBL03-121
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-122

• VSP E590/E790 DB configuration including • VSP E590/E790 DB configuration not including

DBS2 DBS2
SASPort#/NVMe EXP# ENC SASPort#/NVMe EXP# ENC
Port# Port#
xʻ00ʼ xʻ12ʼ xʻ00ʼ CTL1 xʻ00ʼ xʻ12ʼ xʻ00ʼ CTL1
xʻ02ʼ xʻ10ʼ xʻ00ʼ CTL1 xʻ02ʼ xʻ10ʼ xʻ00ʼ CTL1
xʻ08ʼ xʻ1aʼ xʻ00ʼ CTL2 xʻ08ʼ xʻ1aʼ xʻ00ʼ CTL2
xʻ0aʼ xʻ18ʼ xʻ00ʼ CTL2 xʻ0aʼ xʻ18ʼ xʻ00ʼ CTL2
xʻ04ʼ xʻ14ʼ xʻ00ʼ 50-1 xʻ04ʼ xʻ00ʼ 50-1
xʻ05ʼ xʻ15ʼ xʻ00ʼ 52-1 xʻ05ʼ xʻ00ʼ 51-1
xʻ0cʼ xʻ1cʼ xʻ00ʼ 50-2 xʻ0cʼ xʻ00ʼ 50-2
xʻ0dʼ xʻ1dʼ xʻ00ʼ 52-2 xʻ0dʼ xʻ00ʼ 51-2
xʻ04ʼ xʻ01ʼ 54-1 xʻ04ʼ xʻ01ʼ 52-1
xʻ05ʼ xʻ01ʼ 56-1 xʻ05ʼ xʻ01ʼ 53-1
xʻ0cʼ xʻ01ʼ 54-2 xʻ0cʼ xʻ01ʼ 52-2
xʻ0dʼ xʻ01ʼ 56-2 xʻ0dʼ xʻ01ʼ 53-2
xʻ14ʼ xʻ01ʼ 55-1 xʻ04ʼ xʻ02ʼ 54-1
xʻ15ʼ xʻ01ʼ 57-1 xʻ05ʼ xʻ02ʼ 55-1
xʻ1cʼ xʻ01ʼ 55-2 xʻ0cʼ xʻ02ʼ 54-2
xʻ1dʼ xʻ01ʼ 57-2 xʻ0dʼ xʻ02ʼ 55-2
xʻ04ʼ xʻ02ʼ 58-1 xʻ04ʼ xʻ03ʼ 56-1
xʻ05ʼ xʻ02ʼ 60-1 xʻ05ʼ xʻ03ʼ 57-1
xʻ0cʼ xʻ02ʼ 58-2 xʻ0cʼ xʻ03ʼ 56-2
xʻ0dʼ xʻ02ʼ 60-2 xʻ0dʼ xʻ03ʼ 57-2
xʻ14ʼ xʻ02ʼ 59-1 xʻ04ʼ xʻ04ʼ 58-1
xʻ15ʼ xʻ02ʼ 61-1 xʻ05ʼ xʻ04ʼ 59-1
xʻ1cʼ xʻ02ʼ 59-2 xʻ0cʼ xʻ04ʼ 58-2
xʻ1dʼ xʻ02ʼ 61-2 xʻ0dʼ xʻ04ʼ 59-2
xʻ04ʼ xʻ03ʼ 62-1 xʻ04ʼ xʻ05ʼ 60-1
xʻ05ʼ xʻ03ʼ 64-1 xʻ05ʼ xʻ05ʼ 61-1
xʻ0cʼ xʻ03ʼ 62-2 xʻ0cʼ xʻ05ʼ 60-2
xʻ0dʼ xʻ03ʼ 64-2 xʻ0dʼ xʻ05ʼ 61-2
xʻ14ʼ xʻ03ʼ 63-1
xʻ15ʼ xʻ03ʼ 65-1
xʻ1cʼ xʻ03ʼ 63-2
xʻ1dʼ xʻ03ʼ 65-2
xʻ04ʼ xʻ04ʼ 66-1
xʻ05ʼ xʻ04ʼ 68-1
xʻ0cʼ xʻ04ʼ 66-2
xʻ0dʼ xʻ04ʼ 68-2
xʻ14ʼ xʻ04ʼ 67-1
xʻ15ʼ xʻ04ʼ 69-1
xʻ1cʼ xʻ04ʼ 67-2
xʻ1dʼ xʻ04ʼ 69-2
xʻ04ʼ xʻ05ʼ 70-1
xʻ05ʼ xʻ05ʼ 72-1
xʻ0cʼ xʻ05ʼ 70-2
xʻ0dʼ xʻ05ʼ 72-2
xʻ14ʼ xʻ05ʼ 71-1
xʻ15ʼ xʻ05ʼ 73-1
xʻ1cʼ xʻ05ʼ 71-2
xʻ1dʼ xʻ05ʼ 73-2
TRBL03-122
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-123

• VSP E990
SASPort#/NVMe Port# EXP# ENC (DBN)
xʻ00ʼ xʻ12ʼ xʻ00ʼ 0-1
xʻ01ʼ xʻ13ʼ xʻ00ʼ 1-1
xʻ02ʼ xʻ10ʼ xʻ00ʼ 0-1
xʻ03ʼ xʻ11ʼ xʻ00ʼ 1-1
xʻ04ʼ xʻ16ʼ xʻ00ʼ 2-1
xʻ05ʼ xʻ17ʼ xʻ00ʼ 3-1
xʻ06ʼ xʻ14ʼ xʻ00ʼ 2-1
xʻ07ʼ xʻ15ʼ xʻ00ʼ 3-1
xʻ08ʼ xʻ1aʼ xʻ00ʼ 0-2
xʻ09ʼ xʻ1bʼ xʻ00ʼ 1-2
xʻ0aʼ xʻ18ʼ xʻ00ʼ 0-2
xʻ0bʼ xʻ19ʼ xʻ00ʼ 1-2
xʻ0cʼ xʻ1eʼ xʻ00ʼ 2-2
xʻ0dʼ xʻ1fʼ xʻ00ʼ 3-2
xʻ0eʼ xʻ1cʼ xʻ00ʼ 2-2
xʻ0fʼ xʻ1dʼ xʻ00ʼ 3-2

• VSP E1090 (When the first connected Drive Box is DBN)

SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ12ʼ xʻ00ʼ 0-1
xʻ01ʼ xʻ13ʼ xʻ00ʼ 2-1
xʻ02ʼ xʻ10ʼ xʻ00ʼ 0-1
xʻ03ʼ xʻ11ʼ xʻ00ʼ 2-1
xʻ04ʼ xʻ16ʼ xʻ00ʼ 4-1
xʻ05ʼ xʻ17ʼ xʻ00ʼ 6-1
xʻ06ʼ xʻ14ʼ xʻ00ʼ 4-1
xʻ07ʼ xʻ15ʼ xʻ00ʼ 6-1
xʻ08ʼ xʻ1aʼ xʻ00ʼ 0-2
xʻ09ʼ xʻ1bʼ xʻ00ʼ 2-2
xʻ0aʼ xʻ18ʼ xʻ00ʼ 0-2
xʻ0bʼ xʻ19ʼ xʻ00ʼ 2-2
xʻ0cʼ xʻ1eʼ xʻ00ʼ 4-2
xʻ0dʼ xʻ1fʼ xʻ00ʼ 6-2
xʻ0eʼ xʻ1cʼ xʻ00ʼ 4-2
xʻ0fʼ xʻ1dʼ xʻ00ʼ 6-2

• VSP E1090 (When the first connected Drive Box is DBS2)

SASPort#/NVMe Port# EXP# ENC SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ12ʼ xʻ00 0-1 xʻ08ʼ xʻ1aʼ xʻ00 0-2
xʻ01ʼ xʻ13ʼ xʻ00 2-1 xʻ09ʼ xʻ1bʼ xʻ00 2-2
xʻ02ʼ xʻ10ʼ xʻ00 0-1 xʻ0aʼ xʻ18ʼ xʻ00 0-2
xʻ03ʼ xʻ11ʼ xʻ00 2-1 xʻ0bʼ xʻ19ʼ xʻ00 2-2
xʻ04ʼ xʻ16ʼ xʻ00 50-1 xʻ0cʼ xʻ1eʼ xʻ00 50-2
xʻ05ʼ xʻ17ʼ xʻ00 52-1 xʻ0dʼ xʻ1fʼ xʻ00 52-2
xʻ06ʼ xʻ14ʼ xʻ00 50-1 xʻ0eʼ xʻ1cʼ xʻ00 50-2
xʻ07ʼ xʻ15ʼ xʻ00 52-1 xʻ0fʼ xʻ1dʼ xʻ00 52-2
(To be continued)

TRBL03-123
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-124

(Continued from the preceding page)

SASPort#/NVMe Port# EXP# ENC SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ01ʼ 4-1 xʻ12ʼ xʻ02ʼ 8-1
xʻ01ʼ xʻ01ʼ 6-1 xʻ13ʼ xʻ02ʼ 10-1
xʻ02ʼ xʻ01ʼ 5-1 xʻ10ʼ xʻ02ʼ 9-1
xʻ03ʼ xʻ01ʼ 7-1 xʻ11ʼ xʻ02ʼ 11-1
xʻ04ʼ xʻ01ʼ 54-1 xʻ16ʼ xʻ02ʼ 58-1
xʻ05ʼ xʻ01ʼ 56-1 xʻ17ʼ xʻ02ʼ 60-1
xʻ06ʼ xʻ01ʼ 55-1 xʻ14ʼ xʻ02ʼ 59-1
xʻ07ʼ xʻ01ʼ 57-1 xʻ15ʼ xʻ02ʼ 61-1
xʻ08ʼ xʻ01ʼ 4-2 xʻ1aʼ xʻ02ʼ 8-2
xʻ09ʼ xʻ01ʼ 6-2 xʻ1bʼ xʻ02ʼ 10-2
xʻ0aʼ xʻ01ʼ 5-2 xʻ18ʼ xʻ02ʼ 9-2
xʻ0bʼ xʻ01ʼ 7-2 xʻ19ʼ xʻ02ʼ 11-2
xʻ0cʼ xʻ01ʼ 54-2 xʻ1eʼ xʻ02ʼ 58-2
xʻ0dʼ xʻ01ʼ 56-2 xʻ1fʼ xʻ02ʼ 60-2
xʻ0eʼ xʻ01ʼ 55-2 xʻ1cʼ xʻ02ʼ 59-2
xʻ0fʼ xʻ01ʼ 57-2 xʻ1dʼ xʻ02ʼ 61-2
xʻ12ʼ xʻ01ʼ 4-1 xʻ00ʼ xʻ03ʼ 12-1
xʻ13ʼ xʻ01ʼ 6-1 xʻ01ʼ xʻ03ʼ 14-1
xʻ10ʼ xʻ01ʼ 5-1 xʻ02ʼ xʻ03ʼ 13-1
xʻ11ʼ xʻ01ʼ 7-1 xʻ03ʼ xʻ03ʼ 15-1
xʻ16ʼ xʻ01ʼ 54-1 xʻ04ʼ xʻ03ʼ 62-1
xʻ17ʼ xʻ01ʼ 56-1 xʻ05ʼ xʻ03ʼ 64-1
xʻ14ʼ xʻ01ʼ 55-1 xʻ06ʼ xʻ03ʼ 63-1
xʻ15ʼ xʻ01ʼ 57-1 xʻ07ʼ xʻ03ʼ 65-1
xʻ1aʼ xʻ01ʼ 4-2 xʻ08ʼ xʻ03ʼ 12-2
xʻ1bʼ xʻ01ʼ 6-2 xʻ09ʼ xʻ03ʼ 14-2
xʻ18ʼ xʻ01ʼ 5-2 xʻ0aʼ xʻ03ʼ 13-2
xʻ19ʼ xʻ01ʼ 7-2 xʻ0bʼ xʻ03ʼ 15-2
xʻ1eʼ xʻ01ʼ 54-2 xʻ0cʼ xʻ03ʼ 62-2
xʻ1fʼ xʻ01ʼ 56-2 xʻ0dʼ xʻ03ʼ 64-2
xʻ1cʼ xʻ01ʼ 55-2 xʻ0eʼ xʻ03ʼ 63-2
xʻ1dʼ xʻ01ʼ 57-2 xʻ0fʼ xʻ03ʼ 65-2
xʻ00ʼ xʻ02ʼ 8-1 xʻ12ʼ xʻ03ʼ 12-1
xʻ01ʼ xʻ02ʼ 10-1 xʻ13ʼ xʻ03ʼ 14-1
xʻ02ʼ xʻ02ʼ 9-1 xʻ10ʼ xʻ03ʼ 13-1
xʻ03ʼ xʻ02ʼ 11-1 xʻ11ʼ xʻ03ʼ 15-1
xʻ04ʼ xʻ02ʼ 58-1 xʻ16ʼ xʻ03ʼ 62-1
xʻ05ʼ xʻ02ʼ 60-1 xʻ17ʼ xʻ03ʼ 64-1
xʻ06ʼ xʻ02ʼ 59-1 xʻ14ʼ xʻ03ʼ 63-1
xʻ07ʼ xʻ02ʼ 61-1 xʻ15ʼ xʻ03ʼ 65-1
xʻ08ʼ xʻ02ʼ 8-2 xʻ1aʼ xʻ03ʼ 12-2
xʻ09ʼ xʻ02ʼ 10-2 xʻ1bʼ xʻ03ʼ 14-2
xʻ0aʼ xʻ02ʼ 9-2 xʻ18ʼ xʻ03ʼ 13-2
xʻ0bʼ xʻ02ʼ 11-2 xʻ19ʼ xʻ03ʼ 15-2
xʻ0cʼ xʻ02ʼ 58-2 xʻ1eʼ xʻ03ʼ 62-2
xʻ0dʼ xʻ02ʼ 60-2 xʻ1fʼ xʻ03ʼ 64-2
xʻ0eʼ xʻ02ʼ 59-2 xʻ1cʼ xʻ03ʼ 63-2
xʻ0fʼ xʻ02ʼ 61-2 xʻ1dʼ xʻ03ʼ 65-2
(To be continued)

TRBL03-124
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-125

(Continued from the preceding page)

SASPort#/NVMe Port# EXP# ENC SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ04ʼ 16-1 xʻ12ʼ xʻ05ʼ 20-1
xʻ01ʼ xʻ04ʼ 18-1 xʻ13ʼ xʻ05ʼ 22-1
xʻ02ʼ xʻ04ʼ 17-1 xʻ10ʼ xʻ05ʼ 21-1
xʻ03ʼ xʻ04ʼ 19-1 xʻ11ʼ xʻ05ʼ 23-1
xʻ04ʼ xʻ04ʼ 66-1 xʻ16ʼ xʻ05ʼ 70-1
xʻ05ʼ xʻ04ʼ 68-1 xʻ17ʼ xʻ05ʼ 72-1
xʻ06ʼ xʻ04ʼ 67-1 xʻ14ʼ xʻ05ʼ 71-1
xʻ07ʼ xʻ04ʼ 69-1 xʻ15ʼ xʻ05ʼ 73-1
xʻ08ʼ xʻ04ʼ 16-2 xʻ1aʼ xʻ05ʼ 20-2
xʻ09ʼ xʻ04ʼ 18-2 xʻ1bʼ xʻ05ʼ 22-2
xʻ0aʼ xʻ04ʼ 17-2 xʻ18ʼ xʻ05ʼ 21-2
xʻ0bʼ xʻ04ʼ 19-2 xʻ19ʼ xʻ05ʼ 23-2
xʻ0cʼ xʻ04ʼ 66-2 xʻ1eʼ xʻ05ʼ 70-2
xʻ0dʼ xʻ04ʼ 68-2 xʻ1fʼ xʻ05ʼ 72-2
xʻ0eʼ xʻ04ʼ 67-2 xʻ1cʼ xʻ05ʼ 71-2
xʻ0fʼ xʻ04ʼ 69-2 xʻ1dʼ xʻ05ʼ 73-2
xʻ12ʼ xʻ04ʼ 16-1 xʻ00ʼ xʻ06ʼ 24-1
xʻ13ʼ xʻ04ʼ 18-1 xʻ01ʼ xʻ06ʼ 26-1
xʻ10ʼ xʻ04ʼ 17-1 xʻ02ʼ xʻ06ʼ 25-1
xʻ11ʼ xʻ04ʼ 19-1 xʻ03ʼ xʻ06ʼ 27-1
xʻ16ʼ xʻ04ʼ 66-1 xʻ04ʼ xʻ06ʼ 74-1
xʻ17ʼ xʻ04ʼ 68-1 xʻ05ʼ xʻ06ʼ 76-1
xʻ14ʼ xʻ04ʼ 67-1 xʻ06ʼ xʻ06ʼ 75-1
xʻ15ʼ xʻ04ʼ 69-1 xʻ07ʼ xʻ06ʼ 77-1
xʻ1aʼ xʻ04ʼ 16-2 xʻ08ʼ xʻ06ʼ 24-2
xʻ1bʼ xʻ04ʼ 18-2 xʻ09ʼ xʻ06ʼ 26-2
xʻ18ʼ xʻ04ʼ 17-2 xʻ0aʼ xʻ06ʼ 25-2
xʻ19ʼ xʻ04ʼ 19-2 xʻ0bʼ xʻ06ʼ 27-2
xʻ1eʼ xʻ04ʼ 66-2 xʻ0cʼ xʻ06ʼ 74-2
xʻ1fʼ xʻ04ʼ 68-2 xʻ0dʼ xʻ06ʼ 76-2
xʻ1cʼ xʻ04ʼ 67-2 xʻ0eʼ xʻ06ʼ 75-2
xʻ1dʼ xʻ04ʼ 69-2 xʻ0fʼ xʻ06ʼ 77-2
xʻ00ʼ xʻ05ʼ 20-1 xʻ12ʼ xʻ06ʼ 24-1
xʻ01ʼ xʻ05ʼ 22-1 xʻ13ʼ xʻ06ʼ 26-1
xʻ02ʼ xʻ05ʼ 21-1 xʻ10ʼ xʻ06ʼ 25-1
xʻ03ʼ xʻ05ʼ 23-1 xʻ11ʼ xʻ06ʼ 27-1
xʻ04ʼ xʻ05ʼ 70-1 xʻ16ʼ xʻ06ʼ 74-1
xʻ05ʼ xʻ05ʼ 72-1 xʻ17ʼ xʻ06ʼ 76-1
xʻ06ʼ xʻ05ʼ 71-1 xʻ14ʼ xʻ06ʼ 75-1
xʻ07ʼ xʻ05ʼ 73-1 xʻ15ʼ xʻ06ʼ 77-1
xʻ08ʼ xʻ05ʼ 20-2 xʻ1aʼ xʻ06ʼ 24-2
xʻ09ʼ xʻ05ʼ 22-2 xʻ1bʼ xʻ06ʼ 26-2
xʻ0aʼ xʻ05ʼ 21-2 xʻ18ʼ xʻ06ʼ 25-2
xʻ0bʼ xʻ05ʼ 23-2 xʻ19ʼ xʻ06ʼ 27-2
xʻ0cʼ xʻ05ʼ 70-2 xʻ1eʼ xʻ06ʼ 74-2
xʻ0dʼ xʻ05ʼ 72-2 xʻ1fʼ xʻ06ʼ 76-2
xʻ0eʼ xʻ05ʼ 71-2 xʻ1cʼ xʻ06ʼ 75-2
xʻ0fʼ xʻ05ʼ 73-2 xʻ1dʼ xʻ06ʼ 77-2
(To be continued)

TRBL03-125
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-126

(Continued from the preceding page)

SASPort#/NVMe Port# EXP# ENC SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ07ʼ 28-1 xʻ12ʼ xʻ07ʼ 28-1
xʻ01ʼ xʻ07ʼ 30-1 xʻ13ʼ xʻ07ʼ 30-1
xʻ02ʼ xʻ07ʼ 29-1 xʻ10ʼ xʻ07ʼ 29-1
xʻ03ʼ xʻ07ʼ 31-1 xʻ11ʼ xʻ07ʼ 31-1
xʻ04ʼ xʻ07ʼ 78-1 xʻ16ʼ xʻ07ʼ 78-1
xʻ05ʼ xʻ07ʼ 80-1 xʻ17ʼ xʻ07ʼ 80-1
xʻ06ʼ xʻ07ʼ 79-1 xʻ14ʼ xʻ07ʼ 79-1
xʻ07ʼ xʻ07ʼ 81-1 xʻ15ʼ xʻ07ʼ 81-1
xʻ08ʼ xʻ07ʼ 28-2 xʻ1aʼ xʻ07ʼ 28-2
xʻ09ʼ xʻ07ʼ 30-2 xʻ1bʼ xʻ07ʼ 30-2
xʻ0aʼ xʻ07ʼ 29-2 xʻ18ʼ xʻ07ʼ 29-2
xʻ0bʼ xʻ07ʼ 31-2 xʻ19ʼ xʻ07ʼ 31-2
xʻ0cʼ xʻ07ʼ 78-2 xʻ1eʼ xʻ07ʼ 78-2
xʻ0dʼ xʻ07ʼ 80-2 xʻ1fʼ xʻ07ʼ 80-2
xʻ0eʼ xʻ07ʼ 79-2 xʻ1cʼ xʻ07ʼ 79-2
xʻ0fʼ xʻ07ʼ 81-2 xʻ1dʼ xʻ07ʼ 81-2

• VSP E1090 (When the first connected Drive Box is other than DBS2)
SASPort#/NVMe Port# EXP# ENC SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ00ʼ 0-1 xʻ08ʼ xʻ01ʼ 4-2
xʻ01ʼ xʻ00ʼ 2-1 xʻ09ʼ xʻ01ʼ 6-2
xʻ02ʼ xʻ00ʼ 1-1 xʻ0aʼ xʻ01ʼ 5-2
xʻ03ʼ xʻ00ʼ 3-1 xʻ0bʼ xʻ01ʼ 7-2
xʻ04ʼ xʻ00ʼ 50-1 xʻ0cʼ xʻ01ʼ 54-2
xʻ05ʼ xʻ00ʼ 52-1 xʻ0dʼ xʻ01ʼ 56-2
xʻ06ʼ xʻ00ʼ 51-1 xʻ0eʼ xʻ01ʼ 55-2
xʻ07ʼ xʻ00ʼ 53-1 xʻ0fʼ xʻ01ʼ 57-2
xʻ08ʼ xʻ00ʼ 0-2 xʻ00ʼ xʻ02ʼ 8-1
xʻ09ʼ xʻ00ʼ 2-2 xʻ01ʼ xʻ02ʼ 10-1
xʻ0aʼ xʻ00ʼ 1-2 xʻ02ʼ xʻ02ʼ 9-1
xʻ0bʼ xʻ00ʼ 3-2 xʻ03ʼ xʻ02ʼ 11-1
xʻ0cʼ xʻ00ʼ 50-2 xʻ04ʼ xʻ02ʼ 58-1
xʻ0dʼ xʻ00ʼ 52-2 xʻ05ʼ xʻ02ʼ 60-1
xʻ0eʼ xʻ00ʼ 51-2 xʻ06ʼ xʻ02ʼ 59-1
xʻ0fʼ xʻ00ʼ 53-2 xʻ07ʼ xʻ02ʼ 61-1
xʻ00ʼ xʻ01ʼ 4-1 xʻ08ʼ xʻ02ʼ 8-2
xʻ01ʼ xʻ01ʼ 6-1 xʻ09ʼ xʻ02ʼ 10-2
xʻ02ʼ xʻ01ʼ 5-1 xʻ0aʼ xʻ02ʼ 9-2
xʻ03ʼ xʻ01ʼ 7-1 xʻ0bʼ xʻ02ʼ 11-2
xʻ04ʼ xʻ01ʼ 54-1 xʻ0cʼ xʻ02ʼ 58-2
xʻ05ʼ xʻ01ʼ 56-1 xʻ0dʼ xʻ02ʼ 60-2
xʻ06ʼ xʻ01ʼ 55-1 xʻ0eʼ xʻ02ʼ 59-2
xʻ07ʼ xʻ01ʼ 57-1 xʻ0fʼ xʻ02ʼ 61-2
(To be continued)

TRBL03-126
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-127

(Continued from the preceding page)

SASPort#/NVMe Port# EXP# ENC SASPort#/NVMe Port# EXP# ENC
xʻ00ʼ xʻ03ʼ 12-1 xʻ08ʼ xʻ05ʼ 20-2
xʻ01ʼ xʻ03ʼ 14-1 xʻ09ʼ xʻ05ʼ 22-2
xʻ02ʼ xʻ03ʼ 13-1 xʻ0aʼ xʻ05ʼ 21-2
xʻ03ʼ xʻ03ʼ 15-1 xʻ0bʼ xʻ05ʼ 23-2
xʻ04ʼ xʻ03ʼ 62-1 xʻ0cʼ xʻ05ʼ 70-2
xʻ05ʼ xʻ03ʼ 64-1 xʻ0dʼ xʻ05ʼ 72-2
xʻ06ʼ xʻ03ʼ 63-1 xʻ0eʼ xʻ05ʼ 71-2
xʻ07ʼ xʻ03ʼ 65-1 xʻ0fʼ xʻ05ʼ 73-2
xʻ08ʼ xʻ03ʼ 12-2 xʻ00ʼ xʻ06ʼ 24-1
xʻ09ʼ xʻ03ʼ 14-2 xʻ01ʼ xʻ06ʼ 26-1
xʻ0aʼ xʻ03ʼ 13-2 xʻ02ʼ xʻ06ʼ 25-1
xʻ0bʼ xʻ03ʼ 15-2 xʻ03ʼ xʻ06ʼ 27-1
xʻ0cʼ xʻ03ʼ 62-2 xʻ04ʼ xʻ06ʼ 74-1
xʻ0dʼ xʻ03ʼ 64-2 xʻ05ʼ xʻ06ʼ 76-1
xʻ0eʼ xʻ03ʼ 63-2 xʻ06ʼ xʻ06ʼ 75-1
xʻ0fʼ xʻ03ʼ 65-2 xʻ07ʼ xʻ06ʼ 77-1
xʻ00ʼ xʻ04ʼ 16-1 xʻ08ʼ xʻ06ʼ 24-2
xʻ01ʼ xʻ04ʼ 18-1 xʻ09ʼ xʻ06ʼ 26-2
xʻ02ʼ xʻ04ʼ 17-1 xʻ0aʼ xʻ06ʼ 25-2
xʻ03ʼ xʻ04ʼ 19-1 xʻ0bʼ xʻ06ʼ 27-2
xʻ04ʼ xʻ04ʼ 66-1 xʻ0cʼ xʻ06ʼ 74-2
xʻ05ʼ xʻ04ʼ 68-1 xʻ0dʼ xʻ06ʼ 76-2
xʻ06ʼ xʻ04ʼ 67-1 xʻ0eʼ xʻ06ʼ 75-2
xʻ07ʼ xʻ04ʼ 69-1 xʻ0fʼ xʻ06ʼ 77-2
xʻ08ʼ xʻ04ʼ 16-2 xʻ00ʼ xʻ07ʼ 28-1
xʻ09ʼ xʻ04ʼ 18-2 xʻ01ʼ xʻ07ʼ 30-1
xʻ0aʼ xʻ04ʼ 17-2 xʻ02ʼ xʻ07ʼ 29-1
xʻ0bʼ xʻ04ʼ 19-2 xʻ03ʼ xʻ07ʼ 31-1
xʻ0cʼ xʻ04ʼ 66-2 xʻ04ʼ xʻ07ʼ 78-1
xʻ0dʼ xʻ04ʼ 68-2 xʻ05ʼ xʻ07ʼ 80-1
xʻ0eʼ xʻ04ʼ 67-2 xʻ06ʼ xʻ07ʼ 79-1
xʻ0fʼ xʻ04ʼ 69-2 xʻ07ʼ xʻ07ʼ 81-1
xʻ00ʼ xʻ05ʼ 20-1 xʻ08ʼ xʻ07ʼ 28-2
xʻ01ʼ xʻ05ʼ 22-1 xʻ09ʼ xʻ07ʼ 30-2
xʻ02ʼ xʻ05ʼ 21-1 xʻ0aʼ xʻ07ʼ 29-2
xʻ03ʼ xʻ05ʼ 23-1 xʻ0bʼ xʻ07ʼ 31-2
xʻ04ʼ xʻ05ʼ 70-1 xʻ0cʼ xʻ07ʼ 78-2
xʻ05ʼ xʻ05ʼ 72-1 xʻ0dʼ xʻ07ʼ 80-2
xʻ06ʼ xʻ05ʼ 71-1 xʻ0eʼ xʻ07ʼ 79-2
xʻ07ʼ xʻ05ʼ 73-1 xʻ0fʼ xʻ07ʼ 81-2

*4: When replacing SAS cables , perform the dummy replacement of the ENCs to which the cables are
connected. (see REP02-16-10)

TRBL03-127
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-130

3.4 Action When Time Synchronization Failed (SIM = 7ffa00)

START

Synchronization time failure

Ask the customer to verity that the

communication on the port number 123
of the NTP server is allowed.
If it is allowed, ask the customer to
check for errors in the communication
path with the NTP server. If it is not
allowed, ask the customer to change the
settings to allow it.

END

TRBL03-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-140

3.5 Recovery Procedure for LDEV Blockade due to Firmware Error (SIM = 3a0xyy)

START

T.S.D. call.

Execute the operation directed by T.S.D.

Are there any blocked No

MP or CTL?

Yes
Execute the dummy replacement of CTL.
(Refer to REP02-04-10)

Is there any
LDEV whose status is No
displayed as “Blocked” in the
“Status” column?

Yes
Restore LDEVs.
(Refer to MPC04-640) (*1)(*2)

END

*1: Delete [TrueCopy / Universal Replicator / ShadowImage / Volume Migration / Thin Image / Thin
Image Advanced / global-active device] pairs that use the LDEV before restoring the LDEV. After
the recovery flow completes, create pairs again.
*2: When recovering the LDEV used in a GAD pair, recover the LDEV in accordance with the
procedure described in TRBL18-80.

TRBL03-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-150

3.6 Recovery Procedure for the Failure on the Occurrence of Unmatched Memory
Installation Capacity (SIM = ffe800)
SIM-RC = ffe80x should be recovered following the procedure below.
This SIM indicates that “Installation type and set type of CMGs” or “Installed number and set number of
CMGs” are unmatched, so that they need to be matched. Click the [CTL] tab in the “Controller Chassis”
window of “Maintenance Utility” window before starting the work and take notes on CMG types and
installation positions.

START

Was SIM RC = ffe800 issued No

during New Install procedure?
T.S.D. Call

Yes
END
Are
the type and number
No
of CMGs displayed in the “Controller
Chassis” window
correct? Confirm the type and number.
(INST03-01-20)
Yes
Turn off the DKC power forcibly.
Re-define the Cache Memory.
(INST03-07-10)
Correct the CMG type and installation
position noted before starting the work for
END
the actual ones.

Execute PS ON

No
Was SIM-RC = ffe800 issued?

Yes
T.S.D. Call

END

TRBL03-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-160

3.7 Recovery procedure of SIM occurrence during battery charge (SIM = fe0000)
If this SIM is reported, the battery charge level is below 30% and the system is waiting for start up.
It takes a maximum of 90 minutes until the battery charge level becomes 30% or more.

For details, THEORY OF OPERATION SECTION “4.6.4 Hardware Component” - “5. Battery”.

START

Wait for the charge to be complete as

the battery charge was consumed due to
power outage or the like.
(See (*1) for the procedure of battery
charge)

Did the system

become ready No within 90 No
minutes from when the SIM
was reported?

Yes T.S.D. call

END

*1: Turn on the breakers on the PDPs and the PDUs, which makes the POWER LED lit, and then
charge the batteries until the STATUS LED (See LOCATION SECTION “3.2 Other Switches
and LEDs” - “1. Controller Board”) goes from blinking (charge in progress) to solid (charge
completed).

TRBL03-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-170

3.8 Action when Cache Write Through by battery factor is detected (SIM = fe0100, fe0200)
If SIM = fe02xx is reported, the battery charge level is below 50% and the system operates in cache write
through mode. It takes a maximum of 60 minutes until the battery charge level becomes 50% or more. SIM =
fe0100 is reported when the battery charge level becomes 50% or more.

For details, THEORY OF OPERATION SECTION “4.6.4 Hardware Component” - ”5. Battery”.

START

Was SIM
= fe0100 reported within 60 No
minutes from when SIM = fe0200
was reported?

Yes

END T.S.D. call

TRBL03-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-180

3.9 Isolation and Recovery Procedure for Common SAS/NVMe Failure (SIM = db0xxx,
db1xxx, db2xxx, db3xxx, db4xxx, db5xxx, db6xxx, db7xxx, df6xxx, df7xxx, df8xxx,
df9xxx)
When a port error SIM for a drive (PDEV) is reported, this section provides the procedures for judging
whether the error is caused by the pertinent drive error, SAS I/F error, or NVMe I/F error, and how to recover
the error.

As a HDD port error SIM managed in each PDEV, a Port temporary error (REF code = db0xxx, db1xxx,
db2xxx, db3xxx, df6xxx, df7xxx) is reported when a warning is issued, and Port blocking (REF code =
db4xxx, db5xxx, db6xxx, db7xxx, df8xxx, df9xxx) is reported when the equipment is blocked.
(See THEORY OF OPERATION SECTION “4. Appendixes”.)

Possible causes for the malfunction are:

(1) Failure of drive specified in FPC
(2) For SAS connection: Defects in SAS Chip on DKB
For NVMe connection: Defects in PSW on DKB
(3) For SAS connection: Defects in SAS I/F (SAS cable, ENC)
For NVMe connection: Defects in NVMe I/F (NVMe cable, ENC)
(4) Other drive failure
(5) DB platter failure
(6) Removal of Drive whose ALM LED (red) does not light up
(7) Failure of I/F built in CTL

Before performing the maintenance and replacement only for the failed drive, follow these isolation and
recovery procedures to check that a common SAS port error occurs on other PDEVs on the same SAS I/F,
NVMe I/F. If a common error exists, perform the appropriate recovery for the common error parts.

TRBL03-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-190

Common SAS/NVMe Error Isolation Procedure

START

Does Yes
uncompleted SIM = 6620xx
exist?
Collect Dump and Log.
No (See MPC05-50)
2

Check DB# and RDEV# from SIM Log.

(See THEORY04-01-10) T.S.D. call

Has an LDEV blockade Yes

occurred? (*3)
Check
No drives in the parity
group to which the blocked LDEV Yes
belongs. Is there the same drive as the drive
location shown in the SIM
Log? (*4)

No
Is the Drive in the No
physical removal status?

Recover the LDEV blockade

1 (See TRBL03-300) (*2)
Insert the Drive and wait for four
Yes (TRBL03-200)
minutes.
Does the
same failure exist in the Yes
Yes Is the Drive already
other Drive in the Storage
recovered?
System?
No
No 2
Does the Yes
LED (red) on the Drive light
END
up?
No
Recovery by Drive replacement Recovery by Drive replacement
(See REP02-03-10) (*1) (See REP02-03-10) (*2)

Is the No
Drive replacement completed
normally?
Yes T.S.D. call
Does the
same failure exist in the Yes
other Drive in the Storage
System?
No 2

END

TRBL03-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-191

*1: Open Maintenance Utility and block the Drive. Check that the ALM LED (red) lights up and
replace it. For Drive replacement, perform the dummy replacement again and if it fails, replace the
Drive with a new Drive.
*2: Perform the dummy replacement again.
When the dummy replacement fails, replace the Drive with a new Drive.
*3: See “Provisioning Guide”.
*4: See “Provisioning Guide”. For the relation between drive locations and CDEV#/RDEV#, see
THEORY OF OPERATION SECTION “4.1 DB Number - C/R Number Matrix”.

TRBL03-191
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-200

Does a
failure on the same path No: Defective Drive
exist in another drive in the same
Drive Box (2U)? (*1)
(*2)
3
Yes: SAS I/F, NVMe I/F common failure
(TRBL03-201)
Is the Drive 5
Yes
installed in the Controller
Chassis?
Replace the Controller Board connected to
No the Drive port. (See REP02-04-10)
Replace the ENC connected to the Drive
port. (See REP02-16-10)
Recurrence of the No
malfunction?
Recurrence of the No
malfunction? Yes

Yes
Replace the DKB connected to the SAS
Recurrence of the No
cables/NVMe cables on the Drive port
side. (See REP02-14-10) malfunction?

Yes END

Recurrence of the No
malfunction? Are CTLs displayed in Yes
5
ACCs of the SIM?
Yes
END
Replace the SAS cables/NVMe cables No
in accordance with the procedure for
dummy replacement of the ENC on the
Drive port side. (See REP02-16-10) Recovery by Drive replacement
(See REP02-03-10)

Recurrence of the No
malfunction?

Yes
END

T.S.D. call

*1: The relation between SIMs and paths is shown below.

Path 0: db0xxx, db1xxx, db4xxx, db5xxx, df6xxx, and df8xxx
Path 1: db2xxx, db3xxx, db6xxx, db7xxx, df7xxx, and df9xxx
Check whether a SIM indicating the same Drive Box and path as those of the target SIM is output.
How to identify DB# by xxx is shown in THEORY OF OPERATION SECTION 4. Appendixes .
*2: For DBS2 (2U), two consecutive DB#, which are displayed as such as DB-050 051 on
Maintenance Utility, are assigned to one Drive Box. Assume that such two consecutive DB# are in
the same Drive Box (2U) when performing this recovery procedure.

TRBL03-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-201

Recovery by Drive replacement

(See REP02-03-10)

Recurrence of the No
malfunction?
Yes END

When SSB
= A40X or ABA0 is
logged and then the drives of CDEV#
and RDEV# are identified from the SSB detailed No
information, are they maintenance target drives?
(See SSBLOG05-3940, 3960)

Yes
Recovery by Drive replacement
(See REP02-03-10)

Recurrence of the No
malfunction?
Yes END

Is the Drive installed in the Yes

Controller Chassis?
Replace the Controller Board connected to
No the drive port. (See REP02-04-10)
When both Drive ports of the Drive are
Replace the ENC connected to the Drive
blocked, replace both Controller Boards one
port. (See REP02-16-10)
by one.
When both Drive ports of the Drive are
blocked, replace both ENCs in the Drive
Box one by one. If there is an unrecovered drive, recover it by
drive replacement. (See REP02-03-10)
* Perform dummy replacement of the drive.
If there is an unrecovered drive, recover it by
drive replacement. (See REP02-03-10)
* Perform dummy replacement of the drive. Yes
Recurrence of the
malfunction?

Recurrence of the No No
malfunction? T.S.D. call

Yes
END

4
(TRBL03-202)

TRBL03-201
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-202

Replace the DKB connected to the SAS

cables/NVMe cables on the Drive port side.
(See REP02-14-10)

Recurrence of the No
malfunction?
Yes
Replace the SAS cables/NVMe cables in
accordance with the procedure for dummy
replacement of the ENC on the Drive port
side. (See REP02-16-10)

Recurrence of the No
malfunction?
Yes

Are CTLs displayed in No

ACCs of the SIM?

Yes T.S.D. call

Replace the Controller Boards connected to
the Drive port. (See REP02-04-10)

Recurrence of the No
malfunction?
Yes Perform dummy replacement of the drive.

T.S.D. call
END

TRBL03-202
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-203

*1: SSB detailed information

The case of Byte36: bit0-3 = D & Byte26: bit4-7 = 0 & Byte27: bit0-2 = 0
SSB detailed information
+0x0 +0x4 +0x8 +0xC
00000000: 7404190b 00279f00 b1a40000 00aa2000
00000010: 00000000 00002e0d 00000000 00000004
00000020: 00000000 00000000 a4b1d84f 7492XX00
00000030: 00000000 0000d0YY 00000000 00000000
00000040: d84f7492 80eeeeee eeeeeeee eeeeeeee
00000050: 21120083 00000000 100000ee 00010000
00000060: 800f0021 ffffffff 01210503 00000000
00000070: 02010046 00000000 10000000 00100302

XX: CDEV
YY: RDEV

The case of Byte36: bit0-3 = E & Byte26: bit4-7 = 0

SSB detailed information
+0x0 +0x4 +0x8 +0xC
00000000: 7404190b 00279f00 b1a40000 00aa2000
00000010: 00000000 00002e0d 00000000 00000004
00000020: 00000000 00000000 a4b1d84f 7492XX00
00000030: 00000000 0000e0YY 00000000 00000000
00000040: d84f7492 80eeeeee eeeeeeee eeeeeeee
00000050: 21120083 00000000 100000ee 00010000
00000060: 800f0021 ffffffff 01210503 00000000
00000070: 02010046 00000000 10000000 00100302

XX: CDEV
YY: RDEV

For the relation between CDEV#/RDEV#, DB# and HDD location#, see THEORY OF
OPERATION SECTION “4.1 DB Number - C/R Number Matrix”.

TRBL03-203
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-210

3.10 Recovery Procedure for LAN Error (SIM = 7d01xx,7d02xx)

3.10.1 Recovery Procedure When an Internal LAN Failure Occurs (SIM = 7d01xx) (2U
Controller Chassis)

The storage system that detected this SIM may fell into serious error state due to DKC processor
abnormality. Therefore, restore the storage system according to the following flow immediately.
(*1)

START (*1)

Does
ALARM LED of Yes Perform recovery procedure for
DKCPANEL light up? other failure. (See TRBL02-120)

No
Check whether the IP address, subnet mask, and default gateway are properly set for
communication between the Maintenance PC/SVP and CTL in the following network
settings (When SVP is used for communication, ask the customer.):
• Maintenance PC Network Settings (see MPC02-60)
• Storage Device List Network Settings (see MPC02-130)
• Maintenance Utility Network Settings (see MPC03-510)

Are the network settings No

correct?
Correct the network settings.
Yes
Execute LAN Check
(See DIAG04-210)
Perform steps 1 through 4 in
MAINTENANCE PC SECTION
“3.26 Resetting GUM”.
No
Normally ended?
Execute LAN Check
(See DIAG04-210)
Yes

No Replace the CTL in which an

Normally ended? 1
abnormality was detected by LAN
Check. (See REP02-04-10) (TRBL03-211)
Yes
Execute LAN Check
(See DIAG04-210)
1
(TRBL03-211)
No
Normally ended?

Collect dumps (See MPC05-50)

Yes

1 (TRBL03-211) T.S.D Call

*1: This SIM might not be generated at LAN error.

TRBL03-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-211

Collect dumps
(See MPC05-50)

Is the window
shown in MPC05-141
(3) (b) that is indicating the Yes
MPs for which dump collection is
not done displayed during
dump collection?
T.S.D Call

No

END

TRBL03-211
Hitachi Proprietary DW850/DW900/DW1000
Rev.8 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-220

3.10.2 Recovery Procedure When an Internal LAN Failure Occurs (SIM = 7d01xx) (4U
Controller Chassis)

The storage system that detected this SIM may fell into serious error state due to DKC processor
abnormality. Therefore, restore the storage system according to the following flow immediately.
(*1)

START (*1)

Does
ALARM LED of Yes Perform recovery procedure for
DKCPANEL light up? other failure. (See TRBL02-120)

No
Check whether the IP address, subnet mask, and default gateway are properly set for
communication between the Maintenance PC/SVP and CTL in the following network
settings (When SVP is used for communication, ask the customer.):
• Maintenance PC Network Settings (see MPC02-60)
• Storage Device List Network Settings (see MPC02-130)
• Maintenance Utility Network Settings (see MPC03-510)

Are the network settings No

correct?
Correct the network settings.
Yes
Execute LAN Check
(See DIAG04-210)
Perform steps 1 through 4 in
MAINTENANCE PC SECTION
“3.26 Resetting GUM”.
No
Normally ended?
Execute LAN Check
(See DIAG04-210) Yes

2
Yes
Normally ended? (TRBL03-221)

No
2
Check the SSB
(See MPC05-250) (TRBL03-221)

1
(TRBL03-221)

*1: This SIM might not be generated at LAN error.

TRBL03-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-221

Yes
SSB = 33cc?

Replace the LANB (*1)

No
(See REP02-11-10)
Execute LAN Check
(See DIAG04-210)
Execute LAN Check
(See DIAG04-210)

Yes
Normally ended?

Are only particular Yes No

MPs abnormal?

No
Replace the LANB (*1) Replace the CTL (*1)
(See REP02-11-10) (See REP02-04-10)

Execute LAN Check

(See DIAG04-210)

No
Normally ended?

Collect dumps (See MPC05-50)

Yes

2 T.S.D Call

Collect dumps
(See MPC05-50)

Is the window
shown in MPC05-141
(3) (b) that is indicating the Yes
MPs for which dump collection is
not done displayed during
dump collection?
T.S.D Call

No

END

*1: For 7d0100, perform replacement on the CTL1 side.

For 7d0101, perform replacement on the CTL2 side.

TRBL03-221
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-230

3.10.3 Recovery Procedure When a LAN Failure Occurs between CTL (SIM = 7d02xx) (2U
Controller Chassis)

The storage system that detected this SIM may fell into serious error state due to DKC processor
abnormality. Therefore, restore the storage system according to the following flow immediately. (*1)

START (*1)

Connect the Maintenance PC to both CTLs

and check the failure log information (refer to
MAINTENANCE PC SECTION “5.3 Log”)
Execute the recovery procedure for a failure
Is SIM = aff1xx Yes when SIM = aff1xx occurs. (Refer to “3.41 Recovery
reported? Procedure when a GUM Failure Occurs (SIM =
aff1xx)”)
No
Execute the recovery procedure for a failure
Is SIM = 7d01xx Yes when SIM = 7d01xx occurs. (Refer to “3.10.1
reported? Recovery Procedure When an Internal LAN Failure
Occurs (SIM = 7d01xx) (2U Controller Chassis)”)
No

Yes Take action according to ACCs of SIM

Is SIM = fff7xx
= 2154xx. (Refer to ACC (ACTION CODE)
reported?
SECTION (ACC00-00)).
No
Check whether the IP address, subnet mask, and default gateway are properly set for
communication between the Maintenance PC/SVP and CTL in the following network
settings (When SVP is used for communication, ask the customer.) (If you open the
“Maintenance Utility” window, see MPC02-260.):
• Maintenance PC Network Settings (see MPC02-60)
• Storage Device List Network Settings (see MPC02-130)
• Maintenance Utility Network Settings (see MPC03-510)

Are the network settings No

correct?
Correct the network settings.
Yes
Execute LAN Check
Replace the LAN cable connected to (See DIAG04-210)
the CTL that has the failure.

Execute LAN Check No

Normally ended?
(See DIAG04-210)

Yes
No
Normally ended?
2
Yes 1 (TRBL03-231)
2 (TRBL03-231) (TRBL03-231)
*1: This SIM might not be generated at LAN error.

TRBL03-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-231

Collect dumps (See MPC05-50)

Perform Step 1 through Step 4 in

MAINTENANCE PC SECTION
“3.26 Resetting GUM”.

Execute LAN Check

(See DIAG04-210)

Yes
Normally ended?

No
2
Replace the CTL1
(See REP02-04-10)

Execute LAN Check

(See DIAG04-210)

No
Normally ended?

Replace the CTL2

Yes
(See REP02-04-10)

Execute LAN Check

(See DIAG04-210)

No
Normally ended?

Collect dumps (See MPC05-50)

Yes
2

Collect dumps T.S.D Call

(See MPC05-50)

Is the window
shown in MPC05-141
(3) (b) that is indicating the Yes
MPs for which dump collection is
not done displayed during
dump collection?
T.S.D Call

No

END

TRBL03-231
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-240

3.10.4 Recovery Procedure When a LAN Failure Occurs between CTL (SIM = 7d02xx) (4U
Controller Chassis)

The storage system that detected this SIM may fell into serious error state due to DKC processor
abnormality. Therefore, restore the storage system according to the following flow immediately. (*1)

START (*1)

Connect the Maintenance PC to both CTLs

and check the failure log information (refer to
MAINTENANCE PC SECTION “5.3 Log”)

Execute the recovery procedure for a failure

Is SIM = aff1xx Yes when SIM = aff1xx occurs. (Refer to “3.41
reported? Recovery Procedure when a GUM Failure Occurs
(SIM = aff1xx)”)
No
Execute the recovery procedure for a failure
Is SIM = 7d01xx Yes when SIM = 7d01xx occurs. (Refer to “3.10.2
reported? Recovery Procedure When an Internal LAN Failure
Occurs (SIM = 7d01xx) (4U Controller Chassis)”)
No

Yes Take action according to ACCs of SIM

Is SIM = fff7xx
= 2154xx. (Refer to ACC (ACTION CODE)
reported?
SECTION (ACC00-00)).
No
Check whether the IP address, subnet mask, and default gateway are properly set for
communication between the Maintenance PC/SVP and CTL in the following network
settings (When SVP is used for communication, ask the customer.) (If you open the
“Maintenance Utility” window, see MPC02-260.):
• Maintenance PC Network Settings (see MPC02-60)
• Storage Device List Network Settings (see MPC02-130)
• Maintenance Utility Network Settings (see MPC03-510)

Are the network settings No

correct?
Correct the network settings.
Yes
Execute LAN Check
(See DIAG04-210)
Replace the LAN cable connected to
the CTL that has the failure.
No
Normally ended?
Execute LAN Check
(See DIAG04-210)
Yes

4 2
(TRBL03-251) (TRBL03-250)

*1: This SIM might not be generated at LAN error.

TRBL03-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-250

Execute LAN Check

(See DIAG04-210)

Yes
Normally ended?

No
Replace the LANB on CTL1
(See REP02-11-10)

Execute LAN Check

(See DIAG04-210)

Yes
Normally ended?

No
Replace the LANB on CTL2
(See REP02-11-10)

Execute LAN Check

(See DIAG04-210)

Yes
Normally ended?

No
2
Replace the CTL1
(See REP02-04-10)

Execute LAN Check

(See DIAG04-210)

No
Normally ended?
Replace the CTL2
Yes (See REP02-04-10)
2
Execute LAN Check
(See DIAG04-210)
Collect dumps
(See MPC05-50)
No
Normally ended?

3 Collect dumps (See MPC05-50)

Yes
(TRBL03-251)
2
T.S.D Call

TRBL03-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-251

Is the window
shown in MPC05-141
(3) (b) that is indicating the Yes
MPs for which dump collection is
not done displayed during
dump collection?
T.S.D Call

No

END

Yes
Normally ended?

No
2
Collect dumps (See MPC05-50)
(TRBL03-250)

Perform Step 1 through Step 4 in

MAINTENANCE PC SECTION
“3.26 Resetting GUM”.

1
(TRBL03-250)

TRBL03-251
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-260

3.11 Recovery Procedure for the Failure on Both Sides of CACHE at the Time of Starting
(SIM = fff50x)
This procedure is to recover errors of the both sides of cache at powering on the storage system.
At this time, if pending data (non-written data to the drive) exists on the cache, the drive will be blocked and
the LDEV formatted drive will be required.

START

Check the status of LDEV. Inform the customer that the userʼs files need the
(See MPC04-110) recovery because the blocked LDEV needs to be
formatted after maintenance.

Check a cluster with blocked Cache or CTL.

(See MPC09-60)

Replace the CTL of the cluster with blocked Cache

or CTL.
(See REP02-04-10)

Replace the CTL of the other clusters.

Cache of the other cluster is not blocked, but be
(See REP02-04-10)
sure to replace it.

Check the status of LDEV.

(See MPC04-110)

No
Is there blocked LDEV?

Yes

Format the blocked LDEV (LDEV format).

(See MPC04-370)

END

TRBL03-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-270

3.12 Recovery Procedure When Cache Correctable Error Is Detected (SIM = fff0xx,
fe05xx)

START

Check the DIMM locations where the

error occurs according to the failure part
specified by the SIM = fff0xx.
(See SIMRC02-20.)

Does the Yes

error occur in multiple DIMM
locations?

No
Replace the DIMM with the Replace the CTL with the maintenance
maintenance part. (See REP02-05-10.) part. (See REP02-04-10.)

Is the SIM = fff0xx No Is the SIM = fff0xx No

reported again? reported again?

Yes Yes
Replace the CTL with the maintenance Replace the DIMMs with the
part. (See REP02-04-10.) maintenance parts. (See REP02-05-10.)

END

TRBL03-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-280

This page is for editorial purpose only.

TRBL03-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-290

This page is for editorial purpose only.

TRBL03-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-300

3.13 Recovery Procedure for LDEV Blockade (SIM = ef8xxx, ef9xxx, db8xxx, db9xxx,
dbaxxx, dbbxxx, dfaxxx, dfbxxx, 46cxxx, 46dxxx)
When LDEVs are blocked due to blockade of several drives (PDEVs) (SIM = ef8xxx, ef9xxx, db8xxx,
db9xxx, dbaxxx, dbbxxx, dfaxxx, and dfbxxx) or when data copy processes are skipped during drive
restoration procedure for blocked LDEVs (SIM = 46cxxx and 46dxxx), perform the following recovery
procedure to restore the LDEVs. The LDEVs will be restored to the correction access status.

If SIM = 623xxx is reported, prioritize 10.2 Recovery Procedure for Pool Failure (SIM = 623xxx) .

You might perform drive replacement and LDEV formatting after data backup because the
following is not a procedure for removing the cause of error.
Be sure to follow instructions by Technical Support Division.
If you perform PDEVs replacement, only one thing you can do is to restore the data by using
backups after performing LDEV formatting.

If you need to replace a Controller Board, before doing that, restore all DP-VOLs for
which Capacity Saving is enabled, Deduplication System Data Volumes (Fingerprint), and
Deduplication System Data Volumes (Data store) by performing the following procedure. Data
of blocked volumes cannot be copied by drive copy or correction copy. When the volumes are
blocked, destage of dirty data on cache to drives, which should be executed before replacement
of a Controller Board, is not possible.

TRBL03-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-310

START

Are there blocked basic No

volumes (including pool-VOLs)? (*8)

Yes

Is there any
drive whose status is displayed No
as Blocked in the Status
column? (*9) Restore LDEVs. (See MPC04-640.)

Yes

Are there
unrecoverable LDEVs (status is No
Do you need data in the No not Normal) among the target
blocked LDEVs? LDEVs?

Yes
Yes 2
(TRBL03-321)
3
4
(TRBL03-321)
(TRBL03-311)

Are there
blocked DP-VOLs
(including DP-VOLs for which
Capacity Saving is enabled), Deduplication No
System Data Volumes (Fingerprint), and
Deduplication System Data
Volumes (Data store)? END
(*10)

Yes

6
(TRBL03-322)

TRBL03-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-311

Restore the blocked LDEVs. (See

MPC04-640.)
The targets are basic volumes
(including pool-VOLs) only.

Are all the target

basic volumes (including No
pool-VOLs) restored (to the
Normal status)?
3
Yes (TRBL03-321)

Are there blocked DP- Yes

VOLs?

No 6
(TRBL03-322)
1
(TRBL03-320)

TRBL03-311
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-320

1 8

Call T.S.D in order to know which

action A or B should be taken.

B
A or B

A Replace drive(s) whose status is Failed

action action or Blocked , and perform correction
Backup the data from LDEVs. (*11)
A B copy in order to recover the parity
groups redundancy.

2 5
(TRBL03-321) (TRBL03-321)

TRBL03-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-321

Replace PDEVs related to SIM RC = eb2xxx,

eb3xxx, db4xxx, db5xxx, db6xxx, db7xxx,
ef1xxx, df8xxx, df9xxx.
(See REP01-05-10) (*4) (*6)

Are
there pool-VOLs Yes
among the LDEVs to be
formatted?
Format the LDEVs (pool-VOLs).
No For DP pool, see 10.1 Recovery Procedure
for pool-VOL Blockade (When Two (Three in
Format the LDEVs.
RAID6) or More Are Blocked in the RAID Gr
(See MPC04-370) (*6) (*7)
the pool-VOL Belongs) .
For Thin Image/Thin Image Advanced pool,
see 8.7 Recovery Procedure for Thin Image
pool-VOL Failure .

END

3
Is LDEV formatting No
successful?
Get Auto Dump (See MPC05-50.), and call
Yes T.S.D in order to know what action should be
taken.
Restore the LDEV data by using the data
backed up in the action A. (*7)

END
5

System
Option Mode 803 or Yes
Protect V-VOLs when I/O fails to
Blocked Pool VOL is (Request to user)
ON? (*5) Please confirm whether DP-VOL to which the
Protect attribute of DRU is added exists. (*3)
No
(Request to user)
When DP-VOL to which the Protect attribute
has been added exists, release the protection
attribute of the DP-VOLs using the Data
Retention window of Storage Navigator. (See
the Provisioning Guide for Open Systems.)

END

TRBL03-321
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-322

[Judgement of whether some data copy processes are skipped or not and recovery procedure when no data
copy process is skipped]

If drive copy or correction copy Restore the blocked LDEVs forcibly

processes are in progress, stop them. (without safety checks) in the
(*12) following order.
---- Ask the Technical
(See MPC04-695.)
Support Division
(1) Deduplication System Data
In the Install window of the about the password.
Volumes (Fingerprint) and
Maintenance PC, select [Change
Deduplication System Data
Configuration]-[System Option]. In
Volumes (Data store)
the Copy Operation field, uncheck
(2) DP-VOLs (including DP-VOLs
Dynamic Sparing and Correction
for which Capacity Saving is
Copy. (See MPC05-850.)
enabled)

Check that no drive copy or

In the Install window of the
correction copy process is in
Maintenance PC, select [Change
progress. If any process is in
Configuration]-[System Option].
progress, stop it. (*12)
In the Copy Operation field,
restore the Dynamic Sparing and
Correction Copy checkboxes to the
original settings.
Are there blocked Yes (See MPC05-850.)
basic volumes (including pool-
VOLs)? (*8)

Is there any
No drive for which Blocked Yes
is displayed in the [Status]
Is column? (*9)
the
number of 8
No
drives for which (TRBL03-320)
Blocked is displayed in No
the [Status] column in the same 5
parity group less than two (TRBL03-321)
(three for the RAID6
configuration)? 3
(*9) (TRBL03-321)

Yes

Is SSB = 9b97
reported for the copy
Yes
destination drive for which drive
copy/correction copy ended
normally? (*13)
7
(TRBL03-323)
No

TRBL03-322
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-323

[Recovery procedure when some data copy is skipped]

(Step A)
For maintenance, block all copy destination
drives for which SSB = 9b97 is reported.

Restore the blocked LDEVs forcibly (without

safety checks) in the following order.
(See MPC04-695.)
---- Ask the Technical Support
(1) Deduplication System Data Volumes
Division about the
(Fingerprint) and Deduplication System
password.
Data Volumes (Data store)
(2) DP-VOLs (including DP-VOLs for
which Capacity Saving is enabled)

In the Install window of the Maintenance

PC, select [Change Configuration]-
[System Option]. In the “Copy Operation”
field, restore the “Dynamic Sparing” and
“Correction Copy” checkboxes to the original
settings. (See MPC05-850.)

Perform the dummy replacement of the

drives that you blocked for maintenance in
Step A and start correction copy.

System
Option Mode 803 or Yes
“Protect V-VOLs when I/O fails to
(Request to user)
Blocked Pool VOL” is
ON? (*5) Please confirm whether DP-VOL to which the Protect
attribute of DRU is added exists. (*3)
No
(Request to user)
When DP-VOL to which the Protect attribute has been
added exists, release the protection attribute of the DP-VOLs
using the Data Retention window of Storage Navigator. (See
the “Provisioning Guide for Open Systems”.)

(Request to user)
Read the data of all DP-VOLs for which
Capacity Saving is enabled in the pool.

Yes
Is SIM = 680001 reported?

Perform “20.1 Recovery Procedure for dedupe and

No compression Operation Error (SIM = 680001)”.

END

TRBL03-323
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-330

*1: (Blank)
*2: (Blank)
*3: Please specify the following condition for the filter using Virtual Volumes tab of Pools: Volume
tabs to display DP-VOL to which the Protect attribute is added in all DP-VOL related to concerned
POOL. (Please make Access Attribute column visible if it is hidden.)
• Please input “protect” specifying the access attribute for conditional expression.
See “System Administrator Guide” for details.
*4: When PDEV replacement fails and the following conditions (a) and (b) are met, check the box of
“Forcibly run without safety checks”, and then replace the PDEV again.
The checkbox is displayed only when Maintenance Utility is started from the “Web Console”
window or the “MPC” window. To check the checkbox, start Maintenance Utility from the “Web
Console” window or the “MPC” window.
(a) Data in the blocked LDEV is not needed.
(b) No error code other than shown in (b-1) is included when PDEV replacement fails.
(b-1) “30762-208312”, “30762-208307”
*5: Check V-VOL protection function settings when the pool-VOL is blocked in [Protect V-VOLs
when I/O fails to Blocked Pool VOL] of the “Pools” window, or the window displayed after
selecting a pool in the “Pools” window of Storage Navigator.
[Yes] indicates that the V-VOL protection function is set to ON.
*6: If an LDEV to be formatted contains pairs of any of the following types, delete the pairs and then
re-create them after restoring the LDEV.
• TrueCopy, Universal Replicator, ShadowImage, Volume Migration, Thin Image, Thin Image
Advanced or global-active device.
*7: If you restore the LDEV being used by a global-active device pair, follow the procedure in
TRBL18-80.
*8: In the “Parity Groups” window in Web Console, select each parity group to display.
To check LDEV, click the [LDEVs] tab.
*9: In the “Parity Groups” window in Web Console, select each parity group to display.
To check PDEV, click the [Drives] tab.
*10: How to check the blockade state of DP-VOLs (including DP-VOLs for which Capacity Saving
is enabled), Deduplication System Data Volumes (Fingerprint), and Deduplication System Data
Volumes (Data store):
In the Logical Devices window in Web Console, if [Blocked] is displayed in the [Status] column,
the volumes are blocked. Check the [Status] column of all LDEVs for which “DP” is displayed in
the [Provisioning Type] column.

TRBL03-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-331

*11: If you have forcibly restored DP-VOLs for which Capacity Saving is enabled, Deduplication
System Data Volumes (Fingerprint), and Deduplication System Data Volumes (Data store), the
LDEVs might be blocked again due to read errors during backup.
When data is in the other area, the data might be able to be read by performing forcible restoration
again.
*12: In the [Drives] tab of Maintenance Utility, select the target drives and click the [Stop Copy] button.
*13: See bytes 0x4e through 0x4f for the C/R number of the drive for which SSB = 9b97 is reported.
For details of the C/R number and the HDD location number, see THEORY OF OPERATION
SECTION “4.1 DB Number - C/R Number Matrix”.

In this case, the C/R number

of the drive is 0x1013.

TRBL03-331
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-340

3.14 Response to the Occurrence of External Temperature Warning or Alarm (SIM =

af110x, af120x)
1. Response to the Occurrence of External Temperature Warning

START

Check if the external temperature environment

of the Storage System DKC is abnormal or
was abnormal when the SIM occurred.

Does it apply to either of No

the above?

Yes
Solve the problem of the Storage System T.S.D Call
environment.

Has the external

No
temperature warning been recovered?
(*1)

Yes
T.S.D Call
END

*1: The recovery status of the external temperature warning can be verified by using the detailed
information of the SSB “f602”.
If the detailed data [Link][3:0] in the SSB “f602” is “1”, this value shows that the external
temperature warning has been recovered.
The following is an example of the detailed information of SSB.
0 1 2 3 4 5 6 7 8 9 a b c d e f
00 77040c12 36178c00 c0330000 00802000
10 00000000 0000bcf2 00000000 00000000
20 10000000 0000018c 00ff0000 00000080
30 33c00000 0000ff8c 00000080 00000000
40 30010001 00000000 48694164 6447756d
50 5373622e 63000000 00000000 00000000
60 ab000000 00000000 00000000 00000000
70 00000000 00000000 00000000 00000000
The detailed information of SSB can be viewed in the “Internal Alert Detail” window of
Maintenance Utility.
To view the detailed information of the SSB “f602” by using Maintenance Utility, click on the alert
ID (link text) on the row of the error code “f602” in the [SSB] tab in the [Internal Alerts (DKC)]
window (see MAINTENANCE PC SECTION “3.21 Alert Display”).

TRBL03-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-350

2. Response to the Occurrence of External Temperature Alarm

START

Does
the POWER LED (Green) No
1
on the Storage System light
up? (TRBL03-360)
Yes
By detecting the external temperature, the
planned shutdown processing of the Storage
System executed automatically. Wait until the
planned shutdown is completed.
Check if the external temperature environment
of the Storage System DKC is abnormal or
was abnormal when the SIM occurred.

Does it apply to either of No

the above?

Yes
Solve the problem of the Storage System T.S.D Call
environment.

Does the POWER LED No

(Green) go out?

Yes
When the Storage System needs to be turned
on again, operate PS ON.

END

[Special instructions when contacting the Technical Support Division]

• Collect a Normal Dump. (See MPC05-80.)
• Check that no failure has occurred in the intake/exhaust duct on the front side (intake side) and rear side
(exhaust side) of the DKC.
• Check that the external temperature environment is not abnormal or was not abnormal.

TRBL03-350
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-360

Check if the external temperature environment

of the Storage System DKC is abnormal or was
abnormal when the SIM occurred.

Does it apply to either of No

the above?

Yes T.S.D Call

Solve the problem of the Storage System
environment.

Has the external temperature No

alarm been recovered? (*1)

Yes T.S.D Call

END

*2: The recovery status of external temperature alarm can be verified by using the detailed information
of the SSB “f602”.
If the detailed data [Link][3:0] in the SSB “f602” is “2”, this value shows that the external
temperature alarm has been recovered.
The following is an example of the detailed information of SSB.
0 1 2 3 4 5 6 7 8 9 a b c d e f
00 77040c12 36178c00 c0330000 00802000
10 00000000 0000bcf2 00000000 00000000
20 10000000 0000018c 00ff0000 00000080
30 33c00000 0000ff8c 00000080 00000000
40 30010001 00000000 48694164 6447756d
50 5373622e 63000000 00000000 00000000
60 ab000000 00000000 00000000 00000000
70 00000000 00000000 00000000 00000000
The detailed information of SSB can be viewed in the “Internal Alert Detail” window of
Maintenance Utility.
To view the detailed information of the SSB “f602” by using Maintenance Utility, click on the alert
ID (link text) on the row of the error code “f602” in the [SSB] tab in the [Internal Alerts (DKC)]
window (see MAINTENANCE PC SECTION “3.21 Alert Display”).

[Special instructions when contacting the Technical Support Division]

• Collect a Normal Dump. (See MPC05-80.)
• Check that no failure has occurred in the intake/exhaust duct on the front side (intake side) and rear side
(exhaust side) of the DKC.
• Check that the external temperature environment is not abnormal or was not abnormal.

TRBL03-360
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-370

3.15 Response to the Detection of CPU Abnormal Temperature (SIM = af100x)

START

Is the external Yes

temperature alarm (SIM = af120x)
detected?
“3.14 Response to the Occurrence of External Temperature
No Warning or Alarm (SIM = af110x, af120x)”(TRBL03-340)

Is the external Yes

temperature warning (SIM = af110x)
detected?
“3.14 Response to the Occurrence of External Temperature
No Warning or Alarm (SIM = af110x, af120x)”(TRBL03-340)

Does
the SIM of the FAN No
warning (RC = aff30x)
exist? Replace the Controller Board.
Yes

Replace the FAN concerned.

Does the SIM of the Yes
abnormal temperature (RC =
af100x) exist?

No

END T.S.D Call

NOTE: When the CPU temperature becomes normal, the system is Ready. When replacing
the FAN, there is a case which needs time of about one hour until the CPU becomes
the normal temperature.

TRBL03-370
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-380

3.16 Response to the Detection of Invalid CEDT(SIM = 399f0x)

START

Check the CEDT setting of the Controller

Board in the “Maintenance Utility” window.
(See MAINTENANCE PC SECTION “3.16
Edit or Confirm System Parameters”.)

Yes
Is the CEDT setting enabled?

Cancel the CEDT setting.

No

Did the invalid Yes

CEDT setting (SIM = 399f0x)
recover?

No

Replace the failed Controller Board

(CTL1 for SIM = 399f00 or CTL2 for
SIM = 399f01). (See REP02-04-10)

END

TRBL03-380
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-390

3.17 Response to the Detection of Uninstalled CFM (SIM = aff20x)

START

SIM for detecting the uninstalled CFM occurs

Is the CFM uninstalled or No

almost disconnected?
Replace the CFM with the maintenance part.
Yes (See REP02-10-10)
Perform the [Replace], [Block], and
[Recover] procedures in accordance with
REPLACEMENT SECTION “2.10 Replacing Yes
a Cache Flash Memories (CFM)”. (When the Recovered?
CFM is not installed, install a normal CFM in
the vacant location. When the CFM is almost No
disconnected, install the CFM properly.) Replace the CTL with the maintenance part.
(See LOC02-20 and MPC03-1220) (See REP02-04-10)

Yes Yes
Recovered? Recovered?

No No
Replace the CFM with the maintenance part.
(See REP02-10-10)
Collect the DUMP (See
MPC05-50.) and contact the
Technical Support Division.
Yes
Recovered?

No
Replace the CTL with the maintenance part.
(See REP02-04-10)

Yes
Recovered?

No

Collect the DUMP (See END

MPC05-50.) and contact the
Technical Support Division.

TRBL03-390
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-400

3.18 Response to the Occurrence of BKM or BKMF Warning (SIM = af400x)

START

Is the Controller Yes

Chassis CBSN?
Are
No multiple SIMs
Yes
= af200x, af210x, af400x,
af410x, and/or fffa0x
reported?
See “3.78 Recovery Procedure
No for Multiple Errors of DKCPS/BKM
Replace the target BKM. in CBSN”.
(See REP02-09-10)

Is the storage system Yes

recovered?

No
When the target BKM is BKM1,
replace the Controller Board 1
(CTL1).
When the target BKM is BKM2,
replace the Controller Board 2
(CTL2). (See REP02-04-10)

Is the storage system Yes

recovered?

No END

T.S.D. call

Is the Controller Chassis Yes

CBXSS/CBXSL?
Open the “Maintenance Utility” window (See
No MPC02-260) and check the location of the
Open the “Maintenance Utility” target Controller Board.
window (See MPC02-260) and
check the location of the target Block the target Controller Board.
BKM/BKMF. (See REP02-04-10)

Replace the target Controller Board.

(See REP02-04-10)
1
(TRBL03-401)
2
(TRBL03-401)

TRBL03-400
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-401

Does the screw No

(blue) fixing the target BKM/
BKMF tighten?
Tighten the screw (blue) to fix.

Yes

Is the storage system Yes

recovered?

No

Replace the target BKM or BKMF.

CBSS/CBSL : (See REP02-09-10)
CBLH : (See REP02-07-10)

Is the storage system Yes

recovered?

No

Replace the Controller Board

containing the target BKM/BKMF.
(See REP02-04-10)
2

Is the storage system Yes

recovered?

No END

T.S.D. call

TRBL03-401
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-410

3.19 Response to the Detection of Forced Volatilization Warning (SIM = fffe0x)

START

Is the jumper
used for cache memory
volatilization enabled? (See No
MAINTENANCE PC SECTION “3.16
Edit or Confirm System
Replace the Controller Board
Parameters”.)
(See REP02-04-10)

Yes Is
there a SIM of the Yes
Disable the jumper used for cache
memory volatilization. (See forced volatilization (RC =
MAINTENANCE PC SECTION “3.16 fffe0x)?
Edit or Confirm System Parameters”.) No

T.S.D Call
END

TRBL03-410
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-420

3.20 Response to the Occurrence of DKCPS Warning (SIM = af200x)

START

Is the Controller Yes

Chassis CBSN?

Are
No multiple SIMs
Yes
= af200x, af210x, af400x,
af410x, and/or fffa0x
reported?
See “3.78 Recovery Procedure
No for Multiple Errors of DKCPS/BKM
in CBSN”.

Is the
abnormal DKCPS input Yes
voltage (SIM = af210x)
reported?
Abnormal DKCPS Input Voltage
No (TRBL03-1550)

Has the
DKCPS warning occurred Yes
in both DKCPS1 and
DKCPS2? Collect Auto Dump.
(See MPC05-50)
No
Check the location of the DKCPS
which reported SIM = af200x in the T.S.D. call
“Maintenance Utility” window.

Is the Controller No
Chassis CBLH?

Yes 1
(TRBL03-430)
Is the target DKCPS No
screwed?
Screw the target DKCPS.
Yes

Did the target DKCPS Yes

recover?

No END

1
(TRBL03-430)

TRBL03-420
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-430

Replace the target DKCPS.

(See REP02-15-10)

Did the target DKCPS Yes

recover?

No

Is AC input voltage
No Abnormal DKCPS Input
at the PS OK?
Voltage (TRBL03-1550)
(Refer to Figure 3-1.)

Yes
Replace the CTL1
(See REP02-04-10)

Did the target DKCPS Yes

recover?

No
Replace the CTL2
(See REP02-04-10)

Did the target DKCPS Yes

recover?

No
Collect Auto Dump.
(See MPC05-50) END

T.S.D. call

TRBL03-430
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-440

3.21 Response to the Detection of Abnormal DBPS Input Voltage (SIM = af60xx, af61xx,
af62xx)

START

Check if there is any problem with the

cable of the PS warning target.

Is there
a cable abnormality? Yes
(e.g., cable is halfway insertied,
disconnected, or faulty)
Correct the problem with the cable and
check the status display.
No
Check AC input voltage for PS of the
PS warning target. Refer to Figure 3-1. END

Is AC input voltage at Yes

the PS OK?
Replace the target DBPS.
No (See REP02-15-10)
Check AC input voltage at the
distributor.
Is the target DBPS No
recovered?
Collect Auto Dump.
Yes (See MPC05-50)

END
Is AC input voltage at Yes T.S.D Call
the distributor OK?

No
1
Perform the check of the power supply
(TRBL03-450)
equipment and the removal of the cause
part.

Turn on the power of the distributor

END

TRBL03-440
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-450

Check the location of the connected

PDU for the warning target PS.

Is the PDU to be replaced No

the Hitachi PDU?
If the PDU is manufactured by other than
Yes Hitachi, ask the customer to replace the
Are PDU.
hardware units other No
than DW700 connected to PDU for
the replacement?
Refer to the PDU manual and perform the
Yes PDU replacement. (See REP02-19-10)

Perform Power OFF of hardware units

other than DW700.
END

Refer to the PDU manual and perform

the PDU replacement.
(See REP02-19-10)

END

TRBL03-450
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-460

3.22 Response to the Detection of Invalid CEMODE (SIM = 399e0x)

START

Check the CEMODE (CEMD) setting of

the Controller Board in the “Maintenance
Utility” window. (See MAINTENANCE PC
SECTION “3.16 Edit or Confirm System
Parameters”.)

Is the CEMODE (CEMD) Yes

setting enabled?
Cancel the CEMODE (CEMD) setting.
No

Did the
invalid CEMODE (CEMD) Yes
setting (SIM = 399e0x)
recover?
No

Replace the failed Controller Board

(CTL1 for SIM = 399e00 or CTL2 for
SIM = 399e01). (See REP02-04-10)

END

TRBL03-460
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-470

3.23 Recovery Procedure When CHK1B or CHK3 Threshold Over Occurs (SIM = 3071xy,
3072xy)

START

Is SIM-RC
= ffe20x, fff40x, fff70x,
cf880x, 3073xy, ff210x, cf8a0x, No
2130xx, 2140xx, 2153xx, or 2154xx
generated in the same time
period?

Yes
Perform the recovery according to ACCs of Perform the recovery according
SIM-RC = ffe20x, fff40x, fff70x, cf880x, to ACCs of SIM-RC = 3071xy or
3073xy, ff210x, cf8a0x, 2130xx, 2140xx, 3072xy.
2153xx, or 2154xx.
(Do not refer to SIM-RC = 3071xy or 3072xy.)

END

TRBL03-470
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-480

3.24 Recovery Procedure for Warning of Channel Board/Disk Board Type (SIM RC =
3c9500)
When “Types of installed Channel Boards and Disk Boards” and “Types of defined Channel Boards and
Disk Boards” differ at the time of start-up, SIM RC = 3c9500 is issued. When it is issued, they need to be
matched. Furthermore, before starting the work, click the [CHB] and [DKB] tabs in the “Controller” window
of Maintenance Utility and take notes on the Channel Board and Disk Board types.

START

Click the [CHB] and [DKB] tabs from the

“Controller” window of Maintenance Utility
and specify the unmatched parts.

Is the
information on CHBs No
and DKBs (type and location) that is
displayed in Maintenance
Utility correct? Is SIM
RC = 3c9500 issued No
Yes during the New Installation
procedure?
Are types and No Yes
locations of installed CHBs and
Check types and locations of CHBs and
DKBs correct?
DKBs and reconfigure them in the New
Installation procedure (*1).
Yes
(See INST05-01-10.)

T.S.D. Call
Turn off the DKC power forcibly. T.S.D. Call
(See “15.1 Non volatilization power-off and
restarting procedure”.)

Match the CHB Type/DKB Type noted

before starting the work and the actual CHB
Type/DKB Type.

Execute PS ON.

END

TRBL03-480
Hitachi Proprietary DW850/DW900/DW1000
Rev.6.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-490

3.25 Isolation Procedure for Failed Part in CACHE Volatilization (SIM = ffe700, ffeb00,
ffcd0x, ffcfyx, 610002)
At the time of the cache volatilization, you carry out the recovery of the involved site according to the
ACC of SIM-RC or the detailed information that it is displayed the following procedure by SSB window to
classify involved sites after enforcement.

START

Is SIM RC = ffeb00 Yes

reported?

No

Is SIM RC = Yes
610002 reported?

No
Please confirm whether it occurred in the following maintenance. Collect dumps (see
•“15.2 Forced volatilization (full) power-off and restarting procedure 1-1” MAINTENANCE PC SECTION
•“15.3 Forced volatilization (full) power-off and restarting procedure 1-2” “5.2 Dump”), and contact T.S.D.
•INSTALLATION SECTION “2.1 Procedures for Installing Storage System” (*1)

Yes Did it occur

during one of the maintenance
above?

No
Please confirm whether SIM RC = ffcd00 or
ffcfy0 is reported.

Yes
Is SIM reported 1
(TRBL03-500)
No
Please confirm whether SIM RC = ffcd01 or
ffcfy1 is reported.

Yes
Is SIM reported 2
(TRBL03-510)
No Clarification of the cause is unnecessary because
the volatilization at start-up is caused by the forced
volatilization operation but not by a failure.

TRBL03-490
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-500

Please confirm whether SIM RC =

ffcd01 or ffcfy1 is reported.

Yes
Is SIM reported?

No
Please confirm whether CTL2 is
blockade. (MPC09-60)

Yes
Is CTL2 blockade?

No Collect dumps (see

MAINTENANCE PC SECTION
“5.2 Dump”), and contact T.S.D. (*1)
Is 35B5 of the Yes
related SSB reported? (See
MPC05-250.)

No Replace failed parts according

to ACCs of SIM = ffcd00.
Clarification of the cause
is unnecessary because the
volatilization at start-up is caused by
the forced volatilization procedure,
occurrence of a power disconnection
during the planned shutdown
procedure, and the like, but not by a
device failure.

Check whether CTL1 or a DIMM in

CTL1 is blocked (MPC09-60).

Is CTL1 or a DIMM in Yes

CTL1 blocked?
Perform the dummy replacement of
No CTL1 to restore it (replacement with
a maintenance part is not necessary).

END

TRBL03-500
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-510

Please confirm whether SIM RC =

ffcd00 or ffcfy0 is reported.

Yes
Is SIM reported?

No
Please confirm whether CTL1 is
blockade. (MPC09-60)

Yes
Is CTL1 blockade?

No Collect dumps (see

MAINTENANCE PC SECTION
“5.2 Dump”), and contact T.S.D. (*1)
Is 35B5 of the Yes
related SSB reported? (See
MPC05-250.)

No Replace failed parts according

to ACCs of SIM = ffcd01.
Clarification of the cause
is unnecessary because the
volatilization at start-up is caused by
the forced volatilization procedure,
occurrence of a power disconnection
during the planned shutdown
procedure, and the like, but not by a
device failure.

Check whether CTL2 or a DIMM in

CTL2 is blocked (MPC09-60).

Is CTL2 or a DIMM in Yes

CTL2 blocked?
Perform the dummy replacement of
No CTL2 to restore it (replacement with
a maintenance part is not necessary).

END

TRBL03-510
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-520

(*1) The SM information is not restored. DKC is in following condition.

Name of the P.P. Phenomenon
TC Differential bitmap is deleted. All copies in next resynchronization
or being executed will be copied.
GAD Differential bitmap is deleted. All copies in next resynchronization
or being executed will be copied.
UR Differential bitmap is deleted. All copies in next resynchronization
or being executed will be copied.
SI Refer to (*2)
TI TI is deleted.
VM Percentage that VM pairs are synchronized goes down to 0%
(differential bitmap is cleared) and copy processing time takes
long.
Quick Format Data will be lost from LDEV that carrying out Quick Format.
Dynamic Provisioning/ The data stored in HDP-VOL is lost.
Dynamic Tiering/
active flash

(*2) PS OFF phenomenon varies according to a ShadowImage pair state before carrying out PS OFF.
Pair Status
Name of the P.P. Phenomenon
(Open Pair Status)
SI COPY (PD)/Pending Percentage that P-VOL and S-VOL are
synchronized goes down to 0% and copy
processing time takes long.
PAIR/Duplex Percentage that P-VOL and S-VOL are
synchronized goes down to 0%.
COPY (SP)/SP-Pend Pair Status turns into PSUE/Suspend.
PSUS (SP)/V-Split Pair Status turns into PSUE/Suspend.
PSUS/Split Percentage that P-VOL and S-VOL are
synchronized goes down to 0% and copy
processing time will takes long in next
resynchronization.
COPY (RS)/Resync Percentage that P-VOL and S-VOL are
synchronized goes down to 0% and copy
processing time takes long.
COPY (RS-R)/Resync-R Percentage that P-VOL and S-VOL are
synchronized goes down to 0% and copy
processing time takes long.
PSUE/Suspend None

TRBL03-520
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-530

3.26 Isolation and Recovery Procedure for Drive Link Rate Error (SIM = dbcxxx, dbdxxx,
dbexxx, dbfxxx, dfcxxx, dfdxxx)
This section describes the method to judge whether a link rate error of a specific drive (PDEV) is caused by a
drive failure or an ENC failure and the recovery method when a link rate error SIM is reported.

With this SIM, when setting Link Rate for each drive port of each PDEV fails, a drive port link rate error of
Path 0 (REF code = dbcxxx, dbdxxx, dfcxxx) or a drive port link rate error of Path 1 (REF code = dbexxx,
dbfxxx, dfdxxx) is reported. (See THEORY OF OPERATION SECTION “4. Appendixes”.)

Possible causes of this failure include:

(1) Failure of the drive
(2) Failure of ENC (EXP)

Therefore before replacing the faulty drive with a service part, isolate the failure and recover it by performing
the appropriate recovery procedure.

TRBL03-530
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-540

START

Is there any Yes

blocked part in DKB/ENC/
HDD?
Recover the faulty part related to the
No blockage SIM first.
From SIM Log, check port#, DB#,
and RDEV# shown in Link Rate
error SIM. (See THEORY04-01-10) See TRBL02-640.

Does the
same failure occur with No: Error of the PDEV
multiple RDEVs# in the
same DB#? Replace HDD.
(See REP02-03-10)
Yes: SAS/NVMe I/F
common error
Are the
HDDs installed in the Yes
chassis that contains
CTLs? Replace the Controller Board
No connected to the HDD port.
(See REP02-04-10)
Replace ENC connected to the HDD
port. (See REP02-16-10)

Is the same SIM output No No Is the same SIM output

again? again?

Yes END Yes

Replace all HDDs under the target Are the
ENC/Controller Board for which Yes HDDs installed in the
SIM is output. (See REP02-03-10) chassis that contains
Replace the Controller Board CTLs?
connected to the HDD port. No
(See REP02-04-10)
Replace ENC connected to the HDD
port. (See REP02-16-10)

Is the same SIM output No

again?

Yes END

T.S.D. call

TRBL03-540
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-550

3.27 Drive failure recovery procedure

Explanation:
Types of the drive copy are shown below. Confirm the copy type and execute the drive recovery procedure.

Copy type Description Operation occasion

Correction This is an operation to restore and copy the data of the • Automatic operation owing to a
copy blocked drive using the data of another drive and parity failure
data when the data drive is blocked. • Operation instructed by the
• A correction copy to the spare drive is referred to as maintenance personnel
another drive correction copy.
• A correction copy to the replacement drive which has
been installed instead of the blocked drive is referred
to as a self-drive correction copy.
Drive copy This is an operation to copy data to the spare drive from • Automatic operation owing to a
the data drive. failure
A copy automatically performed owing to a warning • Operation instructed by the
level failure is referred to as dynamic sparing. maintenance personnel
Copy back This is a copy for returning data which has been copied • Operation instructed by the
to the spare drive by another drive correction copy or maintenance personnel
drive copy to the original data drive.

TRBL03-550
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-560

START

Failure
No
occurred during drive recovery
operation?
Yes Failure recovery owing No
to SIM issue?

Yes
Go to Subsection “3.27.7
Preventive maintenance”
Is there
a SIM stating that a
copy has been started in the drive No
concerned? (SIM RC=451xxx, 461xxx,
4b6xxx, 4b7xxx, 4c6xxx,
4c7xxx) (*2) Is the LDEV status
in the parity group corresponding No
Yes to the drive “Correction access”
status? (*1)
Is the LDEV
status in the parity group No
Yes
corresponding to the drive
Go to Subsection “3.27.5 “Normal”? (*1)
Is there a Correction access status”
SIM stating that the Yes
copy has terminated normally? No
(SIM RC=452xxx, 462xxx, 4b8xxx,
4b9xxx, 4c8xxx, 4c9xxx) Go to Subsection “3.27.7
Is there a Preventive maintenance”
(*2)
SIM stating that the copy
has terminated in a warned state? No
Yes Go to Subsection “3.27.6
(SIM RC=455xxx, 465xxx, 4bexxx,
4bfxxx, 4cexxx, 4cfxxx) Parity group blockade”
Is there
(*2)
Go to Subsection “3.27.1 In the case of a SIM stating that
normal termination (SIM RC = 452xxx, the copy has been aborted? (SIM No
Yes
462xxx, 4b8xxx, 4b9xxx, 4c8xxx, RC= 454xxx, 464xxx, 4bcxxx,
4c9xxx)” 4bdxxx, 4ccxxx,
4cdxxx) Abnormal termination
(SIM RC=453xxx,
Go to Subsection “3.27.2 In the case of Yes 463xxx, 4baxxx, 4bbxxx,
termination with a warning (SIM RC = 455xxx, 4caxxx, 4cbxxx)
465xxx, 4bexxx, 4bfxxx, 4cexxx, 4cfxxx)”

Go to Subsection “3.27.3 In the case of

termination owing to abortion (SIM RC = 454xxx,
464xxx, 4bcxxx, 4bdxxx, 4ccxxx, 4cdxxx)”

Go to Subsection “3.27.4 In the case of

abnormal termination (SIM RC = 453xxx,
463xxx, 4baxxx, 4bbxxx, 4caxxx, 4cbxxx)”

*1: Check the LDEV status in the parity group corresponding to the drive in the “Logical Devices”
window on the Web Console (refer to MAINTENANCE PC SECTION “4.1.2 Checking the
Logical Devices”). Apply a filter to display the information about the specific parity groups only.
For more details about filtering, refer to “System Administrator Guide”.
*2: The term “copy” means drive copy, copy back, or correction copy.

TRBL03-560
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-570

3.27.1 In the case of normal termination (SIM RC = 452xxx, 462xxx, 4b8xxx, 4b9xxx,
4c8xxx, 4c9xxx)
The procedure below is that used after a drive copy, copy back, or correction copy terminates normally.

START

Check if there is a failed track by means of Recover the failed track according to the
the Pinned Track Display. failed track recovery procedure on page
(Refer to page MPC05-1170.) TRBL04-160.

Are there any failed track? Yes

(See TRBL04-160.)

No

Is the
Copy Back Mode set to Yes
“Disable”? (See MPC04-
10.)
Do the
No
No drive and the target
driveY es have the same
capacity?
Was a copy Yes
Yes
back to the drive concerned
performed?
Yes
Was the drive replaced?
No

No
Yes Was a self-drive
correction copy executed? Replace the drive concerned as shown
below. (Copy back is not required.)
• When drive copy ends normally:
No
See Work ID = RDK1 “Drive replace ~
Replace the drive concerned and execute Copy back” Case 19 in REP01-06-10.
copy back as shown below. • When correction copy ends normally:
• When drive copy ends normally: See Work ID = RDK1 “Drive replace ~
See Work ID = RDK1 “Drive replace ~ Copy back” Case 20 in REP01-06-10.
Copy back” Case 1 in REP01-06-10.
• When correction copy ends normally:
See Work ID = RDK1 “Drive replace ~
Copy back” Case 2 in REP01-06-10.

END

TRBL03-570
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-580

3.27.2 In the case of termination with a warning (SIM RC = 455xxx, 465xxx, 4bexxx,
4bfxxx, 4cexxx, 4cfxxx)
The procedure explained below is that used when the drive copy, copy back, or correction copy terminates
but one of the following is detected:
(1) A failed track was detected, but the copy was continued.
(2) One or more blocked LDEVs were detected in the same parity group. Copy of data of the blocked
LDEVs was skipped.

START

Confirm the contents of the SSB related to

the SIM 455xxx/465xxx/4bexxx/4bfxxx
/4cexxx/4cfxxx. (*1)

Is
the LDEV There is a possibility that
corresponding to the drive Yes
the data has been lost. Contact the
concerned blocked? Technical Support Division.
(*2)
No

Check if there is a failed track by means of Recover the failed track according to the
the Pinned Track Display. failed track recovery procedure on page
(Refer to MAINTENANCE PC SECTION TRBL04-160.
“5.12.3 Pin Data Indication”.)

Are there any failed Yes

track? (See TRBL04-160.)

No

Is the Copy Back Mode set to Yes

“Disable”? (See MPC04-10.)

No Do the drive and

No
the target drive have the same
capacity?
1
Yes
(TRBL03-590)
2
(TRBL03-590)

TRBL03-580
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-590

1 2

Was a copy Was the drive Yes

Yes replaced?
back to the drive concerned
performed?
No
No Replace the drive concerned as shown below.
(Copy back is not required.)
Was a
Yes • When drive copy ends normally:
self-drive correction copy
See Work ID = RDK1 “Drive replace ~ Copy
executed?
back” Case 19 in REP01-06-10.
No • When correction copy ends normally:
See Work ID = RDK1 “Drive replace ~ Copy
Replace the drive concerned and execute copy back” Case 20 in REP01-06-10.
back as shown below.
• When drive copy ends normally:
See Work ID = RDK1 “Drive replace ~ Copy
back” Case 1 in REP01-06-10.
• When correction copy ends normally:
See Work ID = RDK1 “Drive replace ~ Copy
back” Case 2 in REP01-06-10.

END

*1: Meaning of bytes 40 to 7E of SSB F/M=9F EC=9355 related to SIM RC=455xxx, 465xxx, 4bexxx,
4bfxxx, 4cexxx, 4cfxxx
Byte (Hex.) Item Meaning
40 Number of failed tracks Number of failed tracks
41 Number of blocked LDEVs Number of blocked LDEVs
42 Blocked LDEV #0 Blocked LDEV No.
: : (Up to 30 LDEVs can be inputted from the top.)
7D Blocked LDEV #29 However, 0xff is inputted in the unused part.
7E E.O.D Means the end of data
*2: Confirm the status of the parity group corresponding to the drive concerned by means of the status.
For the procedure for referring to the status, refer to MAINTENANCE PC SECTION “4.1.1
Creating Parity Groups”.

TRBL03-590
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-600

3.27.3 In the case of termination owing to abortion (SIM RC = 454xxx, 464xxx, 4bcxxx,
4bdxxx, 4ccxxx, 4cdxxx)
The procedure below is that used when a drive copy, copy back, or correction copy is aborted owing to the
Maintenance PC operation by the service personnel. Since the status of the drive concerned is that before
starting copy, execute the recovery operation for the same drive once again.

TRBL03-600
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-610

3.27.4 In the case of abnormal termination (SIM RC = 453xxx, 463xxx, 4baxxx, 4bbxxx,
4caxxx, 4cbxxx)
The procedure below is that used when a drive copy, copy back, or correction copy terminates abnormally.
Since the recovery procedure may differ depending on the copy type, confirm the description on page
TRBL03-550 and execute the following procedure.

START

Abnormal Abnormal termination of a drive copy or a copy

termination of a correction No back (SIM RC=463xxx, 4caxxx, 4cbxxx)
copy? (SIM RC=453xxx,
4baxxx, 4bbxxx)

Yes

1. Go to the item of correction 3. Go to the item of drive

copy abnormal termination on page copy abnormal termination on page
TRBL03-620. TRBL03-680.

TRBL03-610
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-620

1. In the case of correction copy abnormal termination

The procedure below is that used when a correction copy terminates abnormally.

START

Refer to the copy history of the drive concerned corresponding to the SIM and confirm the drive location
of the copy source and destination. (Refer to the copy history logs on page MPC05-410.)

Confirm the status of the drive of the copy destination. (Refer to “(1) HDD detail information view” on
MAINTENANCE PC SECTION “[Link] HDD Information View”.)

Confirm the status of all the drives in the parity group which the source drive concerns. (Refer to “(1)
HDD detail information view” on MAINTENANCE PC SECTION “[Link] HDD Information View”.)

Are more drives

than the number shown below
blocked in the parity group to which the
Yes
copy source drive belongs?
RAID1: Two drives in a mirroring pair
RAID5: Two drives Replace the blocked drives in the parity
RAID6: Three drives group and perform the LDEV formatting
according to Work ID = RDK1 “LDEV
formatting after replacing all the HDDs
No blocked in a parity group” Case 16 in
REP01-06-10.
No NOTE: Data will be lost by executing the
Is the copy destination drive
above. Contact the Technical Support
blocked?
Division to confirm the validity of
the execution.
Yes
Refer to the copy history and confirm the
existence of a copy to still another drive from END
the blocked copy destination drive. (Refer to
the copy history logs on page MPC05-410.)

Is there any copy to another Yes

drive?

Recovery
No
operation against a failure No
occurred during a self-drive
correction copy?
To the next Step 2.
Yes
on page TRBL03-650.

1
(TRBL03-630)

TRBL03-620
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-630

Confirm whether there is a failed track by

means of the Pinned Track Display. (Refer to
MAINTENANCE PC SECTION “5.12.3 Pin Data
Indication”.)

Are there any failed track? No

(See TRBL04-160.)

Yes
Recover the failed track according to the failed track
recovery procedure. (Refer to “4.2.1 Pinned Tracks”.)

When the
correction copy is terminated No
abnormally, is SSB = 9382 reported?
(See MPC05-250.)
2
Yes
(TRBL03-640)
Is the CM
capacity more than or equal to No
the recommended capacity? (See
INST03-01-20.) Ask the customer to increase the CM capacity to
more than or equal to the recommended capacity.
Yes

Is there a pool-VOL in Yes

the parity group containing the copy source
drive?

No Are CLPR of the pool-VOL

and CLPR of the DP-VOL associated No
with the pool to which the pool-VOL
belongs identical?

Yes
Match CLPR of the pool-VOL and CLPR of
the DP-VOL.

Perform the copy again (replace the dummy of the

copy source).

END

TRBL03-630
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-640

When the correction copy Yes

is terminated abnormally, is SSB = 9b3c
reported? (See MPC05-250.)
The capacity of the pool to which a pool-VOL
in the parity group containing the copy source
No drive belongs is depleted. So, ask the customer
to expand the pool.

Perform the copy again (replace the dummy of

the copy source).

END

Recovery operation against a No (Another correction copy)

failure occurred during self-drive correction
copy

Replace the copy destination drive according to

Yes Work ID = RDK1 “Spare drive replace” Case 15
Replace the copy destination drive and execute in REP01-06-10. Then, replace the copy source
the self-drive correction copy again according to drive and execute the self-drive correction copy
Work ID = RDK1 “Drive replace ~ Correction according to Work ID = RDK1 “Drive replace ~
copy” Case 4 in REP01-06-10. Correction copy” Case 4 in REP01-06-10.

END END

TRBL03-640
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-650

2. In the case of correction copy abnormal termination (in which an unused spare drive is available)
This is a case in which a correction copy terminates abnormally owing to a failure in the copy destination
drive. However, if an unused spare drive exists, the correction copy is automatically performed to the
unused spare drive.
In the following procedure, the copy source is referred to as a copy source, the copy destination is
referred to as the first copy destination, and the unused spare drive is referred to as the second copy
destination.

Drive Blocked drive … Drive Spare drive Unused spare drive

(copy source) (copy destination)
(copy source) (the first copy (the second copy
distination) destination)

TRBL03-650
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-660

START

Is there a SIM stating

that a copy terminated abnormally in the No
1
copy source drive? (SIM RC = 453xxx,
4baxxx, 4bbxxx) (TRBL03-670)

Yes
(The copy to the second copy destination drive
terminated abnormally.)

Confirm the drive status. (*1)

Replace the blocked drives in the parity group and
Is other perform the LDEV formatting according to Work ID =
drive(s) in the parity group to Yes RDK1 “LDEV formatting after replacing all the HDDs
which the copy source drive concerns blocked in a parity group” Case 16 in REP01-06-10.
blocked? NOTE: Data will be lost by executing the above.
Contact the Technical Support Division to confirm the
No validity of the execution.
(The second copy destination drive is blocked.)

Confirm whether there is a failed track by means of

the Pinned Track Display. (Refer to MAINTENANCE
PC SECTION “5.12.3 Pin Data Indication”.)

Is there any failed track? No

(See TRBL04-160.)

Yes
Recover the failed track according to the failed
track recovery procedure. (Refer to “4.2.1 Pinned
Tracks”.)

Replace the copy source drive and execute the self-

drive correction copy according to Work ID = RDK1
“Drive replace ~ Correction copy” Case 4 in REP01-
06-10.

Replace the blocked spare drives (the first copy

destination and the second copy destination)
according to Work ID = RDK1 “Spare drive replace”
Case 15 in REP01-06-10.

END

*1: Confirm the following items.

• Confirm the location of the first copy destination and the second copy destination drives referring
to the copy history. Refer to the copy history log on page MPC05-410.
• Confirm the status of the second copy destination drive and the status of all the drives in the
parity group which the copy source drive concerns. (Refer to “(1) HDD detail information view”
on MAINTENANCE PC SECTION “[Link] HDD Information View”.)

TRBL03-660
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-670

Is there a SIM
stating that a copy terminated No
normally in the copy source drive? (SIM
RC = 452xxx, 4b8xxx,
4b9xxx)
Is there a SIM
Yes stating that a copy terminated No
in a warned state in the copy source drive?
(SIM RC = 455xxx, 4bexxx,
(The copy to the second copy destination drive 4bfxxx) (The copy to the second copy
terminated normally.) destination drive aborted.)
Yes
(The copy to the second copy destination drive
terminated in a warned state.)

Go to Subsection “3.27.2 In the case Go to Subsection “3.27.3 In the case

of termination with a warning (SIM RC of termination owing to abortion (SIM
= 455xxx, 465xxx, 4bexxx, 4bfxxx, RC = 454xxx, 464xxx, 4bcxxx, 4bdxxx,
4cexxx, 4cfxxx)” 4ccxxx, 4cdxxx)”

Is the Copy Back Mode set to No

“Disable”? (See MPC04-10.)

Yes

Do the copy source No

drive and the target drive have the
same capacity?

Yes
Replace the copy source drive according to Replace the copy source drive and execute
Work ID = RDK1 “Drive replace ~ Copy copy back according to Work ID = RDK1
back” Case 20 in REP01-06-10. (Copy back “Drive replace ~ Copy back” Case 2 in
is not required.) REP01-06-10.

Replace the blocked spare drives (the first

copy destination and the second copy
destination) according to Work ID = RDK1
“Spare drive replace” Case 15 in REP01-06-
10.

END

TRBL03-670
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-680

3. In the case of drive copy abnormal termination

The procedure below is that used when a drive copy or a copy back terminates abnormally.

START

Refer to the copy history of the drive concerned corresponding

to the SIM and confirm the drive location of the copy source and
destination. (Refer to “[7] Copy History log” on MAINTENANCE
PC SECTION “5.3.1 Log Indication”.)

Confirm the statuses of the copy source and copy destination drives.
(Refer to “(1) HDD detail information view” on MAINTENANCE
PC SECTION “[Link] HDD Information View”.)

Is copy source Yes

drive blocked?
No Did
Yes
the copy back terminate
No Is the copy abnormally?
destination drive blocked? Perform the dummy replacement of
No
the copy destination drive.
Yes
Refer to the copy history and confirm the
existence of a copy to still another drive from
the blocked copy destination drive. (Refer to Replace the copy source drive and execute
“[7] Copy History log” on MAINTENANCE the self-drive correction copy according
PC SECTION “5.3.1 Log Indication”.) to Work ID = RDK1 “Drive replace ~
Correction copy” Case 4 in REP01-06-10.

END
Is
Yes
there any copy to another
drive?
No Recovery
No
operation against a failure occurred during
a copy back?
Yes Go to the next Step 4.
on page TRBL03-710.
Confirm whether there is a failed track by
means of the Pinned Track Display. (Refer to
MAINTENANCE PC SECTION “5.12.3 Pin
Data Indication”.)

Are there any failed Yes

track? (See TRBL04-160.)
Recover the failed track according to the
No failed track recovery procedure on “4.2.1
Pinned Tracks”.

1
(TRBL03-690)

TRBL03-680
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-690

When the drive copy

Yes
is terminated abnormally, is SSB = 9382
reported? (See MPC05-
250.)
No 2
(TRBL03-700)
When the drive copy Yes
is terminated abnormally, is SSB = 9b3c
reported?
The capacity of the pool to which a pool-VOL
No in the parity group containing the copy source
drive belongs is depleted. So, ask the customer
to expand the pool.

Perform the drive copy again.

END

Recovery operation against a No (Drive copy to the spare drive)

failure occurred during a copy
back?
Is the
Yes Copy Back Mode set to Yes
Replace the copy destination drive. ~ “Disable”? (See MPC04-
Execute a copy back. 10.)
Work ID=RDK1 on page REP01-06-10 No Do the
No copy source drive and
the target drive have the same
capacity?
Replace the copy destination spare drive
according to Work ID = RDK1 “Spare drive Yes
replace” Case 15 in REP01-06-10. Then,
execute copy to the spare drive, replace the
copy source drive, and execute copy back
according to Work ID = RDK1 “Copy to
Spare drive ~ Drive replace ~ Copy back”
Case 17 in REP01-06-10.

Replace the copy destination spare drive

according to Work ID = RDK1 “Spare drive
replace” Case 15 in REP01-06-10. Then,
execute copy to the spare drive and replace
the copy source drive according to Work
ID = RDK1 “Copy to Spare drive ~ Drive
replace ~ Copy back” Case 24 in REP01-06-
10. (Copy back is not required.)

END

TRBL03-690
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-700

Is the CM
capacity more than or equal to No
the recommended capacity? (See
INST03-01-20.) Ask the customer to increase the CM capacity to
more than or equal to the recommended capacity.
Yes

Is there a pool-VOL in Yes

the parity group containing the copy source
drive?

No Are CLPR of the pool-VOL

and CLPR of the DP-VOL associated No
with the pool to which the pool-VOL
belongs identical?

Yes
Match CLPR of the pool-VOL and CLPR of
the DP-VOL.

Perform the copy again (replace the dummy of the

copy source).

END

TRBL03-700
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-710

4. In the case of drive copy abnormal termination (in which an unused spare drive is available)
This is a case in which a drive copy terminates abnormally owing to a failure in the copy destination
drive. However, if an unused spare drive exists, the drive copy is automatically performed to the unused
spare drive.
In the following procedure, the copy source is referred to as a copy source, the copy destination is
referred to as the first copy destination, and the unused spare drive is referred to as the second copy
destination.

Drive Drive … Drive Spare drive Unused spare drive

(copy source) (copy destination)
(copy source) (the first copy (the second copy
destination) destination)

TRBL03-710
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-720

START

Is there a SIM
s stating that a copy terminated No
abnormally in the copy source drive? (SIM RC 1
= 463xxx, 4caxxx, 4cbxxx) (TRBL03-730)

Yes
(The copy to the second copy destination drive
terminated abnormally.)

Confirm the drive status. (*1)

Is the copy source drive Yes

blocked?
An automatic correction copy is performed to the
No second copy destination spare drive. (Since this is
an automatic operation, no maintenance operation is
Is the second copy Yes
required.)
destination drive blocked?

No
Go to “START” on page TRBL03-560.
Confirm whether there is a failed track by
means of the Pinned Track Display. (Refer to
MAINTENANCE PC SECTION “5.12.3 Pin Data
Indication”.)

Is there any failed track? No

(See TRBL04-160.)

Yes
Recover the failed track according to the failed track
recovery procedure. (Refer to “4.2.1 Pinned Tracks”.)

Replace the blocked spare drives (the first copy destination

and the second copy destination) according to Work ID =
RDK1 “Spare drive replace” Case 15 in REP01-06-10.

Is the Copy Back Mode set to Yes

“Disable”? (See MPC04-10.)
Do the
No copy source drive
and the target drive (the first copy Yes
destination drive or the second copy
destination drive) have the
same capacity?

No
Execute copy to the spare drive, replace the copy source Execute copy to the spare drive and replace the copy
drive, and execute copy back according to Work ID = source drive according to Work ID = RDK1 “Copy to
RDK1 “Copy to Spare drive ~ Drive replace ~ Copy Spare drive ~ Drive replace ~ Copy back” Case 24 in
back” Case 17 in REP01-06-10. REP01-06-10. (Copy back is not required.)

END
TRBL03-720
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-730

Is there a SIM
stating that a copy terminated No
normally in the copy source drive? (SIM
RC=462xxx, 4c8xxx, 4c9xxx)
Is there a SIM
stating that a copy terminated No
Yes in a warned state in the copy source drive?
(SIM RC=465xxx, 4cexxx,
4cfxxx) (The copy to the second copy
(The copy to the second copy destination drive
terminated normally.) destination drive aborted.)
Yes
(The copy to the second copy destination drive
terminated in a warned state.)

Go to Subsection “3.27.2 In the case Go to Subsection “3.27.3 In the case

of termination with a warning (SIM RC of termination owing to abortion (SIM
= 455xxx, 465xxx, 4bexxx, 4bfxxx, RC = 454xxx, 464xxx, 4bcxxx, 4bdxxx,
4cexxx, 4cfxxx)” 4ccxxx, 4cdxxx)”

Replace the blocked spare drive (the first copy

destination) according to Work ID = RDK1
“Spare drive replace” Case 15 in REP01-06-10.

Is the Copy Back Mode set to No

“Disable”? (See MPC04-10.)

Yes

Do the copy source No

drive and the target drive have the
same capacity?

Yes
Replace the copy source drive according to Replace the copy source drive and execute
Work ID = RDK1 “Drive replace ~ Copy copy back according to Work ID = RDK1
back” Case 19 in REP01-06-10. (Copy back “Drive replace ~ Copy back” Case 1 in
is not required.) REP01-06-10.

END
*1: Confirm the following items.
• Confirm the location of the first copy destination and the second copy destination drives referring
to the copy history. Refer to the copy history log on page MPC05-410.
• Confirm the statuses of the second copy destination and the copy source drives. (Refer to “(1)
HDD detail information view” on MAINTENANCE PC SECTION “[Link] HDD Information
View”.)

TRBL03-730
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-740

3.27.5 Correction access status

The procedure below is that used when one drive in a parity group of RAID 1 or RAID 5 is blocked or when
one or two drives in a parity group of RAID 6 are blocked.

START

Confirm the blocked drive in the

parity group. (Refer to “Status” on
MAINTENANCE PC SECTION
“[Link] HDD Information View”.)

Replace the blocked drive and execute

the self-drive correction copy according
to Work ID = RDK1 “Drive replace ~
Correction copy” Case 4 in REP01-06-10.

END

TRBL03-740
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-750

3.27.6 Parity group blockade

The procedure below is that used when two or more drives in a parity group of RAID 1 or RAID 5 are
blocked or when three or more drives in a parity group of RAID 6 are blocked.
NOTE: Data will be lost when this operation is performed. Contact the Technical Support
Division to confirm the validity of the operation.

START

Do
you want to restore the Yes
blocked Logical Device, such as
backup the data?

No

Replace the blocked drives in the parity group and Go to “START” on

perform the LDEV formatting according to Work Page TRBL03-300.
ID = RDK1 “LDEV formatting after replacing all
the HDDs blocked in a parity group” Case 16 in
REP01-06-10.

END

TRBL03-750
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-760

3.27.7 Preventive maintenance

The procedure below is that used when the drive is not blocked but it must be replaced.

START

Is there any unused Yes

spare drive?

No Is a spare
drive that has the same Yes
capacity as the drive
installed?
Is the
No Copy Back Mode set to Yes
“Disable”? (See MPC04-
10.)
No

Replace the drive concerned and Execute copy to the spare drive, replace Execute copy to the spare drive
execute the self-drive correction the drive concerned, and execute copy and replace the drive concerned
copy according to Work ID = RDK1 back according to Work ID = RDK1 according to Work ID = RDK1 “Copy
“Drive replace ~ Correction copy” “Copy to Spare drive ~ Drive replace ~ to Spare drive ~ Drive replace ~
Case 18 in REP01-06-10. Copy back” Case 17 in REP01-06-10. Copy back” Case 24 in REP01-06-
10. (Copy back is not required.)

END

TRBL03-760
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-770

3.28 SVP Failure Recovery

Table 3-1 List of Solutions to management server Failures
No. Failure Recovery action
1 An alert message of an antivirus • When the installation can be continued, continue the
program is displayed at the time of installation.
SVP installation. • When the installation cannot be continued, stop the
installation, suspend the antivirus program, and then execute
the installation again. If you suspend the antivirus program,
run it again after completing the installation.
2 Management server does not start. • Check that the power cable is inserted into the outlet and the
management server all the way in.
• A failure may have occurred in the OS of the management
server. Connect the display to the management server and
check the status.
• When a USB memory or others are inserted into the
management server, remove them.
3 Nothing can connect to the • Check that the LAN cables are inserted into the network
management server via network. HUB and the LAN ports of the management server all the
way in.
• The network setting of the management server and the LAN
network may be mismatched. Connect the display to the
management server and log in to check the network setting of
the management server.
• Check that the LAN cable is disconnected.
4 Even if accessing Storage Navigator • The port 80/443 setting may be disabled in the Firewall
by the browser, it becomes setting of the management server. Check the Firewall setting
HTTP404. of the management server.
• Storage Navigator takes time to start. Wait for a maximum of
about 10 minutes.
5 Even if accessing Storage Navigator • Another Web server such as IIS may be running in the
by the browser, another page is management server.
displayed.
6 StorageDeviceList cannot start • Check that the remaining storage capacity of the management
server is more than or equal to the recommended capacity to
operate the instance manager of Storage Navigator.
• Check that the memory capacity of the management server is
more than or equal to the recommended capacity to operate
the instance manager of Storage Navigator.
• Check the OS service of the management server and check
that DKCMan is running.
• The folder installing the instance manager of Storage
Navigator may be deleted or the folder name may be changed.
(To be continued)

TRBL03-770
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-780

(Continued from the preceding page)

No. Failure Recovery action
7 The Storage System cannot be • Check that the remaining storage capacity of the management
registered in StorageDeviceList. server is more than or equal to the recommended capacity to
operate Storage Navigator.
• Check that the IP address specified by the Storage
System registration is in the environment accessed by the
management server.
• Check that the user ID/password of GUM specified by the
Storage System registration is correct.
8 An error occurs in the instance • The Drive with the media inserted may have a problem.
update of Storage Navigator
9 Login to Storage Navigator is • Check that the management server is running.
impossible • Check that the instance manager of Storage Navigator is
running.
• Check that the user name and password are correct.
• Check that the Storage System is running.
• Check that the IP address of the Storage System is not
changed.
• When you cannot log in with the correct user name and
password, the problem might be caused by the following
reason. Check whether it is applied.
- The account is disabled by the security administrator.
• When you cannot log in with the correct user name and
password under the condition where the user account policies
are set, the problem might be caused by any of the following
reasons. Check whether they are applied.
- The account is disabled because the password has expired.
- The account is disabled because the number of login
attempts has exceeded the limit.
- The account is locked because the number of login attempts
has exceeded the limit.
- The account is locked or disabled because the number of
login attempts has exceeded the limit due to automatic
authentication such as API authentication.

Consult with the security administrator about the above

matters.
10 Although the storage system status Storage Navigator takes time to start. Wait for a maximum of
on Storage Device List is changed about 10 minutes.
to Ready, Storage Navigator cannot
start.
11 StorageDeviceList shortcut is not on The user operation may have deleted it. Execute wk\
the desk top supervisor\sdlist\ [Link] in the installation folder.
(To be continued)

TRBL03-780
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-781

(Continued from the preceding page)

No. Failure Recovery action
12 The Storage System cannot be Press [Edit] of the Storage System icon on StorageDeviceList.
deleted from StorageDeviceList. Uncheck the checkbox of [Start service automatically, when
the management server is rebooted] and execute [Apply]. After
restarting the management server, the Storage System can be
deleted by restarting StorageDeviceList.
13 The service of the storage system Change the directory settings for antivirus program scan (for
registered on the Storage Device List details, refer to System Administrator Guide). Then, stop the
starts and stops repeatedly. service of the storage system on the Storage Device List and
start it again.
14 The alert message “Close programs Ask the customer to see “Troubleshooting” in “Service
to prevent information loss” is Processor Technical Reference” to solve the problem.
displayed when operating the SVP.

TRBL03-781
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-790

3.28.1 Troubleshooting Storage Navigator

[Link] Troubleshooting Related to Installation and Upgrade
No. Failure Recovery action
1 The installation fails and the message • Operate according to the message that has been displayed in
is displayed. the installer and the recovery action.
• Check the status of the background services of Storage
Navigator to take actions referring to “[Link] Background
Service Log”.
2 The installation success message • Check the status of the background services of Storage
is displayed. However, the Storage Navigator to take actions referring to “[Link] Background
Device List will not run or cannot Service Log”.
register the storage system. • If the collection fails, collect the target files manually.
3 When starting the Update window The electronic certificate for Java applications used in
of Maintenance Utility, “Application maintenance work might be expired.
Blocked by Java Security” or Change the security settings of Java on the Maintenance PC,
“Application Blocked by Security and then retry the operation. After the maintenance work,
Settings” occurs. restore to the original Java security settings. For the procedures
for changing and restoring the Java security settings, see
“11.13 Changing and Restoring the Java Security Settings
When the Java Certificate Is Expired” in MAINTENANCE PC
SECTION.
(To be continued)

TRBL03-790
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-791

(Continued from the preceding page)

No. Failure Recovery action
4 The installation failed by the error 1. Uninstall the Maintenance PC software, then install it again.
[21443-200027], and the error detail (See MAINTENANCE PC SECTION “8.2 Maintenance
code “1060” or “1072” was displayed. PC Software Uninstallation” and “1.4 Maintenance PC
Software Initial Installation/Update Installation”.)
2. If the problem persists, restart the Maintenance PC,
uninstall the Maintenance PC software, then install it again.
3. If the problem is not solved yet, get the following data, and
then contact the Technical Support Division.
• Windows event logs (the System log and the Application
log) of the Maintenance PC (*1)
• Screenshots of the “Services” window of the Maintenance
PC (*2)
• All files in the “C:\SetupTrace” folder

*1: In the Control Panel, select [Administrative Tools]–

[Event Viewer] and display the System log and the
Application log. Then, from the menu of each of them,
select [Action]–[Save All Events As...]. (The operation
might differ depending on the OS type.)
NOTE: For Windows 11, select [Start]-[All Apps]-
[Windows Tools]-[Event Viewer].
*2: In the Control Panel, select [Administrative Tools]–
[Services] to open the “Services” window.(The operation
might differ depending on the OS type.)
Then, take screenshots containing all items while
scrolling the window.
NOTE: For Windows 11, select [Start]-[All Apps]-
[Windows Tools]-[Services].
(To be continued)

TRBL03-791
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-800

(Continued from the preceding page)

No. Failure Recovery action
5 The error [21443-200027] occurs When Event Viewer is running, close Event Viewer, and then
at the time of upgrading the SVP try to update the SVP software again.
software. If the trouble is not solved, check that the process of BackSvc.
exe or [Link] exists by following the procedure
below.
• For Windows 7 and Windows Server 2008 R2
Start Task Manager and check Image Name in the Processes
tab window.
• For Windows 8.1, Windows 10, Windows 11, Windows
Server 2012, Windows Server 2012 R2, Windows Server
2016, Windows Sever 2019, and Windows Server 2022
Start Task Manager and check Name in the Details tab
window.
If such a process exists, run Command Prompt as
Administrator and execute the following:
sc stop HtBack
sc stop HtFront
After executing the above, try to update the SVP software
again. Then, run Command Prompt as Administrator without
fail and execute the following:
sc start HtFront
sc start HtBack
If the trouble is not solved, troubleshoot using DllsCheck.
bat, and then update the SVP software again by referring to
[Link] Checking Duplicated Ports and Using DLL Load
Confirmation Tools .
If the trouble is not solved, check that the process of Astcmd.
exe or [Link] exists by following the procedure below.
• For Windows 7 and Windows Server 2008 R2
Start Task Manager and check Image Name in the Processes
tab window.
• For Windows 8.1, Windows 10, Windows 11, Windows
Server 2012, Windows Server 2012 R2, Windows Server
2016, Windows Sever 2019, and Windows Server 2022
Start Task Manager and check Name in the Details tab
window.
If such a process exists, force stop the process, and then try to
update the SVP software again.
(To be continued)
(To be continued)

TRBL03-800
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-810

(Continued from the preceding page)

No. Failure Recovery action
(Continued from the preceding page)
If the trouble is not solved, check that a process whose image
path name includes the name of the folder in which the storage
management software is installed (example: C\Mapp) exists by
following the procedure below.
• For Windows 7 and Windows Server 2008 R2
Start Task Manager, select [View]-[Select Columns] in the
Processes tab window, put a check on Image path name ,
click the [OK] button, and then check the [Image Path Name]
column.
• For Windows 8.1, Windows 10, Windows 11, Windows
Server 2012, Windows Server 2012 R2, Windows Server
2016, Windows Sever 2019, and Windows Server 2022
Start Task Manage, right-click the display item (example:
name) in the Details tab window, and click [Select Columns].
Then, put a check on Image path name in the column
selection window, click the [OK] button, and then check the
[Image Path Name] column.
If such a process exists, force stop the process, and then try to
update the SVP software again.
6 The error [21542-005024] or [21542- The software installation file might be corrupted.
005040] occurs when the storage When using a file copied from media, the file might not be
system is registered, or when the copied properly. Make sure that the copied file is not different
SVP software is updated. from the copy source, and then perform the operations again.
If this failure still occurs, use the software installation media
directly, and then perform the operations again.
7 The error [21542-005012] occurs Confirm that the requirements shown in MAINTENANCE
when the storage system is PC SECTION Table 1-1 Maintenance PC Specifications are
registered, or when the SVP software satisfied.
is updated. When the requirements are satisfied, some failure might
be occurred temporarily or continuously on the installed
components. Check the event logs and the like to confirm
whether a failure occurs on the installed components, and then
perform the operations again after solving the failure.
(To be continued)

TRBL03-810
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-811

(Continued from the preceding page)

No. Failure Recovery action
8 The error [21443-005017] occurs When Event Viewer is running, close Event Viewer, and then
at the time of removing the storage try to remove the storage management software again.
management software. If the trouble is not solved, check that the process of BackSvc.
exe or [Link] exists by following the procedure
below.
• For Windows 7 and Windows Server 2008 R2
Start Task Manager and check Image Name in the Processes
tab window.
• For Windows 8.1, Windows 10, Windows 11, Windows
Server 2012, Windows Server 2012 R2, Windows Server
2016, Windows Sever 2019, and Windows Server 2022
Start Task Manager and check Name in the Details tab
window.
If such a process exists, run Command Prompt as
Administrator and execute the following:
sc stop HtBack
sc stop HtFront
After executing the above, try to remove the storage
management software again. Then, run Command Prompt as
Administrator without fail and execute the following:
sc start HtFront
sc start HtBack
If the trouble is not solved, check that the process of Astcmd.
exe or [Link] exists by following the procedure below.
• For Windows 7 and Windows Server 2008 R2
Start Task Manager and check Image Name in the Processes
tab window.
• For Windows 8.1, Windows 10, Windows 11, Windows
Server 2012, Windows Server 2012 R2, Windows Server
2016, Windows Sever 2019, and Windows Server 2022
Start Task Manager and check Name in the Details tab
window.
If such a process exists, force stop the process, and then try to
remove the storage management software again.
(To be continued)
(To be continued)

TRBL03-811
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-812

(Continued from the preceding page)

No. Failure Recovery action
(Continued from the preceding page)
If the trouble is not solved, check that a process whose image
path name includes the name of the folder in which the storage
management software is installed (example: C\Mapp) exists by
following the procedure below.
• For Windows 7 and Windows Server 2008 R2
Start Task Manager, select [View]-[Select Columns] in the
Processes tab window, put a check on Image path name ,
click the [OK] button, and then check the [Image Path Name]
column.
• For Windows 8.1, Windows 10, Windows 11, Windows
Server 2012, Windows Server 2012 R2, Windows Server
2016, Windows Sever 2019, and Windows Server 2022
Start Task Manage, right-click the display item (example:
name) in the Details tab window, and click [Select Columns].
Then, put a check on Image path name in the column
selection window, click the [OK] button, and then check the
[Image Path Name] column.
If such a process exists, force stop the process, and then try to
remove the storage management software again.
9 The error (21443-200010) occurred After restarting the Maintenance PC, uninstall the Maintenance
during the installation. PC software, then install it again. (See MAINTENANCE PC
SECTION 8.2 Maintenance PC Software Uninstallation
and 1.4 Maintenance PC Software Initial Installation/Update
Installation .)
10 When the firmware update button • If the version of JRE (Client) on the Maintenance PC is
is clicked, Unable to launch the JRE7, install JRE8 or later.
application. is displayed, and then • Check that the Use TLSv1.2 setting for Java is enabled.
an abnormal end occurs. If the Use TLSv1.2 setting is disabled, perform the TLS
settings as shown in the following procedure.
(1) From the Windows [Start] menu, select [Windows
System Tools]-[Control Panel] to open the control panel.
NOTE: For Windows 11, from the Windows [Start]
menu, select [All Apps]-[Windows Tools]-
[Control Panel].
(2) Click the [Java] icon.
(3) In the Java Control Panel window, open the [Advanced]
tab.
(4) Click [Advanced Security Settings] to confirm that [Use
TLS1.2] is checked, and then click [OK].
(To be continued)

TRBL03-812
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-812A

(Continued from the preceding page)

No. Failure Recovery action
11 The error [21443-200017] occurs This error occurs when services of the storage management
at the time of updating the storage software are not completely stopped. Wait for 10 minutes, and
management software. then retry the update installation.
If the update installation fails again, restart the Maintenance
PC, and then retry the update installation.
If the problem persists, contact the Technical Support Division.
The error [21443-200017] occurs If the current directory of the command prompt is the folder
at the time of removing the storage targeted for deletion, the error occurs when the command
management software or the SVP prompt is open.
software. Restart the Maintenance PC, install the storage management
software and the SVP software, then remove both the software.
Move the current directory of the command prompt to a
location other than the folder where folders targeted for
deletion are stored or close the command prompt. Then, try
to remove the storage management software and the SVP
software again.
When you retry the removal, a message saying that the
Maintenance PC software or the SVP firmware is not installed
might appear. Perform either of the following:
• When you are performing the removal for the purpose of
reinstallation
(1) Delete the installation folder of the Maintenance PC
software and the SVP firmware from the explorer.
(2) Install the Maintenance PC software and the SVP
firmware.
• When you are performing the removal to delete what is
unnecessary
(1) Delete the installation folder of the Maintenance PC
software and the SVP firmware from the explorer.
(2) Install the Maintenance PC software and the SVP
firmware.
(3) Delete the Maintenance PC software and the SVP
firmware.
(To be continued)

TRBL03-812A
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-813

(Continued from the preceding page)

No. Failure Recovery action
12 The error [31862-20001] occurs at • Check the set values of IPv4 Address, Maintenance Port, and
the time of setting the network. Internal Network and make the network settings again.
• If the error [31862-20001] still occurs after you do the above,
the internal network address might be the same as an address
in the upper network. Ask the customer whether they are the
same. If they are the same, change the internal network IP
address (see MAINTENANCE PC SECTION “3.6.1 Network
Setting”).
13 When you start the Update Firmware Release the system lock forcibly and retry firmware update (see
window, the warning window “The MAINTENANCE PC SECTION “3.17 Force Release System
firmware is being updated. (32061- Lock”).
208061, 33361-203116)” or “The Even when the “System Unlocked” status is displayed in the
firmware is being updated. (30162- upper right of the Maintenance Utility window, you can release
205057, 33361-203116)” is displayed the system lock forcibly.
and you cannot update firmware.
14 The (21443-200026) occurred during The port number of the port number key name
the installation. “RestAPIServerStop” might be the same as a port number of
another application.
Perform the steps below to retry the installation.
(1) Check whether the port number of the port number key
name “RestAPIServerStop” is the same as a port number
of another application (see Hitachi Virtual Storage
Platform F/Gx00 User Guide).
(2) If the port numbers are identical, change either of them
(see Hitachi Virtual Storage Platform F/Gx00 User
Guide).
(3) Retry the installation.
(To be continued)

TRBL03-813
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-814

(Continued from the preceding page)

No. Failure Recovery action
15 When you try to open the “Update” Perform the following:
window of Maintenance Utility, 1. Cancel the association with the jnlp file and set it again
the message “Do you want to open (see MAINTENANCE PC SECTION “11.12 Association
or save [Link] of Web Console Launcher with the jnlp file”). Then, try to
from <IP address> ?” is displayed. open the “Update” window again.
The “Update” window cannot be 2. When the tool for setting or cancelling the association with
displayed even if you select [Open]. the jnlp file is not installed, install the SVP software version
83-05-30-x0/xx or later, and then perform Procedure 1.
3. When the “Update” window cannot be displayed in spite of
doing Procedure 1/2, check whether the Maintenance PC
has the free space (minimum buffer capacity) that meets
the required specifications (see MAINTENANCE PC
SECTION “1.1 Specifications for the Maintenance PC”). If
it does not have sufficient free space, reserve the required
space, and then try to open the “Update” window again.
4. When the “Update” window cannot be displayed in spite of
doing the above procedures, send the following information
and files to Technical Support Division.
(1) Free HDD space on the Maintenance PC
(2) Whether a user-assigned area size is specified or not and
the free space
(3) Whether Java other than that included in the MPC
software is installed or not. The Java version and the
installation location if that is true.
(4) Information set for the association with the “jnlp”
extension (result of the following commands in
Command Prompt)
① >assoc .jnlp
② >ftype <file type> (Enter the result of the assoc
command.)
(5) In response to the message “Do you want to open or
save [Link] from <IP address> ?”,
select [Save] to save the file.
(6) Get GUM dump files.
(To be continued)

TRBL03-814
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-815

(Continued from the preceding page)

No. Failure Recovery action
16 When you try to open the “Update” Perform the following:
window of Maintenance Utility, 1. Check whether the Maintenance PC has the free space
the message “Do you want to (minimum buffer capacity) that meets the required
open or save https_<IP Address>_ specifications (see MAINTENANCE PC SECTION “1.1
help_en_GUM_GUM00xx from Requirements for the Maintenance PC”). If it does not have
<IP Address>?” is displayed. sufficient free space, reserve the required space, and then
The “Update” window cannot be try to open the “Update” window again.
displayed even if you select [Open]. 2. When the “Update” window cannot be displayed in spite of
doing Procedure 1, send the following information and files
to Technical Support Division.
(1) Free HDD space on the Maintenance PC
(2) Whether a user-assigned area size is specified or not and
the free space
(3) Whether Java other than that included in the MPC
software is installed or not. The Java version and the
installation location if that is true.
(4) Information set for the association with the “jnlp”
extension (result of the following commands in
Command Prompt)
① >assoc .jnlp
② >ftype <file type> (Enter the result of the assoc
command.)
(5) In response to the message “Do you want to open or
save https_<IP Address>_help_en_GUM_GUM00xx
from <IP Address>?”, select [Save] to save the file.
(6) Get GUM dump files.
17 The error [21443-200051] occurs Confirm the following on the Maintenance PC, and then try to
at the time of updating the storage update the storage management software again.
management software. • Confirm that neither a secondary window of Web Console nor
Initial Startup Tool is running. When either of the programs is
running, close the window of the program.

TRBL03-815
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-820

[Link] Troubleshooting Related to the Initial Setting Command of the SVP

No. Failure Recovery action
1 The initial setting command was • Follow the message and coping method displayed by the
executed but failed, and a message initial setting command.
was displayed.
2 The initial setting is completed • Check the status of the background services of Storage
normally but Storage Device List Navigator to take actions referring to “[Link] Background
does not start or the Storage System Service Log”.
cannot be registered. • Gather dump files (See MAINTENANCE PC SECTION “5.2
Dump”.).
If it fails, gather the files manually.

TRBL03-820
Hitachi Proprietary DW850/DW900/DW1000
Rev.7 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-830

[Link] Storage Device List Troubleshooting

Refer to “<Installation Directory of MPC>\wk\supervisor\sdlist\help\sdl_message.html” for the messages that
are not described in the following table.

No. Message ID Failure Recovery action

1 21542-005003 [Apply] was clicked in the “Add If you have entered an IP address, enter a
System” window but the “(21542- different IP address.
005003) error” has occurred and If you have entered a host name, its IP address
Storage System icons cannot be resolved by the DNS server is duplicate.
created. Check the settings on the DNS server.
2 After clicking [Apply] in the “Edit
System” window, the “(21542-
005003) error” occurs and the SVP
software update is not performed.
3 21542-005011 [Apply] was clicked in the “Add The Drive capacity necessary for creating
System” window but the “(21542- Storage System icons is insufficient. Secure free
005011) error” has occurred and capacity of 20 GB or more in the Drive of the
Storage System icons cannot be installation directory.
created.
4 21542-005012 After clicking [Apply] in the “Add Confirm that the requirements shown in
System” window, the “(21542- MAINTENANCE PC SECTION “Table 1-1
005012) error” occurs and the Maintenance PC Specifications” are satisfied.
Storage System icons cannot be When the requirements are satisfied, some
created. failure might be occurred temporarily or
5 After clicking [Apply] in the “Edit continuously on the installed components. Check
System” window, the “(21542- the event logs and the like to confirm whether a
005012) error” occurs and the SVP failure occurs on the installed components, and
software update is not performed. then perform the operations again after solving
the failure.

6 21542-005019 [Start Services] was clicked but the Two or more services cannot start at the same
“(21542-005019) error” message time. Stop the running services.
has occurred and the services
cannot start.
7 21542-005024 After clicking [Apply] in the “Add The software installation file might be corrupted.
System” window, the “(21542- When using a file copied from media, the file
005024) error” occurs and the might not be copied properly. Make sure that the
Storage System icons cannot be copied file is not different from the copy source,
created. and then perform the operations again. If this
8 After clicking [Apply] in the “Edit failure still occurs, use the software installation
System” window, the “(21542- media directly, and then perform the operations
005024) error” occurs and the SVP again.
software update is not performed.
(To be continued)

TRBL03-830
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-840

(Continued from the preceding page)

No. Message ID Failure Recovery action
9 21542-005026 [Start Services] was clicked but Invalid values are set for the IP addresses of the
the (21542-005026) error has Maintenance PC.
occurred and the services cannot 1. Click [MPC IP Address] on the upper right
start. of the [Storage Device List] window and set
10 [Error] was displayed in the IP addresses of the Maintenance PC from
Storage System icon when [Change MPC IP Address].
restarting the Maintenance PC in 2. Click [Start Service] again.
the status where [Start Service] of
the Storage System icon is Auto.
Clicking [Error] displayed the
(21542-005026) error in Status
of BASE.
11 21542-005028 After clicking [Stop Service], the After confirming the following conditions, retry
warning 21542-005028 occurred. the operation.
• All setting windows of Storage Navigator are
closed.
• A maintenance person is not operating the
storage system.
If the above conditions are not met, restart the
Maintenance PC, and then retry the operation.
If the same message is still displayed, force
release the system lock (see MAINTENANCE
PC SECTION 3.17 Force Release System
Lock ).
12 21542-005033 Clicking [Start Service] occurred Ignore the warning when you do not perform the
(21542-005033) Warning. New Installation procedure.
13 Restarting the Maintenance PC in When you perform the New Installation
the status where [Starting Service] procedure, set up the IIS/FTP server again (see
of the Storage System icon is MAINTENANCE PC SECTION 1.3.8 IIS/FTP
Auto displayed [Warning] in the Server Setup ).
Storage System icon. If (21542-005033) Warning does not disappear
Clicking [Warning] displayed after you install IIS/FTP, uninstall IIS/FTP, and
(21542-005033) Warning in then install IIS/FTP again (see MAINTENANCE
Status of BASE. PC SECTION 1.3.10 Uninstalling IIS/FTP ).
14 21542-005037 [Start Services] was clicked but The SVP might not have sufficient memory.
the (21542-005037) error has Install sufficient memory to satisfy the Hardware
occurred and the services cannot requirements (see System Administrator Guide).
start.
(To be continued)

TRBL03-840
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-850

(Continued from the preceding page)

No. Message ID Failure Recovery action
15 21542-005040 After clicking [Apply] in the Add The software installation file might be corrupted.
System window, the (21542- When using a file copied from media, the file
005040) error occurs and the might not be copied properly. Make sure that the
Storage System icons cannot be copied file is not different from the copy source,
created. and then perform the operations again. If this
16 After clicking [Apply] in the Edit failure still occurs, use the software installation
System window, the (21542- media directly, and then perform the operations
005040) error occurs and the SVP again.
software update is not performed.
17 21542-005050 After clicking [Apply] in the Add Storage system registration failed because
System window, the (21542- OSS required for it was not installed. This
005050) error occurs and the problem might occur when the already installed
Maintenance PC software version and the
Storage System icons cannot be
installation media used for storage system
created. registration are as follows.

<Already installed Maintenance PC software

version>
One of the following versions:
• 83-05-55-00/00 or later
• 88-08-15-00/00 or later
• 93-06-85-00/00 or later in the case of the
version starting with 93-06-
• 93-07-22-00/00 or later in the case of the
version starting with 93-07-
• Version starting with A3

<Installation media used for storage system

registration>
One of the following versions:
• 83-05-54-x0/xx or less
• 88-08-14-x0/xx or less
• 93-06-84-x0/xx or less in the case of the
version starting with 93-06-
• 93-07-21-x0/xx or less in the case of the
version starting with 93-07-

Check the version of the already installed

Maintenance PC software and use either of the
following recovery methods according to the
installed version.
<Already installed Maintenance PC software
version>
• Version starting with 83
• Version starting with 88
• Version starting with 93
(To be continued)
(To be continued)

TRBL03-850
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-851

(Continued from the preceding page)

No. Message ID Failure Recovery action
(Continued from the preceding page)
[Recovery method when the already installed
Maintenance PC software version starts with 83,
88, or 93]
Perform one of the following solutions:
• Perform the update installation and storage
system registration with the installation media
that you used for storage system registration.
• Uninstall the Maintenance PC software. Then,
perform the initial installation and storage
system registration with the installation media
that you used for storage system registration.
• Perform storage system registration with one of
the following installation media versions.
<Installation media used for storage system
registration>
For VSP G200, G400, G600, G800, F400,
F600, F800:
• Version 83-05-55-x0/00 or later
For VSP G130, G350, G370, G700, G900, VSP
F350, F370, F700, F900:
• Version 88-08-15-x0/00 or later
For VSP E590, E790, E990, E1090:
• 93-06-85-x0/00 or later in the case of the
version starting with 93-06-
• 93-07-22-x0/00 or later in the case of the
version starting with 93-07-

<Already installed Maintenance PC software

version>
• Version starting with A3
(To be continued)
(To be continued)

TRBL03-851
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-852

(Continued from the preceding page)

No. Message ID Failure Recovery action
(Continued from the preceding page)
[Recovery method when the already installed
Maintenance PC software version starts with A3]
Perform one of the following solutions:
• Uninstall the Maintenance PC software. Then,
perform the initial installation and storage
system registration with the installation media
that you used for storage system registration.
• Perform storage system registration with one of
the following installation media versions.
<Installation media used for storage system
registration>
For VSP G200, G400, G600, G800, F400,
F600, F800:
• Version 83-05-55-x0/00 or later
For VSP G130, G350, G370, G700, G900, VSP
F350, F370, F700, F900:
• Version 88-08-15-x0/00 or later
For VSP E590, E790, E990, E1090:
• 93-06-85-x0/00 or later in the case of the
version starting with 93-06-
• 93-07-22-x0/00 or later in the case of the
version starting with 93-07-
18 21542-008001 [Warning] was displayed in the Processing time-out has occurred in the service
Storage System icon. in which the error code shown on the left has
Clicking [Warning] displayed occurred.
21542-008001 in Status. • If it occurs repeatedly, refer to the [Link]
Background Service Log and perform the
relevant coping method.
• If the background service log does not exist
or the phenomenon does not improve despite
the copying method was performed, stop the
service or reboot the Maintenance PC.
19 21542-008002 [Warning] (or [Error]) was An error has occurred in the service in which the
displayed in the Storage System error code shown on the left has occurred.
icon. • Refer to the [Link] Background Service
Clicking [Warning] (or [Error]) Log and perform the relevant coping method.
displayed 21542-008002 in • If the background service log does not exist
Status. or the phenomenon does not improve despite
the copying method was performed, stop the
service or reboot the Maintenance PC.
20 21041-006002 When clicking the Storage System, The default browser is not set. Set the default
the (21041-006002) error has browser (or a specified browser) by the installed
occurred and Storage Navigator browser setting, and then execute it again.
does not start.
(To be continued)

TRBL03-852
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-860

(Continued from the preceding page)

No. Message ID Failure Recovery action
21 21041-006004 After clicking [Apply] in the Add Perform the following, and then retry the
System window, the (21041- operation.
006004) error occurs and the • Ensure that the Maintenance PC drive on which
Storage System icons cannot be the Storage Device List is installed has at least
created. 20 GB of free space.
• Ensure that any antivirus programs (including
Windows Defender) are not activated.
• If you are operating the Storage Device List
that was copied from the installation media to
the Maintenance PC, copy it again from the
installation media.
• Ensure that the installation drive on the
Maintenance PC does not have a problem such
as a physical damage or access error.
22 21041-006005 At the time of starting The communication with the Supervisor service
StorageDeviceList, the (21041- (DKCMan/MAPPAppServer/MAPPWebServer)
006005) error has occurred and it has failed.
failed to start. • Troubleshoot using [Link] by referring
to [Link] Checking Duplicated Ports and
Using DLL Load Confirmation Tools .
• Select [Control Panel] - [System and Security]
- [Administrative Tools] - [Services] from
the Windows start menu, and confirm the
status of DKCMan, MAPPAppServer and
MAPPWebServer is Started . And then
it is restarting Storage Device List as an
Administrator.
NOTE: For Windows 11, select [Start]-[All
Apps]-[Windows Tools]-[Services].
• If the status is not Start, right-click the
service name to execute [Start] or change [Type
of Start-up] to [Automatic] from [Property] and
restart the Maintenance PC.
23 Startup of the Storage Device List If you are performing an operation that requires
fails with the (21041 006005) a restart of a service used by the SVP, there is no
error. problem. Wait until the operation is complete.
After you confirm that the operation is complete
successfully, click the [Close] button. If you
are not performing an operation that requires a
restart of a service used by the SVP, perform the
recovery action for No.21.
(To be continued)

TRBL03-860
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-861

(Continued from the preceding page)

No. Message ID Failure Recovery action
24 21041-007006 After clicking [Apply] in the Add The SVP and the storage system are not
21041-007008 System window, the (21041- connected. Check the following:
007006) error or (21041-007008) • Whether the storage system is powered on
error occurred. • Whether the management LAN works normally
• Whether the IP address or host name of the
CTL1 and CTL2 are correct
If you want to create an icon of a storage system
when the storage system that is powered on is
not connected to the management LAN, select
[Manual] and fill in the necessary items.
25 21041-007018 The error 21041-007018 occurred You might not have started Storage Device List
when you clicked [Edit], and you as an administrator.
cannot modify the storage system • Exit Storage Device List, and then start it as an
information. administrator.
• If the error persists even after you start Storage
Device List as an administrator, reboot the
SVP and start Storage Device List as an
administrator again.
21041-007019 The error 21041-007019 occurred You might not have started Storage Device List
when you clicked [Start Service] or as an administrator.
[Stop Service]. • Exit Storage Device List, and then start it as an
26 You cannot remove a storage administrator.
system from Storage Device List. • If the error persists even after you start Storage
Device List as an administrator, reboot the
SVP and start Storage Device List as an
administrator again.
27 21513-008004 [Warning] was displayed in the The other Maintenance PC already connected to
Storage System icon. the storage system to be used.
Clicking [Warning] displayed Stop the services of the storage system running
21513-008004 in Status. on the PC of the IP address described in the
troubleshooting code TRCOMM000004 of the
[Link] Background Service Log .
28 21513-008005 [Warning] was displayed in the The IP address for each CTL set in the Add
Storage System icon. System window and that set for GUM are not
Clicking [Warning] displayed identical.
21513-008005 in Status. Correct the IP address setting for each CTL in
the Storage Device List.
(To be continued)

TRBL03-861
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-862

(Continued from the preceding page)

No. Message ID Failure Recovery action
29 21513-008006 [Warning] was displayed in the The storage system model set in the Add System
Storage System icon. window and the storage system model set for the
Clicking [Warning] displayed storage system are not identical.
21513-008006 in Status. Delete the storage system from the Storage
Device List once and register it again with the
correct storage system model.
30 21513-008007 [Warning] was displayed in the The Config model set in the Add System window
Storage System icon. and the Config model installed in the storage
Clicking [Warning] displayed system are not identical.
21513-008007 in Status. Delete the storage system from the Storage
Device List once and register it again with the
correct Config model.
31 21513-008008 [Warning] was displayed in the The serial number set in the Add System window
Storage System icon. and the serial number set in the storage system
Clicking [Warning] displayed are not identical.
21513-008008 in Status. Delete the storage system from the Storage
Device List once and register it again with the
correct serial number.
32 21513-008009 [Warning] was displayed in the The user name and the password set in Add
Storage System icon. System window might be incorrect.
Clicking [Warning] displayed Set the user name and the password in the
21513-008009 in Status. Storage Device List again.
33 21513-008011 [Warning] was displayed in the The information update failed.
Storage System icon. It is updated again automatically. However, if
Clicking [Warning] displayed the message does not disappear after waiting
21513-008011 in Status. for about five minutes, select the corresponding
storage system from the Storage Device List.
Stop the system, and then restart it.
If the failure does not recover, restart the
Maintenance PC.
34 21513-008012 [Warning] was displayed in the • The other Maintenance PC might already
Storage System icon. connect to the storage system to be used.
Clicking [Warning] displayed • Check whether a PC starting the services of
21513-008012 in Status. the other storage system exists for the storage
system to be used. If an Maintenance PC
already started the services of the storage
system, stop the services.
35 The login window of Storage You might not have started Storage Device List
Navigator cannot be opened by as an administrator.
clicking a storage system on the • Exit Storage Device List, and then start it as an
Storage Device List window. administrator.
• If the error persists even after you start Storage
Device List as an administrator, reboot the
SVP and start Storage Device List as an
administrator again.
TRBL03-862
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-870

[Link] Troubleshooting of Storage Navigator other than the Above-Mentioned

No. Failure Recovery action
1 Some errors have occurred during • Check the status of the background services of Storage
the operation after succeeding at the Navigator to take actions referring to [Link] Background
Storage System registration. Service Log.
• Gather dump files (See MAINTENANCE PC SECTION 5.2
Dump.).
If it fails, gather the files manually.
2 Storage Navigator runs slowly. • Check whether the SVP meets the specifications described in
Service Processor Technical Reference .
• Check whether the antivirus program runs on the SVP (see
Service Processor Technical Reference ).
• Check whether defragmentation is running on the SVP (see
Service Processor Technical Reference ).

TRBL03-870
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-880

[Link] Background Service Log

Output the logs of the background services that operate the Maintenance PC.
See the background service logs
• Checking that the Maintenance PC has started normally
• Coping method cannot be specified only by the message output from the user interface.

The background service logs are stored in the following directory.

<installDir>\wk\supervisor\system\log

The log files are stored with the following names.

Log File Type Log File Name
Storage Device List log system_<Sequential Number>.log
Storage Navigator log system_<Serial Number>_<Sequential Number>.log

NOTE: installDir ... indicates an installation directory of the Maintenance PC

(e.g. C: \Mapp) <Sequential Number> ... A sequential number of a log file is given
beginning with 0.

The background services include the following.

• List of background services of Storage Device List
Storage Device List Background Service Service Name
Storage Device List Server SDLSrv
SVP RMI- API Forward Server RMI-API Forward Server
Web Application Server Web Application Server

• List of background services of Storage Navigator

Storage Navigator List Background Service Service Name
Web Application Server Web Application Server
Storage Navigator Server Storage Navigator
SVP RMI- API Server RMI-API Server
External authentication relay service External Authenticator
Communication service Communication
KMIP Communicator KMIP Communicator

TRBL03-880
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-890

The output format of logs is shown below.

[Occurrence Date and Time] [Failure Level] [Troubleshooting Code] [Service Name] [Log Content]

Item Description
Occurrence Date and Time Date and time is output in the following format.
YYYY/MM/DD hh:mm:[Link]
Failure level The following failure levels are output.
INFO ... Reference information (start, termination log and others)
WARN ... Warning information
(Setting values or others are insufficient and operating in the default status.)
ERROR ... It cannot start due to an error.
Troubleshooting Code Troubleshooting codes are output.
Service Name Service Names are output.
Log Content Message are output.

The following logs are output in respective background services.

You can check with these logs that the initialization processing of each background service is completed
normally and it has started or any errors have occurred while running the service.

[2015/01/01 [Link].000][INFO][TRSTRN00001][STRN][Initialize Start]

[2015/01/01 [Link].000][INFO][TRSTRN00002][STRN][Initialize Normal end]
[2015/01/01 [Link].000][WARN][TRSTRN01000][STRN][…]
[2015/01/01 [Link].000][INFO][TRSTRN00001][STRN][Terminate Start]

Troubleshooting codes and coping methods of respective background services are described below.

TRBL03-890
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-900

• Storage Device List server

Example of log output when it is normal:
[2015/03/18 [Link].372][INFO ] [TRSDLS000001] [SDLSrv] [Initialize Start.]
• • •
[2015/03/18 [Link].009][INFO ] [TRSDLS000002] [SDLSrv] [Initialize Normal end.]

Example of log output when it is abnormal:

[2015/03/19 [Link].551][INFO ] [TRSDLS000006] [SDLSrv] [Terminate Start.]
[2015/03/19 [Link].934][ERROR] [TRSDLS000011] [SDLSrv] [System is locked (SN:400001).]
[2015/03/19 [Link].216][ERROR] [TRSDLS000008] [SDLSrv] [Terminate Error end.]

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRSDLS000001 INFO The initialization processing of the Storage Device List server
started. Check that TRSDLS000002 is output and the initialization
processing is completed normally.
TRSDLS000002 INFO The initialization processing of the Storage Device List server
was completed normally.
TRSDLS000003 ERROR The initialization processing of the Storage Device List server
terminated in error. Refer to the troubleshooting codes output
before and after this log and perform the corresponding coping
method.
1. If no other error log is output, restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRSDLS000004 ERROR The port displayed on the log is unusable. Check whether an
application using the port exists.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible,
and restart the Maintenance PC.
If it cannot change, see MAINTENANCE PC SECTION “10.1
Changing Port Numbers Used by the Maintenance PC” and
change the port number of “DKCManPrivate”.
(To be continued)

TRBL03-900
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-910

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRSDLS000005 ERROR The initialization processing of the Storage Device List server
timed out.
Execute the following procedure to start the Storage Device
List server. If the result does not change despite the operation is
repeated, restart the Maintenance PC.
If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install it again.
After that, register the storage system. (See MAINTENANCE PC
SECTION “8.2 Maintenance PC Software Uninstallation”, “1.4
Maintenance PC Software Initial Installation/Update Installation”,
and “2.4 Registering Storage Systems to Be Maintained in Storage
Device List”.)
1. Select [Control Panel] - [System and Security] - [Management
Tool] - [Services] of Windows. (*1)
NOTE: For Windows 11, select [Start]-[All Apps]-[Windows
Tools]-[Services].
2. Select DKCMan from the list and select [Start Services].
TRSDLS000006 INFO The stop processing of the Storage Device List server started.
Check that TRSDLS0000007 is output and the stop processing is
completed normally.
TRSDLS000007 INFO The stop processing of the Storage Device List server was
completed normally.
TRSDLS000008 ERROR The stop processing of the Storage Device List server terminated
in error.
Refer to the troubleshooting codes output before and after this log
and perform the corresponding coping method.
If no other error log is output, execute the following procedure for
stopping the Storage Device List server.
1. Select [Control Panel] - [System and Security] - [Management
Tool] - [Services] of Windows.(*1)
NOTE: For Windows 11, select [Start]-[All Apps]-[Windows
Tools]-[Services].
2. Display the DKCMan property and set [Type of Start-up] of
the [General] tab to [Manual].
3. Reboot the Maintenance PC.
TRSDLS000009 ERROR The Storage Device List server cannot stop because the
environment construction processing of the Maintenance PC is in
execution. Operate it again after a while.
(To be continued)

TRBL03-910
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-920

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRSDLS000010 ERROR The Storage System with the serial number (SN) displayed on the
log does not support the service stop processing.
Execute the following procedure for stopping the Storage Device
List server.
1. Select [Control Panel] - [System and Security] - [Management
Tool] - [Services] of Windows.(*1)
NOTE: For Windows 11, select [Start]-[All Apps]-[Windows
Tools]-[Services].
2. Display the DKCMan property and set [Type of Start-up] of
the [General] tab to [Manual].
3. Reboot the Maintenance PC.
TRSDLS000011 ERROR The system with the serial number (SN) displayed on the log
cannot stop the service because another user acquired the lock.
Release the lock acquired by another user, and then operate it
again.
TRSDLS000012 ERROR The stop processing of the Storage Device List server timed out.
If it occurs repeatedly, stop the Storage Device List server in the
following procedure.
1. Select [Control Panel] - [System and Security] - [Management
Tool] - [Services] of Windows.
NOTE: For Windows 11, select [Start]-[All Apps]-[Windows
Tools]-[Services].
When the user account control of Windows started, select
[Continue].
2. Display the DKCMan property and set [Type of Start-up] of
the [General] tab to [Manual].
3. Reboot the Maintenance PC.
TRSDLS000013 WARN Service status acquisition failed.
If warning does not disappear even after waiting for three minutes,
perform the following procedure.
1. Stop this Storage System by Storage Device List and restart it.
2. If not recovered, restart the Maintenance PC.
3. If the problem persists, uninstall the Maintenance PC software,
then install it again. After that, register the storage system.
(See MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)

TRBL03-920
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-930

• SVP RMI- API Forward Server

Example of log output when it is normal:
An example of output when it started normally and terminated is shown below.
[2015/03/17 [Link].638][INFO ][TRRMIS002001][RMI-API Forward Server][Initialize Start.]
[2015/03/17 [Link].544][INFO ][TRRMIS002002][RMI-API Forward Server][Initialize Normal end.]
[2015/03/17 [Link].982][INFO ][TRRMIS002012][RMI-API Forward Server][Terminate Start.]
[2015/03/17 [Link].003][INFO ][TRRMIS002013][RMI-API Forward Server][Terminate Normal end.]

Example of log output when it is abnormal:

An example of output when it has occurred abnormally is shown below.
[2015/03/17 [Link].638][INFO ][TRRMIS002001][RMI-API Forward Server][Initialize Start.]
[2015/03/17 [Link].001][ERROR][TRRMIS002005][RMI-API Forward Server][Environment is unjust.]
[2015/03/17 [Link].102][INFO ][TRRMIS002004][RMI-API Forward Server][Initialize Error end.]

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRRMIS002001 INFO This is output when the RMI - API Forward Server service starts.
To confirm that the RMI - API Forward Server service has started
normally, match it to the log and check that TRRMIS002002 is
output.
TRRMIS002002 INFO This is output when the start of the RMI - API Forward Server
service is completed normally.
TRRMIS002003 WARN The RMI - API Forward Server service succeeded to start but a
warning has occurred in the processing. Check the troubleshooting
codes output through TRRMIS002001 and the log and take
actions.
TRRMIS002004 ERROR The RMI - API Forward Server service failed to start.
Check the troubleshooting codes output through TRRMIS002001
and the log and take actions.
TRRMIS002005 ERROR Acquiring the environment setting information necessary for
TRRMIS002006 ERROR starting the RMI - API Forward Server service has failed.
TRRMIS002007 WARN 1. Restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-930
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-940

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS002008 WARN The ports numbers necessary for the RMI - API Forward Server
service are unusable.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If it cannot change, see MAINTENANCE PC SECTION “10.1
Changing Port Numbers Used by the Maintenance PC” and
change the port number of “RMIIFRegist”.
TRRMIS002009 WARN The ports numbers necessary for the RMI - API Forward Server
service are unusable.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If it cannot change, see MAINTENANCE PC SECTION “10.1
Changing Port Numbers Used by the Maintenance PC” and
change the port number of “DKCManPrivate”.
TRRMIS002010 WARN This is the similar to the coping method of TRRMIS002008.
Refer to the coping method of TRRMIS002008.
TRRMIS002011 WARN This is the similar to the coping method of TRRMIS002009.
Refer to the coping method of TRRMIS002009.
TRRMIS002012 INFO This is output when the RMI - API Forward Server service stops.
To confirm that the RMI - API Forward Server service is stopped
normally, match it to the log and check that TRRMIS002013 is
output.
TRRMIS002013 INFO This is output when the RMI - API Forward Server service is
stopped normally.

TRBL03-940
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-950

• Web Application Server

Example of log output when it is normal:
An example of output when it started normally and terminated is shown below.
[2015/12/02 [Link].113][INFO ][TRMAAS000001][Web Application Server][Initializing]
[2015/12/02 [Link].410][INFO ][TRMAAS000002][Web Application Server][Ready]

Example of log output when it is abnormal:

An example of output when it has occurred abnormally is shown below.
[2015/12/03 [Link].020][INFO ][TRMAAS000001][Web Application Server][Initializing]
[2015/12/03 [Link].004][ERROR][TRMAAS000004][Web Application Server][Failed : Failed to
connect to the starting port of the web server. Port=8080.]
[2015/12/03 [Link].174][INFO ][TRMAAS000007][Web Application Server][Stopped]

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRMAAS000001 INFO This is output when the Web application server starts.
To check whether the Web application server is running normally,
check whether this troubleshooting code and TRMAAS000002
are output.
TRMAAS000002 INFO This is output when the Web application server started completely.
TRMAAS000003 WARN The ports numbers necessary for the Web application server
service cannot be used.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different
application. Change the port number of the application if possible,
and restart the Maintenance PC.
If they cannot be changed, change the port numbers used in other
applications among “MAPPWebServer”, “MAPPWebServerHttps”,
“RMIClassLoader” and “RMIClassLoaderHttps”. For the
operation of changing the port numbers, see MAINTENANCE
PC SECTION “10.1 Changing Port Numbers Used by the
Maintenance PC”.
TRMAAS000004 ERROR The ports numbers necessary for the Web application server
service cannot be used.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If they cannot be changed, see MAINTENANCE PC SECTION
“10.1 Changing Port Numbers Used by the Maintenance PC” and
change the port numbers of “CommonJettyStart”.
(To be continued)
TRBL03-950
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-960

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRMAAS000005 ERROR The ports numbers necessary for the Web application server
service cannot be used.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If they cannot be changed, see MAINTENANCE PC SECTION
“10.1 Changing Port Numbers Used by the Maintenance PC” and
change the port numbers of “CommonJettyStop”.
TRMAAS000006 INFO This is output when the Web application server stops.
To check whether the Web application server stopped normally,
check whether this troubleshooting code and TRMAAS000007
are output.
TRMAAS000007 INFO This is output when the Web application server stopped normally
and completely.

TRBL03-960
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-970

• Storage Navigator Server

Example of log output when it is normal
 At the time of start-up:
[2015/03/19 [Link].046][INFO ][TRSTNA000001][Web Application Server][Initializing]
[2015/03/19 [Link].592][INFO ][TRSTNA000002][Web Application Server][Ready]
[2015/03/19 [Link].903][INFO ][TRSTNA001001][Storage Navigator][Initializing]
[2015/03/19 [Link].387][INFO ][TRSTNA001002][Storage Navigator][Ready]
 At the time of termination:
[2015/03/19 [Link].942][INFO ][TRSTNA000004][Web Application Server][Stopping]
[2015/03/19 [Link].478][INFO ][TRSTNA001004][Storage Navigator][Stopping]
[2015/03/19 [Link].859][INFO ][TRSTNA001005][Storage Navigator][Stopped]
[2015/03/19 [Link].209][INFO ][TRSTNA000005][Web Application Server][Stopped]

Example of log output when it is abnormal

 At the time of start-up:
[2015/03/20 [Link].543][INFO ][TRSTNA000001][Web Application Server][Initializing]
[2015/03/20 [Link].364][ERROR][TRSTNA000003][Web Application Server][Failed : Failed to start a
Storage Navigator.]
 At the time of termination:
[2015/03/20 [Link].175][INFO ][TRSTNA000004][Web Application Server][Stopping]
[2015/03/20 [Link].931][INFO ][TRSTNA001004][Storage Navigator][Stopping]
[2015/03/20 [Link].634][WARN ][TRSTNA001006][Storage Navigator][Stopping : Timeout has
occurred in the stop processing of a Storage Navigator.]
[2015/03/20 [Link].114][INFO ][TRSTNA000005][Web Application Server][Stopped]
[2015/03/20 [Link].652][INFO ][TRSTNA001005][Storage Navigator][Stopped]

TRBL03-970
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-980

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRSTNA000001 INFO This is output when the Web Application Server starts up.
To confirm that the Web Application Server has started
normally, match it to the troubleshooting code and check that
TRSTNA000002 is output.
TRSTNA000002 INFO This is output when the start of the Web Application Server is
completed.
TRSTNA000003 ERROR The Web Application Server has failed to start.
1. Select the relevant Storage System from the Storage Device
List, stop it, and then restart it.
2. If not recover, restart the Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRSTNA000004 INFO This is output when the Web Application Server stops.
TRSTNA000005 INFO An error occurred by stopping the Web Application Server.
TRSTNA000006 ERROR 1. Restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-980
Hitachi Proprietary DW850/DW900/DW1000
Rev.10.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-981

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRSTNA000007 WARN The Storage Navigator service stopped unexpectedly, and then it
is restarting.
1. If the phenomenon does not change even after waiting for
three minutes, perform Stop Service, and then Start Service to
restart the service for the target Storage System.
2. If not recovered, restart the Maintenance PC.
3. If the problem persists, stop the service for the Storage
System registered in Storage Device List and perform the
update installation of the Maintenance PC software according
to MAINTENANCE PC SECTION “1.4 Maintenance PC
Software Initial Installation/Update Installation”.
4. If the problem persists, set the virtual memory according
to MAINTENANCE PC SECTION “1.3.9 Setting Virtual
Memory” and restart the Maintenance PC.
5. If the problem persists, uninstall Storage Navigator and
then install it and register the Storage System again. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRSTNA000008 ERROR 1. See MAINTENANCE PC SECTION “10.5 Changing Range
of Port Numbers to be Allocated Automatically” to change the
port number range of “DeviceJettyStart” to the unused range.
2. Restart the Maintenance PC after the change.
TRSTNA000009 ERROR 1. See MAINTENANCE PC SECTION “10.5 Changing Range
of Port Numbers to be Allocated Automatically” to change the
port number range of “DeviceJettyStop” to the unused range.
2. Restart the Maintenance PC after the change.
(To be continued)

TRBL03-981
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-990

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRSTNA000010 ERROR The Web application server is stopped forcibly.
TRSTNA000011 ERROR This might be output when Maintenance PC restarts while the
server is running.
1. Select the relevant Storage System from the Storage Device
List, stop it, and then restart it.
2. If not recover, restart the Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRSTNA001001 INFO This is output when the Storage Navigator starts.
To check whether the Storage Navigator service is starting
normally, confirm that this log and TRSTNA001002 are output.
TRSTNA001002 INFO The Storage Navigator service is starting normally.
TRSTNA001003 WARN This troubleshooting code might be output while the service of
Storage Navigator is being started. After TRSTNA001001 is
output, wait for a while (up to 10 minutes). If TRSTNA001002
is not output after 10 minutes, check whether the required setup
is complete by referring to System Administrator Guide, and
complete it if not finished. Then, in the Storage Device List
window, stop the service of the storage system and restart it.
TRSTNA001004 INFO This is output when the Storage Navigator service stops.
To check whether the Storage Navigator service stopped normally,
check whether this troubleshooting code and TRSTNA001005 are
output.
TRSTNA001005 INFO This is output when the Storage Navigator service is stopped
completely.
TRSTNA001006 WARN A time-out has occurred when stopping the Storage Navigator
service.
1. If it does not become start completion (TRSTNA001002) at
the next start time, restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-990
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-991

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRSTNA001007 ERROR The Storage Navigator service stopped forcibly.
TRSTNA001008 ERROR This might be output when Maintenance PC restarts while the
service is running.
1. Stop the storage system by Storage Device List and restart it.
2. If not recovered, restart the Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)

TRBL03-991
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1000

• SVP RMI- API Server

Example of log output when it is normal:
An example of output when it started normally and terminated is shown below.
[2015/03/17 [Link].750][INFO ][TRRMIS001001][RMI-API Server][Initialize Start.]
[2015/03/17 [Link].000][INFO ][TRRMIS001002][RMI-API Server][Initialize Normal end.]
[2015/03/17 [Link].638][INFO ][TRRMIS002501][RMI-API Server][Initialize Start.]
[2015/03/17 [Link].544][INFO ][TRRMIS002502][RMI-API Server][Initialize Normal end.]
[2015/03/17 [Link].405][INFO ][TRRMIS000001][RMI-API Server][Initialize Start.]
[2015/03/17 [Link].364][INFO ][TRRMIS000002][RMI-API Server][Initialize Normal end.]
• • •
[2015/03/17 [Link].982][INFO ][TRRMIS002510][RMI-API Server][Terminate Start.]
[2015/03/17 [Link].003][INFO ][TRRMIS002511][RMI-API Server][Terminate Normal end.]
[2015/03/17 [Link].645][INFO ][TRRMIS001006][RMI-API Server][Terminate Start.]
[2015/03/17 [Link].927][INFO ][TRRMIS000015][RMI-API Server][Terminate Start.]
[2015/03/17 [Link].249][INFO ][TRRMIS000016][RMI-API Server][Terminate Normal end.]
[2015/03/17 [Link].695][INFO ][TRRMIS001007][RMI-API Server][Terminate Normal end.]
The start logs of two or more services are output in the SVP RMI - API server. To confirm the normal start
of the SVP RMI - API server, check the logs of TRRMIS000002, TRRMIS001002 and TRRMIS002502.
Furthermore, to check the normal completion, check the logs of TRRMIS000016, TRRMIS001007 and
TRRMIS002511

Example of log output when it is abnormal:

An example of output when it has occurred abnormally is shown below.
[2015/03/17 [Link].750][INFO ][TRRMIS001001][RMI-API Server][Initialize Start.]
[2015/03/17 [Link].000][INFO ][TRRMIS001002][RMI-API Server][Initialize Normal end.]
[2015/03/17 [Link].638][INFO ][TRRMIS002501][RMI-API Server][Initialize Start.]
[2015/03/17 [Link].544][INFO ][TRRMIS002502][RMI-API Server][Initialize Normal end.]
[2015/03/17 [Link].405][INFO ][TRRMIS000001][RMI-API Server][Initialize Start.]
[2015/03/17 [Link].968][ERROR][TRRMIS000007][RMI-API Server][Port already in use. Port:51100]
[2015/03/17 [Link].003][INFO ][TRRMIS000015][RMI-API Server][Terminate Start.]
[2015/03/17 [Link].125][INFO ][TRRMIS000016][RMI-API Server][Terminate Normal end.]

TRBL03-1000
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1010

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRRMIS000001 INFO This is output when the RMI - API Server service starts.
The log is output two or more times by retry at the time of error
occurrence.
To confirm that the RMI - API Server service has started normally,
match it to the log and check that TRRMIS000002 is output.
TRRMIS000002 INFO This is output when the start of the RMI - API Server service is
completed normally.
TRRMIS000003 WARN Reading the environment setting files necessary for the RMI - API
Server service failed.
1. Restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS000004 WARN This is operating with the default value indicated in the log
content because the acquisition of the environment setting
information necessary for the RMI - API Server service failed.
1. Restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS000005 WARN This is operating with the default value indicated in the log
content because the acquisition of the environment setting
information necessary for the RMI - API Server service failed.
1. Restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-1010
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1020

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS000006 WARN The port number used of the RMI - API Server service is already
used.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If they cannot be changed, see MAINTENANCE PC SECTION
“10.1 Changing Port Numbers Used by the Maintenance PC” and
change the port numbers of “RMIIFRegist”.
TRRMIS000007 ERROR The port number used of the RMI - API Server service is already
used.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If they cannot be changed, see MAINTENANCE PC SECTION
“10.1 Changing Port Numbers Used by the Maintenance PC” and
change the port numbers of “PreRMIServer”.
TRRMIS000008 WARN The file operation indicated by the log content failed in the RMI -
API Server service.
Another application may access the file. Close all other
applications, and then stop the relevant Storage System once from
the Storage Device List and restart it.
TRRMIS000009 ERROR An unexpected error occurred in the RMI - API Server service.
1. Stop the relevant Storage System once and restart it.
2. If the phenomenon does not change after restarting, delete the
Storage System from the Storage Device List once and register
it again.
3. If it does not recover after registering the Storage System,
restart Maintenance PC.
4. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-1020
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1030

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS000010 WARN The connection to the necessary services failed in the RMI - API
TRRMIS000011 ERROR Server service.
1. Stop the relevant Storage System once and restart it.
2. If the phenomenon does not change after restarting, restart the
Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS000012 WARN The IP address used in the RMI - API Server service is invalid.
TRRMIS000013 ERROR 1. Check that the IP address of the Maintenance PC set by the
Storage Device List is correct and restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS000014 WARN This is operating with the default value indicated in the log
content because the acquisition of the port number used for the
RMI - API Server service failed.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance PC”
to check if the port number is not used by a different application.
Change the port number of the application if possible, and restart
the
Maintenance PC.
If they cannot be changed, see MAINTENANCE PC SECTION
“10.1 Changing Port Numbers Used by the Maintenance PC” and
change the port numbers of “PreRMIServer”.
TRRMIS000015 INFO This is output when the RMI - API Server service terminates.
The log is output two or more times by retry at the time of error
occurrence.
To confirm that the RMI - API Server service is completed
normally, match it to the log and check the output of
TRRMIS000016 is output.
TRRMIS000016 INFO This is output when the RMI- API Server service is stopped
normally.
(To be continued)

TRBL03-1030
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1040

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS000017 WARN The connection to the necessary services failed in the RMI - API
TRRMIS000018 ERROR Server service.
1. Restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS000019 ERROR The file operation indicated in the log content failed in the RMI -
API Server service failed.
Another application may access the relevant file. Close all other
applications.
TRRMIS000020 WARN The client cannot connect to the RMI-API Server because the
connection to the necessary service failed in the RMI-API Server
service.
Check whether [Link] exists in the following paths.
• Windows system directory (example: C:\Windows\system32)
• Windows directory (example: C:\Windows)
• Directory defined in environment variable PATH
When [Link] exists, delete DLL and restart the Maintenance
PC.
If the problem persists even after restarting the Maintenance PC,
or if [Link] does not exist in the above paths, uninstall the
Maintenance PC software, then install it again. After that, register
the storage system. (See MAINTENANCE PC SECTION “8.2
Maintenance PC Software Uninstallation”, “1.4 Maintenance
PC Software Initial Installation/Update Installation”, and “2.4
Registering Storage Systems to Be Maintained in Storage Device
List”.)

This log is output when RMI-API Server detects a connection

error even once.
Ignore this log when the connection is successful by retry and
Storage Navigator (or the client connected by external RMI) is
operating normally.
(To be continued)

TRBL03-1040
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1050

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS000021 WARN An unexpected error occurred in the RMI-API Server service.
TRRMIS000022 WARN 1. Stop the relevant Storage System once and restart it.
TRRMIS000023 ERROR 2. If the phenomenon does not change after restarting, delete the
TRRMIS000024 ERROR Storage System from the Storage Device List once and register
TRRMIS000025 ERROR it again.
3. If it does not recover after registering the Storage System,
restart Maintenance PC.
4. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS001001 INFO This is output when starting the RMI - API Server service. To
check that the RMI - API Server service has started normally,
match it to the log and check that TRRMIS001002 is output.
TRRMIS001002 INFO This is output when the start of the RMI - API Server service is
completed normally.
TRRMIS001003 WARN This is operating with the default value indicated in the log
content because the acquisition of the port number used in the
RMI -API Server service failed.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance PC”
to check if the port number is not used by a different application.
Change the port number of the application if possible, and restart
the Maintenance PC.
If they cannot be changed, see MAINTENANCE PC SECTION
“10.1 Changing Port Numbers Used by the Maintenance PC” and
change the port numbers of “PreRMIServer”.
TRRMIS001004 WARN This is operating with the default value indicated in the log
content because the acquisition of the environment setting
information necessary for the RMI - API Server service failed.
1. Check that the IP address of the Maintenance PC set by
Storage Device List is correct and restart the Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-1050
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1060

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS001005 WARN This is a log waiting for other services necessary for starting the
RMI - API Server service to start.
First, check whether TRMAAS000003, TRMAAS000004, and
TRMAAS000005 are output in the Storage Device List log that
is described in [Link] Background Service Log . If the above
troubleshooting codes are output, apply the coping methods for
them.
The log is output once per ten minutes up to six times.
If Storage Navigator still cannot start after output of
TRRMIS001002 then TRRMIS001005 (six times), perform either
of the following depending on whether the SVP system setting
information is restored or not.
[When restored]
1. Perform the restoration again by using the backup files of the
SVP software version same as the restoration location.
2. If the backup files of the same version do not exist and the
signed certificate is made, perform the following:
• Update the signed certificate for SSL communication (see
System Administrator Guide).
3. If the backup files of the same version do not exist and the
signed certificate is not made, perform the following after the
restoration:
• Change the certificate for SSL communication back to the
default (see System Administrator Guide).
[When not restored]
1. Stop the relevant Storage System once from the Storage
Device List and restart it.
2. When TRRMIS001003 and TRRMIS001004 are output
with the log, check the coping method of the relevant
troubleshooting code together.
3. If the phenomenon does not change after restarting, restart the
Maintenance PC.
4. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION 8.2 Maintenance PC
Software Uninstallation, 1.4 Maintenance PC Software Initial
Installation/Update Installation, and 2.4 Registering Storage
Systems to Be Maintained in Storage Device List.)
TRRMIS001006 INFO This is output when the RMI - API Server service terminates.
To confirm that the SVP RMI - API Server service is
completed normally, match it to the log and check the output of
TRRMIS001007.
TRRMIS001007 INFO This is output when the RMI - API Server service is stopped
normally.
(To be continued)
TRBL03-1060
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1061

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS001008 WARN A part of the functions of the RMI-API Server services is not
operating normally.
The Storage System cannot stop normally. Restart the
Maintenance PC.
TRRMIS001009 ERROR An unexpected error occurred in the RMI-API Server service.
• In the case of MPC failure, see MAINTENANCE PC SECTION
“5.2 Dump” and collect a dump file.
• In the case of an SVP failure, collect dump files in accordance
with “System Administrator Guide”. If the dump collection fails,
collect necessary files manually in accordance with “System
Administrator Guide”.
TRRMIS001010 ERROR The RMI-API Server service detects the state of memory shortage
and performs the recovery procedure. When the recovery
procedure is being performed, an error might occur temporarily.
Check the subsequent log to confirm that the RMI-API Server
service is running normally in the Ready status.
TRRMIS001998 ERROR The RMI-API Server service terminated abnormally.
(To be continued)

TRBL03-1061
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1070

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS001999 ERROR The service stopped forcibly. This message might be output when
Maintenance PC restarted while the service is running.
Stop the Storage System by Storage Device List once, and then
restart it.
TRRMIS002501 INFO This is output when the RMI - API Server service starts.
To confirm that the RMI - API Server service has started normally,
match it to the log and check that TRRMIS002502 is output.
TRRMIS002502 INFO This is output when the start of the RMI - API Server service is
completed normally.
TRRMIS002503 WARN The RMI - API Server service succeeded to start but a warning
has occurred in the processing.
Check the troubleshooting codes output from TRRMIS002501 to
the log and take actions.
TRRMIS002504 ERROR The RMI - API Server service failed to start.
Check the troubleshooting codes output through TRRMIS002501
and the log and take actions.
TRRMIS002505 ERROR Acquiring the environment setting information necessary for
TRRMIS002506 ERROR starting the RMI - API Server service has failed.
TRRMIS002507 ERROR 1. For the Storage System, restart of the service by Stop Service,
Start Service from Storage Device List.
2. If the phenomenon does not change even after restarting it,
restart the Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS002508 ERROR The ports necessary for the RMI - API Server service are
TRRMIS002509 ERROR unusable.
See MAINTENANCE PC SECTION “10.8 Checking the
Application Using the Port Number Used by the Maintenance
PC” to check if the port number output in logs is not used by a
different application. Change the port number of the application if
possible, and restart the Maintenance PC.
If it cannot change, see MAINTENANCE PC SECTION “10.1
Changing Port Numbers Used by the Maintenance PC” and
change the port number of “DKCManPrivate”.
TRRMIS002510 INFO This is output when the RMI - API Server service stops.
To confirm that the RMI - API Server service is stopped normally,
match it to the log and check that TRRMIS002511 is output.
TRRMIS002511 INFO This is output when the RMI - API Server service is stopped
normally.
(To be continued)
TRBL03-1070
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1071

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS002512 ERROR The RMI - API Server service has stopped.
If the phenomenon does not change after waiting for five minutes,
execute the following procedures in order.
1. For the Storage System, restart of the service by Stop Service,
Start Service from Storage Device List.
2. If not recover, restart the Maintenance PC.
3. If the problem persists, uninstall the Maintenance PC software,
then install it again. After that, register the storage system.
(See MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS002513 ERROR The RMI-API Server service stopped forcibly. This error might
occur when restarting the Maintenance PC while the service is
running.
When the Maintenance PC restarted or the Storage System
stopped, restart the Storage System by Storage Device List. In
other cases, the RMI-API Server service restarts automatically.
If the phenomenon does not change after waiting for three
minutes, perform the following procedure sequentially.
1. Stop the relevant Storage System once and restart it.
2. If the phenomenon does not change after restarting, delete the
Storage System from the Storage Device List once and register
it again.
3. If it does not recover after registering the Storage System,
restart Maintenance PC.
4. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
(To be continued)

TRBL03-1071
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1072

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRRMIS002514 ERROR An error occurred in the communication with the RMI-API Server
service. The RMI-API Server service restarts automatically.
If the phenomenon does not change after waiting for one minute,
perform the following procedure sequentially.
1. Check whether the Maintenance PC IP address set by Storage
Device List is correct. If not, set it. After that, ensure that the
IP address is correctly set, and then click the [Apply] button to
complete the address setting.
2. If not recovered, perform Stop Service, and then Start Service
to restart the service for the target Storage System.
3. If still not recovered, restart the Maintenance PC.
4. If the problem persists, uninstall the Maintenance PC software,
then install it again. After that, register the storage system.
(See MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TRRMIS002515 ERROR The RMI-API Server service stopped abnormally.
Check the troubleshooting codes output from TRRMIS002501 to
this log and take necessary actions.
TRRMIS002516 INFO This is output when the stop processing of the RMI-API Server
service is executed.
• StatusCode=0: Normal end
• StatusCode=1: Ready
• StatusCode=3: In progress
If a numeric value other than the above is displayed, contact the
Technical Support Division.

TRBL03-1072
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1080

• External authentication relay service

Example of log output when it is normal
 At the time of start-up:
[2015/03/19 [Link].265][INFO ][TREXAU000001][External Authenticator][Start.]
[2015/03/19 [Link].858][INFO ][TREXAU000002][External Authenticator][Succeeded:Start.]
 At the time of termination:
[2015/03/19 [Link].812][INFO ][TREXAU000004][External Authenticator][Stop.]
[2015/03/19 [Link].943][INFO ][TREXAU000005][External Authenticator][Succeeded:Stop.]

Example of log output when it is abnormal

 At the time of start-up:
[2015/03/20 [Link].265][INFO ][TREXAU000001][External Authenticator][Start.]
[2015/03/20 [Link].364][ERROR][TREXAU000003][External Authenticator][Failed:Start.]
 At the time of termination:
[2015/03/20 [Link].317][INFO ][TREXAU000004][External Authenticator][Stop.]
[2015/03/20 [Link].113][ERROR][TREXAU000006][External Authenticator][Failed:Stop.]

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TREXAU000001 INFO This is output when the external authentication relay service
starts.
To confirm that the external authentication relay service has
started normally, match it to the troubleshooting code and check
that TREXAU000002 is output.
TREXAU000002 INFO The External authentication relay service has started normally.
TREXAU000003 ERROR The External authentication relay service failed to start.
1. Select the relevant Storage System from the Storage Device
List, stop it, and then start it.
2. If it does not recover, restart the Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TREXAU000004 INFO This is output when the External authentication relay service
stops.
To confirm that the external authentication relay serviced is
stopped normally, match it to the troubleshooting code and check
that TREXAU000002 is output.
TREXAU000005 INFO This is output when the External authentication relay service
stops.
(To be continued)

TRBL03-1080
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1090

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TREXAU000006 ERROR An error occurred by stopping the external authentication relay
service.
1. If the external authentication relay service does not start
normally (TREXAU000002) at the next start time, restart the
Maintenance PC.
2. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TREXAU000007 ERROR The external authentication relay service is not started.
1. Select the relevant Storage System from the Storage Device
List, stop it, and then start it.
2. If it does not recover, restart the Maintenance PC.
3. If the problem persists even after restarting the Maintenance
PC, uninstall the Maintenance PC software, then install
it again. After that, register the storage system. (See
MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)
TREXAU000008 ERROR The test communication to the HCS server when setting the
external authentication link of the HCS server failed.
The network setting of the HCS server or the setting of the
external authentication may have a problem.
Check the setting of the HCS server.
TREXAU000009 ERROR The connection with the HCS server failed when performing the
external authentication for the HCS server.
The network setting of the HCS server or the setting of the
external authentication may have a problem.
Check the setting of the HCS server.
(To be continued)

TRBL03-1090
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1091

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TREXAU000010 ERROR The external authentication relay service is stopped forcibly.
TREXAU000011 ERROR This might be output when Maintenance PC restarts while the
service is running.
1. Stop the relevant Storage System from the Storage Device List
and restart it.
2. If not recover, restart the Maintenance PC.
3. If the problem persists, uninstall the Maintenance PC software,
then install it again. After that, register the storage system.
(See MAINTENANCE PC SECTION “8.2 Maintenance PC
Software Uninstallation”, “1.4 Maintenance PC Software Initial
Installation/Update Installation”, and “2.4 Registering Storage
Systems to Be Maintained in Storage Device List”.)

TRBL03-1091
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1100

• Communication service
Example of log output when it is normal
An example of output when it started normally and terminated is shown below.
[2015/05/27 [Link].875][INFO ][TRCOMM000001][Communication]
[Ready : Connection to GUM2 opened.]
[2015/05/27 [Link].972][INFO ][TRCOMM000001][Communication]
[Ready : Connection to GUM1 opened.]
• • •

Example of log output when it is abnormal

An example of output when it has occurred abnormally is shown below.
[2015/05/27 [Link].288][ERROR][TRCOMM000004][Communication]
[Failed : Connection to GUM2 failed. Already connected MPCʼs IP Address is (1)[Link] ]
[2015/05/27 [Link].428][ERROR][TRCOMM000009][Communication]
[Failed : Authentication failed by GUM2.]

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRCOMM000001 INFO This is output when completing the communication path
connection with GUM normally after the communication service
started.
TRCOMM000002 INFO This is output when completing the device authentication in the
communication path to GUM normally after the communication
service started.
TRCOMM000003 INFO This is output when completing the consistency check in the
communication path to GUM after the communication service
started. (Indicates the state that Serial numbers, Config models,
and models are identical)
TRCOMM000004 ERROR This is output when the other Maintenance PC already connected
to the storage system to be used.
Stop the services of the storage system running on the PC of the
IP address (*1) described in the background service log.
*1: If the router converts the IP address, the address might be different from the IP address of the PC
itself. In that case, confirm with the network administrator.
(To be continued)

TRBL03-1100
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1101

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRCOMM000005 WARN This is output when detecting that the IP address for each CTL set
in the Add System window and the CTL number set for GUM are
not identical.
Correct the IP Address setting for each CTL in the Storage Device
List.
Then, check the background service log.
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM1.]
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM2.]
You can determine that the system has recovered from the
error if the above log, which indicates the completion of
check, is displayed later than the time when the error code
TRCOMM000005 was generated.
TRCOMM000006 WARN This is output when detecting that the storage system model set in
the Add System window and the storage system model set for the
storage system are not identical.
Delete the storage system from the Storage Device List once and
register it again with the correct storage system model.
Then, check the background service log.
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM1.]
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM2.]
You can determine that the system has recovered from the
error if the above log, which indicates the completion of
check, is displayed later than the time when the error code
TRCOMM000006 was generated.
(To be continued)

TRBL03-1101
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1102

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRCOMM000007 WARN This is output when detecting that the Config model set in the
Add System window and the Config model installed in the storage
system are not identical.
Delete the storage system from the Storage Device List once and
register it again with the correct Config model.
Then, check the background service log.
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM1.]
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM2.]
You can determine that the system has recovered from the
error if the above log, which indicates the completion of
check, is displayed later than the time when the error code
TRCOMM000007 was generated.
TRCOMM000008 WARN This is output when detecting that the serial number set in the Add
System window and the serial number set in the storage system
are not identical.
Delete the storage system from the Storage Device List once and
register it again with the correct serial number.
Then, check the background service log.
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM1.]
[xxxxx yyyyyy][INFO ][TRCOMM000003][Communication]
[Ready : Consistency check completed by GUM2.]
You can determine that the system has recovered from the
error if the above log, which indicates the completion of
check, is displayed later than the time when the error code
TRCOMM000008 was generated.
(To be continued)

TRBL03-1102
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1110

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRCOMM000009 ERROR This is output when authentication fails at connection with GUM.
If the troubleshooting code TRCOMM000002 is output within a
minute after this log is output, no action is required because it is
caused by temporary communication failure.
If the troubleshooting code TRCOMM000002 is not output, the
user name and password set in the Add System window might
not be correct. Set the user name and the password in the Storage
Device List again.
Then, check the background service log.
[xxxxx yyyyyy][INFO ][TRCOMM000002][Communication]
[Ready : Authentication completed by GUM1.]
[xxxxx yyyyyy][INFO ][TRCOMM000002][Communication]
[Ready : Authentication completed by GUM2.]
You can determine that the system has recovered from the
error if the above log, which indicates the completion of
authentication, is displayed later than the time when the error code
TRCOMM000009 was generated.

• When you cannot log in with the correct user name and
password, the problem might be caused by the following reason.
Check whether it is applied.
- The account is disabled by the security administrator.
• When you cannot log in with the correct user name and password
under the condition where the user account policies are set, the
problem might be caused by any of the following reasons. Check
whether they are applied.
- The account is disabled because the password has expired.
- The account is disabled because the number of login attempts
has exceeded the limit.
- The account is locked because the number of login attempts has
exceeded the limit.
- This is the first login.
- The account is locked or disabled because the number of login
attempts has exceeded the limit due to automatic authentication
such as API authentication.

Consult with the security administrator about the above matters.

TRCOMM000010 INFO This is output when the communication path to GUM is
disconnected after the communication service is started. Check
the communication path and GUM activities.
(To be continued)

TRBL03-1110
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1111

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRCOMM000011 ERROR This is output when the information update failed.
It is updated again automatically. However, if the
“TRCOMM000002” log is not output after waiting for about five
minutes from the log output, select the storage system from the
Storage Device List. Stop the system, and then restart it.
If the failure does not recover, restart the Maintenance PC.
TRCOMM000012 ERROR The other Maintenance PC might already connect to the storage
system to be used.
Check whether any other PCs starting the services of the storage
system exist for the storage system to be used.
If an Maintenance PC already started the services of the storage
system, stop the services.
TRCOMM000013 INFO This is output when the Communication service starts.
To check whether the communication service is starting normally,
confirm that this log and TRCOMM000002 are output.
TRCOMM000014 INFO This is output when the communication service stops.
To check whether the communication service is stopped normally,
confirm that this log and TRCOMM0000015 are output.
TRCOMM000015 INFO This is output when the communication service stops normally.
(To be continued)

TRBL03-1111
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1120

(Continued from the preceding page)

Troubleshooting code Failure level Coping Method
TRCOMM000016 WARN This is output when the connection with the storage system fails.
1. Check that the IP addresses of CTL1 and CTL2 that are set
in Storage Device List are correct. If the IP addresses are
incorrect, stop the service of this storage system, and then set
correct IP addresses. After setting, restart the service.
2. If the IP addresses are correct, check that you can log in to
Maintenance Utility from the browser (see “2.7.2 Starting
the Maintenance Utility Window from the MPC Window” in
MAINETNANCE PC SECTION).
NOTE: If you cannot log in, there might be a problem in
the communication path between the storage system
and the Maintenance PC or in the GUM operation.
Perform a recovery action suitable for the problem
(see “2.11 Troubleshooting of Maintenance Utility”
in MAINTENANCE PC SECTION).
3. After checking that you can log in to Maintenance Utility
from the browser, check the background service log. If
TRCOMM000016 is output more than once within about 10
minutes, restart the service of the target storage system from
Storage Device List ([Stop Service] → [Start Service]).
4. If the problem persists after you restart the service of the
storage system, reboot GUM (see “3.18 Reboot GUM” in
MAINTENANCE PC SECTION).
5. Check the background service log. If the problem is solved,
the following are output after TRCOMM000016, and
TRCOMM000016 is not repeated.
[xxxxx yyyyyy][INFO][TRCOMM000002][Communication]
[Ready : Authentication completed by GUM1.]
[xxxxx yyyyyy][INFO][TRCOMM000002][Communication]
[Ready : Authentication completed by GUM2.]
TRCOMM000017 ERROR The communication service is terminated abnormally.
TRCOMM000018 ERROR The communication service is stopped forcibly.
This might be output when Maintenance PC restarts while the
communication service is running.
Stop the service of this storage system by Storage Device List and
restart it.

TRBL03-1120
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1130

• KMIP Communicator
Example of log output when it is abnormal
An example of output when it has occurred abnormally is shown below.
[2015/11/19 [Link].617][ERROR][TRKMIP000001][KMIPCom][Failed : SSL settings are invalid.]

Troubleshooting codes and coping methods are shown below.

Troubleshooting code Failure level Coping Method
TRKMIP000001 ERROR An unexpected error occurred in the KMIP Communicator Server
service.
• In the case of MPC failure, see MAINTENANCE PC SECTION
“5.2 Dump” and collect a dump file.
• In the case of an SVP failure, collect dump files in accordance
with “System Administrator Guide”. If the dump collection fails,
collect necessary files manually in accordance with “System
Administrator Guide”.

TRBL03-1130
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1131

[Link] Checking Duplicated Ports and Using DLL Load Confirmation Tools
NOTICE: • Install the tools by referring to “1. Installing tools” before using the tools.
• Uninstall the tools by referring to “4. Uninstalling tools” after using the tools.
• Use the tools described in this section to forcibly close the applications that prevent
the storage management software and SVP software from being installed and
updated.
• When executing the tools described in this section, an Error event log might be
issued depending on the forcibly closed applications.

1. Installing tools
(1) Insert the installation media (DVD) indicated as “SVP” on the surface, which is included in the
VSP G130/G350/G370/G700/G900/F350/F370/F700/F900, VSP E590/E790/E990/E1090, into the
DVD drive on the SVP.

(2) Copy the “tool\install_trbl” folder directly under the DVD drive to the directory in the SVP.
NOTE: • Do not specify the directory where the storage management software is installed as
the copy destination directory.
• It must be possible to write to the copy destination directory or lower-level
directories.

TRBL03-1131
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1132

2. Troubleshooting using [Link]

If the “21542-005016” error occurs due to the updates of the storage management software and SVP
software, execute the tool.
When the Technical Support Division provides any instructions even if the above error does not occur,
execute the tool.

(1) Start the Command Prompt with Administrator privilege on the SVP.

(2) Move to the directory where the tool is installed with the cd command.
Example: If the installation directory is C:\wk\install_trbl:
cd /d C:\wk\install_trbl

(3) Execute the following command:

[Link]

(4) When prompted to forcibly close the processes and services detected by the tool, enter “Y”.

(5) Close the command prompt when the tool execution is completed.

Update the storage management software and SVP software again.

If the problem still occurs after executing the tool, collect the logs of the tool, and then contact the
Technical Support Division.
The logs of the tool are issued to the logs directory directly under the directory where the tool is copied
during the installation.

TRBL03-1132
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1133

3. Troubleshooting using [Link]

If the “21041-006005” error occurs due to the updates of the storage management software and SVP
software, execute the tool.
When the Technical Support Division provides any instructions even if the above error does not occur,
execute the tool.

(1) Start the Command Prompt with Administrator privilege on the SVP.

(2) Move to the directory where the tool is installed with the cd command.
Example: If the installation directory is C:\wk\install_trbl:
cd /d C:\wk\install_trbl

(3) Execute the following command:

[Link]

(4) When prompted to forcibly close the processes and services detected by the tool, enter “Y”.

(5) Close the command prompt when the tool execution is completed.

Update the storage management software and SVP software again.

If the problem still occurs after executing the tool, collect the logs of the tool, and then contact the
Technical Support Division.
The logs of the tool are issued to the logs directory directly under the directory where the tool is copied
during the installation.

4. Uninstalling tools
Remove the directory where the tools are copied during the installation.

TRBL03-1133
Hitachi Proprietary DW850/DW900/DW1000
Rev.6.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1134

[Link] Troubleshooting Related to Jetty Periodic Reboot Function

No. Failure Recovery action
1 You cannot log in to Storage On storage Device List, stop the target storage system, and
Navigator after the Jetty periodic then restart it.
reboot is executed.
2 You cannot view or change the Release the system lock forcibly (see MAINTENANCE PC
storage system configuration settings SECTION “3.17 Force Release System Lock”).
after the Jetty periodic reboot is
executed.

TRBL03-1134
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1140

3.29 MPC Failure Recovery

3.29.1 When I cannot be connected from MPC to the GUM or Storage System

The Maintenance PC cannot

connect to the Storage System.

Did making the network

Yes
settings (MPC03-510) cause the
disconnection?

An IP address that should not be used

No might be set. Contact the Technical Support
Division.

Are two LAN ports

on MPC/SVP and two LAN ports Yes
on the storage system connected
without HUB? Perform the bridge setting according to
MAINTENANCE PC SECTION “2.3.2 Bridge
No Setting of LAN Ports”.

No Can MPC/SVP connect to

the storage system?

Yes

END

Check the “3.30.1 Reference procedure of the Take a note of the date and time at the present
event log of MPC/SVP” and take a note of the working on the failure recovery of the Maintenance
date and time of the most recent “Event ID = 9”. PC.(Define it as Date and Time T1)

6
(TRBL03-1141)

TRBL03-1140
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1141

Check the “3.30.1 Reference procedure of the event log of MPC/

SVP” and perform the recovery operation following this procedure.
Refer to the event log of Date and Time T1 or later and the event
log which “Serial Number” recorded in the event log matches “Serial
Number” of the maintenance operation target. (*1)

Is the event of “User Authentication Failure” Yes

4
recorded? (Record “Event ID = 4”)
(TRBL03-1170)

No

Is the event of “Establish

Connection” recorded? No
2
(Record “Event ID = 0” or “Event ID = 1”) (TRBL03-1150)

Yes

Is “Disconnect Connection” recorded? Yes

3
(Record “Event ID = 2” or “Event ID = 3”)
(TRBL03-1160)

No

5
(TRBL03-1180)

*1: When checking the even logs, sort them by “Date and Time” and operate “Update to the Most
Recent Information” to update the event log display to the most recent status, and then check the
content. (See “3.30.1 Reference procedure of the event log of MPC/SVP”.)

TRBL03-1141
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1150

Is the IP
address of the CTL that is No
registered in Storage Device
List correct? Correct the IP address of the CTL and check
whether it can be connected. (See MPC02-520.)
Yes

No Can the Maintenance PC

connect to the Storage System?

Yes

3 END
(TRBL03-1160)

TRBL03-1150
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1160

Run ping from the command prompt on the (Specify an IP address of

Maintenance PC to check whether the CTL CTL connecting an LAN
returns a response. cable)

Did the CTL No

respond?
Yes
One or multiple items of the following are the causes of the communication failure.
Check the validity of each item. If there is any problem, take actions.
・ Is the LAN cable between the Maintenance PC and the CTL connected correctly?
・ Are the respective LAN ports of the Maintenance PC and the CTL linked up?
・ Are the respective IP addresses, subnet masks and default gateways of the
Maintenance PC and the CTL set appropriately?
・Is the firewall setting correct?

Run ping from the command prompt on the (Specify an IP address of

Maintenance PC to check whether the CTL CTL connecting an LAN
returns a response. cable)

Did the CTL No

respond?
Yes

Check the event log of the Maintenance PC/SVP which the T.S.D. call
event occurrence time is Date and Time T1 or later. (See
“3.30.1 Reference procedure of the event log of MPC/SVP”.)

No
Is the event log output?

Yes Did you check

No
whether it can connect to both CTL1
and CTL2?

Yes Connect the LAN cable connected to the CTL

to the maintenance port of the opposite CTL.

1 T.S.D. call 1
(TRBL03-1140) (TRBL03-1140)

TRBL03-1160
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1170

Perform the processing corresponding to the event log of

“Event ID = 4”. (See “3.30.2 List of event ID of MPC/SVP”.)
(If this procedure is used despite the correct setting,
perform CTL replacement operation.)

Can the No
Maintenance PC connect to the
Storage System?

Yes

END 1
(TRBL03-1140)

TRBL03-1170
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1180

Check the event log of the Maintenance PC/SVP. For the event log after
outputting the event log of “Event ID = 0, 1” with the most recent event
occurrence time, check whether it is applied to any of the following. (See
“3.30.1 Reference procedure of the event log of MPC/SVP”.)
・The event log of “Event ID = 5, 6, 7, 8” is output and the processing
corresponding to the event ID is not performed.

Is it applied to any Yes

of the above?
No Perform the processing corresponding to each
event log. (See“3.30.2 List of event ID of MPC/
SVP”.)

Can the
No
Maintenance PC connect to the
Storage System?

Yes

END T.S.D. call

TRBL03-1180
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1190

3.29.2 When the Set Network Location dialog is displayed

The “Set Network Location” dialog might be displayed on the Maintenance PC at the timing when the
network environment is changed. However the display of the dialog does not affect the Maintenance PC
function.
Click the [Cancel] button in the lower right of the dialog to close it.

The “Set Network Location” dialog.

3.29.3 When the drive letter of the Maintenance PC is not displayed or is redundant
If the drive letter of the Maintenance PC is not displayed in the drop down list to select a drive or more than
one same drive letters are displayed when you perform the maintenance operation on the Maintenance PC,
restart the Maintenance PC, and then continue the operation.

3.29.4 When the installation folder of the Maintenance PC software (for example, C:\
Mapp) is deleted by mistake
Restore the software of Maintenance PC in the following procedures, when you have deleted the software of
Maintenance PC by Windows Explore.

(1) Confirm the version of the installed software. Prepare for the media of the same version.
(2) Perform the installation again.
(3) Uninstall the Maintenance PC software. (See MAINTENANCE PC SECTION “8.2 Maintenance
PC Software Uninstallation”.)

TRBL03-1190
Hitachi Proprietary DW850/DW900/DW1000
Rev.7.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1191

3.29.5 When an Alert Message of an Antivirus Program is Displayed at the Time of

Maintenance PC Installation
If an antivirus program is installed on the Maintenance PC, too much time might be taken for the installation,
or an alert message of the antivirus program might be displayed, affecting the installation operation.
Even when an alert message of an antivirus program is displayed at the time of Maintenance PC installation,
continue the installation if the installation can be continued.
If the installation cannot be continued, stop the installation, suspend the antivirus program, and then execute
the installation again. If you suspend the antivirus program, run it again after completing the installation.

3.29.6 When There Is a Performance Problem of the Maintenance PC

If a high CPU usage rate of the Maintenance PC, slow operation of the Maintenance PC or Web Console, or
similar phenomenon occurs, collect the performance information of the Maintenance PC and dumps during
the occurrence of that phenomenon and send them to the Technical Support Division.
NOTE: • If the customer informs you of the SVP performance problem, ask the customer to
see System Administrator Guide to solve the problem.
• The Maintenance PC software with version 88-03-23-x0/xx or later is required.
Version 88-03-23-x0/xx or later supports the performance information collection
tool.
• Collect dumps immediately after collecting the performance information. It takes
about 30 minutes to collect the performance information.
• During the collection of the performance information and dumps, the performance
of the Maintenance PC might be affected. The Maintenance PC operation might
become much slower depending on the workload.
Collect the performance information and dumps by following the procedure below.

Required Condition
The collection procedure must be performed under the condition where a high CPU usage rate of the
Maintenance PC, slow operation of the Maintenance PC or Web Console, or similar phenomenon is
occurring. If the collection procedure is performed when that phenomenon does not occur, an accurate
analysis is not possible at the Technical Support Division.

1. Start the command prompt as Administrator on the Maintenance PC.

2. Change the current directory to the directory in which the performance information collection tool exists.
cd /d C:\Mapp\wk\882000400001\DKC200\mp\pc
• “C:\Mapp” is the default installation directory of the Maintenance PC software. Enter the directory
specified at the time of its installation.
• “882000400001” is an identification number of the storage system. The lower six digits represent a
serial number of the storage system. Specify the folder name for the target storage system.

TRBL03-1191
Hitachi Proprietary DW850/DW900/DW1000
Rev.7.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1192

3. Run the following command:

[Link] C:\Result
• “C:\Result” is the output directory of the performance information. Specify an absolute path.
You can omit the output directory. If you omit it, the performance information is output in the following
directory:
[Installation directory of the Maintenance PC software]\wk\[storage system identification number]\
DKC200\tmp\PerfLog
You cannot specify a network drive folder for the output directory.
4. The performance information collection tool is executed, and “Executing...” is displayed on the screen.
Do not click or close the command prompt window during the execution.
5. The Maintenance PC system information is collected along with the performance information. When
a dialog box is displayed during the collection of the Maintenance PC system information, do not
respond to the dialog box by clicking the [Cancel] button or other operations. After the collection of the
Maintenance PC system information is complete, the dialog box automatically disappears.
6. When the execution of the performance information collection tool is completed, the message shown
below is displayed on the screen. It takes about 30 minutes for the execution to be completed.
MPC Performance Information tool is completed.
7. Check that the following files are output in the specified directory.
• CounterResult_YYYYMMDDhhmmss.blg : Windows performance monitor log
• ProcessList_YYYYMMDDhhmmss.csv : Information of the processes run on the Maintenance PC
• Sysinfo_YYYYMMDDhhmmss.txt : Maintenance PC system information
8. Close the command prompt.
9. Collect “Normal” type dumps (see MPC05-50).
NOTE: Collect dumps immediately after collecting the performance information. If you
collet dumps after a long time has passed from the completion of the performance
information collection, an accurate analysis is not possible.
10. Send the performance information file and dump files to the Technical Support Division.

TRBL03-1192
Hitachi Proprietary DW850/DW900/DW1000
Rev.7.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1193

3.29.7 When the Alert Message Close programs to prevent information loss Is
Displayed
If the following message is displayed while you are operating the Maintenance PC, reboot the Maintenance
PC.
NOTE: Displayed program names might vary.

TRBL03-1193
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1200

3.30 Event log of MPC/SVP

You can confirm an event that occurred in Maintenance PC/SVP by referring to event log.

3.30.1 Reference procedure of the event log of MPC/SVP

1. Select [Control Panel]-[Administrative Tools]-[Event Viewer] from the [Start] menu. An Event Viewer
window is displayed.
NOTE: For Windows 11, select [Start]-[All Apps]-[Windows Tools]-[Event Viewer].

TRBL03-1200
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1210

2. In a tree of the window left side, Select [Applications and Services Logs]-[Hitachi Device Manager -
Storage Navigator].

TRBL03-1210
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1220

3. In the upper part of the center pane of the “Event Viewer” window, a log list of the events related to the
Maintenance PC or SVP is displayed.

Item Description
Level Severity of the log
Information Log of the information level
Warning Log of the warning level
Error Log of the serious error level
Date and Time The time of day which an event produced
Source Fixed with “Hitachi Device Manager – Storage Navigator”
Event ID ID of the event log
(See “3.30.2 List of event ID of MPC/SVP” for the list of ID.)
Task Category Fixed with “None”

NOTE: In the Windows Logs in the tree in the left pane, error-level events related to the
Maintenance PC software or SVP software might be logged. For details of such events
and actions to take, see “3.30.3 Actions for Windows Logs Related to Maintenance PC
Software/SVP Software”.

TRBL03-1220
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1230

4. Selecting an event from the list of events displays the detailed information of the events in the [General]
tab at the lower of the center of the “Event Viewer” window.

Item Description
S/N Serial number of the storage system
Detail Contents of the event
Action Action for the event
No Action The action is unnecessary
See Maintenance Take actions in accordance with the measures described in “3.30.2
Manual List of event ID of MPC/SVP”.

TRBL03-1230
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1240

3.30.2 List of event ID of MPC/SVP

Event ID Level Item Contents
0 Information Description Connection to CTL1 has been established
Display of Connection to CTL1 has been established
Detail
Action None
1 Information Description Connection to CTL2 has been established
Display of Connection to CTL2 has been established
Detail
Action None
2 Information Description Connection to CTL1 was disconnected
Display of Connection to CTL1 was disconnected
Detail
Action None
3 Information Description Connection to CTL2 was disconnected
Display of Connection to CTL2 was disconnected
Detail
Action None
4 Error Description The user authentication to a storage system failed.
Display of User authentication is failed
Detail
Action A communication failure might occur between the Maintenance PC/
SVP and the GUM/Storage System.
Check the status of the connection to the GUM/Storage System in
accordance with the procedure from number  described in the flow
chart of “3.29.1 When I cannot be connected from MPC to the GUM
or Storage System”.
If disconnected, connect the Maintenance PC/SVP and GUM to run
again.
If connected, check whether [User name] and [Password] set in the
“Add System/Edit System” window of the Storage Device List are
correct.
In the case of a wrong, set right [User name] and [Password] in “Edit
System” window of Storage Device List.
In the case of a correct, perform CTL replacement operation.

TRBL03-1240
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1250

Event ID Level Item Contents

5 Error Description Serial number set in Maintenance PC/SVP is mismatched with serial
number of the storage system.
Display of Serial Number disagreement
Detail
Action Confirm whether [Serial Number] set in “Add System” window of
Storage Device List are not wrong.
In the case of a wrong,
By the following procedure, register storage system information again.
1. Stop the service of the storage system. (See MAINTENANCE PC
SECTION “2.14.2 Stopping the Service of Storage System”.)
2. Delete the device icon with [X] button in “Storage Device List”
window.
3. Register a storage system in correct [Serial Number] in the “Add
System of the Storage Device List” window.
In the case of a correct, T.S.D. call.
6 Error Description System Type set in Maintenance PC/SVP is mismatched with System
Type of the storage system.
Display of System Type disagreement
Detail
Action Confirm whether [System Type] set in “Add System” window of
Storage Device List are not wrong.
In the case of a wrong,
By the following procedure, register storage system information again.
1. Stop the service of the storage system. (See MAINTENANCE PC
SECTION “2.14.2 Stopping the Service of Storage System”.)
2. Delete the device icon with [X] button in Storage Device List
window.
3. Register a storage system in correct [System Type] in the “Add
System of the Storage Device List” window.
In the case of a correct, T.S.D. call.

TRBL03-1250
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1260

Event ID Level Item Contents

7 Error Description Configuration type set in Maintenance PC/SVP is mismatched with
Configuration type of the storage system.
Display of Configuration type disagreement
Detail
Action Confirm whether configuration type of [Software Version] (MPC02-
160) set in “Add System/Edit System” window of Storage Device List
are not wrong.
In the case of a wrong,
By the following procedure, register storage system information again.
1. Stop the service of the storage system. (See MAINTENANCE PC
SECTION “2.14.2 Stopping the Service of Storage System”.)
2. Delete the device icon with [X] button in “Storage Device List”
window.
3. Register a storage system in correct configuration type in the “Add
System of the Storage Device List” window.
In the case of a correct, T.S.D. call.
8 Error Description Connection to other side CTL of CTL1/CTL2 set in Maintenance PC/
SVP
Display of Connected to the opposite side controller.
Detail
Action Confirm whether [IP Address] of CTL1/CTL2 set in “Add System/Edit
System” window of Storage Device List are not wrong.
In the case of a wrong,
set right [IP Address] in “Edit System” window of Storage Device List.
In the case of a correct, T.S.D. call.
9 Information Description The service of the Storage Navigator instance started
Display of The service of the Storage Navigator instance started
Detail
Action None

TRBL03-1260
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1270

Event ID Level Item Contents

16 Error Description Connection to CTL1 remains disconnected for a long time
Display of Connection to CTL1 remains disconnected for a long time
Detail
Action A communication failure might occur between the Maintenance PC/
SVP and the GUM/Storage System.
Check the status of the connection to the GUM/Storage System in
accordance with the procedure from number  described in the flow
chart of “3.29.1 When I cannot be connected from MPC to the GUM
or Storage System”.
If disconnected, connect the Maintenance PC/SVP and GUM to run
again.
If connected, check whether [User name] and [Password] set in the
“Add System/Edit System” window of the Storage Device List are
correct.
In the case of a wrong, set right [User name] and [Password] in “Edit
System” window of Storage Device List.
In the case of a correct, T.S.D. call.
17 Error Description Connection to CTL2 remains disconnected for a long time
Display of Connection to CTL2 remains disconnected for a long time
Detail
Action A communication failure might occur between the Maintenance PC/
SVP and the GUM/Storage System.
Check the status of the connection to the GUM/Storage System in
accordance with the procedure from number  described in the flow
chart of “3.29.1 When I cannot be connected from MPC to the GUM
or Storage System”.
If disconnected, connect the Maintenance PC/SVP and GUM to run
again.
If connected, check whether [User name] and [Password] set in the
“Add System/Edit System” window of the Storage Device List are
correct.
In the case of a wrong, set right [User name] and [Password] in “Edit
System” window of Storage Device List.
In the case of a correct, T.S.D. call.

TRBL03-1270
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1280

Event ID Level Item Contents

18 Error Description Connection to CTL1/CTL2 remains disconnected for a long time
Display of Connection to CTL1/CTL2 remains disconnected for a long time
Detail
Action A communication failure might occur between the Maintenance PC/
SVP and the GUM/Storage System.
Check the status of the connection to the GUM/Storage System in
accordance with the procedure from number  described in the flow
chart of “3.29.1 When I cannot be connected from MPC to the GUM
or Storage System”.
If disconnected, connect the Maintenance PC/SVP and GUM to run
again.
If connected, check whether [User name] and [Password] set in the
“Add System/Edit System” window of the Storage Device List are
correct.
In the case of a wrong, set right [User name] and [Password] in “Edit
System” window of Storage Device List.
In the case of a correct, T.S.D. call.
19 Information Description The automatic dump collection is started on the SVP by the Automatic
Log Dump Collection function.
Display of Dump collection starts
Detail
Action None
20 Information Description The automatic dump collection that was started on the SVP by the
Automatic Log Dump Collection function ends normally.
Display of Dump collection ends normally
Detail
Action None

TRBL03-1280
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1280A

Event ID Level Item Contents

21 Information Description The automatic dump collection that was started on the SVP by the
Automatic Log Dump Collection function ends abnormally.
Display of Dump collection ends abnormally
Detail
Action The free space on the drive of the SVP might be insufficient or the
maintenance work might be performed during automatic dump
collection.
The following free space to store dump files (for one generation) is
available on the drive where the SVP software is installed:
VSP G130/G350/G370/G700/G900/F350/F370/F700/F900: 20 GB or
more
VSP E590/E790/E990/E1090: 25 GB or more
If this event occurs during maintenance work, no action is required.
If this event occurs when there is sufficient free space and the
maintenance work is not performed, contact the Technical Support
Division.
22 Information Description The automatic dump collection that was started on the SVP by the
Automatic Log Dump Collection function is stopped.
Display of Cancellation of the dump collection completed
Detail
Action None

TRBL03-1280A
Hitachi Proprietary DW850/DW900/DW1000
Rev.7 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1281

3.30.3 Actions for Windows Logs Related to Maintenance PC Software/SVP Software

Windows Log Action
Log type: Application Ignore this event.
Source: Application Error This event might be reported when either
Event ID: 1000 of the following occurs, but it is not a
Level: Error problem.
Name of application of which error is reported: [Link] • When the Maintenance PC software/SVP
Name of module of which error is reported: [Link], or [Link] software is updated
Exception code: 0xc0000005 • When Maintenance PC/SVP is shutdown
or restarted
Log type: Application Ignore this event.
Source: Application Error This event might be reported when the
Event ID: 1000 service of the storage system is stopped,
Level: Error but it is not a problem.
Name of application of which error is reported: [Link]
Name of module of which error is reported: [Link]
Exception code: 0xc0000005
Log type: Application Ignore this event.
Source: Application Error This event might be reported when any
Event ID: 1000 of the following occurs, but it is not a
Level: Error problem.
Name of application of which error is reported: MpcL7Comm. • When the service of the storage system is
exe stopped
Name of module of which error is reported: [Link] • When the Maintenance PC software/SVP
Exception code: 0xc0000005 software is updated
• When Maintenance PC/SVP is shutdown
or restarted
Log Type: System Ignore this event.
Source: TaskScheduler This event might be reported when the
Event ID: 414 Maintenance PC software/SVP software is
Level: Warning updated, but it is not a problem.
Task Category: Task Misconfiguration
Detail: Task Scheduler service found a misconfiguration in the
NT TASK\HitachiDeviceManager-NASConfigBackup
definition.
Log type: Application Ignore this event.
Source: Application Error This event might be reported when the
Event ID: 1000 service of the storage system is stopped,
Level: Error but it is not a problem.
Name of application of which error is reported: RestPush_Base.
exe
Name of module of which error is reported: [Link]
Exception code: 0xc0000005, or 0xc000041d

TRBL03-1281
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1290

3.31 Procedure for Responding to the Used Endurance of Flash Drives, NVMe Drives,
and Flash Module Drives (FMDs) (SIM = 50axyy, 50bxyy, 50cxyy, 50dxyy)
The SIMs indicate the write endurance (Used Endurance) threshold over of Flash Drives, NVMe Drives, and
Flash Module Drives (FMD).

1. The SIMs are reported for the first time when the rate of write endurance reaches 95%, and then reported
each time the percentage rises by 1%.
When the rate of write endurance reaches 99%, Dynamic Sparing starts to run, and data is saved to an
available spare drive. Then, the data drive (flash drive, NVMe drive, or Flash Module Drive (FMD)) is
blocked. If a spare drive for data saving is not available and the data drive continues to be used at 100%
of write endurance, performance degradation or drive blockade might occur.
Replace the data drive while using the spare drive.
• Copy the data in the data drive to the spare drive and remove the data drive.
• Install a new data drive and copy the data to the new data drive from the spare drive.

2. When the rate of write endurance reaches 99% (*1), Dynamic Sparing (*2) starts to run.
Replace the data drive where Dynamic Sparing is complete.

*1: See Used Endurance Indicator in the ORM window ( MPC05-510) to check if the drive reaches
99% of the write endurance.
When a drive reaches 99% of the write endurance, SIM = 50bxyy (Flash drive End of life) or SIM
= 50cxyy (Flash module drive End of life) is reported.
*2: SIMs of Dynamic Sparing generated at 99% of write endurance of Flash Drives (SSDs), NVMe
Drives, and Flash Module Drives (FMDs):
ef2xyy (Drive blockade (Effect of Dynamic sparing normal end))
461xyy (Dynamic sparing start)
462xyy (Dynamic sparing normal end)

TRBL03-1290
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1300

3.32 Recovery Procedure for CFM Patrol Check Error (SIM = ffccxy)

START

Analyze the SSB log.

(See MPC05-250.)

Was SSB = 34ef output

No
around the same time as SIM = ffccxy
was output?

Perform recovery
Yes
actions according to ACC
Encryption CFMs (BM5E/BM6E/BM7E/BM7EA) and of SIM = ffccxy.
non-encryption CFMs (BM55/BM65/BM70/BM70A) are
mixed in the storage system. Check which of encryption
CFMs (BM5E/BM6E/BM7E/BM7EA) or non-encryption
CFMs (BM55/BM65/BM70/BM70A) should be installed
by seeing the delivery history or asking the customer.

Should
encryption CFMs
No
(BM5E/BM6E/BM7E/BM7EA) be
installed in the storage
system?
Yes
The CFM indicated by SIM = ffccxy is the The CFM not indicated by SIM = ffccxy is
non-encryption CFM (BM55/BM65/BM70/ the encryption CFM (BM5E/BM6E/BM7E/
BM70A). Replace the non-encryption CFM BM7EA). Replace the encryption CFM with
with the encryption CFM (BM5E/BM6E/ the non-encryption CFM (BM55/BM65/
BM7E/BM7EA). (See REP02-10-10.) BM70/BM70A). (See REP02-10-10.)

END

TRBL03-1300
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1310

This page is for editorial purpose only.

TRBL03-1310
Hitachi Proprietary DW850/DW900/DW1000
Rev.7 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1320

3.33 Recovery Procedure for CUDG Error (SIM = 760000)

START

Were SIM
= 30750x and SSB = 34ed Yes
output around the same time as SIM =
760000 was output?

Perform the maintenance

No
work according to “3.60 Recovery
Procedure When CFM Failure
Perform the maintenance Occurs (SIM = 30750x)”.
work according to ACC of
SIM = 760000.

TRBL03-1320
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1330

3.34 Procedure for responding to the product program expiration (SIM = 7ff7xx)
If this SIM is reported, the term of validity of the program product was lost.
About of which program product the term was lost, please refer to 7ff7xx of SIMRC02-120.

START

Is it required
to change a program product Yes
into the state where it can be
used again?
Installing program product.
No (See MAINTENANCE PC SECTION
“3.7 Setting up License Keys”)

END

TRBL03-1330
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1340

3.35 Procedure for responding to an excess of the allowed capacity (SIM = 7ff8xx)
If this SIM is reported, The capacity of the validity of a program product was exceeded.
About of which program product is excess of capacity, please refer to 7ff8xx of SIMRC02-120.

START

It is necessary to add capacity of Yes

program product?
Installing program product.
No (See MAINTENANCE PC SECTION
“3.7 Setting up License Keys”)

END

TRBL03-1340
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1350

3.36 Procedure for responding to the prerequisite program product expiration (SIM =
7ff9xx)
If this SIM is reported, A program product cannot be used by the term of validity of the premise program
product.
About whether it became impossible which program product to use, please refer to 7ff9xx of SIMRC02-120.

START

Is it required to change Yes

to the state which can use a program
product?
Installing premise program product (*1).
(See “System Administrator Guide”)
No

END

*1: About which program product will be the requisite, (See “System Administrator Guide”.)

TRBL03-1350
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1360

3.37 Recovery Procedure when Cable Connection Error Occurs (SIM = effbxx, effcxx,
effdxx, effexx)
3.37.1 Recovery Procedure when SAS Cable/NVMe Cable Connection Error Occurs (SIM
= effbxx, effdxx, effexx)
The recovery procedure when incorrect recognition of DB location is detected at the processing to
initialization on backend SAS/backend NVMe is as follows.
This SIM might occur by the CTL, DKB, ENC and other failures.
The NSW failure (REF code = effbxx), the Expander failure (REF code = effdxx) or the UNIT connection
cable order error (REF code = effexx) is reported (xx: SAS Port#/NVMe Port#) as the SIM of the failure
managed by each SAS Port/NVMe Port.
As a cause of the error, it is assumed that one of the following failures occurs in the reported SAS port/
NVMe port or in another SAS port/NVMe port of the opposite cluster.
If the SIM is generated at startup, the storage system does not change to the Ready status. The SAS port/
NVMe port might be blocked and more than one PDEV under the SAS port/NVMe port might be blocked.
By performing the recovery procedure described here, the storage system changes to the Ready status and the
SAS port/NVMe port blockade and the PDEV blockade are resolved.
When this troubleshooting is performed during the initial installation, check that the system configuration is
initialized after the recovery.

No. Assumed cause Details

1 SAS cable/NVMe cable is • Connected cluster is wrong.
connected with wrong ENC
Next DB CL1 CL2
(*1)
The DB CL1 CL2

• Connected with different ENCs between clusters.

The Next DB CL1 CL2

Next DB CL1 CL2

The DB CL1 CL2

• Connected with wrong DB.

Next DB CL1 CL2 CL1 CL2

The DB CL1 CL2 CL1 CL2

*1: See LOCATION SECTION “5.1 SAS Cable Diagram” for right connection.
(To be continued)

TRBL03-1360
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1370

(Continued from preceding page)

No. Assumed cause Details
2 SAS cable/NVMe cable is not As the number of set DBs and the number of actually recognized
connected or the number of DBs are different, SAS cable/NVMe cable is not connected or the
DBs is insufficient (*1) number of DBs is not enough.
3 Connection order of DBs is Because of wrong connection, the connection order of DB is
wrong (*1) switched.

The Next DB CL1 CL2

Next DB CL1 CL2

The DB CL1 CL2

4 Power is not supplied to DB There is any DB to which the power is not supplied.
5 The type of the connected DB The specified DB type (DBS2/DBS/DBL/DB60/DBF/DBN) is
is incorrect inconsistent with the DB type that is actually recosgnized.
6 SAS Ports/NVMe Port in both When DKB in both CL or ENC has failure and cannot access to DB.
CL are blocked
7 SAS cable/NVMe cable is See “SAS Cable/NVMe Cable Diagram” (LOC05-10) for right
connected to wrong port of connection.
ENC
*1:See LOCATION SECTION “5.1 SAS Cable Diagram” for right connection.
(To be continued)

TRBL03-1370
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1380

(Continued from preceding page)

No. Assumed cause Details
8 All Drives in the DB are All Drives in the DB are replaced.
replaced.
[Before restarting the Storage System/Before recovering DB power-
off]
DB-XX

A B C D

HDDXX-00 HDDXX-01 HDDXX-02 HDDXX-03

[After restarting the Storage System/After recovering DB power-off]

• All Drive locations in the DB are changed.
DB-XX

D C B A

HDDXX-00 HDDXX-01 HDDXX-02 HDDXX-03

• All Drives in the DB are changed.

DB-XX

E F G H

HDDXX-00 HDDXX-01 HDDXX-02 HDDXX-03

9 Failures other than stated The access to DB is abnormal due to the CTL/MP failures or other
above occur. failures.

TRBL03-1380
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1390

[Recovery procedure for SAS/NVMe cable connection failure]

START

No Is powering on at new
installation?

Yes
Confirm ENC# or CTL# from SIM Log.

Powering off the Storage System

(See INST01-05-40).

Is
effbxx (NSW failure) No
or effdxx (Expander failure) output
to the SIM Log?

Yes
Replace the indicated part with the
maintenance part

Perform new installation operation again

(See INST02-01-10).

Recurrence of the No
malfunction?

Yes
END

Is powering on the No
equipment?

Yes
4
(TRBL03-1430)
Is SSB = 00EC reported? No
(See MPC05-250.)
Confirm ENC# or CTL# from SIM
Yes Log.(*1)

T.S.D. call 1
(TRBL03-1400)

TRBL03-1390
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1400

Is any of
cf10xx/2140xx/cf88xx/cf20xx Yes
reported to SIM Log or any of SSB = ab70/f77c/
ab73/ab74 reported tor SSB Log?
(See MPC05-250)
T.S.D. call
No
Powering off the Storage System.
(See INST01-05-40).

Is effbxx (NSW failure) or No

effdxx (Expander failure) output to the SIM
Log?

Yes
Replace the indicated part with the maintenance part.

Are the SAS cables/

NVMe cables connected correctly No
to the ENC that is indicated as a failed part
according to ACC?
(See LOC05-10) Re-connect SAS cable/NVMe cable correctly.

Yes

Are the number and type of DBs No

correct? (See LOC02-60)
Install the correct number and type of DBs.

Yes

2
(TRBL03-1410)

TRBL03-1400
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1410

Is SSB = AB72, 0583 No

reported? (See MPC05-250.)

Yes

Is the Drive replaced while No

the power is off?

Yes
Return the replaced Drives to the
location before the power-off.

Is power supplied No
to all DBs?
Supply power to all DBs.
Yes

Powering on the Storage System

(See INST01-05-10).

Recurrence of the No
malfunction?

Yes END
Confirm ENC# from SIM Log.

Powering off the Storage System

(See INST01-05-40).

Perform ENC replacement operation.

Powering on the Storage System

(See INST01-05-10).

Recurrence of the No
malfunction?

Yes END

3
(TRBL03-1420)

TRBL03-1410
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1420

Is
effbxx (NSW failure) or Yes
effdxx (Expander failure) output to
the SIM Log?

No T.S.D. call
Confirm DKB# from SIM Log.

Powering off the Storage System

(See INST01-05-40).

Perform DKB replacement operation.

Powering on the Storage System

(See INST01-05-10).

Recurrence No
of the malfunction?

Yes
END
T.S.D. call

TRBL03-1420
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1430

Is DB installation No
performed?

Yes 5
Confirm ENC# or CTL# from SIM Log. (TRBL03-1440)

Is effbxx (NSW failure) or effdxx No

(Expander failure) output to the SIM Log?

Yes
Replace the indicated part with the
maintenance part.

Are the SAS

cables/NVMe cables connected No
correctly to the ENC that is indicated as a failed
part according to ACC? (See
LOC05-10) Re-connect SAS cable/NVMe cable in
installed DB correctly.
Yes

Are the number of DB

and DB type specified in Maintenance No
Utility the same as the ones of actually
connected DB? Reconnect the SAS cable/NVMe cable according
to the settings in Maintenance Utility. Then,
Yes remove the installed DBs and install correct DBs.

Confirm that power is supplied to the

installed DB and perform the DB installation
operation again.

Recurrence of the No
malfunction?

Yes END

T.S.D. call

TRBL03-1430
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1440

Is ENC No
replacement operation taken
place?
Yes 6
(TRBL03-1450)
Confirm ENC# or CTL# from
SIM Log.

Is SSB = AB72, 0583 Yes

reported?
Is the
No Drive in the pointed DB Yes
replaced while the power
is off? Power off the DB forcibly and return the
replaced Drive to the original location.
No
After that, restart the DB.

Is effbxx Yes
(NSW failure) or effdxx Yes Recurrence of the
(Expander failure) output to malfunction?
the SIM Log? Replace the indicated part with No
the maintenance part.
No
END

Are the SAS cables/

NVMe cables connected correctly No
to the ENC that is indicated as a failed part
according to ACC?
(See LOC05-10) Re-connect the SAS cable/
NVMe cable in ENC correctly.
Yes

Were SAS cable/ No

NVMe cable set up correctly? (*1)

Yes
Perform ENC dummy Perform ENC replacement
replacement operation. operation.

Recurrence of the No
malfunction?

Yes

T.S.D. call END

*1: When the replacement failed because of wrong connection of SAS cable/NVMe cable setting,
make recovery by replacement operation as the failure was not caused by ENC failure.

TRBL03-1440
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1450

Is DKB
replacement operation taken
No
place?
Yes
7
Confirm ENC# or CTL# from
SIM Log.
(TRBL03-1460)

Is SSB = AB72, 0583 Yes

reported? (See MPC05-260)
Is the
No Drive in the pointed DB Yes
replaced while the power is
off? Power off the DB forcibly and return the
replaced Drive to the original location.
No
After that, restart the DB.

Is
effbxx (NSW failure) Yes Yes Recurrence of the
or effdxx (Expander failure) output malfunction?
to the SIM Log? Replace the indicated part with
the maintenance part. No
No
END

Are the SAS

cables/NVMe cables connected No
correctly to the ENC that is indicated as a
failed part according to ACC?
(See LOC05-10) Re-connect SAS cable/NVMe
cable correctly.
Yes

Were SAS cable/NVMe No

cable set up correctly? (*1)

Yes
Perform DKB dummy Perform DKB replacement
replacement operation. operation.

Recurrence of the No
malfunction?

Yes
T.S.D. call END
*1: When the replacement failed because of wrong connection of SAS cable/NVMe cable setting,
make recovery by replacement operation as the failure was not caused by DKB failure. If not
recovered by the dummy replacement, perform the normal replacement.

TRBL03-1450
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1460

Is the Controller Board No

being installed?

T.S.D. call
Yes
Check ENC# or CTL# in the SIM
log.

Is
effbxx (NSW
failure) or effdxx (Expander Yes
failure) output to the
SIM log? Replace the indicated part with the
maintenance part.
No

Are the
SAS cables/NVMe
cables connected correctly No
to the ENC that is indicated as
a failed part according
to ACC? (See Connect the SAS cables/NVMe
LOC05-10) cables to the ENC correctly.

Yes

Perform the dummy replacement of

the DKB whose port is indicated by
SIM = effexx.
When multiple DKBs are
replacement targets, perform the
dummy replacement of all the DKBs.
(*1)

Recurrence of the No
malfunction?

END
Yes

T.S.D. call

*1: When the replacement fails due to the wrong connections of SAS cables/NVMe cables, perform
the dummy replacement as the recovery action because the DKB is not faulty. If the recovery by
the dummy replacement fails, perform the hardware replacement.

TRBL03-1460
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1470

This page is for editorial purpose only.

TRBL03-1470
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1480

3.37.2 Recovery Procefure when PCIe Cable Connection Error Occurs (SIM = effcxx)
This section describes the recovery procedure when the PCIe cable connection error was detected in the
initialization of the Channel Board Box (CHBB).
As a SIM for failure managed per DKC Slot, PCIe cable connection error (REF code =effcxx) is reported. (xx:
PECB #)
This SIM is reported once by switch package (SWPK) at the timing of detecting the PCIe cable connection
error.
Review the connection of the PECB other than PECB # indicated by SIM because multiple connection errors
might exist.
Any of the following errors might have occurred as a cause of this failure.

No. Assumed cause Details

1 PCP Port of the connection • PCP Port to be connected is reversed.
destination is incorrect. (*1)
CHBB
SWPK1 SWPK2
PCP PCP

Port1

Port2

Port1

Port2
DKC DKC
(SWPK1) (SWPK2)
1A

1B

2A

2B
PCIe Channel Board PCIe Channel Board

*1: Refer to INSTALLATION SECTION “[Link] Connecting PCIe Cables” for the correct
connection.
(To be continued)

TRBL03-1480
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1490

(Continued from preceding page)

No. Assumed cause Details
2 PCP of the connection • Connected to PCP Port of reverse SWPK.
destination is incorrect. (*1)
CHBB
SWPK1 SWPK2
PCP PCP

Port1

Port2

Port1

Port2
DKC DKC
(SWPK1) (SWPK2)

1A

1B

2A

2B
PCIe Channel Board PCIe Channel Board

• Slot1B and 2B are connected to PCP Port of reverse SWPK.

CHBB
SWPK1 SWPK2
PCP PCP
Port1

Port2

Port1

Port2
DKC DKC
(SWPK1) (SWPK2)
1A

1B

2A

2B
PCIe Channel Board PCIe Channel Board

*1: Refer to INSTALLATION SECTION “[Link] Connecting PCIe Cables” for the correct
connection.
(To be continued)

TRBL03-1490
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1500

(Continued from preceding page)

No. Assumed cause Details
3 CHBB of the connection • SWPK1 and SWPK2 are connected to different CHBBs.
destination is incorrect. (*1)
CHBB
SWPK1 SWPK2
PCP PCP

Port1

Port2

Port1

Port2
CHBB
SWPK1 SWPK2
PCP PCP

Port1

Port2

Port1

Port2
DKC DKC
(SWPK1) (SWPK2)

1A

1B

2A

2B
PCIe Channel Board PCIe Channel Board

*1: Refer to INSTALLATION SECTION “[Link] Connecting PCIe Cables” for the correct
connection.
(To be continued)

TRBL03-1500
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1510

(Continued from preceding page)

No. Assumed cause Details
4 The PCIe cable is not The PCIe cable is not connected to the PCIe Channel Board or PCP.
connected.
5 SWPK or PCP is not mounted. SWPK or PCP is not mounted on CHBB.
6 Power is not supplied to Power is not supplied to CHBB.
CHBB.

TRBL03-1510
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1520

[Recovery procedure for PCIe cable connection error]

START

Is power supplied to No
CHBB?
Power off the Storage System.
Yes (Refer to INST01-05-40).

Supply power to CHBB.

Power on the Storage System.

(Refer to INST01-05-10).

Recurrence of the No
malfunction?

Yes
END
Power off the Storage System.
(Refer to INST01-05-40).

Stop the power supply to CHBB.

Are SWPK
No
and PCB mounted correctly in
CHBB?
Mount SWPK and PCP correctly again.
Yes

Is the
PCIe cable connected to the No
PCIe Channel Board and PCP
correctly?
Connect the PCIe cable correctly again.
Yes

(TRBL03-1530)

TRBL03-1520
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1530

Is the PCIe cable No

connected to the correct position?
(Refer to INST02-10-170)
Connect the PCIe cable correctly again.
Yes

Supply power to CHBB.

Power on the Storage System.

(Refer to INST01-05-10).

Recurrence of the No
malfunction?

Yes

T.S.D. call 終了

TRBL03-1530
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1540

3.38 When Detecting Abnormal DB External Temperature (SIM = af7000, af7100)

START

Is DB power off SIM Yes Solve the problem of the

TRBL03-30
= ac50xx reported? Storage System environment.

No

Are multiple DBPS No

blinking?
Replace the blinking DBPS module.
Yes

Is the
No
Is or was the abnormal DB temperature
external temperature environment detected?
Yes
of the Storage System DB Yes
module abnormal?

No T.S.D. call END

Replace the blinking DBPS module. Solve the problem of the

Storage System environment.

Is the
DBPS failure SIM Yes
(af50xx, af51xx, af52xx)
detected?
No TRBL03-1680

Is the abnormal
No
DB external temperature
detected?

Yes

T.S.D. call END

TRBL03-1540
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1550

3.39 Response to the Detection of Abnormal DKCPS Input Voltage (SIM = af210x)(Use AC
input voltage)

START

Is the Controller Yes

Chassis CBSN?

Are
No multiple SIMs = Yes
af200x, af210x, af400x, and/or
fffa0x reported?

See “3.78 Recovery Procedure

No for Multiple Errors of DKCPS/BKM
in CBSN”.
Check that the cable of the PS having
an AC power input failure has no
abnormality.

Is
there a cable
abnormality? (e.g., Yes
cable is halfway insertied,
disconnected, or
Fix the cable abnormality, and check
faulty)
the status window.
No
Check the AC input voltage to the PS
having an AC power input failure. END
(See Figure 3-1.)

Is
the correct AC input Yes
voltage applied to the
PS? Replace the target DKCPS.
No (See REP02-15-10)
Check AC input voltage at the
distributor.
Is the target DKCPS No
recovered?
1 Collect Auto Dump.
Yes (See MPC05-50)
(TRBL03-1551)

END
T.S.D. call

TRBL03-1550
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1551

Is AC input Yes
voltage at the distributor
normality?
Check the location of the connected
No PDU for the warning target PS.
Perform the check of the power
supply equipment and the removal of
the cause part. Is the PDU to No
be replaced the Hitachi PDU?

Turn on the power of the distributor

Yes If the PDU is manufactured by
other than Hitachi, ask the customer
Are
to replace the PDU.
END hardware units
other than DW800 connected No
to PDU for the
replacement? Refer to the PDU manual and
perform the PDU replacement
Yes (See REP02-19-10)
Perform Power OFF of hardware
units other than DW800.
END
Refer to the PDU manual and
perform the PDU replacement.
(See REP02-19-10)

END

TRBL03-1551
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1560

[AC Input voltage check]

(1) Remove the cable of target PS.
(2) Measure AC input voltage at terminal of removed cables.

Figure 3-1 AC Input Voltage Check

CBLH1/CBLH2/CBLHN/CBLMH4
DKCPS1 DKCPS2

CBLH1/CBLH2/CBLHN/CBLMH4 Rear view

DKCPS
Voltage Check Point
Range of acceptable
AC Voltage: 200V through 240V

 

Cable

Cable

TRBL03-1560
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1570

CBSS/CBSL

DKCPS2

DKCPS1
CBSS/CBSL Rear view

DKCPS
Voltage Check Point
Range of acceptable
AC Voltage:
100V through 120V or 200V through 240V
 

Cable

Cable

CBXSS/CBXSL

DKCPS2

DKCPS1
CBXSS/CBXSL Rear view

DKCPS
Voltage Check Point
Range of acceptable
AC Voltage:
100V through 120V or 200V through 240V
 

Cable

Cable

TRBL03-1570
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1571

CBSN

DKCPS2

CBSN Rear view

DKCPS1

Voltage Check Point

DKCPS
Range of acceptable
AC Voltage:
200V through 240V
 

Cable

Cable

TRBL03-1571
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1580

DB60

DBPS1 DBPS2

DB60 Rear view

Voltage Check Point

Range of acceptable
AC Voltage: 200V through 240V
DBPS
 

Cable

Cable
DBF
DBPS1 DBPS2

DBF Rear view

Voltage Check Point

Range of acceptable
AC Voltage:
100V through 120V or 200V through 240V
 
DBPS

Cable

Cable

TRBL03-1580
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1590

DBS/DBL

DBS/DBL Rear view

DBPS1 DBPS2

Voltage Check Point

Range of acceptable
AC Voltage: 100V through 120V
or 200V through 240V
  DBPS

Cable

Cable

DBN

DBN Rear view

DBPS1 DBPS2

Voltage Check Point

Range of acceptable
AC Voltage: 200V through 240V

 
DBPS

Cable

Cable

TRBL03-1590
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1591

DBS2

DBS2 Rear view

DBPS1 DBPS2

Voltage Check Point

Range of acceptable
AC Voltage: 200V through 240V
 
DBPS

Cable

Cable

TRBL03-1591
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1600

3.40 Response to the Occurrence of Battery Warning (SIM = fffa0x)

START

Is the Controller Yes

Chassis CBSN?

Are
No
multiple SIMs = Yes
af200x, af210x, af400x, and/or
fffa0x reported?

See 3.78 Recovery Procedure

No for Multiple Errors of DKCPS/BKM
in CBSN .

Is the Controller Chassis Yes

CBXSS/CBXSL?

Are multiple SIMs = Yes

No
fffa0x reported?
Open the Maintenance Utility
window (See MPC02-260) and
No T.S.D. call
check the location of the BKM/
BKMF in which the target battery (Because the CTL blockade
and other batteries are installed. 1 needs to be forcibly executed)
(TRBL03-1601)

Is the Yes
Controller Chassis CBSS/
CBSL?
Replace the target BKM CBSS/
No CBSL: (See REP02-09-10)
Remove the target BKM/BKMF.
CBLH : (See REP02-08-20)
CBSN : (See REP02-08-380) END

Check that the plug of the battery

cable is inserted into the socket
correctly.

Is it inserted No
correctly?
Insert the plug of the battery cable
Yes into the socket.

Install the target BKM/BKMF.

CBLH : (See REP02-08-20)
CBSN : (See REP02-08-380)

2
(TRBL03-1602)

TRBL03-1600
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1601

Open the “Maintenance Utility” window (See

MPC02-260) and check the location of the
Controller Board in which the target battery
and other batteries are installed.

Block the target Controller Board.

(See REP02-04-10)

Remove the target Controller Board.

(See REP02-04-10)

Check that the plug of the battery cable is

inserted into the socket correctly.

No
Is it inserted correctly?

Insert the plug of the battery cable into the

Yes socket.

Install the removed Controller Board.

(See REP02-04-10)

Did the target battery Yes

recover?

No

Replace the target battery

CTLXSx battery: (See REP02-08-240)

Did the target battery Yes

recover?

No

T.S.D. call END

TRBL03-1601
Hitachi Proprietary DW850/DW900/DW1000
Rev.9.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1602

Did the target battery Yes

recover?

No
Replace the target battery BKM/
BKMF battery: (See REP02-08-10)

Did the target battery Yes

recover?

No END

T.S.D. call

TRBL03-1602
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1610

3.41 Recovery Procedure when a GUM Failure Occurs (SIM = aff1xx)

START

Is the
Maintenance PC connectable No
to the CTL in which the failure
occurs?

Yes
Connect the Maintenance PC to the CTL in Connect the Maintenance PC to the normal
which the failure has occurred. CTL.

Gather GUM Dumps (*1) Gather GUM Dumps (*1)

(See MPC05-50.) (See MPC05-50.)

See the MAINTENANCE PC SECTION See the MAINTENANCE PC SECTION

“3.26 Resetting GUM” to reset GUM of the “3.26 Resetting GUM” to reset GUM of the
failed CTL. failed CTL.

Connect the Maintenance PC to the normal Check the status of the Storage System.
CTL and check the statuses of the Storage
System.

Is the
Maintenance PC connectable No
1
to the CTL in which the failure
occurs? (TRBL03-1620)

Yes

No
Is there a blocked part?

Is SIM =
Yes Yes aff1xx reported again after the
GUM of the failed CTL was
reset?

1 No
(TRBL03-1620) Collect a Normal Dump. (*2)
(See MPC05-50.)

END
*1: Select “GUM” in the Auto Dump type selection.
Dump gathering may fail, but proceed to the next work.
*2: Regardless of the success or failure of the dump collection in (*1), collect Normal Dump while the
Maintenance PC is connected to the normal CTL.
After that, send both the dump collected in (*1) and the newly collected Normal Dump.
Also, when collecting Normal Dump, change the file name of the dump collected in (*1) to hdcp_
[Link] or others so that the dump name is not overwritten.
TRBL03-1610
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1620

Check the detailed data of SSB = f601 that

is output around the same time as the GUM
warning (aff1xx) (see [1] SSB Log in
MAINTENANCE PC SECTION 5.3.1 Log
Indication ).

Is 0x00ff00ff
displayed in XXXXXXXX No
in the detailed data of SSB
= f601? (*3)

Yes

Is any SIM
No other than SIM =
aff1xx reported after the GUM
of the failed CTL was
reset?

Yes

Is SIM = ffef00 or No
7d02xx reported?
Collect a Normal dump. (*2)
Yes

Perform dummy replacement (see See 2.3 Analyze by SIM Log .

REPLACEMENT SECTION 2.4 Replacing
a Controller Board ) of the CTL in which the
failure has occurred.

No
Normally ended?

Collect a Normal dump. (*2)

Yes
Collect a Normal dump. (*2) Replace the CTL in which the failure
has occurred with a new CTL (see
REPLACEMENT SECTION 2.4 Replacing
END a Controller Board ).

No
Normally ended?

Yes T.S.D. call

Collect a Normal dump.

END

TRBL03-1620
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1621

*1: Select GUM in the Auto Dump type selection.

Dump gathering may fail, but proceed to the next work.
*2: Regardless of the success or failure of the dump collection in (*1), collect Normal Dump while the
Maintenance PC is connected to the normal CTL.
After that, send both the dump collected in (*1) and the newly collected Normal Dump.
Also, when collecting Normal Dump, change the file name of the dump collected in (*1) to hdcp_
[Link] or others so that the dump name is not overwritten.
*3: Detailed data of SSB
+0x0 +0x4 +0x8 +0xC
00000000: 7b0a0311 0937ec39 01f60000 00a22800
00000010: 00000000 00004fe8 00004ee8 00000004
00000020: 00000000 000000ec a1390100 00000000
00000030: ff000000 1000ffec 00000000 00000000
00000040: 220f0091 01101802 ffff8180 00000000
00000050: 00000000 00000000 00000000 00000000
00000060: 40003200 ffffffff ffffffff ffffffff
00000070: 02010000 ffffffff 70120000 XXXXXXXX

TRBL03-1621
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1630

3.42 Recovery procedure when an alert notification failure occurs (SIM = 7d05xx)

START

Refer to the “Information” window of the MPC and check if

a SIM which needs an action exist.

Does a SIM which needs an No

action exist?

Yes
Take an action in accordance with ACC of the SIM.

Is the service personnel No

report set? (*1)

Yes
Check the following items set in the procedure in
MAINTENANCE PC SECTION “3.4.1 Setting up Email
Notification when Storage System Failures Occur”.
• Email Address
• IP address of Mail Server
• Account and Password of SMTP

Ask the customer to check the following.

• The Storage System service is Ready on the Storage
Device List of SVP.
• The test transmission is performed from SVP to the
maintenance center and the reporting function runs
correctly.

Does a setting error or No

trouble exist?

Yes
Correct the setting error and trouble.

Request the user to research if no error exists in the alert

notification setting (Refer to MAINTENANCE PC SECTION
“3.4 Alert Notifications”) and no trouble has occurred in the
SNMP/SMTP/SYSLOG/DNS server or network. (*2)

1 (TRBL03-1650)

*1: Check that Email Notice is set to Enable in the [Email] tab in the “Set Up Alert Notifications”
window (see MPC03-190).
TRBL03-1630
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1640

*2: A communication path through which the alert notification failed can be identified by referring to
Byte 44 in the associated SSB detailed data.
The SIM whose alert notification failed can be identified by referring to the associated SSB as
well.
For detailed SSB data, see the following table and output example.

No. Byte (Hex.) Item Meaning

① 40 - 42 Reference code of the SIM Example : 0x7d0a00  7d0a00
whose alert notification
failed
② 44 Communication path where 01 : email
the error occurred 02 : syslog
04 : snmp
③ 48 - 4d Date and time when the Written every byte in hexadecimal
SIM to notify the alert Add 1900 to year.
notification failure was Example : 7408030b 0936
generated Year : 0x74 (116) 2016
Month : 0x08 (8) August
Day : 0x03 (3) 3 days
Hour : 0x0b (11) 11 hour
Minute : 0x09 (9) 9 minutes
Second : 0x36 (54) 54 seconds
④ 5E - 5F Alert ID of the SIM whose Written in hexadecimal (little endian)
alert notification failed Example : 51f0  0xf051 (61521)

Example of associated SSB byte data output

+0x0 +0x4 +0x8 +0xC
00000000: 7408030c 01198c00 e033fcb6 eadc2857
00000010: 40d10c00 090328f4 000027f4 090362ff
00000020: 10000000 e4fa018c 00ff0000 e4fa2c80
00000030: 33e00000 0000ff8c 30e88e80 c8f290b6
00000040: 7d0a0000 01000000 7408030b 0936e000
00000050:①00000000②
00002000③00000000 000051f0
④
00000060: 00000000 00000000 00000000 00000000
00000070: 00000000 00000000 00000000 00000000

TRBL03-1640
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1650

Is the SIM detected No

again?

Yes
END

Is the maintenance No
work in progress?

Yes
Complete the maintenance in
progress first.

Is the SVP No
connected?

Yes
Complete the operation by the
SVP and close the browser.

Is AutoDump No
running?

Yes
Wait until AutoDump is
completed.

Reboot GUM.
(Refer to MAINTENANCE PC
SECTION “3.18 Reboot GUM”)

Is the SIM detected No

again?

Yes

T.S.D. call END

TRBL03-1650
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1660

3.43 Response to a loss of the GUM audit log and the warning issuance (unsent audit log
occurrence) (SIM = 7d03xx, 7d04xx)
Recovery procedure when the GUM audit log is lost and the GUM audit log waning is issued (unsent audit
log occurs) is shown below.

START

Export the audit log from the Maintenance Utility

“Audit Log Setting” window. (See MPC03-760.)

Perform the test transmission of Syslog from the

Maintenance Utility “Audit Log Setting” window. (See
MPC03-790.)
If the test transmission fails, solve the problem
according to NOTICE described in MPC03-790.

Did the Yes

transfer to the Syslog server
fail?
No
Research the customer
END environment.

TRBL03-1660
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1670

3.44 Response when UPS warning occurs (SIM = aff0xx)

START

Reset the UPS interlock mode.

Is a UPS or remote No (Set the normal mode when [Link] the details
adapter connected? of UPS interlock mode, refer to MAINTENANCE PC
SECTION “3.12 Edit UPS Mode”)
Yes

Has power Yes

outage of the AC input
occurred?

No Does the AC input No

recover?
If power outage has occurred,
Yes recover the AC input.

Is the UPS interlock Yes

cable removed?
Remove the UPS interlock cable and
No insert it again.

Cancel the alarm inaccordance with

theUPS manual

Is SSB = f602 No
displayed?

Yes Yes Is the UPS warning

SIM displayed?
Is there
any SSB = f602 whose No No
value of Byte43 is 0x17?
(*1)
END
Yes T.S.D Call

END

*1: To view the detailed information of the SSB “f602” by using Maintenance Utility, click on the alert
ID (link text) on the row of the error code “f602” in the [SSB] tab in the [Internal Alerts (DKC)]
window (see MAINTENANCE PC SECTION “3.21 Alert Display”).
When the value of Byte43 in the detailed data of SSB “f602” is 0x17, the UPS warning is resolved.

TRBL03-1670
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1680

3.45 Response to the Occurrence of DBPS Warning (SIM = af50xx, af51xx, af52xx)

START

Has more
than one piece of PS
Yes warning (SIM= af50xx/af51xx/
af52xx) or abnormal AC input (SIM=
af60xx/af61xx/af62xx)
Check the power supply to DBPS.
occurred?
• Is the connection between DBPS and PDU
correct?
• Is the connection between PDU and the No
switchboard correct?
• Is the PDU circuit breaker turned on? Replace the target PS
• Is the power supply from the switchboard (Refer to REP02-15-10)
normal?

Did the target DBPS Yes

Is there any problem with No recover?
the power supply?
No
Yes
Fix the power supply problem. No Is AC input voltage at
the PS OK? (Refer to Figure 3-1.)

No Abnormal DBPS Input Yes

Did the target DBPS
recover? Voltage (TRBL03-440)

Yes Replace the ENC#1

(Refer to REP02-16-10)
END

Did the target DBPS Yes

recover?

No
Replace the ENC#2
Check if there is any problem with the cable (Refer to REP02-16-10)
of the PS warning target.

No Did the target DBPS

Is there any problem with No recover?
the cable?
Yes
Yes 1
Correct the problem with the cable and (TRBL03-1690)
check the status display.
END

END

TRBL03-1680
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1690

Inform the Technical Support Division that

the Drive Box needs to be replaced.

Get approval to power off the storage system

from the customer.

Replace the Drive Box.

(See REP02-17-10)

Has the DBPS

No
warning disappeared from
Maintenance Utility?
Collect Auto Dump.
Yes (See MPC05-50)

END T.S.D. call

TRBL03-1690
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1700

3.46 Response to the Detection of Unmounted Channel Board (SIM = 3c9600)

When there are no Channel Boards mounted at the time of start-up, SIM RC = 3c9600 is issued. In this case,
please install Channel Boards.

START

Confirm the number of Channel Boards

in the system.

Install Channel Boards. (INST03-05-10)

END

TRBL03-1700
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1710

3.47 Procedure for Responding to the Firmware Replacement Failure due to Cache High
Load (SIM = eb8xxx, eb9xxx, efexxx)
Since the write pending data on the Cache is large, the Drive Firmware replacement was suspended. To
restart the Firmware replacement, reduce the Cache load and execute it.

START

Open the MPC monitor

(See MPC06-10)

Is Cache Write Pending No

Rate 50% or more?

Yes

Ask the customer to adjust the Cache

load so that Cache Write Pending Rate
is less than 50%.

Is Cache Write Pending No

Rate 49% or less?

Yes

Update the firmware using the same

version as the suspended firmware. (*2)

Is the Update Firmware No

completed normally?
Perform the maintenance in accordance
Yes with FIRMWARE SECTION “4.1
Recovery Procedure in Online Menu
Was Selected” (*1)

END

*1: When the same failure occurs repeatedly, contact the Technical Support Division.
*2: If the update is performed with the firmware version before replacement instead of the suspended
one, the drive firmware version might not be consistent.

TRBL03-1710
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1720

3.48 Recovery Procedure for the SAS PORT Temporary Failure (SIM = cf11xx)
The SAS PORT temporary failure (SIM = cf11xx) indicates that the SAS PORT is partially blocked (*1).
When the SAS PORT blockade (SIM = cf12xx) is not output, the SAS PORT is usable, but the early
replacement is recommended.

START

Is SIM = cf12xx Yes

TRBL03-30
output? (*2)

No

Are multiple Yes

SIMs = cf11xx with same “xx”
output?
Perform the recovery action for the
No latest SIM = cf11xx.

1
(TRBL03-1730)

*1: There are four paths in the SAS Cable and this indicates that one or more of them is blocked. If
four paths are all blocked, it is the SAS PORT blockade and (SIM = cf12xx) is output.
*2: When SIM = cf12xx is output, replace the part pointed by SIM = cf12xx first and recover the SAS
PORT
When SIM = cf11xx has occurred in the different SAS PORT from SIM = cf12xx, the recovery
processing of SIM = cf11xx is required after recovering SIM = cf12xx. The part xx of SIM =
cf11xx and SIM = cf12xx indicates the SAS PORT number.

TRBL03-1720
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1730

Replace the ENCs pointed by SIM ACC

in the displayed order.
(See REP02-16-10.)

Is the SAS
Yes
PORT of the maintenance target
recovered?

No
Replace the DKB or CTL pointed by
SIM ACC. (See REP02-14-10 for DKB,
REP02-04-10 for CTL.)

Is the SAS Yes

PORT of the maintenance target
recovered?

No
Replace the SAS Cable between ENC
and ENC, DKB and ENC or CTL and
ENC pointed by SIM ACC.
(See REP02-20-10.)

Is the SAS Yes

PORT of the maintenance target
recovered?

No Is SIM = cf11xx output in Yes

2
the other SAS PORT?
(TRBL03-1720)
T.S.D Call
No

END

TRBL03-1730
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1740

3.49 Procedure for Responding to the Flash Module Drive Firmware Version Warning (SIM
= 50f000)
The Flash Module Drive Firmware installed in the Storage System is not the latest version. Update the Flash
Module Drive to the latest Firmware in accordance with the following flow.
Be careful that if you perform the high-speed LDEV Format without updating it to the latest version, it
becomes the low-speed format.

START

Check the Firmware version of the FMD

installed in the Storage System.
(See MPC05-1060.)

Perform the Firmware replacement of

the FMD.
(Refer to FIRM01-10)

Is the Firmware No
update of the FMD completed
normally?

Yes
Take an action in accordance
END with FIRM04-90

TRBL03-1740
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1750

3.50 Recovery Procedure When DKC Warning Occurs (SIM = 7d0900)

START

SIM “DKC Warning” occurred

Has SIM = aff10x “GUM No

Warning” occurred?

Yes
Is I/O operation available No
from host computer?
Execute “3.41 Recovery
Procedure when a GUM Failure
Yes Go to “2.1.4 Lighting up ALARM
Occurs (SIM = aff1xx)”
(red) of Storage System LED”, and
• CBXSS/CBXSL/CBSS/CBSL/ then perform the procedure from .
CBSN (2U): Execute “3.10.1 In the procedure, make sure to
Recovery Procedure When an collect dumps before maintenance
Internal LAN Failure Occurs (SIM replacement in the order shown in the
= 7d01xx) (2U Controller Chassis)” flowchart.
• CBLH (4U): Execute “3.10.2 If you collect dumps after dummy
Recovery Procedure When an replacement or maintenance
Internal LAN Failure Occurs (SIM replacement, the GUM trace
= 7d01xx) (4U Controller Chassis)” volatilizes.

NOTE: There is no problem if SIM = 7d0900 is output when performing the offline firmware
update.
Furthermore, there is no problem if the Storage System status of the “Maintenance
Utility” window becomes Failed.
The Storage System status changes to Ready when the offline firmware update is
completed.

TRBL03-1750
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1760

3.51 Recovery Procedure When an MP Error Occurs (SIM = 7d06xy)

START

SIM “MP error” occurred

Has SIM “Processor No

blocking” occurred?

Is the
Yes GUM version less than No
88-08-15/00 or 93-07-
Perform the maintenance 22/00?
according to ACC of SIM “Processor Collect the DUMP (See
Yes MPC05-50.) and contact the
blocking”. (See “2.3 Analyze by SIM
Log”.) Technical Support Division.

(In the case of SVP, ask a user to perform the procedure.)

Is the (In the case of SVP,

free space on HDD of Yes ask a user to perform
the Maintenance PC/SVP less the procedure.)
than 20 GB?
Increase the free space on HDD to at
least 20 GB (recommended value).
(In the case of SVP, No
ask a user to perform
the procedure.)
Restart the Maintenance PC/SVP.

Log into the Maintenance Utility of

the CTL that output SIM.

Was the hardware status Yes

END
displayed?

No (In the case of SVP, ask a user to perform the procedure.)

Check whether the Storage System meets all the conditions (1) to (3).
(1) The Storage System is registered on Maintenance PC /SVP.
(2) The virus detection program is installed in Maintenance PC /SVP.
(3) “C:\Mapp\wk” (*1) is included in the scan targets of the real-time virus scan
of the virus detection program.

Are all the conditions Yes

(1) to (3) met?

No 2
(TRBL03-1770)
1
(TRBL03-1770)
*1: “C:\Mapp” is the installation directory of Storage Navigator.
If you specified an installation directory other than “C:\Mapp ”, replace “C:\Mapp\wk” with the
directory that you specified.
TRBL03-1760
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1770

2 1
(In the case of
SVP, ask a user
to perform the
procedure.)
Exclude “C:\Mapp\wk” (*1) from
the real-time virus scan of the virus
detection program.

Log into the Maintenance Utility of

the CTL that output SIM.

Was the hardware status Yes

displayed?
Log into the Maintenance Utility of
No END the CTL that output SIM.

No Was the hardware status

displayed?
Reboot the GUM of the CTL that
output SIM in the Maintenance Yes
Utility. (See MAINTENANCE PC
SECTION “3.18 Reboot GUM”) If
you cannot log into the Maintenance
Utility, see the MAINTENANCE PC
SECTION “3.26 Resetting GUM” to
reset GUM of the failed CTL.

Log into the Maintenance Utility of

the CTL that output SIM.

Was the hardware status No

displayed?

Yes Collect the DUMP (See

MPC05-50.) and contact the
Technical Support Division.
END

*1: “C:\Mapp” is the installation directory of Storage Navigator.

If you specified an installation directory other than “C:\Mapp ”, replace “C:\Mapp\wk” with the
directory that you specified.

TRBL03-1770
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1780

3.52 Reclaiming the Control Pages Inside the DP-VOL

There are following two methods to reclaim the control pages inside the DP-VOL(s).
Select either method according to the condition.

Condition Method
All of the following are met: 1 or 2
• Capacity Saving is disabled.
• The volume(s) is already backed up or can be backed up.
• The LDEV can be formatted or deleted. (The TC/UR/GAD/SI/VM ex-S-VOLs
can also be used as a backup.)
All of the following are met: 2
• Capacity Saving is disabled.
• The volume(s) is not backed up yet or cannot be backed up.

NOTE: Method 1 is usually a way quicker than Method 2 to complete.

By using Method 2, you can keep DR configuration during this process.

(Method 1) Formatting or decreasing LDEV

(1) Delete the TC/UR/GAD pairs with 4 TB or less.
(2) Take a backup of the target LDEVs if you have not at this point.
(3) If you select to format the target LDEV(s), set System Option Mode 867 to ON before to do so.
(See MAINTENANCE PC SECTION “5.8 Setting System Option Mode”.)
(4) Format or delete the target LDEV(s).
NOTE: If the firmware version is earlier than 88-02-01-x0/xx and the LDEVs are attached
to the server through Hitachi Storage Advisor Embedded (HSAE), perform the
procedure through HSAE (see Hitachi Storage Advisor Embedded Guide “Deleting
a volume”). To start HSAE, specify the URL in the Web browser (see the table in
“2.7.3 Starting the Maintenance Utility Window by Specifying IP Address of CTL” in
MAINTENANCE PC SECTION).
(5) If you set System Option Mode 867 to ON in the step (3), set it to OFF after formatting the
LDEV(s).
(6) Restore the data from the backup.

TRBL03-1780
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1781

(Method 2) Reclaiming zero pages

(1) Set System Option Mode 755 to OFF if it is ON. (See MAINTENANCE PC SECTION “5.8
Setting System Option Mode”.)
(2) Execute Reclaim Zero Pages with CCI or Hitachi Device Manager – Storage Navigator.
When using CCI:
(a) Run the raidcom modify ldev command with the -status discard_zero_page option specified.
(See Command Control Interface Command Reference.)
(b) Run the raidcom get ldev command to check that ZPD is not displayed as OPE_TYPE. (See
Command Control Interface Command Reference.)
When using Hitachi Device Manager – Storage Navigator:
(a) In the “Reclaim Zero Pages” window, fill in [Task Name] and click [Apply]. (See Provisioning
Guide.)
(b) In the [Virtual Volumes] tab of the “View Pool Management Status” window, check [V-VOL
Management Task] to confirm that [Status] is blank. (See Provisioning Guide.)
(3) If you set System Option Mode 755 to OFF on the step (1), set it to ON.

TRBL03-1781
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1790

3.53 Recovery Procedure When SWPK is Blocked (SIM = 2154xx)

START

Are SIM = 21540x No

and 21541x output in the same time
zone?
Recover the blockade in accordance with
Yes ACC of SIM = 2154xx.

Is it sure that the

ALM/RDY LEDs (LOC03-300) No
on both CHBBPS1 and CHBBPS2
are not lit in green? Replace SWPK1 and SWPK2 with the
maintenance parts. (See REP02-25-10)
Yes
Check the following and recover the power supply to CHBB.
• Is the connection between CHBBPS and PDU correct?
• Is the connection between PDU and the switchboard correct?
• Is the PDU circuit breaker turned on?
• Is the power supply from the switchboard normal?

Check the above and if no error has occurred, replace CHBBPS1

and CHBBPS2 with the maintenance parts. (See REP02-15-340)

Are the ALM/RDY

LEDs (LOC03-300) on both No
CHBBPS1 and CHBBPS2 lit in
green?
T.S.D Call
Yes
Recover SWPK1 and SWPK2 by dummy
replacement. (See REP02-25-10)

Was the SWPK recovery No

completed normally?

Yes T.S.D Call

END

TRBL03-1790
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1800

3.54 Recovery Procedure When the Initial Installation Fails

START

Was the message 4590E or No

4468E displayed?

Was the message No

Yes
4466I displayed?

Yes
END

CTL2 What is the CTL number Nothing

displayed in the message?

CTL1

4 5 6
(TRBL03-1830) (TRBL03-1840) (TRBL03-1850)

Is the message No
4590E?

Yes
The CE mode check failed. Reboot
the Maintenance PC, and then
perform this procedure again.

No
Normally ended?

Yes

END T.S.D Call

CTL1 What is the CTL number CTL1, CTL2

displayed in the message?

CTL2

1 2 3
(TRBL03-1810) (TRBL03-1810) (TRBL03-1820)

TRBL03-1800
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1810

The following hardware failures are assumed.

Replace the suspicious failed parts, and then
perform this procedure again.
[Suspicious failed parts]: In order of priority
1. DIMM of CTL1
2. CTL1
3. LANB1 (4U only)

Recurrence of the No
malfunction?

Yes

T.S.D Call END

The following hardware failures are assumed.

Replace the suspicious failed parts, and then
perform this procedure again.
[Suspicious failed parts]: In order of priority
1. DIMM of CTL2
2. CTL2
3. LANB2 (4U only)
4. LANB1 (4U only)

Recurrence of the No
malfunction?

Yes

T.S.D Call END

TRBL03-1810
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1820

Check the following.

• IP addresses of MPC and DKC
• Network connection between MPC and DKC
• Connected to the maintenance port
• Storage System types of MPC and DKC are
identical
• The Storage System is turned on (the
POWER LED on the front of the Storage
System lights up in green)

Did the setting No

and connection have any
problems?
The following hardware failures are assumed.
Yes Replace the suspicious failed parts, and then
perform this procedure again.
Correct the setting and connection
[Suspicious failed parts]: In order of priority
problems.
1. LANB1 (4U only)
2. CTL1
Then perform this procedure again.

END
Recurrence of the No
malfunction?

Yes

T.S.D Call END

TRBL03-1820
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1830

See MAINTENANCE PC SECTION

“3.16 Edit or Confirm System
Parameters” and check that the jumper
(CEMD) for initial installation is
enabled.

No
Is the CE mode enabled?

Turn off the Storage System.

Yes
Wait until the Storage System is turned
off and the POWER LED on the front of
the Storage System changes to amber.

See “1. Enable the jumper used for

initial installation” in INSTALLATION
SECTION “5.2.4 New Installation” and
perform this procedure again.

Yes Recurrence of the

malfunction?
The following hardware failures are assumed.
Replace the suspicious failed parts, and then No
perform this procedure again.
[Suspicious failed parts]: In order of priority
END
1. CTL1

Recurrence of the No
malfunction?

Yes

T.S.D Call END

TRBL03-1830
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1840

See MAINTENANCE PC SECTION

“3.16 Edit or Confirm System
Parameters” and check that the jumper
(CEMD) for initial installation is
enabled.

No
Is the CE mode enabled?

Turn off the Storage System.

Yes
Wait until the Storage System is turned
off and the POWER LED on the front of
the Storage System changes to amber.

See “1. Enable the jumper used for

initial installation” in INSTALLATION
SECTION “5.2.4 New Installation” and
perform this procedure again.

Yes Recurrence of the

malfunction?
The following hardware failures are assumed.
Replace the suspicious failed parts, and then No
perform this procedure again.
[Suspicious failed parts]: In order of priority
END
1. CTL2

Recurrence of the No
malfunction?

Yes

T.S.D Call END

TRBL03-1840
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1850

See MAINTENANCE PC SECTION

“3.16 Edit or Confirm System
Parameters” and check that the jumper
(CEMD) for initial installation is
enabled.

No
Is the CE mode enabled?

Turn off the Storage System.

Yes
Wait until the Storage System is turned
off and the POWER LED on the front of
the Storage System changes to amber.

See “1. Enable the jumper used for

initial installation” in INSTALLATION
SECTION “5.2.4 New Installation” and
perform this procedure again.

Yes Recurrence of the

malfunction?
The following hardware failures are assumed.
Replace the suspicious failed parts, and then No
perform this procedure again.
[Suspicious failed parts]: In order of priority
END
1. CTL1
2. CTL2

Recurrence of the No
malfunction?

Yes

T.S.D Call END

TRBL03-1850
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1860

3.55 Recovery Procedure When the Part Installation Error Occurs (SIM = ffd400)
SIM = ffd400 notifies that the part, that is not embedded in the configuration, is inserted into the Storage
System.
In this case, removing the part from the Storage System is required by identifying the part type/location in
accordance with the following procedure.

If the removal target part is incorrect, the Storage System might have the significant damage.

START

No
Is “SSB=156F” issued?

Yes T.S.D. call

2

See MAINTENANCE PC SECTION

“[1] SSB Log” in “5.3.1 Log Indication”
to confirm the detailed information of
“SSB=156F”.

Is the Bit array

indicated by XXXXXXXX
No
and YYYYYYYY in the “Content -
SSB” window other than
“0”? (*1)
T.S.D. call

Yes
See the location correspondence table
(*2) to confirm the part insertion
location.

Is the location
confirmed by the location
No
correspondence table displayed in the
(Take notes the location)
“Maintenance Utility”
windowg?

Yes
1
T.S.D. call (TRBL03-1870)

TRBL03-1860
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1870

Turn off the Storage System.

(See INST01-05-40).

Remove the part in the location

where the notes taken. Be careful that
the Storage System might have the
significant damage if the removal part is
incorrect.

Turn on the Storage System.

(See INST01-05-10).

No
Is “SIM=ffd400” issued?

Yes END

2
(TRBL03-1860)

*1: SSB detailed information

+0x0 +0x4 +0x8 +0xC
00000000: 720a0914 32149f04 156f0000 00aa2000
00000010: 00000000 000004dd 00000000 00000004
00000020: 00000000 0000009f 156f0000 00000000
00000030: 00000000 0000ff9f 00000000 00000000
00000040: 00000000 00000000 XXXXXXXX YYYYYYYY
XXXXXXXX: CFM detection location (leftmost one bit is bit location 0 of CFM location)
YYYYYYYY: PECB detection location (leftmost one bit is bit location 0 of PECB location)
*2: Location correspondence table
• CFM location correspondence table
Bit location 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Part location (CFM-xx) 10 11 20 21 Unused
Bit location 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Part location (CFM-xx) Unused

• PECB location correspondence table

Bit location 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Part location (Slot-xx) 1A 1B 1C 1D 1E 1F Unused
Bit location 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Part location (Slot-xx) 2A 2B 2C 2D 2E 2F Unused

TRBL03-1870
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1880

3.56 Recovery Procedure When Flash Module Drive Initialization Fails (SIM = 4c4xxx,
4c5xxx)
This SIM is output if Flash Module Drive (FMD) initialization fails. The following triggers are considered.
• Spinning up
• Creating parity group
• Formatting parity group
• PSON
• Adding FMD
• Allocating spare

The cause of failing Flash Module Drive (FMD) initialization is a defect of individual FMD or FMD might
be involved in other failures. Recover it in accordance with the following recovery procedure.

START

Are CTL/DKB/ENC all No

“Normal”? (*1)
Maintain the CTL, ENC, and DKB
Yes that are not “Normal” in accordance
with the maintenance priority in “2.4
Failures of Multiple Parts”.

Are CTL/DKB/ENC all No

“Normal”? (*1)

Yes T.S.D Call

What is the
[Utilization] status of the Spare/Free
FMD indicated by “SIM =
4c4xxx/4c5xxx”?
No (Free)
DATA Is it Spare?

1 Yes (Spare) 2
(TRBL03-1890) (TRBL03-1890)
3
(TRBL03-1900)
*1: It might be involved in the CTL/DKB/ENC failure. Recover the CTL/DKB/ENC before starting
the recovery processing.

TRBL03-1880
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1890

Is the LDEV
No available in the parity group
that the FMD indicated by “SIM =
4c4xxx/4c5xxx” belongs to?

Yes

Can you delete

the data in the parity group No
that the FMD indicated by “SIM =
4c4xxx/4c5xxx” belongs to?

Yes

Are all LDEVs

blocked in the parity group No
that the FMD indicated by “SIM =
4c4xxx/4c5xxx” belongs to?

3
Yes (TRBL03-1900)

Delete the parity group. (Refer to MAINTENANCE

PC SECTION “[Link] Deleting Parity Group
(Without Safety Checks)”.

No
Was the deletion successful?

Yes
2

Perform dummy replacement of the FMD indicated

by “SIM = 4c4xxx/4c5xxx”.

Did the
FMD indicated by SIM = No
4c4xxx/4c5xxx change to
“Normal”?
Yes 3
(TRBL03-1900)
END (*1)
*1: If the parity group is deleted, create a parity group and format it as needed.

TRBL03-1890
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1900

Replace the FMD specified by “SIM =

4c4xxx/4c5xxx” with a maintenance part.

Did the
FMD indicated by SIM = No
4c4xxx/4c5xxx change to
“Normal”?
Yes T.S.D Call

END (*1)

*1: If the parity group is deleted, create a parity group and format it as needed.

TRBL03-1900
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1910

3.57 Recovery Procedure When the Panel Switch Warning (SIM = af4d0x)
SIM = af4d0x is reported when it is detected that the main switch on the panel of the Controller Chassis is
pressed and held for 60 seconds or more.

START

Did you press and

hold the main switch on the panel Yes
for 60 seconds or more to turn off
the power?

No
The SIM might occur while updating
DKCMAIN firmware. Wait until firmware
update is complete.

Check whether both CTL1 and CTL2 on END

DKC detected panel switch warning (SIM =
af4d00, af4d01).

Are both SIM No

= af4d00 and SIM = af4d01
reported?

Yes
There is a possibility that the Storage Replace the failed Controller Board (CTL1
System will be shut down (planned for SIM = af4d00 or CTL2 for SIM =
shutdown) (*). af4d01). (See REP02-04-10)
Make the customerʼs Storage System ready
to be shut down.

T.S.D Call END

*: The following actions might lead to a planned shutdown of the Storage System.
• Removing or attaching a bezel: The main switch on the Controller Chassis might be held down
by contact with the bezel.
• Removing a CTL: The main switch might be held down by a CTL failure.

TRBL03-1910
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1920

3.58 Recovery Procedure When Processor Is Blocked (SIM = 3073xx)

START

Is “SIM = cf880x” Yes

(CTL blockade) output in the same time
zone?
Perform the maintenance in accordance
No with “3.62 Recovery Procedure for CTL
Blocking (SIM = cf880x)”.

Is “SIM = cf8a0x”
(CTL blockade due to CTL Yes
interconnect path failure) output in
the same time zone? Perform the maintenance in accordance with
ACC of “SIM = cf8a0x”.
No
END
Is the
model CBLH1/CBLH2/ No
CBLHN/CBLMH4/CBSN1/
CBSN2?
Yes

Is “SIM =
Yes
3073xx” output for all MPs shown in
(*1)?
No

Is “SIM = No
3073xx” output for all MPs shown in
(*2)?

Yes

2
1
(TRBL03-1931)
(TRBL03-1930)

*1: “xx” output in “SIM = 3073xx” is MP#. The range of MP# is shown in the following table.
CBLH1 CBLH2 CBLHN CBSN1/CBSN1E CBSN2/CBSN2E/
CBLMH4
00~05 00~09 00~0D 00~05 00~0F
20~25 20~29 1C~29 20~25 20~2F
*2: “xx” output in “SIM = 3073xx” is MP#. The range of MP# is shown in the following table.
CBLH1 CBLH2 CBLHN CBSN1/CBSN1E CBSN2/CBSN2E/
CBLMH4
06~0B 0A~13 0E~1B 06~0B 10~1F
26~2B 2A~33 2A~37 26~2B 30~3F
TRBL03-1920
Hitachi Proprietary DW850/DW900/DW1000
Rev.9.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1930

Is “SSB
= 32fd” output in the time No
zone when “SIM-3037xx” was
output?
Yes
Replace CTL to which MP that output Replace CTL to which MP pointed by first
“SSB=32fd” belongs. output “SIM=3073xx” belongs.
Replace the CTL to which the MP pointed by
the first output “SSB=32fd” belongs if the SSB
is output for both CTLs.

Was CTL replacement No

completed normally?
Recover it in accordance with “2.2.1 Error Recovery
Yes
Procedure when Removing/Inserting CTL”.

Does the unrecovered No

(blocked) MP remain in CTL of the
opposite cluster?
END
Yes (Replacing CTL of the opposite cluster is not
required.)
Replace CTL of the opposite cluster.

Was CTL replacement No

completed normally?
Recover it in accordance with “2.2.1 Error Recovery
Yes
Procedure when Removing/Inserting CTL”.

END

TRBL03-1930
Hitachi Proprietary DW850/DW900/DW1000
Rev.5 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1931

Perform the maintenance in accordance

with ACC of “SIM = 3073xx”.

Is the storage system No

recovered?

Yes No
Is “SIM = fff40x” output
at about the same time?

Yes

END Perform the maintenance in T.S.D Call

accordance with ACC of “SIM =
fff40x”.

TRBL03-1931
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1940

3.59 Response to a Loss of the DKC Audit Log (SIM = 180000)

START

Execute LAN Check

(See DIAG04-210.)

No
Normally ended?

Yes
No Is SIM = 7d01xx
reported?

Yes
Execute the recovery procedure for a
failure when SIM = 7d01xx occurs.
(CBXSS/CBXSL/CBSS/CBSL/CBSN
(2U): See “3.10.1 Recovery Procedure
When an Internal LAN Failure Occurs
(SIM = 7d01xx) (2U Controller
Chassis)”
CBLH (4U): See “3.10.2 Recovery
Procedure When an Internal LAN
Failure Occurs (SIM = 7d01xx) (4U
Controller Chassis)”)

Yes Is SIM = 180000

detected again?

Collect dump. No
(See MPC05-50.)
END

T.S.D Call

TRBL03-1940
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1950

3.60 Recovery Procedure When CFM Failure Occurs (SIM = 30750x)

If the Storage System is powered off when its CFM is in abnormal state, customer data might be
lost. To recover from CFM failure, follow the steps below.
If you check firmware versions from Maintenance Utility when both CFM-1 and CFM-2 are
blocked, the version acquisition error occurs.

START

Is the
Storage System CBXSS/ No
CBXSL/CBSS/CBSL/
CBSN?

Yes Yes Is either of CFM-10 or

CFM-20 normal?

Is either of CFM-1 or Yes

2 (TRBL03-1952) No
CFM-2 normal?

No 5 1
(TRBL03-1951)

Recover the Storage System in

accordance with ACC of SIM =
30750x.

Are all the

CFMs other than Yes
those for which the maintenance
operation was performed
normal?
END
No

No Are you
performing maintenance on
VSP G130?

1 Yes
(TRBL03-1951)
Perform “3.75 Recovery
Procedure When a CFM Failure
Occurs in the CTL Other Than the
CTL Removed for Maintenance (for
VSP G130)”.

TRBL03-1950
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1951

Replace the abnormal CFMs so that all CFMs are in the normal state. (See REP02-10-10)
If both the CFMs and the CTLs are blocked, replace the CFMs first, and then the CTLs. (See REP02-04-10)
If SIM = cf88xx is reported when you replace the CTLs, see 3.62 Recovery Procedure for CTL Blocking (SIM =
cf880x) .
If the storage system is CBSN and SSB = 34ec was output around the same time as SIM = 30750x was output,
check whether the combination of the CTL FRU and the blocked CFM FRU is correct (see INST01-03-110). If
it is incorrect, replace the CTL or CFM with an appropriate FRU. (SSB = 34ec is output only in the power-on
procedure.)
NOTE: To replace both CFM-1 and CFM-2, check the checkbox for Forcibly run without safety checks at the
time of the first CFM replacement.

Is SIM =
661000 or SIM = 661001 Yes
reported at the same period
of time?
Collect the Dump (See
No MPC05-50) and contact the
Check the maintenance priority of Technical Support Division.
the failure parts according to Table
2-3 and Table 2-4 in 2.4 Failures of
Multiple Parts .

Is there
any failure part that has No
a higher priority than
firmware?

Yes
Perform the maintenance work for
the failure part that has a higher
priority.

To update the firmware online, use the installation media for the SVP, which comes with the Storage System and is
owned by the customer. (See FIRMWARE SECTION 3.3.1 Updating Firmware of the Storage System .)
• The firmware update to be performed here aims to save the firmware of the version running in the Storage
System to the CFM after the replacement.
• Since this is the update to the same version of the firmware running in the Storage System, a performance is not
affected by rebooting MP described in FIRM03-150 (Table 3-3 ).
• Set the Update Type to Online (default) and the Reboot pattern to By 1/4 (default).
• Check the checkbox for Forcibly upload the firmware. in Step 5 in FIRMWARE SECTION 3.3.1 Updating
Firmware of the Storage System .

Is the firmware update No

completed normally?

Yes T.S.D Call

6
(TRBL03-1955)
TRBL03-1951
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1952

Analyze the SSB log.

See (MPC05-250)

Is the storage system VSP No

E990 or VSP E1090?

Yes
Did
you perform
maintenance procedure No
including CTL removal and insertion
or the power-on operation
just before?

Yes

Is the blocked CFM No

CFM-11 or CFM-12?

Yes

Was SSB =
34ed output around the same No
time as SIM = 30750x was
output?

Yes 3
Start Maintenance Utility and check the (TRBL03-1954)
status of the CTL indicated by the reference
code of SIM = 30750x.

Is the status of the Yes

CTL any of Warning, Failed, or
Blocked?

No 4
Perform the dummy replacement of the CFM indicated (TRBL03-1953)
by ACC of SIM = 30750x. (See REP02-10-10)

Normally No
ended?
Replace the CFM with a maintenance part.
Yes (See REP02-10-10)

Regardless of success or failure of the

CFM replacement (regardless of whether the
CFM is restored or not), perform the dump
collection (see MPC05-50), and contact the
Technical Support Division.

TRBL03-1952
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1953

Perform the dummy replacement of the CTL

indicated by the reference code of SIM =
30750x. (See REP02-04-10)

Normally No
ended?
Perform the dummy replacement of the CTL
Yes again and also replace the CFM indicated by
ACC of SIM = 30750x with a maintenance
part in the process of removing and inserting
the CTL. (See REP02-04-10)

Regardless of success or failure of the CTL

replacement (regardless of whether the CTL is
restored or not), perform the dump collection (see
MPC05-50), and contact the Technical Support
Division.

TRBL03-1953
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1954

Is the storage system No

CBSN?

Yes

Was SSB =
34ec output around
the same time as SIM = No
30750x was output? (SSB = 34ec
is output only in the power-
on procedure.)
5
(TRBL03-1950)
Yes
Check whether the combination of
the CTL FRU and the blocked CFM
FRU is correct (see INST01-03-110).
If it is incorrect, replace the CTL or
CFM with an appropriate FRU.

Power off the storage system, and

then power on it.

Is the
storage system in the No
Ready status without any
failure?

Yes Perform the recovery

procedure in TRBL02-40.

END

TRBL03-1954
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1955

Is the storage system No

CBSN?

Yes

Was SSB =
34ec output around
the same time as SIM = No
30750x was output? (SSB = 34ec
is output only in the power-
on procedure.)
END

Yes
Power off the storage system, and
then power on it.

Is the
storage system in the No
Ready status without any
failure?

Yes Perform the recovery

procedure in TRBL02-40.

END

TRBL03-1955
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1960

3.61 Recovery Procedure for Differential Area Blocking (SIM = 4d1xyy)

This SIM indicates that the pair differential area is blocked caused by a hardware error. Recover it in
accordance with the following procedure. Note that, when resynchronizing the pair next time, all the data of
the primary volume is copied to the secondary volume.

START

Is the SIM
reported which indicates No
a hardware error in the
volume?

Yes
Recover the error by following
the recovery procedure of the SIM
indicating the hardware error.

Does the volume No

belong to either of TC/UR/GAD/SI/
VM pair?

END
Yes

Is the SIM reported No

which indicates a pool error in the
volume?

Yes
Recover the error by following
the recovery procedure of the SIM
indicating the pool error.

1
(TRBL03-1970)

TRBL03-1960
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1970

Is
the SIM reported which No
indicates a blocked LDEV in
the volume?
Yes
Recover the error by following the recovery
procedure of the SIM indicating the blocked
LDEV in the volume.

Did a pinned track No

occur outside the user area in the
volume?

Yes
Recover the error by following the recovery
procedure for a pinned track for each P.P.

Is
the SIM reported which No
indicates an error of the pair in
the volume?
Yes
Recover the error by following the recovery
procedure for the error of the pair.

Is the TC/UR/GAD pair No

suspended?

Yes END
Resynchronize the pair.

Is the pair resynchronization No

successful?
Delete the pair, and then recreate it.
Yes

END

TRBL03-1970
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1980

3.62 Recovery Procedure for CTL Blocking (SIM = cf880x)

NOTE: The top ACC means the ACC displayed at the top of the list in the Alert Detail
window of Maintenance Utility.

START

Are
both of the
following met?
Yes
・SIM = 3075xx is reported.
・CFMs are blocked in the other
CTL than the blocked
CTL. Replace the CFMs first according to “3.60
Recovery Procedure When CFM Failure Occurs
No
(SIM = 30750x)”.
Does the
top ACC of “SIM =
cf880x” (including another “SIM
Yes
= cf880x” that is output within 20 minutes
before or after the SIM) instruct
you to replace DIMM Perform the maintenance procedure according to
(40Axxxxx)? ACCs of “SIM-RC = cf880x”, which instructs you to
replace DIMM in its top ACC.
No

Was “SIM =
cf8c0x” (CTL power failure) output Yes
within 20 minutes after “SIM =
cf880x”? Perform the maintenance procedure according to
ACCs of “SIM-RC = cf8c0x”.
No
Does
No the top ACC of “SIM-RC =
cf880x” instruct you to replace CTL (ACC =
408xx000 or 408xx100)?

Yes

Is “SIM-RC =
cf8a0x” (CTL blockade due to CTL Yes
interconnect path failure) generated in
the same time period?

No

Replace with the maintenance part in accordance Perform the maintenance procedure according to
with ACC of “SIM-RC = cf880x”. ACCs of “SIM-RC = cf8a0x”.

1
(TRBL03-1981)

TRBL03-1980
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1981

Did the CTL blockade No

recover after replacing the CTL with the
maintenance part?

Yes Perform the recovery procedure in

accordance with TRBL02-260.

END

TRBL03-1981
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-1990

3.63 Recovery Procedure when the Configuration Backup Fails (SIM = 7d0bxx)
If the configuration information is changed by setting operations during the execution of the automatic
backup, the backup is stopped, and then executed again after completion of the configuration information
change. Therefore, the backup cannot be complete while setting operations are performed continuously. If the
backup remains incomplete, the SIM = 7d0bxx is reported.
<Confirming the normality after performing the recovery procedure>
Verify the success of the recovery procedure by making sure that the SIM = 7d0bxx has not been reported for
more than two days after the following procedure is performed.

START

Is any SIM
Yes
other than SIM = 7d0bxx
reported?
Perform the recovery procedure for the failure
No specified in the reported SIM.

END
Is the SSB = 0x33e4 Yes
reported?

No
In the Controller Chassis window of Maintenance In the Controller Chassis window of Maintenance
Utility, select the [CTL] tab and check the CTL Utility, select the [CFM] tab and check the CFM
status. status.

1
(TRBL03-2000)
No
Is the status “Normal”?

Replace the CFM that indicates the error. (See

REPLACEMENT SECTION “2.10 Replacing a
Yes
Cache Flash Memory (CFM)”.)

END Is the
period when no setting
Yes
operation is performed one hour or
more a day? (Ask the
T.S.D Call customer.)

No
Ask the customer to have the period no setting
operation is performed for one hour or more a day.

END
TRBL03-1990
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2000

No
Is the status “Normal”?

Recover the CTL that indicates the error. (See

Yes “3.62 Recovery Procedure for CTL Blocking
(SIM = cf880x)”.)

END
Is the SSB = 0x33e7 No
reported?

Yes Is a quite
recent backup date is
Perform [GUM reboot] from displayed in [Latest backup] in the No
Maintenance Utility of the “Download Configuration Backup”
CTL that output the SIM. (See window of Maintenance
MAINTENANCE PC SECTION Collect the dump.(*2)
Utility? (*1)
“3.18 Reboot GUM”.)
Yes Release the system lock forcibly
because the system lock might
remain for some reason. (See
TRBL02-530.))

Yes Is the system unlocking

successful?

Is END No
the [GUM reboot] No
processing completed T.S.D Call
normally?
Press the [LAN-RST] switch of the CTL
Yes indicated by SIM to reset GUM. (See
MAINTENANCE PC SECTION “3.26
Resetting GUM”.)

END

*1: For the timing of the automatic backup of the configuration information, see MAINTENANCE PC
SECTION “3.28 Obtaining Configuration Information Backup”.
*2: If the maintenance personnel performed maintenance work with the Maintenance PC on the day
before the occurrence of the SIM, collect the Rapid Dump by using the Maintenance PC used by
him or her. (See MPC05-50.)
If the maintenance personnel did not perform maintenance work on the day before the occurrence
of the SIM, or if you are not sure about it, ask the customer to collect the Normal Dump by using
the dump tool on the SVP (customerʼs PC) used for managing the storage system that reported the
SIM.

TRBL03-2000
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2010

3.64 Response to the Detection of SWPK Temperature Warning (SIM = af46xx)

START

Is the external Yes

temperature alarm (SIM = af120x)
detected?

“3.14 Response to the Occurrence of External Temperature

No
Warning or Alarm (SIM = af110x, af120x)”

Is the external Yes

temperature warning (SIM = af110x)
detected?

“3.14 Response to the Occurrence of External Temperature

No
Warning or Alarm (SIM = af110x, af120x)”

Does the SIM of the No

CHBBFAN warning (RC = af4c0x)
exist?
Replace the SWPK.
(See REP02-25-10)
Yes
Replace the CHBBFAN concerned.
(See REP02-26-10)
Does the SIM of the Yes
abnormal temperature (RC = af46xx)
exist?

T.S.D Call
No

END

TRBL03-2010
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2020

3.65 Response to the Occurrence of CHBBFAN Warning (SIM = af4c0x)

START

Open the “Maintenance Utility” window

(See MPC02-260) and check the
location of the target CHBBFAN.

Does the screw (blue) fixing No

the target CHBBFAN tighten?
Tighten the screw (blue) to fix.
Yes

Did failed parts Yes

recover?

No

Replace the target CHBBFAN.

(See REP02-26-10)

Did failed parts Yes

recover?

No
Replace the SWPK installing the target
CHBBFAN.
(See REP02-25-10)

Did failed parts Yes

recover?

No

T.S.D. call END

TRBL03-2020
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2030

3.66 Response to the Occurrence of CHBBPS Warning (SIM = af4a0x)

START

Is the
abnormal CHBBPS input Yes Abnormal CHBBPS Input
voltage (SIM = af4b0x) Voltage (TRBL03-2050)
reported?

No

Has the
CHBBPS warning occurred Yes
in both CHBBPS1 and
CHBBPS2? Collect Auto Dump.
No (See MPC05-50)

Check the location of the CHBBPS

which reported SIM = af4a0x in the
“Maintenance Utility” window. T.S.D. call

1
(TRBL03-2040)

TRBL03-2030
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2040

Replace the target CHBBPS.

(See REP02-15-10)

Did the target CHBBPS Yes

recover?

No

Is AC input voltage
No Abnormal CHBBPS Input
at the PS OK?
Voltage (TRBL03-2050)
(Refer to Figure 3-2.)

Yes
Replace the SWPK1
(See REP02-25-10)

Did the target CHBBPS Yes

recover?

No
Replace the SWPK2
(See REP02-25-10)

Did the target CHBBPS Yes

recover?

No
Collect Auto Dump.
(See MPC05-50) END

T.S.D. call

TRBL03-2040
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2050

3.67 Response to the Detection of Abnormal CHBBPS Input Voltage (SIM = af4b0x)

START

Check AC input voltage for

CHBBPS of the CHBBPS warning
target. Refer to Figure 3-2.

Check AC input voltage at the

distributor.

Is AC input
Yes
voltage at the distributor
normality?
Check the location of the connected
No PDU for the warning target PS.
Perform the check of the power
supply equipment and the removal of
the cause part.
Is the PDU to be No
replaced the Hitachi PDU?
Turn on the power of the distributor
If the PDU is manufactured
Yes by other than Hitachi, ask the
END customer to replace the PDU.

Are hardware
units other than DW850 No
connected to PDU for the
replacement?

Yes

Perform Power OFF of hardware units Refer to the PDU manual

other than DW850. and perform the PDU
replacement
(See REP02-19-10)
Refer to the PDU manual and perform
the PDU replacement.
(See REP02-19-10)
END

END

TRBL03-2050
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2060

[AC Input voltage check]

(1) Remove the cable of target PS.
(2) Measure AC input voltage at terminal of removed cables.

Figure 3-2 AC Input Voltage Check

CHBB
CHBBPS2

CHBBPS1
CHBB Rear view

Voltage Check Point

Range of acceptable
AC Voltage: 200V through 240V

 

Cable

Cable

TRBL03-2060
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2070

3.68 Recovery Procedure When the CHBB Firmware Update Occurs (SIM = afa0xx,
afa1xx, afa2xx)

START

No
Is the SIM = afa0xx output?

Yes
Wait for up to 15 minutes after the
occurrence of SIM = afa0xx, and then
check for SIMs again.

No
Is the SIM = afa1xx output?

Yes No
Is the SIM = af44xx output?
Perform the dummy replacement for
restoration as follows:
For xx = 00~07, replace the SWPK1.
Yes
For xx = 10~17, replace the SWPK2.
Perform the maintenance work
according to the ACC of the SIM =
af44xx.
Is the SWPK restoration No
completed normally?

Yes
Wait for up to 5 minutes after the
completion of the dummy replacement,
and then check for SIMs again.

Is the SIM = afa2xx output No

after the restoration?

Yes

END T.S.D. call

TRBL03-2070
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2080

3.69 Recovery Procedure When an Incorrect CFM Type or a Shortage of CFM is detected
(SIM = fe030x)

START

Is “SIM = 30750x” No
reported and is the problem left
unsolved?

Yes Does the type

Yes
of installed CFMs match the
Perform the maintenance work according to configuration definition
ACC of “SIM = 30750x”. (*1)?
(See “3.60 Recovery Procedure When CFM
No
Failure Occurs (SIM = 30750x)”.)
Replace CFMs (see REP02-10-10) so that the CFM
type matches the configuration definition (*1).

END

Is there any blocked CFM No

after the replacement?

Yes END

Does the number

Yes
of installed CFMs match the
configuration definition
(*1)?
No
Replace (add) CFMs (see REP02-10-10) so that the
number of installed CFMs matches the configuration
definition (*1).

Is there any No
blocked CFM after the replacement
(addition)?

Yes END

Replace the blocked CFM with a CFM of the same

type (see REP02-10-10).

Is there any blocked CFM No

after the replacement?

Yes END

T.S.D. call

*1: Information displayed in the [CFMs] tab in the “Controller Chassis” window of Maintenance
Utility
TRBL03-2080
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2090

3.70 Procedure for Version Downgrade from the Configuration Using HSAE Server
If the firmware version downgrade is suppressed with Function ID = 04:15, ask the customer to perform the
following CCI operations. Then, retry the firmware update.

1. From all the servers of Hitachi Storage Advisor Embedded (HSAE), identify the servers whose status
[STS] is “DGG1”.

The following is the example of the rmawk command output.

raidcom get host_grp -allports -key server -I2 | rmawk @5-ne:N -a @5-ne:SRVID
exe="raidcom get server -server_id @5 -key opt -I2 & echo -----"
For “-I”, specify the CCI instance number.

Output results
The following example shows the command output for the server whose ID is 6.
SRV_ID : 6
NAME : RM_TEST
STS : DGG1
PROTOCOL : FC
OS : LINUX/IRIX
OS_OPT :
-----
SRV_ID : 7
NAME : RM_TEST1
STS :
PROTOCOL : FC
OS : LINUX/IRIX
OS_OPT :
-----

2. Delete all “DGG1” servers.

The following is a command example when deleting the server whose ID is 6.

raidcom delete server -server_id 6 -request_id auto

TRBL03-2090
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2100

3.71 Recovery Procedure When the GUM Failure Occurs (SIM = 7d00xx)

START

Is “SSB = 33e1”
output approximately at No
the same time as “SIM =
7d00xx”?
Is “SSB = 33e2”
Yes output approximately at No
Replace the CTL specified by the the same time as “SIM =
ACC. (See REPLACEMENT 7d00xx”?
SECTION “2.4 Replacing a
1
Controller Board”.) Yes
(TRBL03-2110)
The SVP connection certificate is
damaged. Check whether the SVP
Is the CTL No can connect to the storage system.
replacement completed (*1)
successfully?

Yes
Can the SVP connect to Yes
END
the storage system? (The SVP
END
connection
certificate is
No
already restored
Collect dumps. Replace the CTL specified by the automatically.)
(See MPC05-50) ACC. (See REPLACEMENT
SECTION “2.4 Replacing a
Controller Board”.)

T.S.D. call
Is the CTL No
replacement completed
successfully?

Yes

Can the SVP connect to No

the storage system?
Collect dumps.
Yes (See MPC05-50)

END
T.S.D. call

*1: In the “Maintenance Utility” window, confirm that the storage system is in the “Ready” status.
Then, start the service of the storage system on Storage Device List on the SVP, and check that
the storage system status becomes “Ready”. If the configuration does not include the SVP, start the
service of the storage system on Storage Device List on the Maintenance PC, and then check that
the storage system status becomes “Ready”.

TRBL03-2100
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2110

1 Frames surrounding operations show

that the operations are to be performed
by the customer at your request.

Is “SSB=33e3” output No
approximately at the same time as
“SIM=7d00xx”?

Yes Is “SSB=33ec” output No

approximately at the same time as
“SIM=7d00xx”?
The Web server certificate file is
restored to the default file, Ask the Collect dumps.
customer whether the Web server Yes (See MPC05-50)
certificate is updated. (*1)

2
(TRBL03-2111) T.S.D. call

Is the Web server Yes

certificate updated?

No Retry the Web server certificate

update. (See MPC03-1010)

END

*1: Update the Web server certificate in the “Update Certificate Files” window of Maintenance Utility.
(See MPC03-1010)

TRBL03-2110
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2111

Reboot the GUM.

(See MAINTENANCE PC SECTION
“3.18 Reboot GUM”)

Is the “SIM=7d00xx” output Yes

after the GUM reboot?
Replace the CTL specified by the ACC.
(See REPLACEMENT SECTION “2.4
No Replacing a Controller Board”.)

END
Is the CTL No
replacement completed
successfully?
Collect dumps.
Yes (See MPC05-50)

END T.S.D. call

TRBL03-2111
Hitachi Proprietary DW850/DW900/DW1000
Rev.5 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2120

3.72 Recovery Procedure When the SAS CTL Failure Is Detected (SIM = cf13xx)

The storage system reporting this SIM may have a serious failure. Collect a dump and contact
the technical support immediately.

START

Collect a dump and contact technical

support.

Technical support will tell you an action

plan.

END

TRBL03-2120
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2130

3.73 Recovery Procedure for Cache Area Failure (SIM = fff40x)

START

Is “SIM = Yes
cf880x” output at about the
same time?

No Perform the maintenance

according to “3.62 Recovery
Procedure for CTL Blocking (SIM =
cf880x)”.
Is “SIM = Yes
3073xx” output at about the
same time?

No Perform the maintenance

according to “3.58 Recovery
Procedure When Processor Is
Blocked (SIM = 3073xx)”.
Is SIM = ffcd0x output Yes
in about the same time?

No Perform the maintenance

work according to “3.25 Isolation
Procedure for Failed Part in CACHE
Collect dumps (see
Volatilization (SIM = ffe700, ffeb00,
MAINTENANCE PC SECTION
ffcd0x, ffcfyx, 610002)”.
“5.2 Dump”), and contact T.S.D. (*1)

TRBL03-2130
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2140

3.74 Recovery Procedure When a CFM Failure Occurs in the CTL Other Than the Failed
CTL to Be Replaced
1. Replace the failed CTL with a replacement part.
2. Connect the Maintenance PC to the CTL that has a CFM failure (not the failed CTL), and then log in to
Maintenance Utility.
To log in to Maintenance Utility, specify the IP address of the CTL directly from the browser (see
MAINTENANCE PC SECTION 2.7.3 Starting the Maintenance Utility Window by Specifying IP
Address of CTL).
3. Make a note of the set contents in the following setting windows of Maintenance Utility.
<Setting windows of Maintenance Utility (see MAINTENANCE PC SECTION) >
3.1 System Information Setting
3.3 User Administration
NOTE: Ask the customer whether the backup of the user account information is available. If
it is available, the user account information can be restored from the backup.
3.4 Alert Notifications
3.5 Time Setting
3.6 Network Setting
3.8 Audit Log Settings
3.12 Edit UPS Mode
3.13 Edit Login Message
3.14 Select Cipher Suite
4. Log out from Maintenance Utility connected to the CTL that has a CFM failure.
5. Connect the Maintenance PC to the replaced CTL, and then log in to Maintenance Utility.
To log in to Maintenance Utility, specify the IP address of the CTL directly from the browser (see
MAINTENANCE PC SECTION 2.7.3 Starting the Maintenance Utility Window by Specifying IP
Address of CTL).
6. Make the same settings in the windows shown in Step 3 as the set contents that you made a note of.
If the customer has updated the Web server certificate, ask him or her to update it again.
7. Log out from Maintenance Utility.
8. Replace the failed CFM with a maintenance part (see TRBL03-1950).
If the CTL containing the replaced CFM is failed, also replace the CTL with a maintenance part.
9. Even when you have not performed the firmware update in Step 8, execute the firmware update (see
FIRMWARE SECTION 3. Update Firmware ) with the checkbox for Forcibly upload the firmware.
checked in Step 5 in FIRMWARE SECTION 3.3.1 Updating Firmware of the Storage System .

TRBL03-2140
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2150

3.75 Recovery Procedure When a CFM Failure Occurs in the CTL Other Than the CTL
Removed for Maintenance (for VSP G130)
Perform the following recovery procedure when a CFM failure occurs in the CTL other than the CTL
removed for maintenance (for VSP G130).

When CTL1 is removed, perform “3.75.1 Recovery Procedure for a CFM Failure in CTL2 When CTL1 Is
Removed for Maintenance”.
When CTL2 is removed, perform “3.75.2 Recovery Procedure for a CFM Failure in CTL1 When CTL2 Is
Removed for Maintenance”.

TRBL03-2150
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2151

3.75.1 Recovery Procedure for a CFM Failure in CTL2 When CTL1 Is Removed for
Maintenance
1. Checking the GUM set contents and applying them to the CFM
(1) Connect to the GUM in the CTL2 that is not removed and start Maintenance Utility.
(2) Make a note of the set contents in the following setting windows of Maintenance Utility.
<Setting windows of Maintenance Utility (see MAINTENANCE PC SECTION)>
3.1 System Information Setting
3.3 User Administration
NOTE: Ask the customer whether the backup of the user account information is available. If
it is available, the user account information can be restored from the backup.
3.4 Alert Notifications
3.5 Time Setting
3.6 Network Setting
3.8 Audit Log Settings
3.12 Edit UPS Mode
3.13 Edit Login Message
3.14 Select Cipher Suite
(3) Set the date and time to apply the GUM set contents to the CFM.
See MAINTENANCE PC SECTION 3.5.1 Setting Synchronization Information and perform
Steps 1 through 3.
When NTP servers are used, check the checkbox for [Synchronize immediately], and then click
[Apply].
When NTP servers are not used, adjust the date and time according to the time of operation if
necessary (adjustment is not always necessary), and then click [Apply].
• If the error codes 31862-200021 and 31862-200022 are displayed, go to Step (4).
• If the operation ends normally, go to 2. Replacing the failed CFM with a maintenance part .
• If the operation ends abnormally, collect dumps and contact the Technical Support Division.
(4) If the error codes 31862-200021 and 31862-200022 are displayed in Step (3), connect to the GUM
in the CTL1 and reboot the GUM in the CTL1 twice to apply the set contents to the GUM in the
CTL1. Then, go to Step (5).
(5) Connect to the GUM in the CTL1 and start Maintenance Utility.
Then, check if the set contents are the same as those you took a note of in Step (2). If the set
contents are the same, go to 2. Replacing the failed CFM with a maintenance part. If the set
contents are different, collect dumps and contact the Technical Support Division.

TRBL03-2151
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2152

2. Replacing the failed CFM with a maintenance part

Perform the procedure in REPLACEMENT SECTION 2.10 Replacing a Cache Flash Memory (CFM) .
NOTE: After the CFM replacement, SIM = 7d0a00/7d0a01 (GUM version warning) might
occur. That is caused due to the replacement work and there is no problem. Go to Step
3.
3. Reboot the GUM in the CTL1 (not the CTL2 in which the failed CFM was replaced in Step 2) and
release the system lock.
Then, reboot the GUM in the CTL2 in which the failed CFM was replaced in Step 2 and release the
system lock.
See MAINTENANCE PC SECTION 3.18 Reboot GUM and 3.17 Force Release System Lock .
NOTE: • Even if the System Unlocked status is displayed on Maintenance Utility, perform
the system lock release.
• After the GUM reboot, SIM = 7d0800 (Failed to recover GUM configuration
information in CTL1) might occur. That is caused due to the replacement work and
there is no problem.
4. Execute the firmware update (see FIRMWARE SECTION 3. Update Firmware ) with the checkbox for
Forcibly upload the firmware. checked in Step 5 in FIRMWARE SECTION 3.3.1 Updating Firmware
of the Storage System .

TRBL03-2152
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2153

3.75.2 Recovery Procedure for a CFM Failure in CTL1 When CTL2 Is Removed for
Maintenance
1. Checking the GUM set contents and applying them to the CFM
(1) Connect to the GUM in the CTL1 that is not removed and start Maintenance Utility.
(2) Make a note of the set contents in the following setting windows of Maintenance Utility.
<Setting windows of Maintenance Utility (see MAINTENANCE PC SECTION)>
3.1 System Information Setting
3.3 User Administration
NOTE: Ask the customer whether the backup of the user account information is available. If
it is available, the user account information can be restored from the backup.
3.4 Alert Notifications
3.5 Time Setting
3.6 Network Setting
3.8 Audit Log Settings
3.12 Edit UPS Mode
3.13 Edit Login Message
3.14 Select Cipher Suite
(3) Set the date and time to apply the GUM set contents to the CFM.
See MAINTENANCE PC SECTION 3.5.1 Setting Synchronization Information and perform
Steps 1 through 3.
When NTP servers are used, check the checkbox for [Synchronize immediately], and then click
[Apply].
When NTP servers are not used, adjust the date and time according to the time of operation if
necessary (adjustment is not always necessary), and then click [Apply].
• If the error codes 31862-200021 and 31862-200022 are displayed, go to Step (4).
• If the operation ends normally, go to 2. Replacing the failed CFM with a maintenance part .
• If the operation ends abnormally, collect dumps and contact the Technical Support Division.
(4) If the error codes 31862-200021 and 31862-200022 are displayed in Step (3), connect to the GUM
in the CTL2 and reboot the GUM in the CTL2 twice to apply the set contents to the GUM in the
CTL2. Then, go to Step (5).
(5) Connect to the GUM in the CTL2 and start Maintenance Utility.
Then, check if the set contents are the same as those you took a note of in Step (2). If the set
contents are the same, go to 2. Replacing the failed CFM with a maintenance part. If the set
contents are different, collect dumps and contact the Technical Support Division.

TRBL03-2153
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2154

2. Replacing the failed CFM with a maintenance part

Perform the procedure in REPLACEMENT SECTION 2.10 Replacing a Cache Flash Memory (CFM) .
NOTE: After the CFM replacement, SIM = 7d0a00/7d0a01 (GUM version warning) might
occur. That is caused due to the replacement work and there is no problem. Go to Step
3.
3. Reboot the GUM in the CTL2 (not the CTL1 in which the failed CFM was replaced in Step 2) and
release the system lock.
Then, reboot the GUM in the CTL1 in which the failed CFM was replaced in Step 2 and release the
system lock.
See MAINTENANCE PC SECTION 3.18 Reboot GUM and 3.17 Force Release System Lock .
NOTE: • Even if the System Unlocked status is displayed on Maintenance Utility, perform
the system lock release.
• After the GUM reboot, SIM = 7d0801 (Failed to recover GUM configuration
information in CTL2) might occur. That is caused due to the replacement work and
there is no problem.
4. Execute the firmware update (see FIRMWARE SECTION 3. Update Firmware ) with the checkbox for
Forcibly upload the firmware. checked in Step 5 in FIRMWARE SECTION 3.3.1 Updating Firmware
of the Storage System .

TRBL03-2154
Hitachi Proprietary DW850/DW900/DW1000
Rev.8 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2160

3.76 Recovery Procedure When Media Sanitization Ends (SIM = 4e4xxx, 4e6xxx, 4e8xxx)
The SIMs that are output when Media Sanitization ends are shown. For details, see THEORY OF
OPERATION SECTION “2.16.3 Checking Result of Erase”.

TRBL03-2160
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2170

3.77 Recovery Procedure for Transmitted data abnormality between MP and GUM (SIM =
14200x)

START

Perform dummy replacement of the

CTL indicated by “SIM = 14200x”.
(See REP02-04-10)

Was dummy No
replacement completed
normally?

Yes
Collect the Dump
(See MPC05-50)

Is the “SIM = 14200x” Yes

reported again?

No T.S.D. call

END

NOTE: When SIM = 14200x is output, the completion of the cancellation of the dump
collection by Log Dump Tool (event ID 22) is reported in the Windows Event Log on
the SVP, but there is no problem.

TRBL03-2170
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2180

3.78 Recovery Procedure for Multiple Errors of DKCPS/BKM in CBSN

START

Is the Controller Yes

Chassis CBSN?

No Does the CTL have a Yes

failure?

No Replace the CTL.

Are there
multiple errors of SIM = Yes
af200x, af210x, af400x,
and fffa0x?

No
No Is any of SIM =
af2000, af2100, af4000, and
fffa0 reported?
Troubleshooting for multiple
errors of DKCPS/BKM in the CBSN
Controller Chassis is shown here. Yes
Troubleshoot according to SIMs.
No Is any of SIM =
af2001, af2101, af4001, and
fffa1 reported?

1 Yes
(TRBL03-2190)
T.S.D. call

TRBL03-2180
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2190

Is SIM = af210x Yes

reported?

No
2
6
(TRBL03-2200)

Is SIM = af200x Yes

reported?

No
3
7
(TRBL03-2220)

Is SIM = af400x Yes

reported?

No
4
8
(TRBL03-2220)

Is SIM = fffa0x Yes

reported?

No
5
9
(TRBL03-2230)

END

TRBL03-2190
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2200

Check that the cable of the PS having

an AC power input failure has no
abnormality.

Is
there a cable
abnormality? (e.g., cable Yes
is halfway insertied,
disconnected, or Fix the cable abnormality, and check
faulty) the status window.
No
Check the AC input voltage to the PS
having an AC power input failure. 6
(See Figure 3-1.)
(TRBL03-2190)

Is
the correct AC input Yes
voltage applied to the
PS?
Replace the target DKCPS.
No (See REP02-15-10)
Check AC input voltage at the
distributor.
Is the target DKCPS No
recovered?
10
Yes T.S.D. call
(TRBL03-2210)

6
(TRBL03-2190)

TRBL03-2200
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2210

10

Is AC input Yes
voltage at the distributor
normality?
Check the location of the connected
No PDU for the warning target PS.
Perform the check of the power
supply equipment and the removal of Is
the cause part. the PDU for the No
replacement manufactured
by Hitachi?
Turn on the power of the distributor
Yes If the PDU is manufactured by
other than Hitachi, ask the customer
Are to replace the PDU.
hardware units
other than DW800 connected No
to PDU for the
replacement? Refer to the PDU manual and
perform the PDU replacement
Yes (See REP02-19-10)
Perform Power OFF of hardware
units other than DW800.

Refer to the PDU manual and

perform the PDU replacement.
(See REP02-19-10)

6
(TRBL03-2190)

TRBL03-2210
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2220

Replace the target DKCPS.

Is the target DKCPS No

recovered?

Yes T.S.D. call

7
(TRBL03-2190)

Replace the target BKM.

Is the target BKM Yes

recovered?

No
When the target BKM is BKM-1,
replace CTL1.
When the target BKM is BKM-2,
replace CTL2.

Is the target BKM Yes

recovered?

No
8
(TRBL03-2190)
T.S.D. call

TRBL03-2220
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2230

Block the target BKM, and then

remove it.

Check that the plug of the battery

cable is inserted into the socket
correctly.

Is it inserted No
correctly?
Insert the plug of the battery cable
Yes into the socket.
Replace the target battery.

Install the removed BKM, and then

perform the restoration operation.

Did the target battery Yes

recover?

No
9
(TRBL03-2190)
T.S.D. call

TRBL03-2230
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2240

3.79 Recovery Procedure for Environmental Microcomputer Warning (SIM = af300x)

• The warning indicates that the environmental microcomputer detected a failure in a CTL.
The failure might be a temporary soft error that can be resolved by performing dummy replacement.
• When the environmental microcomputer warning is reported, you cannot perform the power off procedure.
Perform the following procedure to remove the warning, and then power off the storage system (planned
shutdown).

START

Perform the dummy replacement

of the CTL indicated by “SIM =
af300x” (see REP02-04-10).

Is the dummy Yes

replacement completed
normally?

No
Replace the CTL indicated by “SIM
= af300x” (see REP02-04-10).

Is the Yes
replacement completed
normally?

No END

T.S.D. call

TRBL03-2240
Hitachi Proprietary DW850/DW900/DW1000
Rev.10.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2250

3.80 Recovery Procedure for Channel Port Blockade (SIM = 2120xx)

START

Perform dummy replacement of the

Channel Board where the port is
blocked (see REP02-12-10).

Is the channel port No

blockade restored?
Replace the Channel Board with a
Yes maintenance part (see REP02-12-
10).

Is the channel port No

blockade restored?

Yes Collect dumps and contact the

Technical Support Division.
Is there a
END
failure in the Fibre
Channel (see “4.1.6 Isolation No
Procedure for Fibre Channel
Failure”)?
Collect dumps and contact the
Technical Support Division.
Yes
Perform recovery actions according
to “4.1.6 Isolation Procedure for
Fibre Channel Failure”.

END

TRBL03-2250
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2260

3.81 Recovery Procedure for Warning of Accelerator Fan Module (ACLF) type (SIM =
3c9800)
When “Types of installed ACLFs” and “Types of defined ACLFs” differ at the time of start-up, SIM = 3c9800
is issued. When it is issued, they need to be matched. Furthermore, before starting the work, click the [BKMFs]
tab in the “Controller” window of Maintenance Utility and take notes on the ACLF (Accelerator Fan Module)
type.

START

Click the [BKMFs] tab from the

“Controller” window of Maintenance
Utility and specify the unmatched
parts.

Is it true that
ACLFs displayed
in Maintenance Utility are No
different from those installed
actually or are not
installed?

Yes
Turn off the DKC power forcibly.
(See “15.1 Non volatilization power-
off and restarting procedure”.)

Match the ACLF type noted before

starting the work and the actual
ACLF type.
If the noted ACLFs are not installed,
install them.

Execute PS ON.

Was the problem No

resolved?

Yes T.S.D. call

END

TRBL03-2260
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2270

3.82 Recovery Procedure for ENC Error (SIM = af80xx, af81xx, af82xx)

START

Is
an ACC
that instructs DBPS No
replacement included in SIM =
af80xx, af81xx or
af82xx?

Yes

Is SIM =
af50xx, af51xx or af52xx No
reported around the same
time?

Yes

Is the
same ACC as the
one that instructs DBPS
No
replacement for SIM = af80xx,
af81xx or af82xx included in
SIM = af50xx, af51xx
or af52xx?

Yes
Perform maintenance work for SIM
= af50xx, af51xx or af52xx first (see
“3.45 Response to the Occurrence
of DBPS Warning (SIM = af50xx,
af51xx, af52xx)”).

Does
SIM = af80xx,
af81xx or af82xx
recur after completion of the Yes
maintenance work for SIM
= af50xx, af51xx or Perform maintenance work other
af52xx? than DBPS replacement according to
ACCs for SIM = af80xx, af81xx or
No af82xx.

Yes Is the error recovery

successful?

END No

Collect the Auto Dump

(see MPC05-50) and contact the
Technical Support Division.

TRBL03-2270
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL03-2280

3.83 Recovery Procedure When an MP Patrol Check Error Occurs (SIM = 39b0xx)

START

Analyze the SSB log.

(See MPC05-250)

Was SSB = b212

output around the same Yes
time as SIM = 39b0xx was
output?
T.S.D. call
No
Perform recovery actions according
to ACC of SIM = 39b0xx.

END

TRBL03-2280
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-10

4. Recovery from Open Platform Failure

4.1 Recovery Procedure for a Failure on Host Fibre Channel Interface
4.1.1 Outline
The Fibre host device may fail to recognize the volumes for the Fibre of the Storage System correctly due to
failures or incorrect settings of the devices between the Storage System and the Fibre Channel host device.
These failures include a cable disconnection improper connection, a Fibre channel board error on the Fibre
host side and improper disk connection work on the Fibre host side (e.g. insufficient cable insertion or an
insertion error).
The failure recovery method in the field when such failures occur is described.

[Link] Possible Failures and causes of them

Table 4-1 Possible error and cause

No. Possible error Cause
1 Storage System LDEV is not (1) SCSI installation, i.e. recognition and connecting procedure
recognized by Fibre initiator from SCSI initiator is not executed correctly.
(2) Problem of Optical cable or connection.
(3) Problem of Fibre initiator.
Fibre board, device driver version, parameters, etc.
(4) SCSI path definition.
(5) The Host Reserve status is left uncanceled.
(6) Problem of FC switch.
(7) Other

TRBL04-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-20

[Link] Matters must be or desirable to be checked

Item Checkpoint Check method
1 Is the READY LED on the DKC on? Check the storage system visually.
2 Is the LED of the port, which corresponds Check the storage system visually.
to the failed SCSI path or NVMe
namespace and NVM subsystem, on?
Open the System window from Action
menu of Storage Navigator main window
and check whether the port status indicator
is on.
3 Is the location of the CHB port correctly Refer to LOCATION SECTION “4.1 Channel Interface”.
understood?
4 Is the status of the CHB corresponding to • VSP G130/G350/G370/G700/G900/F350/F370/F700/
the failed SCSI path or NVMe namespace F900:
and NVM subsystem normal? Check the CHB status in the “Maintenance” window.
(Refer to “4.1.4 Procedure for Checking Normalcy of
the CHB”.)
• VSP E590/E790/E990/E1090:
Check the CHB status by using Maintenance Utility.
(Refer to “4.1.4 Procedure for Checking Normalcy of
the CHB”.)
5 Is the Optical cable connected to the fibre Pull out and then insert the cable connector.
channel board of the server firmly?
6 Is it a problem of the cable? Replace the cable.
7 Is the SFP of the PCB normal? SIM: Check if the 21a8xx is output.
Click “SFP Status” of the CHB in the Maintenance Utility
to check the status and type (Short or Long) of the SFP.
Pull out and then inset the SFP.
8 Did not the AL-PA duplicate in the fibre SIM: Check if the 2190xx is output.
channel?
9 Is the topology not wrong? Turn on/off the Fabric setting.
Make sure which is adopted, the FC-AL or Point to Point?
(See MAINTENANCE PC SECTION “4.3.1 Editing
Fibre Channel”.)
10 Is the path from the MPC set correctly? For FC-SCSI connection: Check the SCSI path of the
Are the NVMe namespace and NVM target port.
subsystem set correctly? For FC-NVMe connection: Check the NVM subsystem
and namespace settings related to the target port and
logical device.
11 Is the device defined as the SCSI path or Check the LDEV status in the “Logical Devices” window
namespace normal? of Web Console. (Refer to MAINTENANCE PC
SECTION “4.1.2 Checking the Logical Devices”.)
(To be continued)

TRBL04-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-30

(Continued from the preceding page)

Item Checkpoint Check method
12 Is the setting of the driver normal? Check the setting of the driver.
13 Is the HBA normal? Replace the HBA.
14 Is the fibre channel port correct? Check the fibre channel information of the Monitor.
(Refer to “4.1.6 Isolation Procedure for Fibre Channel
Failure”.)
15 Are the combinations of PCB types and If the type of PCB is 2HS10, make sure the channel speed
the equipment to be connected correct? of the equipment (HBA, switch, etc) to be connected is
not 1 Gbps/2 Gbps/4 Gbps/8 Gbps.

When the CHB type is 4HF32 with 16 Gbps SFP

installed, check that devices for connection such as HBA
and switches are not 1 Gbps/2 Gbps/32 Gbps.
*: “When the CHB type is 4HF32, the port with 16 Gbps
SFP installed does not support 1 Gbps/2 Gbps/32
Gbps for the channel speed. Set the host channel speed
at 4 Gbps/8 Gbps/16 Gbps.

When the CHB type is 4HF32 and the 32 Gbps SFP is

installed on the port, check that devices for connection
such as HBA and switches are not 1 Gbps/2 Gbps/4G bps.
*: When the CHB type is 4HF32 and the 32 Gbps SFP
is installed on the port, 1 Gbps/2 Gbps/4 Gbps are not
supported for the channel speed. Set the host channel
speed at 8 Gbps/16 Gbps/32 Gbps.
(To be continued)

TRBL04-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-40

(Continued from the preceding page)

Item Checkpoint Check method
16 Is FC switch normal? Check if the status of the connection port is Link up.
Replace the SFP and the FC cable.
Check for a failure on FC switch.
17 Are the settings for FC switch correct? Check if the topology for FC switch is set to Point to
Point. (See MAINTENANCE PC SECTION “4.3.1
Editing Fibre Channel”.)
Check if the port speed for FC switch is set to the same
as the port speed for DKC. (See MAINTENANCE PC
SECTION “4.3.1 Editing Fibre Channel”.)
18 Is the Zoning setting correct? Check if the WWN of the port on DKC and the WWN of
the port on the connected device are set to the same zone.
Check if the port on FC switch connected to the port on
DKC and the port on FC switch connected to the port on
the external device are set to the same zone.

TRBL04-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-50

4.1.2 Recovery Procedure When Device Is Not Recognized

The device cannot be

recognized.

Is the power of the No

device (DKC) turned on? Turn on the power.

Yes

Is the Optical cable No Connect the Optical cable.

connected?

Yes

Does
the port LED light up in Yes
Exchange SFP
red? (See page TRBL04-
80)
END
No

Does the port LED Does the topology No

No
light up in blue? (See page information fit the connection
TRBL04-80) configuration?
3
Yes Yes
(TRBL04-60)
Is
the channel speed
No
inappropriate, or is it set as Auto?
(*1)
4
Yes
(TRBL04-60)
After checking the channel speed, pull out
and then insert the cable connector.

Yes Is the LED of the port

on?

No

4
(TRBL04-60)
Is the
location of the CHB port, No
Make sure of the port at the correct location.
which is the port concerned,
(See page LOC02-100)
correct?

Yes

2
(TRBL04-60)

*1: See No 15 in “[Link] Matters must be or desirable to be checked”.

TRBL04-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-60

2 3

Is the port concerned No Recover the PCB that includes the blocked
normal? port. Refer to page TRBL04-90.
Yes

Does the Set the correct topology.

topology information fit the No
(See MAINTENANCE PC SECTION “4.3.1
connection configuration? Editing Fibre Channel”.)

Yes
It
the mode of the port No
concerned set to SCSI? (Refer to page 6
TRBL04-151) (TRBL04-61)

Yes

Is the setting of the SCSI No

Make the path definition over again. (*2)
path made correctly?

Yes

Is the setting of the LAN No

Make sure of the WWN and reset it. (*3)
security made correctly?

Yes

Is the setting of the virtual No Make the setting of the virtual LDEV ID
LDEV ID made correct? correctly. (See MPC04-10.)

Yes
Is the
GAD reservation set to Yes Release the GAD reservation being set to
the virtual information of the the virtual information of the LDEV ID, and
LDEV ID? then set the virtual LDEV ID.

7 No

Is the LDEV status No

Refer to page TRBL04-100.
information normal?

4 Yes

Is the setting of the No Make the setting of the HBA driver over
HBA driver correct? again correctly.

Yes
Are
both the following
met? No Insert the SFP again and if the trouble is not
・The SFP is inserted correctly. solved in spite of the operation, replace it.
・The SIM = 21a8xx is not
reported.
END
Yes
5 (TRBL04-70)

TRBL04-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-61

Check and correct the settings of the

Is the path from the port to the No namespace assigned for the logical
logical device set correctly?
device, NVM subsystem, and NVM
(Refer to Provisioning Guide.)
subsystem port.

Yes
Check the namespace assigned for the logical device
and NVM subsystem.
(Refer to Provisioning Guide.)

Is the security setting of the No

NVM subsystem enabled? 7
(Refer to Provisioning Guide.)
(TRBL04-60)

Yes

Is the connection
target host set as the host that can No Correct the settings of the connection
access the namespace? target host, NVM subsystem, and
(Refer to Provisioning Guide.) namespace.

Yes END

7
(TRBL04-60)

TRBL04-61
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-70

Diagnose the CHB port following the

instructions given on page TRBL04-110.

Was
no problem is caused. No
found as a result of the
diagnosis?
Yes Replace the CHB PCB.

Power off the host.

Replace the Optical cable.

Reboot the host.

Was the device Yes

recognized?

No
Power off the host.

Reboot the host.

Was the device Yes

recognized?

No
END
T.S.D Call (*4)

TRBL04-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-71

*2: If the firmware version is earlier than 88-02-01-x0/xx and the paths allocated to host groups
created automatically through Hitachi Storage Advisor Embedded (HSAE) (Host Group Name
starting with “[AutoConfig]”) are defined, perform the procedure through HSAE. For the detailed
procedure, see Hitachi Storage Advisor Embedded Guide “Detaching volumes from a server”
and “Attaching volumes to servers by selecting servers”. To start HSAE, specify the URL in the
Web browser. (See the table in “2.7.3 Starting the Maintenance Utility Window by Specifying IP
Address of CTL” in MAINTENANCE PC SECTION)
*3: If the firmware version is earlier than 88-02-01-x0/xx and the WWN is the WWN of the hosts
defined for host groups created automatically through Hitachi Storage Advisor Embedded (HSAE)
(Host Group Name starting with “[AutoConfig]”), perform the procedure through HSAE. For the
detailed procedure, see Hitachi Storage Advisor Embedded Guide “Editing server settings”. To
start HSAE, specify the URL in the Web browser. (See the table in “2.7.3 Starting the Maintenance
Utility Window by Specifying IP Address of CTL” in MAINTENANCE PC SECTION)
*4: Send the following information to the Technical Support Division (T.S.D.).
• Device configuration of the host
• Version of the OS
• Whether the OS is patched or not
• Version of the driver
• Model number of the fibre channel board
• Dump information on the DKC (See MAINTENANCE PC SECTION “5.2 Dump”.)
• Syslogs and/or Messages
• Logs of software when the alternative path exists
• Fibre channel monitoring information if available

TRBL04-71
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-80

4.1.3 Procedure for Checking Storage System Port Status

The port information of the destination Storage System is displayed in the “Port Condition” window ([Action]
– [Component Maintenance] – [View Port Location]) of Web Console.

In the “Port Condition” box, the statuses of the ports are displayed in the image of the practical storage
system.

Channel Board, Board type, Port ID and Condition are displayed for the each port.
The statuses of the displays of the port status are explained below.

Port Condition Means

Available (Connected) The port is installed and in use.
Available (Not Connected) The port is installed and ready for use.
Not Available The port is installed and not ready for use (blocked).
Not Installed The port is not installed or out of use.

TRBL04-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-90

4.1.4 Procedure for Checking Normalcy of the CHB

• VSP G130/G350/G370/G700/G900/F350/F370/F700/F900:
Use the “Maintenance” window to check normality of CHBs. Check the status of CHBs installed in the
Controller Chassis (DKC) and the Channel Board Box (CHBB). For how to check the status of CHBs, see
MAINTENANCE PC SECTION “[Link] DKC Information View”. When the status of a CHB is normal,
“Normal” is displayed in the [Status] column of the CHB.

TRBL04-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-91

• VSP E590/E790/E990/E1090:
In the “Maintenance Utility” window, click [Hardware] – [All Chassis] – [Controller Chassis], and open the
[CHBs] tab to check the CHB status. When the status is normal, “Normal” is displayed as shown below.
For VSP E990/E1090

For VSP E590/E790

TRBL04-91
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-100

4.1.5 Procedure for Checking Status Information of LDEV

Select [Logical Device] from the [Storage System] tree on Web Console and display the [LDEVs] tag.
Clicking [LDEV ID] of the reference LDEV displays the detail window information.
If the displayed status is not Normal, it is highly possible that the device cannot be recognized.
Therefore, call the T.S.D. having the detail window information (the following window) attached.

TRBL04-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-110

4.1.6 Isolation Procedure for Fibre Channel Failure

Select the following items in the “MPC Monitor” window and check the counts at the time when the device
recognition is executed.
When the count has been made, it is possible that a part of the path concerned has a problem. Therefore,
locate the part according to an estimation suggested by the port information.
Display the counts with the polling intervals set to five seconds.
The counts are not advanced normally, but they are advanced when a link failure occurs or a problem occurs
in the storage system port or a connected device.
Locate the failed part according to the actions listed for the count that has been advanced.

If the device cannot be recognized in spite of the locating actions, call the T.S.D.
Report Type Metric Type
1 FC Port Error Loss of Signal Count
2 Information Bad Received Character Count
3 Loss of Synchronization Count
4 Link Failure Count
5 Received EOFa Count
6 Discarded Frame Count
7 Bad CRC Count
8 Protocol Error Count
9 Expired Frame Count
10 Forward Error Correction Count

TRBL04-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-120

Table 4-2 Table for Locating Part in which a Fibre Channel Failure Occurs
Item Metric Type Description Estimated cause Actions to be taken
1 Loss Of Signal • This information shows • The optical signal is not • Check whether the optical
Count the count of the losses output from the connected signal is emitted from the
of signals detected by port. connected port.
the Fibre I/F controller. • Break of the connecting • Pulling out and reinsertion
(The loss of signal: cable. of the connecting cable
A state in which the • The connecting cable connector.
optical input signal connector is not inserted • Replacement of the SFP of
cannot be sensed.) correctly. the Switch.
• Replacement of the HBA.
• Replacement of the SFP of
the CHB PCB.
• Replacement of the
connecting cable.
• Replacement of the CHB
PCB.
2 Bad Received • This information shows • Degradation of the optical • Pulling out and reinsertion
Character Count the count of failures in signal emitted from the of the connecting cable
the transfer character connected port. connector.
conversion. • Break of the connecting • Replacement of the
(The failure: A state cable. (contact failure) connecting cable.
in which characters • Imperfect insertion of • Replacement of the SFP of
cannot be converted.) the connecting cable the Switch.
connector. • Replacement of the HBA.
• Auto Negotiation of the • Replacement of the SFP of
connected port. the CHB PCB.
[4HF32 (16 Gbps SFP): • Replacement of the CHB
4-16 Gbps] PCB.
[4HF32 (32 Gbps SFP):
8-32 Gbps]
(This is not a problem.)
• Pulling out and reinsertion
of the cable connector.
[4HF32 (16 Gbps SFP):
4-16 Gbps]
[4HF32 (32 Gbps SFP):
8-32 Gbps]
(This is not a problem.)
• Reboot or tuning on/off of
the host/Switch. (This is
not a problem.)
(To be continued)

TRBL04-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-130

(Continued from the preceding page)

Item Metric Type Description Estimated cause Actions to be taken
3 Loss of • This information • Degradation of the optical • Pulling out and reinsertion
Synchronization shows the count of signal emitted from the of the connecting cable
Count failures in the signal connected port. connector.
synchronization. • Break of the connecting • Replacement of the
(The phenomenon: cable. (contact failure) connecting cable.
The optical signal • Auto Negotiation of the • Replacement of the SFP of
can be sensed but no connected port. the Switch.
synchronization pattern [4HF32 (16 Gbps SFP): • Replacement of the HBA.
can be sensed.) 4-16 Gbps] • Replacement of the SFP of
[4HF32 (32 Gbps SFP): the CHB PCB.
8-32 Gbps] • Replacement of the CHB
(This is not a problem.) PCB.
• Pulling out and reinsertion
of the cable connector.
(This is not a problem.)
• Reboot or tuning on/off of
the host/Switch. (This is
not a problem.)
4 Link Failure • This information shows • Degradation of the optical • Pulling out and reinsertion
Count the count of the link signal emitted from the of the connecting cable
failures detected. connected port. connector.
(The phenomena: • Break of the connecting • Replacement of the
The optical signal cable. (contact failure) connecting cable.
cannot be sensed, the • Imperfect insertion of • Replacement of the SFP of
state, in which the the connecting cable the Switch.
synchronizing pattern connector. • Replacement of the HBA.
cannot be sensed, • Auto Negotiation of the • Replacement of the SFP of
has lasted longer connected port. the CHB PCB.
than 100ms, or the [4HF32 (16 Gbps SFP): • Replacement of the CHB
Lip signal cannot be 4-16 Gbps] PCB.
sensed when the loop [4HF32 (32 Gbps SFP):
is constructed. (the 8-32 Gbps]
protocol on the other (This is not a problem.)
port side is abnormal)) • Pulling out and reinsertion
of the cable connector.
(This is not a problem.)
• Reboot or tuning on/off of
the host/Switch. (This is
not a problem.)
(To be continued)

TRBL04-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-140

(Continued from the preceding page)

Item Metric Type Description Estimated cause Actions to be taken
5 Received EOFa • This information shows • A problem of the frame • Replacement of the SFP
Count the count of reception output from the host. between the HBA and
of the EOFaʼs. • A problem of the frame Switch.
(The phenomenon: A output from the Switch. • Replacement of the cable
frame sent from the • A problem of the quality between the HBA and
other port was received of the signals transmitted Switch.
but it was invalidated between the host and • Replacement of the HBA.
by the delimiter.) Switch.
6 Discarded • This information shows • A problem of the quality • An amount of flowing
Frame Count the count of discard of of the signals transmitted data between the host and
received frames that between the host and Switch differs from that
were illegal. Switch. between the Switch and
(The phenomenon: A • A problem of the frame DKC. Reduce the amount
frame sent from the output from the host. of data that flows into the
other port was received • A problem of the frame Switch.
but it was invalid.) output from the Switch.
7 Bad CRC Count • This information shows • A problem of the quality • Pulling out and reinsertion
the count of frames, in of the signals transmitted of the connecting cable.
which the CRC errors between the host and • Replacement of the
occurred when the valid Switch. connecting cable.
EOFʼs were received. • A problem of the frame • Replacement of the SFP of
(The phenomenon: A output from the host. the Switch.
CRC error occurred • A problem of the frame • Replacement of the HBA.
in the frame received output from the Switch. • Replacement of the SFP of
from the other port.) the CHB PCB.
• Replacement of the CHB
PCB.
8 Protocol Error • This information shows • A problem of the timing • Replacement of the SFP of
Count the count of reception in the sequence of the the Switch.
of the LRRs at the linking up with the • Replacement of the HBA.
times of the linking up. connected port. (This • Replacement of the SFP of
• (The phenomena: is not a problem if the the CHB PCB.
A protocol error in linking up can be done.) • Replacement of the CHB
the communication PCB.
with the other port
or reception of a
unexpected sequence
in the linking up
sequence.)
(To be continued)

TRBL04-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-150

(Continued from the preceding page)

Item Metric Type Description Estimated cause Actions to be taken
9 Expired Frame • This information shows • A problem of the quality • Replacement of the SFP
Count the count of frames of the signals transmitted between the HBA and
each of which was between the host and Switch.
discarded because a Switch. • Replacement of the cable
state in which it could • A problem of the frame between the HBA and
not be sent lasted so output from the host. Switch.
long that the retention • A problem of the frame • Replacement of the HBA.
expired. output from the Switch. • An examination of the
(The state was such that host/Switch. (An inquiry
the frame was waiting of the manufacturer.)
for the R-RDY of the
other port.)
10 Forward Error • This information shows • Degradation of the optical • Pulling out and reinsertion
Correction the count of bit errors signal emitted from the of the connecting cable.
Count (Uncorrectable Error) connected port. • Replacement of the
that the guarantee • Break of the connecting connecting cable.
code, Forward Error cable. (contact failure) • Replacement of the SFP of
Correction, cannot • Imperfect insertion of the Switch.
correct received the connecting cable • Replacement of the HBA.
transmission words. connector. • Replacement of the SFP of
the CHB PCB.
• Replacement of the CHB
PCB.

TRBL04-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-151

4.1.7 Procedure for Checking Operation Mode of Port

To connect a logical device to a host as a SCSI connection device (SCSI LU), the operation mode of the
Fibre Channel port must be set to SCSI. To connect a logical device to a host as an NVMe connection device,
the operation mode of the Fibre Channel port must be set to NVMe.
Use the following procedure for checking whether the operation mode of the port is set to SCSI or NVMe.

1. Select [Ports/Host Groups/iSCSI Targets] on MPC.

2. Select the [Ports] tab.
3. Check which of the following is displayed in [Mode] of the target port.
[SCSI]: The port operates in the SCSI mode.
[NVMe]: The port operates in the NVMe mode.

TRBL04-151
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-160

4.2 Pinned track recovery

4.2.1 Pinned Tracks
A pinned track may occur triggered by a hardware failure.
This section explains the pinned track and indicates the recovery procedure.
NOTE: When SIM = 627xxx is reported, perform 10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx) first.
The following notifies the occurrence of the pinned track.
• Report of the Permanent Data Check failure
• Continuous report of CHK2 in the same track
• SIM report of the failure track (pinned track) occurrence

SIM [Link] Meaning Comment

ef4xyy Unable to write data to a track on PDEV. (*2) x : CU number (*1)
ff4xyy Unable to read data from a track on cache. yy : LDEV number
ef5xyy Unable to write data to a track on a device in the external storage
system. (*3)
ff5xyy Unable to read data from a track on a device in the external
storage system.
*1: CU number is detected only lower figure in SIM-RC (x0 - xf).
For additional information, see [Error Location] of [Content SIM] in [2] SIM Log in
MAINTENANCE PC SECTION 5.3.1 Log Indication .
*2: Host I/O is not affected because data remains in cache (data can be accessed from a host in the
same way as in normal state). If a pinned track occurs in the copy source drive during a drive copy,
the pinned track is automatically resolved after completion of the drive copy.
*3: Host I/O is not affected because data remains in cache (data can be accessed from a host in the
same way as in normal state).

To recover pinned tracks, the following information about the pinned track to be recovered are necessary.
• LDEV number (Logical device number)
• First and last LBA of stripe including the pinned track (*4)
• Error type of the pinned track
• PDEV number including the pinned track
These information can be obtained by MAINTENANCE PC SECTION 5.12.3 Pin Data Indication .
*4: LBA : Logical Block Address
NOTE: If you delete a pinned track by using a tool (except the case where you delete a pinned
track by LDEV formatting) when either of the following conditions is met, collect
Normal Dump and contact the Technical Support Division (restoration methods need
to be reviewed by analyzing dumps).
• The parity group where the pinned track occurs (*1) is RAID 6 and dynamic sparing
or correction copy is executed (*2) three times or more in the parity group after the
occurrence of the pinned track.
• The parity group where the pinned track occurs (*1) is RAID 5 and dynamic sparing
or correction copy is executed (*2) two times or more in the parity group after the
occurrence of the pinned track.
*1: Parity group to which the PDEV in which the pinned track exists belongs
*2: SIM REF. codes are as follows.
461xxx, 4c6xxx, 4c7xxx (Dynamic sparing start)
451xxx, 4b6xxx, 4b7xxx (Correction copy start)
For details, see SIM RC SECTION.
TRBL04-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-161

Following explains the error types of pinned tracks and shows reference for recovery.
NOTE: Operations by the customer might be required for these recovery procedures.
For the volumes other than the following, refer to “4.2.2 Error Types”.

Pinned Tracks Volume References

ShadowImage Volume “5.3 Recovery Procedure for Pinned Track”
TrueCopy Volume “6.2 Pinned Track Recovery Procedure for TrueCopy”
UR Data Volume or Journal Volume “7.4 Procedure for UR Pinned Track Recovery and Journal
Volume Replacement”
Thin Image/Thin Image Advanced Pool “8.5 Recovery Procedure for Thin Image pool-VOL ECC/LRC
Volume Error”
global-active device pair volume or “18.1.4 Recovery Procedure of the Pinned Track in the GAD
Quorum disk volume Environment”

TRBL04-161
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-170

4.2.2 Error Types

Pinned track has 7 error types as follows.

Display on MPC
Meaning Cause Recovery method
Slot Reason
‒ Write Error Unable to write to PDEV. Drive error “[Link] Write Error”
DATA ECC/LRC Error Unable to read from Cache. Cache error “[Link] ECC/LRC Error”
(Data slot except CMPD,
META and FPTD)
PRTY ECC/LRC Error Unable to generate parity. Cache error ‒
CMPD ECC/LRC Error Unable to read from Cache. Cache error Specify the failed LBA using the
(*1) (“compressed/deduplicated failed LBA output tool before
data” in LDEVs with Capacity performing ECC/LRC Error
Saving enabled) Recovery Processing. (See “[Link]
Using Failed LBA Output Tool”)
META ECC/LRC Error Unable to read from Cache. Cache error When the virtual volume that has a
(*1) (Metadata in LDEVs with failure is the deduplication system
Capacity Saving enabled) data volume (data store), perform
Procedure 1. In the other cases,
perform Procedure 2.
• Procedure 1:
a. Delete any copy pairs (*4) that
are using the virtual volumes
whose [Deduplication Data]
function is [Enabled], which are
associated with the pool.
b. Block the virtual volumes whose
[Deduplication Data] function is
[Enabled], which are associated
with the pool.
c. Block the deduplication system
data volume associated with the
pool.
d. Initialize all virtual volumes
whose [Deduplication Data]
function is [Enabled] in the pool.
(In the [Initialize Duplicated
Data] window, click [Apply].
(*3))
e. Format the blocked
deduplication system data
volume (data store).
f. Format the virtual volumes
whose [Deduplication Data]
function is [Enabled].
(To be continued)
(To be continued)

TRBL04-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-180

(Continued from the preceding page)

Display on MPC
Meaning Cause Recovery method
Slot Reason
(Continued from the preceding
page)
g. Check the compression
acceleration status of the virtual
volumes for which Compression
and Deduplication is set and
the deduplication system data
volumes (data store) that are
associated with the initialized
POOL by using the Web Console
(*8).
Check whether the compression
acceleration status of all the
deduplication system data
volumes (data store) is the same
as expectation (*9). When it
is not the same as expectation,
ask the customer to change
the compression acceleration
settings of the deduplication
system data volumes (data
store) by running the command
of Command Control Interface
(*10).
h. Restore the data from the
backup.
i. Create the deleted copy pairs
again. (*5) (*6)

• Procedure 2:
a. Delete any copy pairs that are
using the virtual volume that has
a failure. (*4)
For a Thin Image Advanced
pair, when the faulty volume is
not the primary volume, release
the assignment of the secondary
volume to snapshot data instead
of performing pair deletion.
b. Set the System Option Mode
1115 to ON. If the mode is
already set to ON, this operation
is not required. (*7)
c. Format the virtual volume that
has a failure.
d. Set the System Option Mode
1115 to OFF. If the mode is not
set to ON in this maintenance
work, this operation is not
required. (*7)
e. Restore the data from the
backup.
(To be continued)
(To be continued)

TRBL04-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-181

(Continued from the preceding page)

Display on MPC
Meaning Cause Recovery method
Slot Reason
f. Create the deleted copy pairs
again. (*5) (*6)
Also, if you have released the
assignment of the secondary
volume to snapshot data in Step
a, assign the secondary volume
to snapshot data again.
FPTD ECC/LRC Error Unable to read from Cache. Cache error Perform the pool initialization as
(*2) (Deduplication system data follows (*5):
volumes) a. Delete any copy pairs (*4) that
are using the virtual volumes
whose [Deduplication Data]
function is [Enabled], which are
associated with the pool.
b. Block the virtual volumes whose
[Deduplication Data] function is
[Enabled], which are associated
with the pool.
c. Block the deduplication system
data volume associated with the
pool.
d. Initialize all virtual volumes
whose [Deduplication Data]
function is [Enabled] in the pool.
(In the [Initialize Duplicated
Data] window, click [Apply].
(*3))
e. Format the blocked
deduplication system data
volume (data store).
f. Format the virtual volumes
whose [Deduplication Data]
function is [Enabled].
(To be continued)
(To be continued)

TRBL04-181
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-182

(Continued from the preceding page)

Display on MPC
Meaning Cause Recovery method
Slot Reason
(Continued from the preceding
page)
g. Check the compression
acceleration status of the virtual
volumes for which Compression
and Deduplication is set and
the deduplication system data
volumes (data store) that are
associated with the initialized
POOL by using the Web Console
(*8).
Check whether the compression
acceleration status of all the
deduplication system data
volumes (data store) is the same
as expectation (*9). When it
is not the same as expectation,
ask the customer to change
the compression acceleration
settings of the deduplication
system data volumes (data
store) by running the command
of Command Control Interface
(*10).
h. Restore the data from the
backup.
i. Create the deleted copy pairs
again. (*5) (*6)
DATA External VOL Unable to write to a device in Device failure of [Link] External VOL Write Error
Write Error the external Storage System. external Storage
System
DATA External VOL Unable to read from a device Device failure of [Link] External VOL Read Error
Read Error in the external Storage System. external Storage
System
*1: Only LDEVs with Capacity Saving enabled.
*2: Only LDEVs with Deduplication System Data Volume enabled.
*3: For Command Control Interface, use the [raidcom initialize pool] command.
*4: The copy pairs include the following pairs:
• TrueCopy
• Universal Replicator
• ShadowImage
• Volume Migration
• global-active device
• Thin Image/Thin Image Advanced
*5: Do not create copy pairs until formatting the virtual volumes is completed. If you do so,
initialization and pair creation might end abnormally.

TRBL04-182
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-183

*6: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair is not possible due to capacity inconsistency.
Perform capacity expansion so that the capacities are consistent, and then create the pair.
*7: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.
*8: In the main window of the Web Console, select [Logical Devices] from the [Storage Systems]
tree, and check Compression Acceleration of the virtual volumes for which Compression and
Deduplication is set that are associated with the initialized POOL and Compression Acceleration
Status of the deduplication system data volumes (data store) that are associated with the initialized
POOL.
*9: When Compression Acceleration is set to Enabled for one or more virtual volumes for which
Compression and Deduplication is set, confirm that Compression Acceleration Status is set to
Enabled for all the deduplication system data volumes (data store). If Compression Acceleration
Status is set to Disabled, there is a problem.
When Compression Acceleration is not set to Enabled for any virtual volumes for which
Compression and Deduplication is set, confirm that Compression Acceleration Status is set to
Disabled for all the deduplication system data volumes (data store). If Compression Acceleration
Status is set to Enabled, there is a problem.
*10: Run the [raidcom modify ldev -ldev_id yyy -compression_ acceleration {enable|disable} -request_
id auto] command.

The following sections (from [Link] ECC/LRC Error to [Link] External VOL Read Error ) explain each
error type of the pinned track and shows the recovery flow chart for the ECC/LRC Error in the OPEN-VOL
and for the External VOL Read Error of the external Storage System device.

TRBL04-183
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-190

[Link] ECC/LRC Error

Cause
• An ECC/LRC type of a pinned track occurs when a CHK2 error occurs during data transfer between
cache and channel, or between cache and drive. If it is a temporary error, such as transfer timeout, the
error may be recovered and the PIN may be deleted by retrying the operation. When the retry operation
fails because the track is the dirty data, Permanent Data Check may occur, and data will be lost. The
host has to reconstruct the data using the backup file etc.
• An ECC/LRC type of a pinned track occurs when the host failed to write data to the cache due to the
failures in two or more drives (In RAID6, 3 or more drives). If it is a temporary failure, the PIN may be
deleted when the host retries the operation. However, data check will be reported to the host.
• When a parity track cannot be created due to a drive failure etc., an ECC/LRC type of a pinned track
occurs, and only the data will be destaged. The ECC/LRC type of a pinned track will be recovered
when the entire stripe is written.
• When the data cannot be read from the source drive during correction copy, the target track cannot be
recovered. As a result, the track will become an ECC/LRC pinned track. This will lead to Permanent
Data Check, and the original data will be lost.
• This error occurs when the emergency destage, which is performed because of a cache failure or a
cache maintenance operation or P/S OFF, failed due to TOV etc., and the error could not be recovered
despite retrying. If the error occurs when the power is being turned off (P/S OFF), the power will be
turned off while the dirty data is still stored in the cache. The data will be retained by the battery. The
emergency destage will be performed again when the power is turned on (P/S ON), and the pinned
track will be recovered.

Result of host I/O operation

When a track with an ECC/LRC Error is accessed, the result of the host I/O operation is as follows;
• If the read in the track is possible, the host I/O operation ends normally.
• If it isnt possible to read a track, (03)h: Medium Error or (0b)h: Abort to I/O operation is reported
to the host. In this case, data is lost.
NOTE: If you delete a pinned track by using a tool (except the case where you delete a pinned
track by LDEV formatting) when either of the following conditions is met, collect
Normal Dump and contact the Technical Support Division (restoration methods need
to be reviewed by analyzing dumps).
• The parity group where the pinned track occurs (*1) is RAID 6 and dynamic sparing
or correction copy is executed (*2) three times or more in the parity group after the
occurrence of the pinned track.
• The parity group where the pinned track occurs (*1) is RAID 5 and dynamic sparing
or correction copy is executed (*2) two times or more in the parity group after the
occurrence of the pinned track.
*1: Parity group to which the PDEV in which the pinned track exists belongs
*2: SIM REF. codes are as follows.
461xxx, 4c6xxx, 4c7xxx (Dynamic sparing start)
451xxx, 4b6xxx, 4b7xxx (Correction copy start)
For details, see SIM RC SECTION.

TRBL04-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-200

Recovery Method
A track with ECC/LRC Error means that the original data for the track may be lost. Therefore, we
recommend to a customer that a recovery of the data for the track with ECC/LRC Error in the OPEN-VOL
should be performed from a backup file etc.
A recovery method for the track with ECC/LRC Error in the OPEN-VOL is as follows;

1. It change into the state that I/O is not issued from connection server.
(It changes into the state that there is not a process/JOB on a server. Details apply to the procedure of
each servers side.)
2. Check whether a blocked CHB part exists or not. Restore a blocked CHB part if it exist.
3. Obtains the LDKC number and the CU-LDEV number which the pinned track occurred by
MAINTENANCE PC SECTION “5.12.3 Pin Data Indication” and the head and the last LBAs of the
pinned track.
4. When the OS is HP-UX or Solaris, execute the “showrel” tool and examine the relation between the fault
LDEV and the device which the file system recognizes. For how to use the “showrel” tool, see TRBL04-
420 for HP-UX or TRBL04-890 for Solaris.
5. Checks a volume on the file system which is composed of the device and also checks data in the volume.
(Using the command like sum)
6. Requests the customer the recovery of the data with “I/O error” or “read error” from a backup file, etc.
7. Confirms pinned track information by MAINTENANCE PC SECTION “5.12.3 Pin Data Indication”. If
there is not a display of the pinned track and the system test result is normal, the recovery is ended.
If a new pinned track occurs, back to the process of hard error recovery.
8. If an old pinned track display is left, executes the Pin Track Tool.
9. For the “slot:PRTY” display, the Pin Track Tool isnʼt necessary.
It is automatically recovered when the pinned track of the “slot:DATA” display is recovered.
10. If MAINTENANCE PC SECTION “5.12.3 Pin Data Indication” doesnʼt indicate LBAs of pinned track,
this indicates that a pinned track occurred OPEN-VOL other than the user area.

In the case of other than DP volumes, perform the following:

• Back up the data, and then execute the PIN deletion by the LDEV formatting.

In the case of DP volumes, perform the following:

[When Capacity Saving is set to “Disabled”]
In the case of the deduplication system data volume (data store), go to [A] in TRBL20-10.
In the other cases, perform “3.52 Reclaiming the Control Pages Inside the DP-VOL”.

[When Capacity Saving is set to “Compression” or “Deduplication and Compression”]

Back up the data, and then perform the LDEV formatting to recover the pinned track.

TRBL04-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-210

[Link] Write Error

Cause
Write Error type of a pinned track is caused when the data de-staging process to the PDEV failed due to
a drive failure. When a drive failure occurs, the drive itself and the DKC perform the following recovery
procedure. A write Error occurs when the following recovery procedure failed.
• Medium failure : Automatic reallocation of alternate sector.
• Other failure : Alternate path retry.
Write Error count information per PDEV is stored in DKC. When a track with Write Error is accessed by the
host after the PDEV is blocked, the Write Error status will reset.

Result of host I/O operation

Any access to a track with Write Error will be successful.

Recovery Method
The PDEV containing a track with Write Error is replaced. At this time, if the blocked PDEV already exist
within the parity group, first replace the blocked PDEV which already exists. Next, replace the PDEV
containing a track with Write Error. Also, if there are many PDEVs containing a track with Write Error,
check the ORM Display on the MPC Panel, then replace the PDEV with the Highest Error Rate. A track with
Write Error is recovered by drive copy or correction copy.

TRBL04-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-220

[Link] External VOL Write Error

Cause
When write processing is performed for a device in an external Storage System and Check Condition (Medium
Error) is received due to a Drive failure of the external Storage System, External VOL Write Error is set.

Recovery Method
Recover the external Storage System, and then perform either of the following procedures.
• Perform dummy replacement of the Controller Board.
Execute dummy replacement of either Controller Board 1 or Controller Board 2. Please see
REPLACEMENT SECTION “2.4 Replacing a Controller Board” to know how to replace.
• Set the System Option Mode 833 to ON, and then set it to OFF after disconnecting the external volume.
(See MAINTENANCE PC SECTION “5.8 Setting System Option Mode”.)
When disconnecting the external volume, if the LDEV created from the target external volume is defined in
the DP pool, all the DP volumes created from the corresponding DP pool need to be blocked in advance.
(See MAINTENANCE PC SECTION “4.4.1 Blocking LDEVs”.)
NOTE: After recovering the device in the external Storage System, you can remove pinned
track of the external devices by writing I/O from the host. However, please note that
the customer data stored in external devices is destroyed. Because the data will be
overwritten by the I/O.

TRBL04-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-221

[Link] External VOL Read Error

Cause
When read processing from the device in the external Storage System is performed, and Check Condition
(Medium Error) is received due to a Drive failure in the external Storage System, External VOL Read Error
is set.

Recovery Method
Recover the external Storage System, and then perform either of the following procedures.
• Perform dummy replacement of the Controller Board.
Execute dummy replacement of either Controller Board 1 or Controller Board 2. Please see
REPLACEMENT SECTION “2.4 Replacing a Controller Board” to know how to replace.
• Set the System Option Mode 833 to ON, and then set it to OFF after disconnecting the external volume.
(See MAINTENANCE PC SECTION “5.8 Setting System Option Mode”.)
When disconnecting the external volume, if the LDEV created from the target external volume is defined in
the DP pool, all the DP volumes created from the corresponding DP pool need to be blocked in advance.
(See MAINTENANCE PC SECTION “4.4.1 Blocking LDEVs”.)
NOTE: After recovering the device in the external Storage System you can remove pinned
track of the external devices by writing I/O from the host. However, please note that
the customer data stored in external devices is destroyed. Because the data will be
overwritten by the I/O.

TRBL04-221
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-230

4.2.3 Procedure for Erasing Pinned Track

NOTE: • If you want to use the tool in this page, confirm to the technical support division
about using this tool.
If operating system is not Solaris, HP-UX, Windows, AIX, and Linux a procedure
peculiar to the operating system does not exist.
For guest OS on VMware, Pin Track Tool is not supported.
• When SIM = 627xxx is reported, perform 10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx) first.
• When there are blocked LDEVs, perform 3.13 Recovery Procedure for LDEV
Blockade (SIM = ef8xxx, ef9xxx, db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx,
dfbxxx, 46cxxx, 46dxxx) first.

NOTE: If you delete a pinned track by using a tool (except the case where you delete a pinned
track by LDEV formatting) when either of the following conditions is met, collect
Normal Dump and contact the Technical Support Division (restoration methods need
to be reviewed by analyzing dumps).
• The parity group where the pinned track occurs (*1) is RAID 6 and dynamic sparing
or correction copy is executed (*2) three times or more in the parity group after the
occurrence of the pinned track.
• The parity group where the pinned track occurs (*1) is RAID 5 and dynamic sparing
or correction copy is executed (*2) two times or more in the parity group after the
occurrence of the pinned track.
*1: Parity group to which the PDEV in which the pinned track exists belongs
*2: SIM REF. codes are as follows.
461xxx, 4c6xxx, 4c7xxx (Dynamic sparing start)
451xxx, 4b6xxx, 4b7xxx (Correction copy start)
For details, see SIM RC SECTION.

TRBL04-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-231

In the case that no information is displayed Pinned track detected

when you click [Detail] in the Pinned Track window
(see MPC05-1170).
2

No Error What kind of pinned track Write Error

3
displayed on MPC?
(TRBL04-260)
Is the LDEV Other than No Error, Write Error
that contains the pinned track a No
DP-VOL with Capacity Saving
9
enabled (*1)?
(TRBL04-240)
Yes
Obtain the failed LBA information by specifying
the DP-VOL with Capacity Saving enabled (*1) It changes into the state that I/O is not issued
with the failed LBA output tool (See TRBL04- from connection server.
1200). (Details apply to the procedure of each
servers side)

No
Does a failed LBA exist?

Is there any blocked No

Yes END CHB?

Yes
Restore the blocked part.
(See TRBL02-370)

(TRBL04-280) 8

*1: How to identify a DP-VOL with Capacity Saving enabled

In the Logical Devices window of Web Console, if [Compression] or [Deduplication and
Compression] is displayed in the [Capacity Saving] column of a DP-VOL, Capacity Saving is
enabled for the DP-VOL.
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see System Administrator Guide).
• To display only the DP-VOLs for which Capacity Saving is enabled, specify the column value
for the filter. For more details about filtering, refer to System Administrator Guide.

TRBL04-231
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-240

External VOL Write Error External VOL Read Error

What kind of pinned track
5 6
displayed in MPC?
(TRBL04-1130) (TRBL04-1150)
ECC/LRC Error
15

Is the slot type META/ Yes

7
CMPD/PFTD?
(TRBL04-270)
No
Procedure for recovering a DP-
VOL with Capacity Saving enabled or
deduplication system data volume

If “Pinned Data Indication” (See

MPC05-1170.) in MPC doesnʼt indicate LBAs
of pinned track, this indicates that a pinned
track occurred outside the user area.

Does Pinned track exist Yes

12
outside the userʼs area?
(TRBL04-300)
No
It changes into the state that I/O is not
issued from connection server.
(Details apply to the procedure of each
servers side)

Are there blocked CHB Yes

parts?

No Restore the blocked part.

(See TRBL02-370)
Is the LDEV
that a failure track occurred Yes
a pool-VOL of Dynamic
Provisioning?
To TRBL04-1090 Perform the
No
[C] ECC/LRC Error recovery processing
of the DP pool-VOL.
1
(TRBL04-250)

TRBL04-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-250

Yes To TRBL04-740 (*1)

Solaris?
“Solaris”

No

Yes To TRBL04-310 (*1)

HP-UX Server?
“HP-UX”

No

Yes To TRBL04-470 (*1)

Windows Server?
“Windows”

No

Yes To TRBL04-930 (*1)

AIX or Linux?
“AIX, Linux”

No
4

Take backup of all files and directories on the LDEV NOTE: When this operation doesnʼt
containing the pinned track. (Operation A) end, call T.S.D.

Block the LDEV which the pinned track occurred.

(See MAINTENANCE PC SECTION “4.4.1 Blocking
LDEVs”.)

Execute the LDEV format on the LDEV containing

the pinned track. (See MPC04-370)

14
(TRBL04-251)

*1: If the Pinned track is not erased by these actions, please start recovery action from .

TRBL04-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-251

14

Did the LDEV No

formatting fail?

Yes

Is SSB EC = 3289 No
logged?

Yes

Is System Option No
Mode 22 set to ON?

Yes

Was
the shredding or the
LDEV formatting in progress on No
the DP-VOL containing the drive
when the drive was Execute SCSI disk administration work according to
blocked? the SCSI Installation manual if necessary.
Yes
Restore the blocked drive by performing the procedure Restore the files and directories from backup taken at
in REPLACEMENT SECTION “2.3 Replacing a (Operation A) to the LDEV. (Operation B)
Drive”.
The drive replacement is dummy replacement that is Recover the files and directories that cannot be
removing the blocked drive and installing it again. recovered at (Operation B) by using older backup or
reproducing the files or directories.

END
Is the drive No
recovered?

Yes
Execute the shredding or the LDEV formatting on the
DP-VOL containing the drive again. (See MPC04-370)

Did the shredding No

or the LDEV formatting end
normally?

Yes
END T.S.D. call

TRBL04-251
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-260

Write Error type pinned tracks exist.

Is
PDEV# displayed for the No
15
pinned track with Write Error
in SVP? (TRBL04-240)
Yes

Is any PDEV blocked in this No

ECC group?

Yes
No Are there unused spare
drives?
Replace the blocked PDEV and perform a
correction copy. (See TRBL03-740) (*3) Yes
Execute drive copy on the drive that contains
the track with Write Error.
(See TRBL03-760) (*1) (*3)

Did
correction
copy or drive copy
end normally (SIM REF. code Yes
2
= 452xxx/4b8xxx/4b9xxx,
462xxx/4c8xxx/4c9xxx)? (TRBL04-230)
(*2)

No
Remove the cause of the abnormal end of
correction copy or drive copy. (*2)

*1: Correction copy can substitute for drive copy.

*2: If correction copy ended abnormally, SIM REF. code is “453xxx/4baxxx/4bbxxx” or
“455xxx/4bexxx/4bfxxx”.
If drive copy ended abnormally, SIM REF. code is “463xxx/4caxxx/4cbxxx” or
“465xxx/4cexxx/4cfxxx”.
*3: If only the error code “30762-208312” is output when PDEV replacement or start of drive copy
fails, check the box for “Forcibly run without safety checks” in “(6) <Block Drive>”, “2.3.1 Before
Replacing Drive”, REPLACEMENT SECTION, and then retry the operation.
The checkbox is displayed only when Maintenance Utility is started from the “Web Console”
window or the “MPC” window. To check the checkbox, start Maintenance Utility from the “Web
Console” window or the “MPC” window.

TRBL04-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-270

Prevent the connected server from

performing I/O to the pool.

Yes Restore the blocked part.

Is there any blocked CHB?
(See TRBL02-370)

No

Yes
Is the slot type FPTD?

No

Is there pinned track in the Yes (Included in META.)

slot type META?
Is the
16 No (Only in CMPD not in META.) LEDV the deduplication Yes
Is the system data volume (data
LDEV the deduplication No store) (*1)?
system data volume (data No
store) (*1)?
Yes 10 13
Obtain the failed LBA information by (TRBL04-281) (TRBL04-301)
specifying all DP-VOLs whose Capacity Is the LDEV a Yes
Saving is set to Deduplication and data reduction shared volume
Compression in the pool to which the target (*2)?
LDEV belongs with the failed LBA output
tool (See TRBL04-1200). No Is the
No volume a volume of a
Thin Image Advanced
Do
pair?
DP-VOLs where
No
failed LBAs exist include a volume Yes
of a Thin Image Advanced
pair? Is the
volume a primary No
Yes
volume of the Thin Image
Delete the Thin Image Advanced pair that Advanced pair?
contains the DP-VOL where the failed LBA
exist. Yes 17
(TRBL04-280)
Delete the Thin Image Advanced
pair that contains the target LDEV.

Obtain the failed LBA information

by specifying the target LDEV with
the failed LBA output tool (See
TRBL04-1200).

8
(TRBL04-280)

TRBL04-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-271

*1: How to identify a deduplication system data volume (data store)

In the Logical Devices window of Web Console, if Deduplication System Data Volume (Data
store) is displayed in the [Attribute] column, the volume is a deduplication system data volume
(data store).
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see System Administrator Guide).
• To display only deduplication system data volumes (data store), specify the column value for the
filter. For more details about filtering, refer to System Administrator Guide.
*2: How to identify a data reduction shared volume
In the Logical Devices window of Web Console, if Yes is displayed in the [Data Reduction
Shared Volume] column, the volume is a data reduction shared volume.
• The [Data Reduction Shared Volume] column is not displayed by default. Display the [Data
Reduction Shared Volume] column by using the [Column Settings] button (for details, see System
Administrator Guide).
• To display only data reduction shared volumes, specify the column value for the filter. For more
details about filtering, refer to System Administrator Guide.

TRBL04-271
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-280

Does a failed No
LBA exist?

Yes Is
CMPD pinned Yes
Go to TRBL04-240 [C] to perform data left in the pinned slot
recovery procedure from the host for information?
HDEV# and each LBA output by the
failed LBA output tool. No
Is the CMPD
No (*1) pinned data that of a data
If you have deleted a Thin Image reduction shared volume
Advanced pair in this maintenance (*3)?
work, create the pair again.
Yes
Back up the LDEV. (*2)
END
Perform the LDEV format on the
17 LDEV.

Release the assignment of the LDEV Is pinned data left Yes

to snapshot data of the Thin Image in the LDEV?
Advanced pair.
No
Format the LDEV. Restore from the obtained backup
data. (*2)
Assign the LDEV to snapshot data of
the Thin Image Advanced pair again. T.S.D. call
If you have deleted a Thin Image
Advanced pair in this maintenance
END work, create the pair again.

END

*1: CMPD pinned data might be left in thePinned Track window after the ECC/LRC error recovery
processing is performed. But the customer data is not affected unless failed LBA is detected
by using the Failed LBA output tool . In a certain period of time, it is removed by the garbage
collection. It can be forcibly removed by performing the LDEV format.
*2: Ask the SE or user to perform the operation.
*3: How to identify a data reduction shared volume
In the Logical Devices window of Web Console, if Yes is displayed in the [Data Reduction
Shared Volume] column, the volume is a data reduction shared volume.
• The [Data Reduction Shared Volume] column is not displayed by default. Display the [Data
Reduction Shared Volume] column by using the [Column Settings] button (for details, see System
Administrator Guide).
• To display only data reduction shared volumes, specify the column value for the filter. For more
details about filtering, refer to System Administrator Guide.

TRBL04-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-281

10 Erase pinned data by

formatting LDEV.

Back up the LDEV. (*1)

Is the LDEV Yes

a volume of a Thin Image
Advanced pair?
Is the
No volume a primary volume No
of the Thin Image Advanced
pair? Release the assignment of the LDEV to
snapshot data of the Thin Image Advanced
Yes
pair.

Delete the TrueCopy/Universal Replicator/

ShadowImage/Volume Migration/global-
active device/Thin Image/Thin Image Set the System Option Mode 1115 to OFF.
Advanced pair that is using the LDEV. (See MPC05-880) If the mode is not set to
ON in this maintenance work, this operation
is not required. (*2)
Set the System Option Mode 1115 to ON.
(See MPC05-880) If the mode is already set
to ON, this operation is not required. (*2)
Is pinned data left in Yes
Perform the LDEV format on the LDEV. the LDEV?
(See MPC04-370)
No
Restore from the obtained backup data. (*1)

Create the deleted TrueCopy/Universal

Replicator/ShadowImage/Volume Migration/
global-active device/Thin Image/Thin Image
Advanced pair again. (*3)

If you have released the assignment of the

LDEV to snapshot data of the Thin Image
Advanced pair in this maintenance work,
assign the LDEV again.

END T.S.D. call

*1: Ask the SE or user to perform the operation.
*2: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.
*3: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.

TRBL04-281
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-290

11

Back up all DP-VOLs whose [Deduplication

Data] is “Enabled” in the pool. (*1)

Check the backed up data. (*1) If the PIN is of FPTD,

because Read can be, expected
to be a backup is successful.

Is the backed up data No

normal?

Yes
Delete all pairs of TrueCopy, Universal
Delete all pairs of TrueCopy, Universal Replicator, ShadowImage, Volume Migration
Replicator, ShadowImage, Volume Migration and global-active device that use the DP-VOLs
and global-active device that use the DP-VOLs associated with the pool and all Thin Image/
associated with the pool and all Thin Image/ Erase pinned Thin Image Advanced pairs (the root volume
Thin Image Advanced pairs (the root volume data by formatting and the pairs in the tree (*3)) that use the pool.
and the pairs in the tree (*3)) that use the pool. the pool.
Block all DP-VOLs whose [Deduplication
Block all DP-VOLs whose [Deduplication Data] is “Enabled” and the deduplication
Data] is “Enabled” and the deduplication system data volume (*6) in the pool.
system data volume (*6) in the pool.
Initialize all virtual volumes whose
Initialize all virtual volumes whose [Deduplication Data] function is [Enabled]
[Deduplication Data] function is [Enabled] in the pool. (In the [Initialize Duplicated
in the pool. (In the [Initialize Duplicated Data] window, click [Apply]. (*2))
Data] window, click [Apply]. (*2))
Specify all the blocked deduplication system
Specify all the blocked deduplication system data volumes (data store) (*7) in the pool,
data volumes (data store) (*7) in the pool, and then perform the LDEV format.
and then perform the LDEV format. (See MPC04-370)
(See MPC04-370)
Perform the LDEV format on all blocked
Perform the LDEV format on all blocked DP-VOLs whose [Deduplication Data] is
DP-VOLs whose [Deduplication Data] is “Enabled” in the pool. (*4)
“Enabled” in the pool. (*4) (See MPC04-370)
(See MPC04-370)
Perform “20.7 Recovery Procedure When
Perform “20.7 Recovery Procedure When the Compression Acceleration Settings for
the Compression Acceleration Settings for Deduplication System Data Volumes Are
Deduplication System Data Volumes Are Invalid after Duplicated Data Initialization”.
Invalid after Duplicated Data Initialization”.
Consider a different method to restore such
Restore from the obtained backup data. (*1) as restoring the previous backup data. (*1)

For the DP-VOLs and LDEVs associated For the DP-VOLs and LDEVs associated
with the pool, recreate TrueCopy, Universal with the pool, recreate TrueCopy, Universal
Replicator, ShadowImage, Volume Migration Replicator, ShadowImage, Volume Migration
and global-active device pairs, and Thin Image/ and global-active device pairs, and Thin Image/
Thin Image Advanced pairs that use the pool. Thin Image Advanced pairs that use the pool.
(*5) (*5)

END END

TRBL04-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-291

*1: Ask the SE or user to perform the operation.

*2: For Command Control Interface, use the [raidcom initialize pool] command.
*3: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in
the tree of the root volume. To identify the root volumes of Thin Image/Thin Image Advanced
pairs that use the pool, specify the pool name (ID) for filtering in the TI Root Volume tab in the
“Local Replication” window of Web Console.
*4: Do not perform the procedure for LDEV recovery.
*5: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.
*6: How to identify a deduplication system data volume
In the Logical Devices window of Web Console, if “Deduplication System Data Volume (Data
store)” or “Deduplication System Data Volume (Fingerprint)” is displayed in the [Attribute]
column, the volume is a deduplication system data volume.
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only deduplication system data volumes (fingerprint) and deduplication system data
volumes (data store), specify the column value for the filter. For more details about filtering, refer
to “System Administrator Guide”.
*7: How to identify a deduplication system data volume (data store)
In the Logical Devices window of Web Console, if “Deduplication System Data Volume (Data
store)” is displayed in the [Attribute] column, the volume is a deduplication system data volume
(data store).
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only deduplication system data volumes (data store), specify the column value for the
filter. For more details about filtering, refer to “System Administrator Guide”.

TRBL04-291
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-300

12

Is the volume in Yes

which the pinned track has occurred
an OPEN DP-VOL?

No Is Capacity Saving
set to “Disabled” for the volume No
in which the pinned track has
occurred?

Yes
Is
the DP-VOL in
which the pinned track has Yes
occurred a deduplication system data
volume (data store)
(*4)?
Go to [A]
No (TRBL20-10)
Perform the Reclaiming the control pages
inside the DP-VOL. Acquire the backup. (*1)
(See to “3.52 Reclaiming the Control Pages
Inside the DP-VOL”.) Delete the TrueCopy/Universal Replicator/
ShadowImage/Volume Migration/global-
Output the pin data to a file (see active device/Thin Image/Thin Image
MAINTENANCE PC SECTION “5.12.3 Advanced pair using the DP-VOL in which
Pin Data Indication”), collect dumps (see the pinned track has occurred.
MAINTENANCE PC SECTION “5.2
Dump”), then contact T.S.D. Set the System Option Mode 1115 to ON. (See
MPC05-880) If the System Option Mode 1115 is
already set to ON, this operation is not required. (*2)

Perform the LDEV formatting.

(See MAINTENANCE PC SECTION
“[Link] Formatting a Specific LDEV”.)

Set the System Option Mode 1115 to OFF. (See

MPC05-880) If the mode is not set to ON in this
workflow this operation is not required. (*2)

Restore from the obtained backup data. (*1)

Recreate the deleted TrueCopy/Universal

Replicator/ShadowImage/Volume Migration/
global-active device/Thin Image/Thin Image
Advanced pair. (*3)

END

TRBL04-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-300A

*1: Ask the SE or user to perform the operation.

*2: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.
*3: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.
*4: How to identify a deduplication system data volume (data store)
In the Logical Devices window of Web Console, if “Deduplication System Data Volume (Data
store)” is displayed in the [Attribute] column, the volume is a deduplication system data volume
(data store).
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only deduplication system data volumes (data store), specify the column value for the
filter. For more details about filtering, refer to “System Administrator Guide”.

TRBL04-300A
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-301

13

Was the cache

memory dummy replacement No
performed more than once in this
procedure for erasing the
pinned track? Perform the cache memory dummy
replacement. (Refer to REPLACEMENT
SECTION “2.5 Replacing a Cache Memory”.)
Yes

2
11
(TRBL04-230)
(TRBL04-290)

TRBL04-301
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-310

[Link] HP-UX Procedure

This chapter shows the pinned track erasing flow about the HP-UX system.
Procedure Flow

HPE Recovery
It stands for customerʼs work.

Is the version
of Operating System No
either HP-UX 11i v2 or HP-UX 11i v3 Cannot use “Pin Track Tool”. 4
running on the HP Integrity (TRBL04-250)
server?

Yes

Set the System Option Mode 95

(See MPC05-880)

Examin the relation between the pinned How to See TRBL04-420

LDEV and cxtxdx by the “showrel” tool. “showrel tool”

Specify the mount point of cxtxdx by the file How to See TRBL04-440
system. “Confirm a mount point”

Did it find a No (NOTE: See TRBL04-460)

mount point?
Is it a raw device Yes Execute of the DB complete
Yes
of DB system? Backup function.

No H2
Make a mount point and mount When both intermingles,
cxtxdx on it. implement processing in (TRBL04-320)
the order.

Check all files under all directories by using

the “sum” command.

Are there some files No

with the read error?

Yes TRBL04-330 “Readable Pin

Process”.

H1
(TRBL04-320)

TRBL04-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-320

H1

Confirm and record the file name, with

the Read Error.
Frames surrounding operations
Notify to the user. show that the operations are to
be performed by the customer
NOTE: Request the customer to do this work.
at your request.
Remove the disappeared file by the File
System and restore the file from Backup.
When directory files disappears, it
recovers all information of the follower.

H3

Executes the sum command checking

once again.

Are there some files Yes

with the read error?
Confirm a pinned track display in MPC.
No
H2
Confirm the pinned track information of Yes Is there a new fault
MPC again. track?

No
Was a fault track No
canceled? Is it a mistake by the Yes
wrong operation?
Yes
Cancel the System Option Mode 95 No
(See MPC05-880)
Cancel the System Option Mode 95
(See MPC05-880)
Confirm that the system is normal.

2
No
Is the system normal? (TRBL04-230)

Yes

T.S.D. call END TRBL04-330

“Unreadable Pin Process”

TRBL04-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-330

Readable Pin Process

The erasing flow in the readable pinned track by Pin Track Tool is as follows.

How to
Confirm that Pin Track Tool exists. TRBL04-410 5.

Was Pin Track Tool No TRBL04-400

found out? “Installation”

Yes
H4

Execute Pin Track tool because of How to

the Readable-Pin erase. (See NOTE TRBL04-350
below)

Was there a Yes

H3 (TRBL04-320)
Unreadable Pin?

No
Confirm that all pinned tracks were Write
deleted in MPC. Error Confirm the type of
the pinned track.

Were all ECC/LRC

pinned tracks except No
the ones whose slot type is Is it “PRTY” Yes
CMPD deleted? display?

Yes No No
Is this path the 2nd?
Do the
pinned tracks whose Yes
slot type is CMPD Yes
remain? Cancel the System Option Mode 95
(TRBL04-270) 16 (See MPC05-880)
No
Cancel the System Option Mode 95
(See MPC05-880) 4 (TRBL04-250)

Confirm that the system is normal. Is it a new Pinned No

NOTE: This is the Track? Wrong operation?
customerʼs work.
Yes
No
Is the system normal?
Cancel the System Option Mode 95
(See MPC05-880)
Yes

2 (TRBL04-230)
END T.S.D. call

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.
TRBL04-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-340

Unreadable Pin Process

The erasing flow in the unreadable pinned track by Pin Track Tool is as follows.

How to
Confirm that Pin Track Tool exists. TRBL04-410 5.

Was Pin Track No TRBL04-400

Tool found out? “Installation”

Yes

Execute Pin Track tool because of How to

the Readable-Pin erase. (See NOTE TRBL04-350
below)

Confirm and record Non-Readable

Pin.

Start Pin Track Tool after putting a How to

command option because of erasing TRBL04-370
Unreadable Pin. (See NOTE below)

Confirm that all pinned tracks were Write

deleted in MPC. Error Confirm the type of
the pinned track.

Were all ECC/LRC (TRBL04-330)

pinned tracks except No H4
the ones whose slot type is Is it “PRTY” Yes
CMPD deleted? display?

Yes No No
Is this path the 2nd?
Do the
pinned tracks whose Yes
slot type is CMPD Yes
remain? Cancel the System Option Mode 95
(TRBL04-270) 16 (See MPC05-880)
No
Cancel the System Option Mode 95
(See MPC05-880) 4 (TRBL04-250)

Confirm that the system is normal. Is it a new Pinned No

NOTE: This is the Track? Wrong operation?
customerʼs work.
Yes
No
Is the system normal?
Cancel the System Option Mode 95
(See MPC05-880)
Yes

END T.S.D. call 2 (TRBL04-230)

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.
TRBL04-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-350

Operation of Readable-Pin Process (HP-UX)

This clause describes how to operate the Pin Track Tool to erase Readable-Pin.
NOTE: - SIMs reported due to use of the Pin Track Tool -
• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Move to the directory of the Pin Track Tool.

# cd /usr/raidopen/pinhp

2. Execute the Pin Track Tool without a command option.

# ./[Link] -log (Put pass “./”)
NOTE: This option “-log” collects detailed logs.
However, when processing LBA with (60)h length, the log becomes about 400KB.
Be careful of the available capacity of the disk. (refer to TRBL04-430)
3. According to the question, input the appropriate information.
# ./[Link] -log
Input Device Name -> /dev/rdsk/c3t0d0
Input Start LBA Data -> 180 (Input the LBA number which was acquired from MPC.
Input End LBA Data -> 1df Do not input the LBA of the “slot:PRTY” display.)
Input Next LBA ?(Y/N) -> n (When there still is a fault track in the same Device, it inputs “y”.)
Input Next Device ?(Y/N) -> n (When erasing different Device at the same time, it inputs “y”.)

4. Because an input data list is displayed, check the input information.

Device Name Start LBA End LBA
/dev/rdsk/c3t0d0 0000000000000180 00000000000001DF
Before you try to proceed the readable pin,
please check the pin information on MPC.
If the pin data have been cleared, please do not try to proceed the pin track again.
Do you want to do the process of the readable Pin?
Please input[y/n(default n)]:y
When the input is not collect, input “n” or just hit [Return] and then start the procedure again from (2).
Confirm whether or not a pinned track is deleted from the display of Maintenance PC.
When the data is already deleted, input “n” or just hit [return]. When canceled, input “y” and [return].

TRBL04-350
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-360

5. When the Pin is judged, Unreadable through the pin type judgment, go to TRBL04-370.
Unreadable Pin:
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0 0000000000000180 00000000000001DF

NOTE: This tool recognizes an inputted range as the 1 processing unit.

Therefore, the range where Unreadable pin exists is displayed in the inputted range.

6. When Pin Track Tool ends, a log file (month -day -hour -minute -second .log) is made on the same
directory. (Eg:[Link])
As for the log file, the execution result of the Pin Track processing is recorded.
Confirm that processing was normally ended (there is “Pin Track Process completed” in the log file).

TRBL04-360
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-370

Operation of Unreadable Pin Process (HP-UX)

This clause describes how to operate the Pin Track Tool to erase Unreadable Pin.

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Move to the directory of the Pin Track Tool.

# cd /usr/raidopen/pinhp

2. Put a command option and execute a pin recovery tool.

# ./[Link] -f -log (Put command option “-f”)
NOTE: This option “-log” collects detailed logs.
However, when processing LBA with (60)h length, the log becomes about 400KB.
Be careful of the available capacity of the disk. (refer to TRBL04-430)

3. According to the question, input the appropriate information.

# ./[Link] -f -log
Input Device Name -> /dev/rdsk/c3t0d0
Input Start LBA Data-> 180 Input the LBA number which was acquired from MPC.
Input End LBA Data -> 1df Do not input the LBA of the “slot:PRTY” display.
Input Next LBA ?(Y/N) -> n (when there still is a fault track in the same device, it input “y”.)
Input Next Device ?(Y/N) -> n (When erasing different device at the same time, it inputs “y”.)

4. Because an input data list is displayed, check the input information.

Device Name Start LBA End LBA
/dev/rdsk/c3t0d0 0000000000000180 00000000000001DF
Before you try to proceed the readable pin,
please check the pin information on MPC.
If the pin data have been cleared, please do not try to proceed the pin track again.
Do you want to do the process of the readable Pin?
Please input[y/n(default n)]:y
When the Input is not correct, input “n” or just hit [Return] and then start the procedure again From (2).
Confirm whether or not a pinned track is deleted from the display of Maintenance PC.
When the data is already deleted, input “n” or just hit [return]. When canceled, input “y” and [return].

TRBL04-370
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-380

5. When Unreadable Pin is judged, the following message is displayed.

Unreadable Pin:
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0 0000000000000180 00000000000001DF
Do you want to do the process of the unreadable Pin?
WARNING! if you input ʻyʼ,Pin Blocks will be over written by ʻ0ʼ.
Please input[y/n(default n)]:y
When erasing by the “0” writing to Unreadable Pin, input “y” and [Return].
NOTE: This tool recognizes an inputted range as the 1 processing unit.
Therefore, the range where Unreadable pin exists is displayed in the inputted range.

6. When “y” is chosen by (5), the check message is displayed at once for every number of inputs.
In case of plural number input, an operator can cancel the pin recovery processing for the device which
you does not want to execute.
Unreadable Pin:
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0 0000000000000180 00000000000001DF
Do you want to do the process of the unreadable Pin?
WARNING! if you input ʻyʼ,Pin Blocks will be over written by ʻ0ʼ.
Please input[y/n(default n)]:y
Do you want to do the process of the unreadable Pin? (The strip of LBA is 0000000000000180-
00000000000001DF). (Y/N)

7. When Pin Track Tool ends, a log file (month -day -hour -minute -second .log) is made on the same
directory. (Eg:[Link])
As for the log file, the execution result of the Pin Track processing is recorded.
Confirm that processing was normally ended (there is “Pin Track Process completed” in the log file).

TRBL04-380
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-390

How to read the Read Test for whole of a disk (HP-UX)

This chapter describes how to discover the Unreadable Pin on select device.
This processing requires long time.

1. Move to the directory of the Pin Track Tool.

# cd /usr/raidopen/pinhp

2. Execute the Pin Track Tool without a command option.

# ./[Link] -all (The “-f” will become invalid if this option is used.)

3. According to the question, input the appropriate information.

# ./[Link] -all
Input Device Name -> /dev/rdsk/c3t0d0
Input Next Device ?(Y/N) ->n (Recommend to “n”) (When erasing different Device at the same time,
it inputs “y”)

4. The Input data list is displayed.

Device Name Start LBA End LBA
/dev/rdsk/c3t0d0 0000000000000000 00000000001F2285
Show all domain of LAB which is specified device, and execute.

5. When Pin Track Tool ends, a log file (month -day -hour -minute -second .log) is made on the same
directory. (Eg:[Link])
The log when two area (120-17F, 1E023F) of Unreadable Pin exists in specified DeviceName becomes as
follows.
Input Device Name = /dev/rdsk/c3t0d0
ERROR: Read Error LBA 0000000000000120-000000000000017F
ERROR: Read Error LBA 00000000000001E0-000000000000023F

NOTE: The area and number of Unreadable Pin listed by other factors here may differ from
the area and number of Unreadable Pin displayed by Maintenance PC.

TRBL04-390
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-400

Installation of Pin Track Tool (HP-UX)

This clause describes the installation of Pin Track Tool.

The preliminary preparation

If work logs need to be collected by the Pin Track Tool, confirm that there is the disk capacity for collecting
in the work log.
An installation procedure from the tape device (Eg: 4mmDDS-DAT) is shown below.

Installation
1. Login to the host as “root”.

2. Move to the install area by the “cd” command and make a directory “raidopen”.
# cd /usr (Eg: Move to the “/usr”)
# mkdir raidopen (Eg: Make the directory “raidopen”)

3. Move to the created directory and copy a file from the tape by the “tar” command.
# cd raidopen (Eg: Move to the “raidopen”)

-In case of DDS-DAT-(Device Name depends on each host)

# mt -t /dev/rmt/0m rew (Eg: Rewing a tape)
# tar -xvf /dev/rmt/0m (Eg: copy a file from the tape.)
# tar -xvf ./[Link] (Eg: copy the tar file for HP-UX)

-In case of DVD-ROM-(Device Name depends on each host)

# mount -F cdfs -o cdcase /dev/dsk/c2t6d0 SD_DVDROM (Eg: mount the DVD-ROM)
# tar -xvf /SD_DVDROM/program/ment/pintrack/hp_ux/[Link]
(Eg: copy a file from the DVD-ROM.)

4. After the thawing is complete, confirm a file name.

# cd ./pinhp (Eg: Move to the directory made by the thawing.)
# ls -l (Eg: Display a file list.)

TRBL04-400
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-410

5. Refer to the contents of “[Link]” file and confirm each file size of the list.
# more /usr/raidopen/pinhp/[Link] display contents of the file
HITACHI RAID storage system PinTrackTool for HP-UX
Ver XX-YY-/Z (Revision ID)
All right reserved, Copyright (c) 1999,2015, Hitachi Ltd.
File size (Bytes) [Link] (Module ID)
File size (Bytes) [Link] (Module ID)
Confirm that the contents of “[Link]” and a list of the “ls -l” command are identical.

File preservation and the way of removing Pin Track Tool

• Log-File preservation
1. Compress the log file made by the pin recovery.
# cd /usr/raidopen/pinhp (Eg: Move to the working directory.)
# mkdir ./log (Eg: Make to the directory for Log-file.)
# mv *.log ./log (Eg: Move logfiles to the directory for Log-file.)
# tar -cvf [Link] ./log (Eg: Make the tar file from logdir.)
# compress [Link] (Eg: Compress the “[Link]” file.)

2. Preserve the log file at the tape and rewind it.

# tar -cvf /dev/rmt/0m [Link].Z (Eg: Preserve log file)
# mt -t /dev/rmt/0m rew (Eg: rewind the tape)

• The way of removing Pin Track Tool

The removal of the Pin Track Tool deletes all bottoms of the installed directory.
# cd / (Eg: Move to the root directory.)
# \rm -r /usr/raidopen/pinhp* (Eg: Deletes all bottoms of the installed directory)

TRBL04-410
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-420

The acquisition of the device information (HP-UX)

This chapter describes the tool “showrel” to acquire the device information.
1. Move to the installed directory.
# cd /usr/raidopen/pinhp

2. Input commands as follows.

# ./[Link] (Put the path “./”)

<Display Example>
The display depends on the specification of the storage system.
For the Hitachi specification, it is displayed as follows.
#./[Link]

Device File ---> Port Serial# LDKC# LDEV#

/dev/rdsk/c0t0d1 ---> CL1M 301234 00 01A6

/dev/rdsk/c0t0d2 ---> CL1M 301234 00 01A7
/dev/rdsk/c0t0d3 ---> CL1M 301234 00 01A8
/dev/rdsk/c0t0d4 ---> CL1M 301234 00 01A9
/dev/rdsk/c0t0d5 ---> CL1M 301234 00 01AA
/dev/rdsk/c0t0d6 ---> CL1M 301234 00 01AB

00 01 AB
LDEV#
CU#
LDKC#

For the OEM specification, it is displayed as follows.

The point of view of LDKC:CU:LDEV# is the same.
#./[Link]

Device File ---> Port Serial# LDKC# LDEV#

/dev/rdsk/c7t2d1 ---> CL2E 00310028 00 03C0

/dev/rdsk/c7t2d2 ---> CL2E 00310028 00 03C1
/dev/rdsk/c7t2d3 ---> CL2E 00310028 00 03C2
/dev/rdsk/c7t2d4 ---> CL2E 00310028 00 03C3
/dev/rdsk/c7t2d5 ---> CL2E 00310028 00 03C4
/dev/rdsk/c7t2d6 ---> CL2E 00310028 00 03C5

“LDEV#” is composed of the CU number and the LDEV number. Confirm LDKC#, CU# and LDEV# with
the pinned track displayed in Maintenance PC and specify a clearing device file.
Device File name is input information to Pin Track Tool.

(Example)
Above mentioned “For the Hitachi specification”,
LDKC# = 00, LDEV# = 01AB → Device File = /dev/rdsk/c0t0d6
NOTE: In the case of HP-UX, If there is LDEV that is non given LUN#, LDKC#= 00 /
LDEV#= 159F or LDKC#= FF / LDEV#= FFFF are displayed to LUN# non-given a
definition by [Link]

TRBL04-420
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-430

The way of collecting detailed information (HP-UX)

It is possible to collect the detailed information of the erasing process when putting a command option to Pin
Track Tool and starting the process.
# ./ [Link] (-f) -log

Like the following, it outputs read data and write data in the log file.

<Display Example>
Unreadable LBA is displayed by “*”.
Input Device Name = /dev/rdsk/c1t0d0
Input Start LBA = 0000000000000180
Input End LBA = 00000000000001DF Unreadable data!
/dev/rdsk/c1t0d0, Start LBA = 0000000000000180, End LBA = 00000000000001df readable Pin
Track read error
Read Data: Top Pin No = 0000000000000180 Execute LBA!
00000000: ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
00000010: ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
00000020: ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
00000030: ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** NOTE: In the processed
00000040: ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
• • •
range, log
Read Data: Top Pin No=0000000000000181 information is
• • •
Read Data: Top Pin No=0000000000000182
recorded.
• • •
Read Data: Top Pin No=0000000000000183
• • •
Read Data: Top Pin No=00000000000001DF This log is executing read
000001A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 processing by the 1 LBA
000001B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 unit.
000001D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Read Data (After Writing): Top Pin No=00000000000001DF It is indicated data which
000001A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 is read, written, and
000001C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 compared.
000001D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Write Data: Top Pin No=0000000000000180

• • • This log shows to have
00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 processed all ranges in the
00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 writing at once.
00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
• • •
• • •
• • •
0000BFC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/dev/rdsk/c1t0d0, Start LBA=0000000000000180, End LBA=00000000000001DF Pin Track process
completed!!

TRBL04-430
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-440

The way of examining Mount Point which has a Pinned Track (HP-UX)
NOTE: As for the following work, request a system administrator to operate.
1. Input the “vgdisplay” command and to display a Volume Group list.
# vgdisplay -v

2. Specify “lvol(/dev/vgx/lvolx)” which is composed of Physical Volume(cxtxdx) with the Pinned Track.

<Display Example>
--- Volume groups ---
VG Name /dev/vg11 Volume Group Name
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 1016
VGDA 8
PE Size (Mbytes) 4
Total PE 2344
Alloc PE 2000
Free PE 344
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes --- “/dev/vgl1/lvol1” is made in a

LV Name /dev/vg11/lvol1
LV Status available/syncd Volume Group (“/dev/vgl1”)
LV Size (Mbytes) 8000
Current LE 2000
Allocated PE 2000
Used PV 4

--- Physical volumes ---

PV Name /dev/dsk/c9t1d0
PV Status available
Total PE 586
Free PE 0

PV Name /dev/dsk/c9t1d1
PV Status available
Total PE 586
Free PE 0 PV(cxtxdx) which composes
volume group “/dev/vgl1” is
PV Name /dev/dsk/c9t1d2
PV Status available
displayed.
Total PE 586
Free PE 0

PV Name /dev/dsk/c9t1d3
PV Status available
Total PE 586
Free PE 344

TRBL04-440
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-450

3. Check if “./etc/fstab” is displayed.

#cat /etc/fstab

4. Specify all the mount points for PV which was confirmed in “vgdisplay”.

<Display Example>
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg00/lvol10 /home1 vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg11/lvol1 /open vxfs delaylog 0 4

mount point (in bold)

5. Input the “bdf” command and confirm the mount point.

#bdf

<Display Example>
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 86016 26109 56212 32% /
/dev/vg00/lvol1 67733 31932 29027 52% /stand
/dev/vg00/lvol8 512000 159876 331072 33% /var
/dev/vg00/lvol7 614400 428475 174362 71% /usr
/dev/vg00/lvol4 32768 1131 29663 4% /tmp
/dev/vg00/lvol6 258048 102174 146171 41% /opt
/dev/vg00/lvol10 1544192 2858 1445062 0% /home1
/dev/vg00/lvol5 20480 6078 13595 31% /home
/dev/vg11/lvol1 8192000 3149893 4726982 40% /open

6. Determine Mount Point to check by the “sum” command.

TRBL04-450
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-460

The attention item for HP-UX

This clause explains notes when using Pin Track Tool.

The notes for use of the Pin Track Tool

1. Specify the start and end LBAs (*1) in Maintenance PC for the setting range of Pin Track Tool. 1 slot is
composed of 96 LBAs ((60)h LBA).
*1: One slot of OPEN-VOL is composed of 512LBAs.
2. Pin Track Tool is not a tool to recover data. Therefore, when Unreadable Pin occurs, it is necessary to be
restored using the backup data of the customer.
3. There is a case that O/S patch is prepared which has an influence to the pinned track read operation.
The patch information of OS may change at frequent intervals. Confirm the latest information.
Request the system administrator to install patch.
When the system administrator judges this action may impact on the system, cancel the System Option
Mode 95 and return to TRBL04-250 .
4. When it isnʼt possible to use Pin Track Tool, use the LDEV Format to clear.
5. Because HP-UX executing retry to read the pinned track where it isnʼt possible to read many times, It
sometimes takes 12 hours maximum about processing 1 slot.

The erasing process of Pinned Track on the DB (HP-UX, Solaris)

DB has two types of the Pinned Track erasing.
1. Raw device-based Data Base type :
Without passing O/S, by the physical level, the data base soft wear manages a disk.
(It is managed by the LBA unit on the physical level.)
The device of local type isnʼt mounted on File System. Then, it has a powerful backup
function.
2. File system-based Data Base type :
Mounted an File System.

In case of 2, it is necessary to be restored from the backup data.

In case of 1, it be restored by the backup-restore feature of the DBMS.

If a pin is left after the data recovers, erase a pin by the Pin Track Tool.
The most important thing is to execute the recovery function in the DB software.

TRBL04-460
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-470

[Link] Procedure on Windows

• If you start the Pin Track Tool when one or more blocked disk drives are connected to the
Windows host, Error: Read Capacity command failed occurs. Then, restore the blocked disk
drives or disconnect them.
• Do not use the Help menu in the Pin Track Tool window because it is not supported.

The following is an erasing procedure to be used when a Pin failure occurs on Windows.

Windows Frames surrounding operations

show that the operations are to
be performed by the customer
at your request.

Is the OS Windows 2012 or No

Windows 2016 or Windows 2019?

Go to the erasing procedure which does

Yes not require the Pin Track Tool.
(Go to Step  on page TRBL04-250)

Start the registry editor and confirm the

Inquiry information on SCSI devices.

Start the Pin Track Tool, quit it How to

Go to page TRBL04-720
immediately, and create a log file.

 View the log file to confirm the

numbers of the LDEV and physical
drive in which the Pin has been
generated.

 Start the Disk Administrator and confirm the maximum

recognized drive number. Further, confirm the drive letter of
the disk in which the Pin has been generated.

How to
Execute the chkdsk Go to page TRBL04-730

Is there a file in which No Go to page TRBL04-490

an error occurred? See the procedure for Readable
pin Process.
Yes
N1
(TRBL04-480)

TRBL04-470
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-480

N1
Frames surrounding operations
show that the operations are to be
Confirm the name of the file (including performed by the customer at your
the directory) in which the error occurred. request.

Contact the user to obtain consent to the

erasing method.
Erasing process in units of volume

Go to page TRBL04-500.
Return to this flowchart after executing
the procedure for recovering from the
unreadable Pin failure.

Recreate the file system by executing a

file system formatting.

No
Was the Pin erased?

Check the Pin indication displayed

Yes
on the MPC.
Restore the whole volume using the backup
data.
Yes Was a new Pin
added?
Verify the correct system operation on the
user side. No
Was
a mistake made in the Yes
recovery operation?
END
No

Go to Step  on page TRBL04-230.

Review the cause of the error.

NOTE: When the Chkdsk is executed, the sector (equivalent to one LBA) with a Pin failure is
treated as a faulty sector.
Therefore, the effective capacity is decreased because the sector is treated as an
unusable one under the control of Windows even after the Pin information is cleared
by the Pin Track Tool.
Only the formatting of the disk concerned can recover the effective capacity, however,
it causes data on the disk to be lost.

TRBL04-480
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-490

Readable Pin Process (Windows)

START Frames surrounding operations show that the operations

are to be performed by the customer at your request.

How to Confirm the method referring

Make sure that the Pin Track Tool is
to the procedure shown on page
installed.
TRBL04-680.

Has the Pin Track No Install the Pin Track Tool

Tool been installed? referring to page TRBL04-680.

Yes

How to
Activate the [Link] and execute See page TRBL04-510.
the procedure for readable Pin failure.
(See NOTE below.)

Was an unreadable Yes

N3
Pin found?
(TRBL04-500)
No
Update the display on the MPC
and check if all the Pins have been Write Go to Step  on
Confirm Error
deleted. page TRBL04-230.
the type of the failed
Review the cause
track.
of the error.
Were all ECC/LRC
pinned tracks except No
the ones whose slot type is
Is the failed LBA Yes
CMPD deleted?
a new one?
Yes
No Was any mistake
made in the operation?
Do the pinned Yes
tracks whose slot type is CMPD 16
Was it a PRTY No
remain? (TRBL04-270) error?
No
Yes
Verify the correct operation of the
system on the user side. Is it the
second time that you No
follow this path?
Has the No
system been recovered Yes
normally?
Go to the erasing procedure which does
Yes T.S.D. call not require the Pin Track Tool.
(Go to Step  on page TRBL04-250.)
END

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.
TRBL04-490
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-500

Unreadable Pin Process (Windows)

START Frames surrounding operations show that the operations

are to be performed by the customer at your request.

How to Confirm the method referring

Make sure that the Pin Track Tool is
to the procedure shown on page
installed.
TRBL04-680.

Has the Pin Track No Install the Pin Track Tool

Tool been installed? referring to page TRBL04-680.

Yes
N3
How to
Activate the [Link] and execute See page TRBL04-510.
the procedure for readable Pin failure.
(See NOTE below.)

Update the display on the MPC

and check if all the Pins have been Write
Confirm Error
deleted. Go to Step  on
the type of the failed
page TRBL04-230.
track.
Were all ECC/LRC
pinned tracks except No
the ones whose slot type is Is the failed LBA Yes
CMPD deleted? a new one?

Yes No Was any mistake

made in the operation?
Do the pinned Yes
tracks whose slot type is CMPD 16 Was it a PRTY No
remain? (TRBL04-270) error?

No Yes

Verify the correct operation of the Is it the

system on the user side. second time that you No
follow this path?

Has the Yes

No
system been recovered
Go to the erasing procedure which does
normally?
not require the Pin Track Tool.
Yes T.S.D. call (Go to Step  on page TRBL04-250.)

END

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

TRBL04-500
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-510

Operation of Readable Pin Process (Windows)

The following explains how to operate the Pin Track Tool for erasing a readable Pin.
The procedure for erasing a readable Pin is to be firstly applied to all types of Pins.
A Pin which cannot be erased by the readable Pin erasing process will be erased by a process which treats it
as an unreadable Pin.

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Activate the [Link]

• Execute the [Link] in the folder in which the tool is installed after activating it by selecting “Open”
by clicking it with the right mouse button or double-clicking it with the left mouse button.

TRBL04-510
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-520

• When the [Link] is executed, the following window is displayed.

2. Input the information, which has been got from the Maintenance PC, on the device from which the Pin is
to be erased.
NOTE: You can enter two or more Pins in order.
(1) Find a name of a drive to which the LDEV in which the Pin has been generated is allocated.
• Select a physical drive for which the LDEV number of the device in which the Pin has been
generated is displayed using an acquired port number (e.g. 1J for CL1J).

NOTE: The drive names are not sorted in order of the drive numbers.

TRBL04-520
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-530

Input the Start LBA and End LBA of the drive input in Step (1) to specify the range where the Pin has
been generated.

• When specifying the LBAs, the allowable range for them is as follows.
[End LBA - Start LBA ≤ 0x1FF]
Input the range of the or 0x1FF shown on the Maintenance PC.

TRBL04-530
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-540

3. Add the input device to the Pin Track Device List.

• When the “Add” button is clicked after making sure that the selected and input items are correct, the
drive is added to the list.

4. Erase the readable Pin.

• Check if the input information is correct. When correcting it, select the device and input the LBA over
again by selecting the item concerned from the list and clicking the “Delete” button.
• When you want to add two or more devices, you can do it by repeating the input.
When they are added, the Pin erasing process is applied to them in an ascending order of the listing.
NOTE: Since the readable Pin is to be erased here, do not check off the check box of the
Unreadable PIN.

TRBL04-540
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-550

• When no wrong input is found, click the “PRoceed” button to erase the readable Pin.

When the “PRoceed” button is clicked, the program checks whether a free area for outputting a log is
ensured in the current drive in which the Pin Track Tool is installed.
If the free area is less than 10 MB, the following dialog box is displayed to warn it.

The current free area on the disk is displayed in the dialog box. A free area of approximately 400KB is
required for (60)h length SLOT to erase a Pin. When the necessary free area is provided, the processing
can be continued.
NOTE: Install the program in a drive in which the enough free area can be ensured.
When [Yes] is selected, the processing is continued. If the disk capacity is less than that required for the
log, as large log file as can be accommodated is acquired.
Normally, select “Yes” only when the free area is enough.

When [No] is selected, the routine is returned to the main window. If the option has been checked off, it
is cancelled. Ensure a free area in the drive, put the collected log file in order, or install the program in
another drive.

TRBL04-550
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-560

When the “PRoceed” button is clicked to continue the processing, the status of each drive is displayed in
the main window and the following dialog box is displayed.

When “readable-pin” is displayed in the “Status” column, it shows that the slot is a readable Pin.
When “Unreadable-pin” is displayed in the “Status” column, it shows that the slot is an unreadable Pin.

• Update the display on the Maintenance PC before executing the erasing process and check if the Pin of
the input device has been erased.
When the Pin has already been erased, click the “No” button to return to the main window.
When the Pin has not been erased, click the “Yes” button to erase the readable Pin.

TRBL04-560
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-570

5. The Pin erasing process is executed.

When the Pin erasing process is executed, the following dialog box is displayed.

When the Pin erasing process completes normally, the items are deleted from the list automatically.
Confirm the execution result of the Pin erasing process in the log file.

TRBL04-570
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-580

• Open the [Link] file in the folder in which the tool is installed by using a memo pad, etc.

2000/03/27 [Link] Pin Track Tool started.

\\.\PhysicalDrive0
No information

\\.\PhysicalDrive1
Product Serial R500 50330036 0042
Port Number 1E
LDKC Number 00
LDEV Number 002A
Disk Capacity 2461040640 bytes
Maximum LBA 000000000049583F

\\.\PhysicalDrive2
\\.\PhysicalDrive3
\\.\PhysicalDrive4

\\.\PhysicalDrive9
Product Serial R500 50330036 0023
Port Number 2F
LDKC Number 00
LDEV Number 0017
Disk Capacity 2461040640 bytes
Maximum LBA 000000000049583F

Read Data: Top Pin No=0000000000000180

00000000:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0000BFE0:00 00 00 00 00 00 00 00 00 00 00 00 3E BC 12 E6
0000BFF0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Read Data (After Writing): Top Pin No=0000000000000180

00000000:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0000BFE0:00 00 00 00 00 00 00 00 00 00 00 00 3E BC 12 E6
0000BFF0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Write Data: Top Pin No=0000000000000180

00000000:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0000BFE0:00 00 00 00 00 00 00 00 00 00 00 00 3E BC 12 E6
0000BFF0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2000/03/27 [Link]
\\.\PhysicalDrive9,Start LBA=0000000000000180,End LBA=00000000000001DF,The Pin Track
process is completed.
2000/03/27 [Link] Pin Track Tool is exited.

TRBL04-580
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-590

The log file is backed up to the log folder under the directory in which the tool is installed with a name
given as “[Link]”.

• When “The Pin Track process is completed.” is displayed in the log file, it means that the Pin has been
erased. View the display on the Maintenance PC to confirm that the Pin has been erased.

6. When you erase another readable Pin successively, repeat the procedure from Step (2).

• When an unreadable Pin exists in the device added to the list.

When the “PRoceed” button is pressed in the case where an unreadable Pin exists in the list, the
following is displayed.

“unreadable” is displayed in the “Status” column showing that the slot is an unreadable Pin. In this case,
the Pin is not erased even if the procedure for erasing a readable Pin is executed and the device is not
deleted from the list as follows.

TRBL04-590
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-600

The log when two area (120-17F, 1E023F) of Unreadable Pin exists in specified Drive Name
(PhysicalDrive2) becomes as follows.

2002/09/03 [Link] Pin Track Tool started.

¥¥.¥PhysicalDrive0 Device information is recorded here.

No information When displayed on [Product Serial]
¥¥.¥PhysicalDrive1
Product Serial No information as [No information], it is a device
Port Number NG besides an object.
LDKC Number NG
LDEV Number NG
Disk Capacity 0 bytes
Maximum LBA FFFFFFFFFFFFFFFF

¥¥.¥PhysicalDrive2
Product Serial HITACHI R5016F700009
Port Number 1K It is listed here when there is area of
LDKC Number 00 Unreadable Pin.
LDEV Number 0009
Disk Capacity 2461040640 bytes
Maximum LBA 000000000049583F

2002/09/03 [Link]
¥¥.¥PhysicalDrive2, Start LBA=0000000000000120, End LBA=000000000000017F,
An error occurred when reading.
2002/09/03 [Link]
¥¥.¥PhysicalDrive2, Start LBA=00000000000001E0, End LBA=000000000000023F,
An error occurred when reading.
2002/09/03 [Link] Pin Track Tool is exited.

TRBL04-600
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-610

When the status is changed to “read error” and the device remains in the list, go to Subsection TRBL04-
620, “Operation of Unreadable Pin Process”.

TRBL04-610
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-620

Operation of Unreadable Pin Process (Windows)

The following explains how to operate the Pin Track Tool for erasing an unreadable Pin. Since the procedure
for erasing a readable Pin is to be applied to all the Pins first,
follow the procedure below after executing the procedure given in Subsection TRBL04-510, “Operation of
Readable Pin Process”.

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. When the log file ([Link]) is open, close it.

2. Reconfirm the device, which was not deleted from the list when the readable Pin erasing process was
executed, and the display on the Maintenance PC.

3. Specify the unreadable Pin erasing process.

After confirming that the input information is correct, check off the check box of the Unreadable Pin.
When it is checked off, the password dialog box is displayed.

The password is to be obtained from the Technical Support Division. Without the password, the
unreadable Pin cannot be erased.
Input the password and click the “OK” button.
When the correct password is input, the check box is checked off.

If the box is not checked off although the correct password has been input, copy the [Link] file in the
folder in which the tool is installed from the media for installation again.

TRBL04-620
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-630

4. Erase the unreadable Pin.

• Check off the check box. When no wrong input is found, click the “PRoceed” button to erase the
unreadable Pin.

When the “PRoceed” button is clicked, the program checks whether a free area for outputting a log is
ensured in the current drive in which the Pin Track Tool is installed.
If the free area is less than 10 MB, the following dialog box is displayed to warn it.

The current free area on the disk is displayed in the dialog box. A free area of approximately 400KB is
required for (60)h length SLOT to erase a Pin. When the necessary free area is provided, the processing
can be continued.
NOTE: Install the program in a drive in which the enough free area can be ensured.
When “Yes” is selected, the processing is continued. If the disk capacity is less than that required for the
log, as large log file as can be accommodated is acquired.
Normally, select “Yes” only when the free area is enough.

When “No” is selected, the routine is returned to the main window. If the option has been checked off, it
is cancelled. Ensure a free area in the drive, put the collected log file in order, or install the program in
another drive.

TRBL04-630
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-640

When the “PRoceed” button is clicked to continue the processing, the following dialog box is displayed.

Try to erase the readable Pin first. When the readable Pin Track process cannot be executed when the “Yes”
is clicked here, the following dialog box is displayed.

A dialog box for confirming whether to execute the unreadable Pin Track process is displayed.
Execution of the unreadable Pin Track process must be decided carefully because it overwrites the Pin
blocks with “0” data.

In case of the unreadable pin erasing operation, Confirmation of execution is demanded every contents in
the pin track drive list. Operator can select execution or cancellation for each operation.

TRBL04-640
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-650

• Update the display on the Maintenance PC before executing the unreadable Pin Track process and
check if the Pin of the input device has been erased. When the Pin has already been erased, click the “No”
button to return to the main window.

• When the Pin has not been erased, click the “Yes” button to erase the unreadable Pin. When the “Yes”
button is clicked, the unreadable Pin Track process is executed and the following window is displayed.

5. Check the log of the Pin Track Tool.

• Open the [Link] file in the folder in which the tool is installed by using a memo pad, etc.
The log file is backed up to the log folder under the directory in which the tool is installed with a name
given as “[Link]”.
• When “Pin Track process is completed” is displayed in the log file, it means that the Pin has been
erased.
View the display on the Maintenance PC to confirm that the Pin has been erased.

6. When you proceed another Pin successively, repeat the “Operation of Readable Pin Process” in TRBL04-
510.

TRBL04-650
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-660

How to Read Test for whole of a disk (Windows)

This chapter describes how to discover the Unreadable Pin on select device.
This processing requires long time.

1. If a check box “Read Test for whole of a disk” is clicked, it becomes impossible to input “Start LBA” and
“End LBA”.
(Then all the contents currently displayed on the Pin Track Drive List are cleared.)

TRBL04-660
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-670

2. Select a device name and click the add button, Drive and all domain of LBA which are specified by the
pin track drive list are indicated.

3. All LBA in the selected device is started by clicking “PRoceed” button.

(This function is only reading and writing is not performed.)

TRBL04-670
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-680

Installation of Pin Track Tool (Windows)

NOTE: Perform the installation only when it is required.

<Preparation>
The Pin Track Tool is provided being contained in one CD-ROM. A free area of more than 10 MB is
required on the disk on which the program is to be installed as the area for collecting a log. The size of the
log file is approximately 400 KB per one erasing process for (60)h length SLOT. The log is collected in the
log folder under the folder in which the tool is to be installed each time the Pin erasing process completes.
Since the log file is to be saved after the collection, prepare a storage media.

<Copying from installation media to local disk>

1. Logon to the Windows system as administrator permission.
2. Execute the Explorer, and open the CD-ROM.
(Path example : X:\program\MENT\pintrack\win)

3. When executing the [Link]., the following dialog is displayed.

4. If you specify an extracting folder and click the [OK] button, Pin Track Tool is extracted by itself.

TRBL04-680
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-690

• Check the file name and file size displaying on the following windows.

The execution file name is [Link]. When the [Link] is executed, a log file, [Link], is
created in the folder in which the tool has been installed. When the program is quit, the log file is copied
to the log folder with a name given as “[Link]”.

• Log file
In the log file, only the head LBA of Read/Write data of specified device is recorded. It can also record
Read/Write data of all the LBAs.
NOTE: When logs of all the LBAs are recorded, a log file of approximately 400 KB is created
for (60)h length SLOT for each erasing process in the list. Therefore, be careful of
the free capacity on the disk on which the tool is installed.
When a log of only the head LBA is recorded, open the [Link] file in the folder in which the tool
is installed and replace “LogMode=1” with “LogMode=0”.

TRBL04-690
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-700

Data in the log file is recorded in the format shown below.

2000/03/27 [Link] Pin Track Tool started.

\\.\PhysicalDrive0
No information

\\.\PhysicalDrive1
Product Serial R500 50430036 0042
Port Number 1E
LDKC Number 00
LDEV Number 002A
Disk Capacity 2461040640 bytes
Maximum LBA 000000000049583F

2000/03/27 [Link]
\\.\PhysicalDrive1,Start LBA=0000000000000180, LBA=00000000000001DF,An error occurred
when reading.

Read Data: Top Pin No=0000000000000180

00000000:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
00000010:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
00000020:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **

0000BFE0:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
0000BFF0:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **

Read Data: Top Pin No=0000000000000181

Read Data: Top Pin No=0000000000000182

Read Data: Top Pin No=00000000000001DF

0000BFE0:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
0000BFF0:** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **

Write Data: Top Pin No=0000000000000180

00000000:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0000BFE0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFF0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2000/03/27 [Link]
\\.\PhysicalDrive9,Start LBA=0000000000000180,End LBA=00000000000001DF,The Pin Track
process is completed.
2000/03/27 [Link] Pin Track Tool is exited.

[Displayed items]
Time when the program was started : Date and time are indicated.
SCSI device information : Port No., LDKC No., LDEV No., disk capacity, maximum LBA,
etc. are displayed.
Read log : Readable Pins in a specified LBA range are displayed in the
lump. Unreadable Pins are displayed for each LBA. Each
unreadable Pin is recorded with an asterisk (*).
Write log : Pins in a specified LBA range are displayed in the lump.
Entered information : Selected devices, Start LBA, and End LBA are displayed.
Error information : When a Pin is unreadable, “read error” is displayed. Besides,
when an error occurs in the program, details of it are displayed.
Time when the program is quit : Date and time are displayed.

TRBL04-700
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-710

Log file saving and de-installation

NOTE: Perform the de-installation only when it is required.

<Saving of log file>

1. Save the log file which executed Pin Track Tool.
Execute Explorer to open the folder in which the tool is installed.
2. Insert the storage media prepared for saving the log and copy the whole log directory to the storage
media.
3. Delete the files under the log directory if they are not necessary.

<De-installation of Pin Track Tool>

To uninstall the Pin Track Tool, delete all the files concerned by deleting the whole PinTrack folder in which
the tool is installed.

TRBL04-710
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-720

Acquisition of disk information

You can confirm information of the disk connected to windows by viewing the log file.
1. Execute the [Link].
2. When the window is displayed, open the [Link] file.
3. A list of the connected devices is recorded in the file.

<Log file>
• For disks other than the storage system, “No Information” is displayed.
• Since the disk information is acquired using the OS function, the recording order in the log may vary.

TRBL04-720
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-730

Identification of files affected by Pin failure

When a drive letter possible to have a Pin failure is found, identify files affected by the failure using the
chkdsk command.
1. Execute Explorer, click the drive concerned by the right mouse button, and display the property.
2. Open the tool tab and click “Check” in the “Error Check”.
3. Check off all the check disk options and click the “Start” button.
4. When the dialog box is displayed, follow the instruction given in it.
5. Perform the above operations for all the drives concerned.

Verification of files and recovery of them using backup

When a file is repaired or partially deleted by the chkdsk command, verify whether the file is normal.
When the file was partially deleted or broken, delete the file and restore it using the backup.
After the file is recovered normally, check the Pin status. If a Pin remains, erase it by executing the readable
Pin Track process first.

TRBL04-730
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-740

[Link] Procedure on Solaris

The following is an erasing procedure to be used when a Pin failure occurs on Solaris.

In Solaris, disk device is shown as cXtYdZsN, which denotes controller, SCSI target ID, logical
unit number, and slice (partition). One LDEV can be logically divided into eight portions, s0 to
s7, and the each portion can be used as a disk drive. For a slice, a capacity can be set in units
of cylinder, and the user accesses each slice treating it as a disk drive having LBAs starting from
LBA 0.
In Solaris, note that some restrictions on the Pin erasing are induced by handling the disk drive
as cXtYdZsN.

• Ensure a free capacity on the disk on which the Pin Track Tool is to be installed.
The showrel tool, which identifies device files of Solaris according to the LDEV and LBA range
shown on the MPC, creates a temporary file on the disk in order to acquire device information.
If the free capacity on the disk is insufficient, the information cannot be displayed accurately.
• The Pin erasing process cannot be applied to all the LBAs.
In Solaris, the last two cylinders are not allocated to the file system because they are reserved
as alternate cylinders. The remedy for it is limited to an elimination of unreadable LBAs in the
file system.
• The Pin Track Tool cannot be used against a Pin including the inaccessible cylinder.
In the case where cylinders are divided to be allocated to slices and there exist cylinders
which are not allocated to any of the slices, if a Pin including such a range is generated, the
Pin shown on the MPC cannot be erased because I/Os cannot be issued. The remedy for it is
limited to an elimination of unreadable LBAs in the file system.
• When an unreadable Pin is generated in the head LBA, the Pin cannot be erased.
The management information including the device geometry is recorded in the range of
LBA0x0 to 0x1FF to the slot#15. If a Pin including this range is generated, the device cannot
be recognized to be a disk by the OS. Format the LDEV following the maintenance manual.
(To be continued)

TRBL04-740
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-750

(Continued from the preceding page)

• Specify the LBA to be input in the Pin Track Tool correctly.
When the input LBA is wrong, Solaris judges the specified range to be an unreadable Pin.
Even if you try to apply the unreadable Pin Track process to it specifying the range, a write
error will be caused and it is not erased. Make sure that the input LBA is correct before
executing the process.
• After executing the Pin Track process, verify that the processing has completed normally
referring to a log.
To verify the execution result of the Pin Track process, refer to the log file. Read/write errors
are not displayed on the screen. Furthermore, check if the input information was correct when
a write error occurred as described above.

For the EFI disk label

The disk label of a disk with a capacity of 2 TB or more is the EFI disk label.
The EFI disk label differs from the SMI (VTOC) disk label (above descriptions are for SMI disk
label) as follows:
• Slices are 0 through 6 (s0 through s6).
• The size unit is blocks (sectors) but not cylinders.
• The beginning of the slice is LBA 34 but not LBA 0.
As with the SMI disk label, the management information including the device geometry is
recorded in the range of LBA0x0 to 0x1FF. When an unreadable Pin is generated in the head
slot, the Pin cannot be erased.
• The reserved area (8 MB) on the end edge of the disk is Slice 8.
The slice is not allocated to the file system, so Pin erasing is not possible.
As with the SMI disk label, the Pin Track Tool cannot be used for a Pin including the
inaccessible sector on the end edge.

When you have to eliminate the unreadable LBA in the file system on the above conditions, operate
according to the flowchart on the following pages.

TRBL04-750
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-760

• The following is an erasing procedure to be used when a Pin failure occurs on Solaris.

Solaris
Frames surrounding operations show that the
operations are to be performed by the customer at
your request.
Is the version
of Operating System either No
Solaris 10 or Solaris 11 running on Go to Step on page
the Solaris 64bit SPARC TRBL04-250.
server?

Yes

Examine which cxtxdxsx corresponds Go to the device information

to the LDEV in which the Pin has been acquisition procedure on page
generated using the “showrel” tool. TRBL04-890.

Determine a MountPoint of the Go to the procedure for

identified cxtxdxsx. determining the MountPoint
explained on page TRBL04-910.

Was
the MountPoint
of the cxtxdxsx in which the Pin No
was generated found
out? Go to page TRBL04-460.
Is it a DB raw Yes See the procedure for
Yes device? erasing of the DB raw
device from the Pin failure.
No
When the both devices
Set the MountPoint and mount
coexist, execute the procedure
the cxtxdxsx.
for each of them one by one.
S2
(TRBL04-770)
Perform a sum check on all the sub-
directories of the MountPoint.

No Go to page TRBL04-780.
Did a read error occur?
See the procedure for Readable
Pin Process.
Yes

S1
(TRBL04-770)

TRBL04-760
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-770

Frames surrounding operations show that the

S1 operations are to be performed by the customer at
your request.

Confirm the name of the file (including the

directory) in which the read error occurred.

Notify the user of the recovery method.

Request the system administrator to remove (rm) the lost

file/directory using the OS and to return data of the file/
directory from the backup.
In the case of the directory file, whole information under
the directory must be returned.

S3

Perform the sum check again.

Did the read error No

occur?
Check the Pin display on the MPC.
Yes
S2

Check the Pin display on the MPC again. No

Was a new Pin added?

No Yes
Was the Pin erased?
Yes Was a
Yes S1 mistake made in the recovery
operation?
Verify the correct system operation on the No
user side.

Go to Step  on
END page TRBL04-230.
Go to page TRBL04-790.
See the procedure for the
Unreadable Pin Process.

TRBL04-770
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-780

Readable Pin Process (Solaris)

START

How to Confirm the method following

Make sure that the Pin Track Tool is
the procedure in Step 5 on page
installed.
TRBL04-870.

Has the Pin Track No Install the Pin Track Tool

Tool been installed? referring to page TRBL04-860.

Yes

How to
Execute the [Link] without the See page TRBL04-800.
option to erase the readable Pin of the
failed LBA. (See NOTE below.)

Was an unreadable Yes

S3
Pin found?
(TRBL04-770)
No
Update the display on the MPC and
check if all the Pins have been erased.
Write Go to Step  on
Confirm Error page TRBL04-230.
Were all the type of the failed
Review the cause
pinned tracks except No track.
of the error.
the ones whose slot type is ECC/LRC
CMPD deleted?
Is the failed LBA Yes
Yes a new one?

Do the pinned Yes No Was any mistake made in the operation?

tracks whose slot type is CMPD 16
remain? (TRBL04-270)

No

Has the No
file system been recovered
normally?

Yes T.S.D. call

Verify the correct operation of the
system on the user side.

END

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.
TRBL04-780
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-790

Unreadable Pin Process (Solaris)

START

How to Confirm the method following

Make sure that the Pin Track Tool is
the procedure in Step 5 on page
installed.
TRBL04-870.

Has the Pin Track No Install the Pin Track Tool

Tool been installed? referring to page TRBL04-860.

Yes

How to
Execute the [Link] without the See page TRBL04-800.
option “-f” to erase the readable Pin of
the failed LBA. (See NOTE below.)

Update the display on the MPC, then

confirm and record remaining Pinned
Tracks.
How to
Execute the [Link] with the See page TRBL04-820.
option to erase the unreadable Pin of
the failed LBA. (See NOTE below.)

Update the display on the MPC and

check if all the Pins have been erased.
Write
Confirm Error
Were all Go to Step  on
the type of the failed
pinned tracks except No page TRBL04-230
track.
the ones whose slot type is
CMPD deleted? ECC/LRC

Yes Is the failed LBA Yes

a new one?
Do the pinned Yes
tracks whose slot type is CMPD 16 No Was any mistake made in the operation?
remain? (TRBL04-270)

No

Has the No
file system been recovered
normally?

Yes T.S.D. call

Verify the correct operation of the
system on the user side.

END

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.
TRBL04-790
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-800

Operation of Readable Pin Process (Solaris)

The following explains how to operate the Pin Track Tool for erasing a readable Pin.

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Move to the directory of the installed Pin Track Tool.

#cd /usr/raidopen/pinsol

2. Execute the [Link] without the option.

# ./[Link] -log Execute with a path “./”.

3. Input the following information in response to questions.

# ./[Link] -log
Input Device Name -> /dev/rdsk/c3t0d0s2 Input the cxtydzsn.
Input Start LBA Data-> 180 Input the Start LBA.
Input End LBA Data-> 1df Input the End LBA.
Input Next LBA? (Y/N) ->n When two or more LBAs exist in the same device, input
“y”.
Input Next Device ? (Y/N) ->n (Input of “n” is recommended.)
When erasing Pins of two or more devices simultaneously,
input “y”.

To input the LBA, convert the LBA of the LDEV shown by the Maintenance PC into the slice of Solaris
the device file of which corresponds to the LBA, and input the slice. For the conversion of indication
between the LBA and slice, refer to “Acquisition of Device Information” (TRBL04-890).
The showrel tool may display the two or more corresponding LBAs depending on the slice structure. In
this case, the same LBA range is possible to be designated as different slices. Execute the Pin erasing
process for the LBAs in the list shown by the showrel one by one in a descending order, and check the
display on the Maintenance PC each time.
NOTE: When the input LBA does not exist in the device file of the specified slice, it is judged
to be an unreadable Pin and causes a write error if the operation is continued leaving
it as it is. Make sure that the input information is correct before starting the processing
and that the Pin has been erased normally referring to the log after the processing
terminates.

TRBL04-800
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-810

4. Since the input data and a message for confirming whether to erase the Pin, check if the input data is
correct.
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0s2 0000000000000180 00000000000001DF
Before you try to proceed the readable pin,
please check the pin information on MPC.
If the pin data have been cleared, please do not try to proceed the pin track again.
Do you want to do the process of the readable Pin?
Please input[y/n(default n)]:y
If the input data is incorrect, input “n” or simply press the “Return” key and perform the data input over
again from Step (2).
Update the display on the Maintenance PC and check if the Pin concerned has been erased following the
message.
When the Pin has already been erased, terminate the processing by inputting “n” or simply press the
“Return” key.
When the Pin has not been erased, input “y” and press the “Return” key.

5. When the Pin is judged unreadable through the Pin type judgment, go to TRBL04-820.
Unreadable Pin:
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0s2 0000000000000180 00000000000001DF

6. When the Pin Track Tool is quit, a log file is created on the same directory.
The log file name is given as “mm-dd-hh-mʻmʼ-[Link]” (m: month; d: date; h: hours; mʼ: minutes; s:
seconds).
Example:
[Link] means a log file created at 5 minutes and 52 seconds after 20 oʼclock on June 14.

In the log file, the execution result of the Pin Track process is recorded. Make sure that the process has
completed normally by checking if “pin track process complete” is displayed.

TRBL04-810
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-820

Operation of Unreadable Pin Process (Solaris)

The following explains how to operate the Pin Track Tool for erasing an unreadable Pin.

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Move to the directory of the installed Pin Track Tool.

# cd /usr/raidopen/pinsol

2. Execute the [Link] with the option.

# ./[Link] -f -log When “-f” is added, the unreadable LBA is overwritten with “0” data.

3. Input the following information in response to questions.

# ./[Link] -f -log
Input Device Name -> /dev/rdsk/c3t0d0s2 Input the cxtydzsn.
Input Start LBA Data-> 180 Input the Start LBA.
Input End LBA Data-> 1df Input the End LBA.
Input Next LBA ?(Y/N) ->n When two or more LBAs exist in the same device, input
“y”.
Input Next Device ?(Y/N) ->n (Input of “n” is recommended.)
When erasing Pins of two or more devices simultaneously,
input “y”.

To input the LBA, convert the LBA of the LDEV shown by the Maintenance PC into the slice of Solaris
the device file of which corresponds to the LBA, and input the slice. For the conversion of indication
between the LBA and slice, refer to “Acquisition of device information” (TRBL04-890).
The showrel tool may display the two or more corresponding LBAs depending on the slice structure. In
this case, the same LBA range is possible to be designated as different slices. Execute the Pin erasing
process for the LBAs in the list shown by the showrel one by one in a descending order, and check the
display on the Maintenance PC each time.
NOTE: When the input LBA does not exist in the device file of the specified slice, it is judged
to be an unreadable Pin and causes a write error if the operation is continued leaving
it as it is. Make sure that the input information is correct before starting the processing
and that the Pin has been erased normally referring to the log after the processing
terminates.

TRBL04-820
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-830

4. Since the input data and a message for confirming whether to erase the Pin, check if the input data is
correct.
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0s2 0000000000000180 00000000000001DF
Before you try to proceed the readable pin,
please check the pin information on MPC.
If the pin data have been cleared, please do not try to proceed the pin track again.
Do you want to do the process of the readable Pin?
Please input[y/n(default n)]:y
If the input data is incorrect, input “n” or simply press the “Return” key and perform the data input over
again from Step (2).
Update the display on the Maintenance PC and check if the Pin concerned has been erased following the
message.
When the Pin has already been erased, terminate the processing by inputting “n” or simply press the
“Return” key.
When the Pin has not been erased, input “y” and press the “Return” key.

5. The following message is displayed and the Pin is judged unreadable through the Pin type judgment.
Unreadable Pin:
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0s2 0000000000000180 00000000000001DF
Do you want to do the process of the unreadable Pin?
WARNING! if you input ʻyʼ, Pin Blocks will be over written by ʻ0ʼ.
Please input[y/n(default n)]:y
In the Pin Track Process, the window may be changed into monochrome, and the following message may
be showed on the window. In the case, please do not pay attention to them. After 3 minutes or so, the
window will back to originally status.
Example:
This is a message which it is displayed on the monochromic window.
WARNING: /sbus@if, 0/fc0@1, 0/sd@0, 0(sd15)
Error for Command: read Error Level: Retryable (or Fatal)
Requested Block: 766560 Error Block: 766560
Vender: HP Serial Number: 0450F4290000
Sense key: Media Error
ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0

TRBL04-830
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-840

6. When “y” is chosen by 5, the check message is displayed at once for every number of inputs.
In case of plural number input, an operator can cancel the pin recovery processing for the device which
you does not want to execute.
Unreadable Pin:
Device Name Start LBA End LBA
/dev/rdsk/c3t0d0s2 0000000000000180 00000000000001DF
Do you want to do the process of the unreadable Pin?
WARNING! if you input ʻyʼ, Pin Blocks will be over written by ʻ0ʼ.
Please input[y/n(default n)]:y
Do you want to do the process of the unreadable Pin? (The strip of LBA is 0000000000000180-
00000000000001DF). (Y/N)

7. When Pin Track Tool ends, a log file (month -day -hour -minute -second .log) is made on the same
directory. (Eg:[Link])
As for the log file, the execution result of the Pin Track processing is recorded. Make sure that the
process has completed normally by checking if “pin track process complete” is displayed.

TRBL04-840
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-850

How to read the Read Test for whole of a disk (Solaris)

This chapter describes how to discover the Unreadable Pin on select device.
This processing requires long time.

1. Move to the directory of the Pin Track Tool.

# cd /usr/raidopen/pinsol

2. Execute the Pin Track Tool without a command option.

# ./[Link] -all (The “-f” will become invalid if this option is used.)

3. According to the question, input the appropriate information.

# ./[Link] -all
Input Device Name -> /dev/rdsk/c3t0d0s2
(Please input the slice which indicate the whole device.) (Usually indicated “s2”.)
Input Next Device ?(Y/N) ->n
(Recommend to “n”) (When erasing different Device at the same time, it inputs “y”)

4. The Input data list is displayed.

Device Name Start LBA End LBA
/dev/rdsk/c3t0d0s2 0000000000000000 00000000001F2285
Show all domain of LAB which is specified device, and execute.

5. When Pin Track Tool ends, a log file (month -day -hour -minute -second .log) is made on the same
directory. (Eg:[Link])
The log when two area (120-17F, 1E023F) of Unreadable Pin exists in specified DeviceName becomes as
follows.
Input Device Name = /dev/rdsk/c3t0d0s2
ERROR: Read Error LBA 0000000000000120-000000000000017F
ERROR: Read Error LBA 00000000000001E0-000000000000023F

NOTE: The area and number of Unreadable Pin listed by other factors here may differ from
the area and number of Unreadable Pin displayed by Maintenance PC.

TRBL04-850
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-860

Installation of Pin Track Tool (Solaris)

NOTICE: Perform the installation only when it is required.

<Preparation>
Since the Pin Track Tool is provided being contained in a CD-ROM, a drive for installing it is necessary
in the host device which controls the Pin erasing operation or on the network which includes the device
concerned.
Acquire a name for the device beforehand.
Besides, ensure a free area on the disk necessary for a log collection because a log of approximately 400
bytes per failed track is output for (60)h length SLOT when the log is collected using the pintool.
NOTE: If the free capacity on the disk is insufficient, the whole information cannot be
collected.
The showrel tool for LBA-slice conversion ensures a memory and creates a temporary file in order to acquire
device information. Make sure that the memory capacity (larger than 128MB/CPU) and the disk free
capacity (larger than 10MB) sufficient for the server are ensured.

<Copying from media to disk>

1. Login to the host as “root”.

2. Move to the install directory by the “cd” command and make a directory “raidopen”.
# cd /usr (Move to the “/usr”)
# mkdir raidopen (Make the directory “raidopen”)
# cd raidopen (Move to the “raidopen”)

3. Move to the created directory and copy the files from the distribution medium.
Confirm the label, and copy the files from the distribution medium.
# volcheck recognize a media
# tar -xvf /cdrom/zzzz/program/ment/pintrack/solaris/[Link]
NOTE: (The volume label (no_name) and directory name (zzzz) is depend on the system.)
If the copy from the media to the disk ends, it takes out a media.
# eject cdrom Eject the medium.

TRBL04-860
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-870

4. After the thawing is complete, confirm the file name.

# cd ./pinsol (Move to the directory made by the thawing.)
# ls -l (Display a file list.)

5. Refer to the contents of the “[Link]” file and confirm each file size of the list.
# more /usr/raidopen/pisol/[Link] display contents of the file

HITACHI RAID storage system Pin Track Tool for Solaris

Ver XX-YY-/Z (Revision ID)
All right reserved, Copyright (c) 1999,2014, Hitachi Ltd.
File Size (Bytes) [Link] (Module ID)
File Size (Bytes) [Link] (Module ID)
File Size (Bytes) [Link] (Module ID)

Refer to the contents of “[Link]” file and confirm each file size of the list.

Saving of log file and de-installation of Pin erasing tool

NOTICE: Perform the de-installation only when it is required.

<Saving of log file>

In order to save the log file created through the Pin erasure, compress the file.
# cd /usr/raidopen/pinsol Move to the execution directory.
# mkdir ./log Create a directory for the log file.
# mv *.log ./log Move the log file to the logdir.
# tar -cvf [Link] ./log Create the tar file.
# compress [Link] Compress the tar file.
Save the log file to the storage media.

<De-installation of Pin Track Tool>

To uninstall the Pin Track Tool, delete all the files concerned by deleting the whole directory in which the
tool is installed.
# cd / Move to the root directory.
# \rm -r /usr/raidopen/pinsol* Delete files created under the /usr/raidopen.
When “\” is added, the alias is invalidated.

TRBL04-870
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-880

Procedure for collecting detail log

You can acquire detailed information on the erasing process from the Pin failure by adding the option to the
Pin Track Tool.

Method of use: ./[Link](-f) -log

By executing the above, you can acquire data which was read and written in the process for erasing from the
Pin failure.

Example:
Input Device Name = /dev/rdsk/c1t0d0s2
Input Start LBA = 0000000000000180
Input End LBA = 00000000000001DF
/dev/rdsk/c1t0d0s2, Start LBA=0000000000000180, End LBA=00000000000001df readable Pin
Track read error
Read Data: Top Pin No=0000000000000180
00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
• • •
Read Data: Top Pin No=0000000000000181
• • •
Read Data: Top Pin No=0000000000000182
• • •
Read Data: Top Pin No=0000000000000183
• • •
Read Data: Top Pin No=00000000000001DF
000001A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Write Data: Top Pin No=0000000000000180
• • •
00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
• • •
• • •
• • •
0000BFC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000BFF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/dev/rdsk/c1t0d0s2, Start LBA=0000000000000180, End LBA=00000000000001DF Pin Track
Process is complete!!

The log size is approximately 400 KB per one Pin erasure for (60)h length SLOT.
When the -log option is not added, data for each LBA is recorded for each of reading and writing.

TRBL04-880
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-890

Acquisition of device information (how to use showrel tool) on Solaris

When the program has been installed, confirm the failed track information.

1. Move to the installed directory.

# cd /usr/raidopen/pinsol Moving of the directory

2. Execute the following program

# ./[Link] Add the ./ path and execute.
Input LDKC -> 00 Input the LDKC# shown on the MPC.
Input LDEV -> 000A Input the CU:LDEV# shown on the MPC.
Input Start LBA -> 0000000000044000 Input the start LBA shown on the MPC.
Input End LBA -> 000000000004405F Input the End LBA shown on the MPC.

Input example and output result.

# ./[Link]
Input LDKC -> 00
Input LDEV -> 0123
Input Start LBA -> 000000000000ABE0
Input End LBA -> 000000000000AC3F

DeviceName=c0t1d0s6 Port=1A LDKC=00 LDEV=0123

Start=0000000000000FA0 End=0000000000000FFF

The LDKC number is indicated with the number of two figures. The LDEV number is indicated with the
CU:LDEV number of four figures. Confirm the LDKC number, CU number and LDEV number of the Pin
displayed on the Maintenance PC and identify the slice of the device file. The device file name identified
here is used as the input information in the process for the Pin failure.
NOTE: • The showrel tool issues commands peculiar to the storage system to all the disk
devices in order to acquire device information. Therefore, when the command is
issued to a disk other than the storage system such as a built-in disk, an error (Illegal
Request) may be reported to the system. It is not a problem, though.
• When an unreadable Pin is generated in the slot#15 including the head LBA in
which the disk management information is recorded, the device information cannot
be acquired because the disk becomes unable to respond to the OS.
• The disk device of the object may not be labeled when “Error: Target devices do not
exist.” is output.

TRBL04-890
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-900

The following may be displayed depending on the setting of the slice.

When there is no information of the input LDEV in the device management table.
LDKC=00,LDEV=010C This is not a target disk.

Check if the input LDEV number is correct.

When an LDEV which does not belong to any slice is input
DeviceName=c2t3d0s6 Port=1D LDKC=00 LDEV=0189 The target LBA is missing or invalid.

In this case, the Pin shown on the Maintenance PC cannot be erased. However, it does not have any effect on
the file system.
When a Pin extends over multiple slices
DeviceName=c0t1d0s5 Port=1A LDKC=00 LDEV=000A
Start=0000000000001357 End=0000000000001387
DeviceName=c0t1d0s1 Port=1A LDKC=00 LDEV=000A
Start=0000000000000000 End=000000000000002F

When it is displayed that a Pin extends over multiple slices, specify the LBA displayed for each slice when
executing the [Link]. The Pin cannot be erased unless all the range concerned are processed by the
[Link].
When an LDEV is allocated to multiple ports
DeviceName=c1t1d0s6 Port=1A LDKC=00 LDEV=0123
Start=0000000000000FA0 End=0000000000000FFF
DeviceName=c0t3d0s6 Port=1C LDKC=00 LDEV=0123
Start=0000000000000FA0 End=0000000000000FFF

When an LDEV is displayed at the different ports with the same LBA range of the slice, a single LDEV is
allocated to multiple ports. In this case, specify any one of the devices to execute the [Link].
When multiple LBAs are displayed for an LDEV
DeviceName=c0t3d0s2 Port=1A LDKC=00 LDEV=0123
Start=0000000000000FA0 End=0000000000000FFF
DeviceName=c0t3d0s6 Port=1A LDKC=00 LDEV=0123
Start=0000000000000FA0 End=0000000000000FFF

When two slices are displayed with the same LBA range for an LDEV, a slice to which the same cylinder is
allocated may exist. Normally one of the slices is 2. In this case, specify a device described ahead in order
to execute the [Link]. If the Pin is not erased when the Maintenance PC display is checked after the Pin
erasing process has terminated normally, execute the [Link] for another device.

TRBL04-900
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-910

Procedure for determining MountPoint (on Solaris)

NOTICE: The following operation must be performed by the system administrator at your
request checking result at each step.

Display by the showrel

When the showrel explained in TRBL04-890 is used, the LDKC number, and the LDEV number
shown on the Maintenance PC and to which device file the range between the Start LBA and End LBA
corresponds are displayed. Refer to TRBL04-890, “How to use showrel tool”.

Display by prtvtoc
Input “#prtvtoc <raw-device-name>” to display the slice list and find out all the slices in which Pins have
been generated.
* /dev/rdsk/c0t1d0s5 partition map
*
* Dimension:
* 512 bytes/sector
* 80 sectors/tarck
* 9 tracks/cylinder
* 720 sectors/cylinders
* 2500 cylinders
* 1151 accsessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 0 76320 76319
1 3 0176320142480 208799
2 5 00 0 828720 828719
5 6 00 208800 131760 340559 /opt
6 4 00 340560 447120 787679 /usr
7 8 00 787680 41040 828719 /export/home

You can confirm the current MountPoint by viewing the display of the Mount Directory.

TRBL04-910
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-920

Determination using /etc/vfstab

Find out the MountPoint where the /dev/dsk/cxtydzsn is mounted using the #cat/etc/fstab.
# cat /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t3d0s1 - - swap - no -
/dev/dsk/c0t3d0s0 /dev/rdsk/c0t3d0s0 / ufs 1 no -
/dev/dsk/c0t3d0s6 /dev/rdsk/c0t3d0s6 /usr ufs 1 no -
/dev/dsk/c0t3d0s3 /dev/rdsk/c0t3d0s3 /var ufs 1 no -
/dev/dsk/c0t3d0s7 /dev/rdsk/c0t3d0s7 /export/home ufs 2 yes
-
/dev/dsk/c0t1d0s7 /dev/rdsk/c0t1d0s7 /export/home1 ufs 3 yes
-
swap - /tmp tmpfs - yes -
#

You can make sure whether the object device is mounted automatically or not.

Determination using df
Reconfirm the “Ivol name” and “mount point” recognized by the filesystem using the #df -k.
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t3d0s0 76767 17735 58956 24% /
/dev/dsk/c0t3d0s6 738902 552048 185931 75% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/dsk/c0t3d0s3 30807 17911 12866 59% /var
/dev/dsk/c0t3d0s7 53535 7923 45559 15% /export/home
/dev/dsk/c0t1d0s7 489702 189635 299578 39% /export/home1
swap 121856 212 121644 1% /tmp
/dev/dsk/c1t0d0s0 7095037 2163405 4860682 31% /open-0
/dev/dsk/c1t1d0s0 7095757 2049632 4975168 30% /open-0
#

You can make sure whether the object device is being mounted currently or not.

Decide the MountPoint to be checked by the “sum” command following the procedure above.

TRBL04-920
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-930

[Link] Procedure on AIX, Linux

The following shows how to erase a pin failure on AIX, Linux.

• Ensure a free capacity on the disk on which the Pin Track Tool is to be installed.
• When an unreadable pin is generated in the head LBA, the pin cannot be erased.
The management information including the device geometry is recorded in the range of
LBA0x0 to 0x1FF to the slot#15. If a pin including this range is generated, the device cannot
be recognized to be a disk by the OS. Format the LDEV following the maintenance manual.
• Specify the LBA to be input in the Pin Track Tool correctly.
The host cannot determine whether or not a pin has been generated in the input LBA. It
performs a pin recovery or erases an unreadable pin for the input LBA. Therefore, if you input
information improperly, data may be lost.
• After executing the pin track process, see the log to confirm that it has completed normally.

To delete the unreadable LBA in the file system under the above-described conditions, perform operations
according to the flowchart on the following pages.

TRBL04-930
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-940

• The flow shows the procedure in the case a pin failure occurs on AIX, Linux.

Frames surrounding operations show that the

AIX, Linux operations are to be performed by the customer at
your request.
How to
Check which device file corresponds See “How to identify a device file” on
to the LDEV in which a pin has been TRBL04-1050 to TRBL04-1070
generated.

Perform a sum check on all the sub-

directories of the MountPoint.

No See “Readable Pin Process”

Did a read error occur?
on TRBL04-960

Yes

A1
(TRBL04-950)

TRBL04-940
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-950

Frames surrounding operations show that the

A1 operations are to be performed by the customer at
your request.

Check and record the name of the file

(including the directory)
in which the read error occurred.

Notify the user of the recovery method.

Ask the system administrator to remove (rm) the lost file/

directory and to recover data of the file/directory from the
backup.
In the case of the directory file, all information under the
directory must be recovered.

Perform the sum check again

Did the read error No

occur?
Check the pin displayed on the MPC
Yes
Check the pin display on the MPC again.
No
Was a new pin added?

No
Was the pin erased?
Yes

Yes Yes
A1 Recovery mistake?
User verifies the system operation.
No

END
Go to TRBL04-230 

Go to TRBL04-970
“Unreadable Pin Process”

TRBL04-950
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-960

Readable Pin Process (AIX, Linux)

START

Has the Pin Track No Install the Pin Track Tool

Tool been installed? (TRBL04-1020)

Yes

How to
Execute [Link] to erase the See TRBL04-980
readable pin of the failed LBA
(See NOTE below)

Yes See “Unreadable Pin Process” on

Unreadable Pin?
TRBL04-970

No
Update the display on the MPC and
check if all the pins have been erased.
Write Go to Step  on
Confirm Error page TRBL04-230.
Were all the type of the failed
Review the cause
pinned tracks except No track?
of the error.
the ones whose slot type is ECC/LRC
CMPD deleted?
Is the failed LBA Yes
Yes a new one?

Do the pinned Yes No Was any mistake made in the operation?

tracks whose slot type is CMPD 16
remain? (TRBL04-270)

No

Has the No
file system been recovered
normally?

Yes T.S.D. call

User verifies that the system operates
normally.

END

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

TRBL04-960
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-970

Unreadable Pin Process (AIX, Linux)

START

Has the Pin Track No Install the Pin Track Tool

Tool been installed? (TRBL04-1020)

Yes

How to
Execute [Link] to erase the See TRBL04-980
readable pin of the failed LBA
(See NOTE below.)

Update the display on the MPC to

check and record the remaining pins
How to
Execute [Link] again to erase the See TRBL04-1000
unreadable pin of the failed LBA
(See NOTE below.)

Update the display on the MPC to

check and record the remaining pins
Write
Confirm Error Go to Step  on
Were all the type of the failed page TRBL04-230.
pinned tracks except No track. Review the cause
the ones whose slot type is ECC/LRC
CMPD deleted?
Is the failed LBA Yes
Yes a new one?

Do the pinned Yes No Was any mistake made in the operation?

tracks whose slot type is CMPD 16
remain? (TRBL04-270)

No

Has the No
file system been recovered
normally?

Yes T.S.D. call

User verifies that the system operates
normally.

END

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.
TRBL04-970
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-980

How to erase Readable Pin (AIX, Linux)

The following explains how to operate the Pin Track Tool to erase a readable pin.
(The tool is available also on Tru64.)

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Move to the directory of the installed Pin Track Tool.

# cd /usr/raidopen/pinsh

2. Execute the [Link] without the option.

# ./[Link]

3. Input the following information in response to questions.

# ./[Link]
Pin Recovery Tool Ver. 01-03 start.
(If you want to cancel the program,please input “q”.)
Input Device Name ->/dev/rhdisk69 Input the RAW device file name (/dev/rhdiskXX)
Input Start LBA Data ->20000 Input the Start LBA
Input End LBA Data ->201ff Input the End LBA

When you make an input mistake and want to redo it from the start, enter “q”. The program will stop.

Before inputting an LBA, check which device file on the AIX host corresponds to the LBA of the LDEV
displayed on the Maintenance PC. See TRBL04-1060 “How to identify a device file”.

Make sure to specify the RAW device file for the device file.
Do not specify a block device.
The device file name in the above example is for AIX.
The file name of the RAW device file of Linux is of the form /dev/raw/rawXX.
Input the LBA to the Pin Track Tool accurately.
If you input it improperly, data loss may occur.

TRBL04-980
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-990

4. When the LBA is read successfully, the following messages are displayed.
Please wait. Now Reading Pin...
Finished.
Before you try to proceed the readable pin,
please check the pin information on MPC.
If the pin track has been cleared,
please do not try to proceed the pin recovery again.
Do you want to do the process of the readable Pin?(Y/N)

Follow the messages and refresh the display on the Maintenance PC to see if the pin has been cleared.
If it has been cleared, enter “n” to exit.
If not, enter “y”.

5. When the pin is judged as an “unreadable pin” through the pin type judgment as follows, go to TRBL04-
1000.
Please wait. Now Reading Pin...
Failed.
Do you want to do the process of the unreadable Pin? (The strip of LBA is 0x20000-0x201ff)(Y/N)

6. When the [Link] starts, a log file will be created on the same directory.
The log file name is given as “[Link]”.
<Example>
[Link]  Log file created on June 14 at [Link] (hour:minutes:seconds).

In the log file, the execution result of erasing the pin is recorded. Make sure that the process has
completed normally by confirming that “Pin Recovery process completed!!” is displayed.

TRBL04-990
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1000

How to erase unreadable pin (AIX, Linux)

The following explains how to operate the Pin Track Tool to erase an unreadable pin.
(The tool is available also on Tru64.)

NOTE: - SIMs reported due to use of the Pin Track Tool -

• If there are two or more pinned tracks in the adjacent LBAs in the same LU, new
temporary pinned tracks might occur due to parity calculation performed when
pinned data is erased. This might generate SIMs.
• SIM = 680001 might be reported during use of the Pin Track Tool. If the SIM is
reported, contact the Technical Support Division.

1. Move to the directory of the installed Pin Track Tool.

# cd /usr/raidopen/pinsh

2. Execute the [Link]

# ./[Link]

3. Input the following information in response to questions.

# ./[Link]
Pin Recovery Tool Ver. 01-03 start.
(If you want to cancel the program,please input “q”.)
Input Device Name ->/dev/rhdisk69 Input the RAW device file name (/dev/rhdiskXX)
Input Start LBA Data ->20000 Input the Start LBA
Input End LBA Data ->201ff Input the End LBA

When you make an input mistake and want to redo it from the start, enter “q”. The program will stop.

Before inputting an LBA, check which device file on the AIX host corresponds to the LBA of the LDEV
displayed on the Maintenance PC. See TRBL04-1060 “How to identify a device file”.

Make sure to specify the RAW device file for the device file.
Do not specify a block device.
The device file name in the above example is for AIX.
The file name of the RAW device file of Linux is of the form /dev/raw/rawXX.
Input the LBA to the Pin Track Tool accurately.
If you input it improperly, data loss may occur.

TRBL04-1000
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1010

4. When the LBA is read successfully, the following messages are displayed.
Please wait. Now Reading Pin...
Finished.
Before you try to proceed the readable pin,
please check the pin information on MPC.
If the pin track has been cleared,
please do not try to proceed the pin recovery again.
Do you want to do the process of the readable Pin?(Y/N)

Follow the messages and refresh the display on the Maintenance PC to see if the pin has been cleared.
If it has been cleared, enter “n” to exit.
If not, enter “y”.

5. When the pin is judged as an “unreadable pin” through the pin type judgment as follows, the following
message is displayed.
Please wait. Now Reading Pin...
Failed.
Do you want to do the process of the unreadable Pin? (The strip of LBA is 0x20000-0x201ff)(Y/N)

6. “Y” is selected in 5, data will be erased for the LBA area in which a pin is generated. When it succeeds,
the following message will be displayed.
When an error occurs, follow the procedure described in TRBL04-970 to review the cause of the failure.
Please wait. Now Clearing Pin ...
Finished.
Pin Recovery process completed!! (unreadable Pin)

7. When the [Link] ends, a log file will be created on the same directory.
The log file name is given as “[Link]”.
<Example>
[Link]  Log file created on June 14 at [Link] (Hour:Minutes:Seconds).

In the log file, the execution result of erasing the pin is recorded. Make sure that the process has
completed normally by confirming that “Pin Recovery process completed!!” is displayed.

TRBL04-1010
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1020

Installation of Pin Track Tool

NOTICE: Perform the installation only when it is required.

<Preparation>
Since the Pin Track Tool is provided being contained in a CD-ROM, a drive for installing it is necessary
in the host device which controls the Pin erasing operation or on the network which includes the device
concerned.
Acquire a name for the device beforehand.
Besides, ensure a free area on the disk necessary for a log collection because a log of approximately 400
bytes per failed track is output for (60)h length SLOT when the log is collected using the pintool.
NOTE: If the free capacity on the disk is insufficient, the whole information cannot be
collected.

<Copying from media to disk>

1. Login to the AIX machine as “root”.

2. Move to the install directory by the “cd” command and make a directory “raidopen”.
# cd /usr (Move to the “/usr”)
# mkdir raidopen (Make the directory “raidopen”)
# cd raidopen (Move to the “raidopen”)

3. Execute the following command to decompress [Link] and copy the files from the medium to the
created directory.

# tar -xvf /cdrom/zzzz/program/ment/pintrack/sh/[Link]

NOTE: The directory name (zzzz) may be different.

TRBL04-1020
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1030

4. After the file is decompressed, confirm the file name.

# cd ./pinsh (Move to the directory created as a result of the decompression)
# ls -l (Display a file list.)

5. Specify the –ver option and execute [Link] to confirm the version.
# ./[Link] -ver

HITACHI RAID storage system Pin Track Tool for AIX,Tru64,Linux

Ver XX-YY
All right reserved, Copyright (c) 2007-2015, Hitachi Ltd.
File size(Bytes) [Link] (Module ID)

Confirm that the contents of the file above and the data displayed with the ls command are consistent.

TRBL04-1030
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1040

Saving the log file and uninstalling Pin Track Tool

NOTICE: Perform the uninstallation only when it is required.

<Saving the log file>

To save the log file created through the pin recovery, compress the file.
# cd /usr/raidopen/pinsh Move to the execution directory.
# mkdir ./log Create a directory for the log file.
# mv *.log ./log Move the log file to logdir.
# tar -cvf [Link] ./log Create a tar file.

Save the log file to the storage media.

<Uninstalling the Pin Track Tool>

To uninstall the Pin Track Tool, delete all the files concerned by deleting the whole directory in which the
tool is installed.
# cd / Move to the root directory.
# \rm -r /usr/raidopen/pinsh* Delete files created under /usr/raidopen.
When “\” is added, the alias is invalidated.

TRBL04-1040
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1050

How to identify a device file (AIX)

The following shows an example of associating a device file, which is to be the input information of the Pin
Track Tool, with the LDEV in which a pin is generated.

(A) How to identify a device file of a SCSI interface connection LDEV

1. Execute the following command to display a list of disk devices that are enabled on the AIX.

lsdev -C -c disk

The result of execution is as follows. “Available” devices are the disk devices that can receive I/Os.

# lsdev -C -c disk
.........
.........
hdisk65 Defined 06-08-02 Hitachi Disk Array (Fibre)
hdisk66 Defined 06-08-02 Hitachi Disk Array (Fibre)
hdisk67 Defined 06-08-02 Hitachi Disk Array (Fibre)
hdisk68 Available 06-08-02 Hitachi Disk Array (Fibre)
hdisk69 Available 06-08-02 Hitachi Disk Array (Fibre)
hdisk70 Available 06-08-02 Hitachi Disk Array (Fibre)

2. Next, execute the following command to check the details of the “Available” devices (Example for
hdisk69).

lsattr -E -l hdisk69|grep lun_id

The result of execution is as follows.

# lsattr -E -l hdisk69|grep lun_id

lun_id 0x1000000000000 Logical Unit Number ID

The result shows that the LDEV of the LUN = 1 is associated with hdisk69.
When the LDEV with the pin is LDKC:CU:LDEV = [Link] and LUN = 1, the corresponding device
file is hdisk69.
You can check LUN in the LUNM window on the Web Console.

In this case, specify a RAW device file /dev/rhdisk69 to the Pin Track Tool.
(Do not specify a block device (/dev/hdisk69). Data loss may occur.)

TRBL04-1050
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1051

(B) How to identify a device file of an NVMe interface connection LDEV

1. Execute the following command to display a list of disk devices that are enabled on the AIX.

lsdev -C -c disk

The result of execution is as follows. “Available” devices are the disk devices that can receive I/Os.
“NVMe Disk” is displayed for NVMe interface connection disk devices.

# lsdev -C -c disk
.........
.........
hdisk2 Available 06-00-02 NVMe Disk
hdisk3 Available 06-00-02 NVMe Disk
hdisk4 Available 06-00-02 NVMe Disk
hdisk5 Available 06-00-02 NVMe Disk
.........
.........

2. Execute the following command to check the details of the NVMe interface connection disk devices of
the Hitachi storage system.

# lscfg | grep hdisk | grep -i w50060e8

………
………
+ hdisk2 U78D2.001.WZS06NS-P1-C8-T1-W50060E8008001F01-L0-L2 NVMe Disk
+ hdisk3 U78D2.001.WZS06NS-P1-C8-T1-W50060E8008001F01-L0-L3 NVMe Disk
+ hdisk4 U78D2.001.WZS06NS-P1-C8-T1-W50060E8008001F01-L0-L4 NVMe Disk
+ hdisk5 U78D2.001.WZS06NS-P1-C8-T1-W50060E8008001F01-L0-L5 NVMe Disk
………
………

TRBL04-1051
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1052

3. Execute the following command to check the details of the NVMe interface connection disk devices of
the Hitachi storage system for which “Available” is displayed.

lsattr -E -l <physical disk number> | grep unique_id

The result of execution is as follows. (Example for hdisk2)

# lsattr -E -l hdisk2 | grep unique_id

unique_id 2C0202200050001f000000000060e808001f0800nvme Unique device identifier
False

The 4-digit hexadecimal number to the left of “nvme” indicates the LDEV number (CU:LDEV).

The result shows that the LDEV of LDKC:CU:LDEV = [Link] is associated with hdisk2.
When the LDEV with the pin is LDKC:CU:LDEV = [Link], the corresponding device file is hdisk2.

In this case, specify a RAW device file /dev/rhdisk2 to the Pin Track Tool.
(Do not specify a block device (/dev/hdisk2). Data loss may occur.)

TRBL04-1052
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1060

How to identify a device file (Linux)

The following shows an example of associating a device file, which is to be the input information of the Pin
Track Tool, with the LDEV in which a pin is generated.

(A) How to identify a device file of a SCSI interface connection LDEV

1. Execute the following command to display a list of disk devices that are enabled on the Linux.

cat /proc/scsi/scsi

The result of execution is as follows. The one whose “Model” is “ (OPEN-V)” are the LU devices that can
receive I/Os.

# cat /proc/scsi/scsi
.........
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: HITACHI Model: OPEN-V Rev: 5008
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor: HITACHI Model: OPEN-V Rev: 5008
Type: Direct-Access ANSI SCSI revision: 03

2. Next, the disk device name corresponding to a peculiar Lun number is confirmed by the following
commands. First of all, the file to which it refers by the following commands is confirmed.

# ls -la /var/log/messages*

The result of execution is as follows.

-rw------- 1 root root 18423 Jun 11 10:11 /var/log/messages

-rw------- 1 root root 36883 Jun 8 04:03 /var/log/messages.1
-rw------- 1 root root 1560 Jun 1 04:03 /var/log/messages.2
-rw------- 1 root root 19539 May 25 04:03 /var/log/messages.3
-rw------- 1 root root 2604 May 18 04:03 /var/log/messages.4

The file date looks for the latest one by the above-mentioned. /var/log/messages is the latest here.

Next, the following commands are executed.

# more /var/log/messages

TRBL04-1060
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1070

The result of execution is as follows.

# more /var/log/messages
.........
Jun 11 [Link] x86AS30 kernel: Attached scsi disk sdb at scsi3, channel 0, id 0, lun 0
Jun 11 [Link] x86AS30 kernel: Attached scsi disk sdc at scsi3, channel 0, id 0, lun 1
.........

The result shows that the LDEV of the LUN = 1 is associated with sdb from “Attached scsi disk”.
When the LDEV with the pin is LDKC:CU:LDEV = [Link] and LUN = 1, the corresponding device
file is sdb.
You can check LUN in the LUNM window on the Maintenance PC or Web Console.

In this case, because the block device file of the object becomes /dev/sdb, the device file specified for Pin
Track Tool becomes RAW device file linked with /dev/sdb.
(Do not specify a block device (/dev/sdb). Data loss may occur.)

(B) How to identify a device file of an NVMe interface connection LDEV

Execute the “nvme list” command to display a list of device files that can be input and output from the
Linux host through the NVMe interface.
See the “SN” column that shows information of the storage system ID (one digit) - serial number (five
digits) – NVM subsystem ID (five digits) and the “Namespace” column that shows information of the
namespace ID to identify a target device file shown in the “Node” column.

For example, if a pin is generated in the LDEV of the storage system serial number 500099, the NVM
subsystem ID 2, and the namespace ID 1, you can find that the target device file is “/dev/nvme2n1”.

# nvme list
Node SN Model Namespace Usage Format FW Rev
----------------- ------------------ ----------------------------------- -------------- --------------------------- --------------- --------------
/dev/nvme1n1 5-00099-00001 HITACHI SVOS-RF-System 1 1.05 MB / 1.05 MB 512 B + 0 B 90060000
/dev/nvme1n2 5-00099-00001 HITACHI SVOS-RF-System 2 1.05 MB / 1.05 MB 512 B + 0 B 90060000
/dev/nvme2n1 5-00099-00002 HITACHI SVOS-RF-System 1 1.05 MB / 1.05 MB 512 B + 0 B 90060000

(C) How to identify a RAW device file that is linked with the device file
Perform the following to identify a RAW device file that is linked with the device file identified in (A) or
(B).

TRBL04-1070
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1071

First of all, to confirm linked the RAW device files, the following commands are
executed.

# raw -qa

The execution result is as follows.

/dev/raw/raw1: bound to major 8, minor 0

/dev/raw/raw2: bound to major 8, minor 1
.........

Then, execute the following command if the device file is “/dev/sdb” for example.

# ls -l /dev/sdb

The execution result is as follows. The numerical values behind “disk” respectively correspond to the
major number and the minor number in the above-mentioned result.

brw-rw---- 1 root disk 8, 0 May 6 2008 sdb

Therefore, the RAW device file becomes /dev/raw/raw1.

TRBL04-1071
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1080

[Link] List of Pin Track Tool Directories

• /program/MENT/pintrack/readme_e.txt
• /program/MENT/pintrack/hp-ux/[Link]
• /program/MENT/pintrack/sh/[Link]
• /program/MENT/pintrack/solaris/[Link]
• /program/MENT/pintrack/win/[Link]

TRBL04-1080
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1090

[Link] ECC/LRC Error Recovery Processing of DP pool-VOL

When an ECC/LRC Error occurs in a pool-VOL, perform the following recovery method because an I/O
cannot be issued directly from the HOST for the track concerned.
NOTE1 : In case of a Write Error, perform TRBL04-260 as well as the normal VOL and
recover it.
NOTE2 : The LDEV that a POOL ID is displayed on the logical device window is a pool-
VOL.

TRBL04-1090
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1100

START

Display “Pin Data indication function (MPC05-

1170)” of MPC.

Is
there an indication of Yes
the DP-VOL as the example 1 in
the next page?

No Return to the [C] of (TRBL04-240), and

perform the recovery processing from the
Delete the LDEV (pool-VOL) in which a
HOST for the HDEV# and the LBA that are
pinned track occurred from the pool.
displayed in the DP-VOL column.
(Refer to “Provisioning Guide”.)

Perform LDEV format on the deleted LDEV.

(See MPC04-370.)

Add to the pool after finishing LDEV format.

END

TRBL04-1100
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1110

Example 1: When there is an indication of a DP-VOL

TRBL04-1110
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1120

Example 2: When there is no indication of a DP-VOL

TRBL04-1120
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1130

[Link] Recovery from External VOL Write Error

When an External VOL Write Error occurs, perform the following recovery procedure.

Pinned track whose failure type is External VOL Write

Error exists.

Recover the device in the external storage system

according to the maintenance procedure. (*1)

Is
the device in the No (*2)
external Storage System 16
recovered? (TRBL04-1170)

Yes

Is the External volume Yes

blocked?
Reconnect to the external volume. (*3)
No

Is it instructed to recover
the pinned track by writing data from the Yes
host in the maintenance procedure for the
external storage system? Restore External VOL Write Error in ECC/LRC
recovery procedure listed in a procedure of “4.2.3
Procedure for Erasing Pinned Track”.
No

Is there any Pinned Yes

track?
Perform either of the following procedures.
No • Perform dummy replacement of the Controller Board (*4)
• Set the System Option Mode 833 to ON (See MPC05-
880.), and then set it to OFF after disconnecting the
external volume (*5)

END

TRBL04-1130
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1140

*1: It should be done in the external Storage System. The user needs to ask the service personnel of
the external Storage System to perform the maintenance operation of the Storage System. (If the
external Storage System is Hitachi storage, recover the faulty part according to the Maintenance
Manual.)
*2: Because data on device of external Storage System cannot be secured with this case, it is not
possible to recommend it. However, you might be able to perform the procedure in the emergency
case that the recovery from the hardware failure of only the local storage system is prioritized
because the maintenance work of the local storage system which is suppressed due to the presence
of the pinned track (for example, firmware update) can be performed.
*3: It should be done using Storage Navigator or CCI. Ask the customer to perform the recovery
operation by using Storage Navigator or CCI according to the “Hitachi Universal Volume Manager
User Guide” or “Command Reference”.
*4: Execute dummy replacement of either Controller Board 1 or Controller Board 2. Please see
REPLACEMENT SECTION “2.4 Replacing a Controller Board” to know how to replace.
*5: When disconnecting the external volume, if the LDEV created from the target external volume
is defined in the DP pool, all the DP volumes created from the corresponding DP pool need to be
blocked in advance.

TRBL04-1140
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1150

[Link] Recovery from External VOL Read Error

When an External VOL Read Error occurs, perform the following recovery procedure.

Pinned track whose failure type is External VOL Read

Error exists.

Recover the device in the external storage system

according to the maintenance procedure. (*1)

Is
the device in the No
external Storage System 16
recovered? (TRBL04-1170)

Yes

Is the External volume Yes

blocked?
Reconnect to the external volume. (*2)
No

Is it instructed to recover
the pinned track by writing data from the Yes
host in the maintenance procedure for the
external storage system? Restore External VOL Read Error in ECC/LRC
recovery procedure listed in a procedure of “4.2.3
Procedure for Erasing Pinned Track”.
No

Is there any Pinned Yes

track?
Perform either of the following procedures.
No • Perform dummy replacement of the Controller Board (*4)
• Set the System Option Mode 833 to ON (See MPC05-
880.), and then set it to OFF after disconnecting the
external volume (*5)

END

TRBL04-1150
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1160

*1: It should be done in the external storage system. The user needs to ask the service personnel of
the external storage system to perform the maintenance operation of the storage system. (If the
external storage system is Hitachi storage, recover the faulty part according to the maintenance
manual.)
*2: It should be done using Storage Navigator or CCI. Ask the customer to perform the recovery
operation by using Storage Navigator or CCI according to the “Hitachi Universal Volume Manager
User Guide” or “Command Reference”.
*3: Execute dummy replacement of either Controller Board 1 or Controller Board 2. Please see
REPLACEMENT SECTION “2.4 Replacing a Controller Board” to know how to replace.
*4: When disconnecting the external volume, if the LDEV created from the target external volume
is defined in the DP pool, all the DP volumes created from the corresponding DP pool need to be
blocked in advance.

TRBL04-1160
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1170

[Link] Recovery Processing of the Device in the External Storage System

When the device of an external storage system is not recovered, perform the following recovery procedure.

16

Is the
device in the external Yes
storage system DP pool-
VOL?
No 17
Stop I/O to the external volume. (TRBL04-1180)

Is the external Yes

volume blocked?

No Reconnect to the external volume. (*1)

Collect dump. (See MAINTENANCE PC

SECTION “5.2 Dump”.)

No
Does backup exist?

Yes Backup data. (*2)

Delete the external volume.

See Hitachi Universal Volume Manager User
Guide.

Does pinned track Yes

remain?

No
T.S.D. call
Newly create the same volume as the deleted
LU. See Hitachi Universal Volume Manager
User Guide.

Restore data to the newly created volume

from the backup.

Resume I/O to the external volume.

END

TRBL04-1170
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1180

17

Stop an I/O to the POOL concerned. (*3)

When System Option Mode 896 is turned on,

it turns it off. (Refer to MAINTENANCE
PC SECTION “5.8 Setting System Option
Mode”.)

Confirm on “5.12.3 Pin Data Indication” in

MAINTENANCE PC SECTION DP-VOLs
containing the pinned track.

Acquire the backup of DP-VOLs containing

the pinned track as much as possible.

Blockade DP-VOLs containing the pinned

track.

Perform LDEV FORMAT for all DP-VOLs

blockaded. (MAINTENANCE PC SECTION
“[Link] Formatting a Specific LDEV”.) (*4)

Execute the shrink POOL to the pool-VOL

containing the pinned track.

Recover the data from the backup. (*5)

When System Option Mode 896 is changed

to turning off, it returns it to turning on.
(Refer to MAINTENANCE PC SECTION
“5.8 Setting System Option Mode”.)

Restart an I/O to the POOL concerned.

END

TRBL04-1180
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1190

*1: It should be done using Storage Navigator. Ask the customer to perform the recovery operation by
using Storage Navigator according to the “Hitachi Universal Volume Manager User Guide”.
*2: Backup may fail with a pinned track (address). In such a case, it is necessary to rerun backup from
the next address by skipping the address of the pinned track.
*3: It is necessary to stop an I/O, so that other DP-VOLs should not use the area released by LDEV
FORMAT again.
*4: The area of pool-VOL allocated in DP-VOL is released by turning on System Option Mode 867
and performing LDEV FORMAT to DP-VOL.
As a result, the area where pinned track occurred is separated from DP-VOL.
*5: Please be careful when restoring data from a backup.
If data is backed up per volume (DP-VOL), unallocated areas in the volume are also backed up.
Therefore when the data is restored, a write operation is performed also for the unallocated areas,
and the areas become allocated (though with zero data), resulting in an increase in the used pool
capacity. If many DP-VOLs are restored at a time, the pool may become full.
To restore DP-VOLs, perform the following procedure for each of all DP-VOLs.
(1) Restore the data from the backup
(2) Perform the Reclaim Zero Pages processing
NOTE: When data is restored per file from the backup, only the consumed (allocated) areas
are restored from the backup, so you do not have to perform the Reclaim Zero Pages
processing.

TRBL04-1190
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1200

[Link] Using Failed LBA Output Tool

This section describes the failed LBA output tool that specifies pinned track.
When there is a blocked pool-VOL, restore the pool-VOL before using this tool.
If a pool-VOL is blocked, a pinned track might not be detected or an error message with the error type “Reject
DKC” might be output.
To start the tool:
1. Move to the directory where the tool is installed.
C:\Mapp\ wk\wwxxxxyyyyyy\DKC200\MP\PC
• ww : 88(VSP G130, G350, G370, G700, G900 and VSP F350, F370, F700, F900)
93(VSP E590, E790, E990, E1090)
• xxxx : Model name of DKC
• yyyyyy : Serial number
2. Perform the following program.
[Link]
Description of Failed LBA dialog box:

# Dialog box display item Details

1 [Refresh] button Collected a list of HDEVs with the data amount compression
enabled. Data collection results are displayed in the CU# and LDEV#
combo-boxes.
Selecting [Refresh] from the [File] menu results in the same process.
2 CU# combo box Displays a list of numbers of failed CUs for HDEV.
3 LDEV# combo box Displays a list of numbers of failed LDEVs with the data amount
compression enabled.
4 [Save] button Outputs LBA information specified by the CU#/LDEV# combo
boxes to a text file. Selecting [Save] from the [File] menu results in
the same process.
By default, information is output to C:\Mapp\wk\wwxxxxyyyyyy\
DKC200\OTHERS as a file named FailLBA_HDEVxxxxxxxx.txt
(xxxxxxxx: HDEV number).
If a file with the same name exists in the directory for output, the file
is overwritten.
The directory for output can be changed by using the [Browse]
button.
(To be continued)
TRBL04-1200
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1210

(Continued from preceding page)

# Dialog box display item Details
5 [Save All] button Outputs LBA information for all HDEVs in the CU#/LDEV# combo
boxes to a text file. A file is output for each HDEV#. Selecting [Save
All] from the [File] menu results in the same process.
By default, information is output to C:\Mapp\wk\wwxxxxyyyyyy\
DKC200\OTHERS as a file named FailLBA_HDEVxxxxxxxx.txt
(xxxxxxxx: HDEV number).
If a file with the same name exists in the directory for output, the file
is overwritten. The directory for output can be changed by using the
[Browse] button.
6 [Browse...] button Changes directories to output a text file. Selecting [Browse...] from
the [File] menu results in the same process.
The changed directory for output is effective until the failed LBA
output tool is finished. It returns to the default directory at the next
startup.
7 File output path display Displays the directory that is currently set to output a text file.
8 Progress bar Displays the progress of processing.
9 Status bar Displays supplementary information on the menu items and a short
message.
-- [ × ] button Finishes [Failed LBA Output Tool].
Finishes the tool during information collection (in processing).
Selecting [End] from the [File] menu results in the same process.

Output file example:

Output file image
LBA Information Report.
-------------------------------------------------------------
HDEV: 00000000
-------------------------------------------------------------
LBA Top(hex), LBA End(hex), [Link],Slot,Reason
-------------------------------------------------------------
0000001200000034,000000AB000000CD,00000000,META,Write error
0000006700000089,000000CD000000EF,--------,CMPD,ECC/LRC error

Troubleshooting information:
The following table shows error messages output by the failed LBA output tool.
Error type ID Message
Connection error 0117 Connection error occurred. SVP-DKC
File I/O 1063 File I/O error has occurred.
Reject DKC 2467 Operation was rejected by DKC.
Windows error 2451 An error occurred in the Windows system.
Logical error 2231 Logical error has occurred.\nReboot the SVP and retry the operation.

TRBL04-1210
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1220

This page is for editorial purpose only.

TRBL04-1220
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1230

This page is for editorial purpose only.

TRBL04-1230
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1240

4.3 Recovery Procedure for AL_PA Conflict (SIM = 2190xy)

The following flow chart is a recovery procedure in the case where AL_PA of the nodes (CHB port, Hostʼs
Fibre channel port) which exist on the same loop overlaps. Before performing the following recovery
procedure, the AL_PA of a SIM reporting port is automatically changed into an other AL_PA from previously
given AL_PA. But AL_PA doesnʼt affect the values on Maintenance PC.

START

(1) AL_PA conflict? No

(SIM = 2190xy)

Yes END
(2) Find the conflict port (or host).
See TRBL04-1250.

(3) Is it possible
No
to change AL_PA of a SIM reporting
port?
(5) Change AL_PA of another conflicted
Yes port to unique AL_PA.
(4) Change AL_PA of the SIM reporting
port to the unique that. (6) Conduct dummy replace PCB of the SIM
See MPC04-450. reporting port.

END

NOTE: Whether AL_PA of (3) is changed or not depends on the condition under operation.

TRBL04-1240
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1250

Value of AL_PA after conflict

Value of AL_PA before conflict

1. Please refer to the SSB corresponded to the SIM (=2190xy) to specify values of AL_PA before/after
conflict.
2. When the value of AL_PA before conflict is determined, please find CHB port or Hostʼs Fibre channel
port whose AL_PA conflicts with this port.
3. If the value of AL_PA before conflict is an expected value of AL_PA when the value of AL_PA after
conflict is “00000000”, you do not need to perform the recovery procedure for AL_PA conflict.
(The SIM of AL_PA conflict might be reported in the process of changing the port attribute and the loop
connection might be completed while the value remains the value of AL_PA before conflict.)

TRBL04-1250
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1260

4.4 Recovery Procedure for a Failure on Host iSCSI Interface

4.4.1 Outline
The failure that the iSCSI host device cannot recognize the iSCSI volume of the Storage System correctly
may occur due to device failures and incorrect settings including the following.
• Cable disconnection and incorrect connection between the Storage System and the iSCSI host device
• iSCSI board trouble on the iSCSI host side
• Incorrect Disk connection work from the iSCSI host side (for example, insufficient cable insertion and
incorrect insertion)
• Other failures
The failure recovery method in the field when such failure occurs is described.

[Link] Possible Failures and causes of them

No. Possible error Cause

1 LDEV is not recognized by iSCSI (1) SCSI installation, i.e. recognition and connecting
initiator. procedure from SCSI initiator is not executed correctly.
(2) Problem of iSCSI cable or connection.
(3) Problem of iSCSI initiator. iSCSI board, device driver
version, parameters, etc.
(4) SCSI path definition.
(5) The Host Reserve status is left uncanceled.
(6) Other

TRBL04-1260
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1270

[Link] Matters must be or desirable to be checked

No. Checkpoint Check method
1 Is the READY LED on the DKC on? Check the storage system visually.
2 Is the LED of the port, which Check the storage system visually.
corresponds to the failed SCSI port,
on?
Open the System window from
Action menu of Storage Navigator
main window and check
whether the port status indicator is
on.
3 Is the location of the CHB port Refer to LOCATION SECTION “4.1 Channel Interface”.
correctly understood?
4 Is the status of the CHB • VSP G130/G350/G370/G700/G900/F350/F370/F700/F900:
corresponding to the failed SCSI Check the CHB status in the “Maintenance” window.
path normal? (Refer to “4.4.4 Procedure for Checking Normalcy of the
CHB”.)
• VSP E590/E790/E990/E1090:
Check the CHB status by using Maintenance Utility.
(Refer to “4.4.4 Procedure for Checking Normalcy of the
CHB”.)
5 Is the iSCSI cable connected to the Pull out and then insert the cable connector.
iSCSI board of the server firmly?
6 Is it a problem of the cable? Replace the cable.
7 Is the SFP of the PCB normal? SIM: Check if the 21A8xx is output.
Check the SFP status of the CHB on Maintenance Utility.
Pull out and then inset the SFP.
8 Is the SCSI path set correctly? Check the SCSI path of the port concerned.
9 Is the device defined as the SCSI Check the LDEV status in the “Logical Devices” window of
path normal? Web Console. (Refer to MAINTENANCE PC SECTION “4.1.2
Checking the Logical Devices”.)
10 Is the CNA of the NIC/iSCSI Replace the CNA of the NIC/iSCSI or update the driver
normal? version.
11 Is the setting of the connection target Check if the MTU (Maximum Transmission Unit) size set for
device normal? the Switch is large enough to accommodate the packet of the
MTU size set for the host or the MTU size set for the DKC
iSCSI port.
12 When the VLAN setting is enabled, check if the Port setting on
the Switch side is in the trunk mode.
13 Is the Ping for the iSCSI Port Check the settings of the IP address, subnet mask and default
normal? gateway of the iSCSI Port.
When connected by the IPv6 address, check if the IPv6 address
status of the iSCSI Port is enabled.
14 Is Login to the iSCSI Port completed When the CHAP setting is enabled, check if the CHAP User/
normally? Secret setting is correct.

TRBL04-1270
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1280

4.4.2 Recovery Procedure When Device Is Not Recognized

The device cannot be recognized.

Is the power of the No

Turn on the power.
DKC turned on?
Yes

Is the cable connected to No

Connect the iSCSI cable.
the iSCSI Port?

Yes

Is the
location of the CHB port, No Make sure of the port at the
which is the port concerned, correct location.
correct?
Yes

Is the port No Recover the PCB that includes

concerned normal? the blocked port.
Yes

Are
both the following
met? Insert the SFP again and if the
No trouble is not solved in spite of
・The SFP is inserted correctly.
・The SIM = 21a8xx is the operation, replace it.
not reported.
END
Yes

Does the iSCSI

No
Port respond to the ping issued by the
host?

Yes One or more of the following items may be the cause of a communication problem.
Check the validity of each item and take actions if there is any problem.
・ VLAN setting
・ Firewall setting
・ Cable connection between the Storage System and the host
・ Power status of the network peripherals (Switch/router) between the Storage
System and the host
・ Are the settings of respective IP addresses, subnet masks, default gateways and
MTU values of the Storage System and the host computer set correctly to comply
with the network?
・ Is the host port linked up?
・ Is the Switch in the trunk mode when the connection is performed with VLAN
enabled?

No Was the device

recognized?

1 Yes
(TRBL04-1290) END
TRBL04-1280
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1290

Is IPv6 enabled in
Yes
the IP address setting of the iSCSI
Port?

No Is the address status of the

Yes No
IPv6 address “Enabled”?
Check if the IPv6 address is set
Yes correctly. Refer to Table 4-3.
Is the iSNS server used?

No Are the IP
address of the iSNS server
Yes No
and the IP address set for the iSCSI Port
on the DKC side matched?
Set the IP address of the iSNS
server correctly.
Is login to the iSCSI Port No
completed normally?

Yes
Is the IP address of
the iSCSI Port on the DKC side No
set by the host at the login time
correct?
Set the IP address correctly.

Yes

END
No Is the CHAP authentication set?

Yes

Is the user secret of the

CHAP authentication set correctly?
Yes
When using the two-way authentication, is the
CHAP information of the iSCSI target
set to the host?

No

Set the user secret of the CHAP

authentication correctly.

2 END
(TRBL04-1300)

TRBL04-1290
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1300

Is the SCSI path No

Redefine the path. (*1)
definition correct?

Yes

Are the LUN

Security setting and the iSCSI No Modify the iSCSI Name to be
Name registration setting registered in LUN Security. (*2)
correct?

Yes

Is the virtual LDEV No Set the virtual LDEV ID

ID set correctly? correctly again.

Yes
Release the GAD reservation
Is the GAD reservation being set to the virtual
Yes
set to the virtual information of the information of the LDEV ID,
LDEV ID? and then set the virtual LDEV
ID.
No

Is the LU Status No See TRBL04-1340

information normal?

Yes
Power off the host.

Replace the iSCSI cable.

Reboot the host.

Was the device Yes

recognized?

No
Power off the host.

Reboot the host.

Was the device Yes

recognized?

No

T.S.D. call (*3) END

TRBL04-1300
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1310

*1: If the firmware version is earlier than 88-02-01-x0/xx and the paths allocated to iSCSI targets
created automatically through Hitachi Storage Advisor Embedded (HSAE) (iSCSI Target Alias
starting with “[AutoConfig]”) are defined, perform the procedure through HSAE. For the detailed
procedure, see Hitachi Storage Advisor Embedded Guide “Detaching volumes from a server” and
“Attaching volumes to servers by selecting servers”. To start HSAE, specify the URL in the Web
browser (see the table in “2.7.3 Starting the Maintenance Utility Window by Specifying IP Address
of CTL” in MAINTENANCE PC SECTION).
*2: If the firmware version is earlier than 88-02-01-x0/xx and the iSCSI names are defined for iSCSI
targets created automatically through Hitachi Storage Advisor Embedded (HSAE) (iSCSI Target
Alias starting with “[AutoConfig]”), perform the procedure through HSAE. For the detailed
procedure, see Hitachi Storage Advisor Embedded Guide “Editing server settings”. To start HSAE,
specify the URL in the Web browser (see the table in “2.7.3 Starting the Maintenance Utility
Window by Specifying IP Address of CTL” in MAINTENANCE PC SECTION).
*3: Send the following information to the Technical Support Division (T.S.D.).
• Device configuration of the host
• Version of the OS
• NIC/CNA version
• Version of the driver
• Model number of the iSCSI board
• Dump information on the DKC (See MAINTENANCE PC SECTION “5.2 Dump”.)
• Syslogs and/or Messages
• Logs of software when the alternative path exists
• Packet capture information
• Dump information on the CHB (for 25G iSCSI CHB) (See MAINTENANCE PC SECTION “3.34
Downloading CHB Dump”.)

TRBL04-1310
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1311

Table 4-3 iSCSI IPv6 Connection Failure Troubleshooting Table

Check Item Troubleshooting
Are the correct values set to the IPv6 address The IPv6 address and default gateway of the iSCSI Port are
and default gateway address of the iSCSI Port generated automatically. When setting them manually, set
to be connected? the appropriate value to the customerʼs environment.
Address status display of the Checking Checking if the IPv6 address and the address of the other
IPv6 address of the iSCSI Port host in the connection network are not duplicated. Check
that the transition is enabled.
Enabled The IPv6 address of the iSCSI Port is not duplicated. The
address is set correctly and normal.
Disabled The iSCSI Port is linked down.
When using the IPv6 address of the iSCSI Port, check that
the cable is connected correctly.
Duplicated The IPv6 address of the iSCSI Port and the address of the
other host in the connection network are duplicated. Set an
unduplicated optional IPv6 address manually.
Unconfirmed The IPv6 address of the iSCSI Port is duplicated with the
address in the same iSCSI Port.
Set an unduplicated optional IPv6 address in the iSCSI Port
manually for the IPv6 address of the iSCSI Port.
Is the correct value set for the MTU size? The IPv6 Link MTU size indicates the MTU size current
value on the network.
When the MTU size and the Link MTU size set for the
iSCSI Port of the Storage System differ, the MTU size of
the host or the router/Switch is different from that of the
Storage System.
Set the MTU size to be the same value.
Is the IPv6 address set correctly in the remote The IPv6 address needs to be enabled.
path setting of the IPv6 address? Enable the IPv6 address in both local and remote iSCSI
Ports to set the remote path.

TRBL04-1311
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1320

4.4.3 Procedure for Checking Storage System Port Status

The port information of the destination Storage System is displayed in the “Port Status” window ([Action] –
[Component Maintenance] – [View Port Location]) of Web Console.

In the “Port Condition” box, the statuses of the ports are displayed in the image of the practical storage
system.
Channel Adapter, Adapter type, Port ID, Attribute and Condition are displayed for the each port.
The statuses of the displays of the port status are explained below.

Port Condition Port Means

Available(Connected) The port is installed and in use.
Available(Not Connected) The port is installed and ready for use.
Not Available The port is installed and not ready for use (blocked).
Not Installed The port is not installed or out of use.

TRBL04-1320
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1330

4.4.4 Procedure for Checking Normalcy of the CHB

• VSP G130/G350/G370/G700/G900/F350/F370/F700/F900:
Use the “Maintenance” window to check normality of CHBs. Check the status of CHBs installed in the
Controller Chassis (DKC) and the Channel Board Box (CHBB). For how to check the status of CHBs, see
MAINTENANCE PC SECTION “[Link] DKC Information View”. When the status of a CHB is normal,
“Normal” is displayed in the [Status] column of the CHB.

TRBL04-1330
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1331

• VSP E590/E790/E990/E1090:
In the “Maintenance Utility” window, click [Hardware] – [All Chassis] – [Controller Chassis], and open the
[CHBs] tab to check the CHB status. When the status is normal, “Normal” is displayed as shown below.
For VSP E990/E1090

For VSP E590/E790

TRBL04-1331
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1340

4.4.5 Procedure for Checking Status Information of LUN or LDEV for which Namespace
ID Is Set
Select [Logical Device] from the [Storage System] tree on Web Console and display the [LDEVs] tag.
Clicking [LDEV ID] of the reference LDEV displays the detail window information.
If the displayed status is not Normal, it is highly possible that the device cannot be recognized.
Therefore, call the T.S.D. having the detail window information (the following window) attached.

TRBL04-1340
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1350

4.5 Recovery Procedure When Disconnection of Host Is Detected during iSCSI Firmware
Update (SIM = 3c97xx)

START

Explain the following to the customer:

• Connections between iSCSI hosts or iSCSI remote paths and CHBs
were temporarily disconnected by the internal processing during the
firmware updates work. The iSCSI firmware update was skipped because
connections of some iSCSI hosts or iSCSI remote paths were not restored
within the prescribed time.
• Therefore, after the firmware updates work, the iSCSI firmware update
for CHBs for which the iSCSI firmware update was skipped must be
performed.

Ask the customer to do the following:

Check all connections of iSCSI hosts or iSCSI remote paths to CHBs
(*1) of which connections to iSCSI hosts or iSCSI remote paths were not
restored within the prescribed time are restored. If there are disconnected
hosts, perform connection operations on the hosts. Disconnected iSCSI
remote paths are automatically restored.

After obtaining a permission to resume updates from the customer, perform

the firmware updates work again using the same firmware media. (*2)

Is SIM = 3c97xx Yes

reported?

No
Ask the customer to check that there is no problem in connecting the iSCSI
hosts to the storage system. If the CHBs are connected to iSCSI remote
paths, verify that the iSCSI remote paths were automatically restored.

END

*1: The lower two digits of the SIM reference code represent a CHB on which a disconnection to
a host or iSCSI remote path is detected. See the Remarks column of SIM = 3c97xx in SIM RC
SECTION.
*2: The iSCSI firmware update for CHBs for which the iSCSI firmware update was skipped is
executed. The iSCSI firmware update for CHBs for which the iSCSI firmware update was executed
is skipped. If SIM = 3c97xx (detection of disconnection of host) is reported during the iSCSI
firmware update for a CHB of a succeeding location number, perform the recovery procedure
again.
TRBL04-1350
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1360

4.6 Procedure When Open System Host Reservation Is Detected (SIM = ac9100)
If the storage system processes an I/O between an initiator (host A in the figure) connected through Fibre
Channel and an LDEV and detects that SCSI-3 reservation is set for the LDEV by another initiator (host B in
the figure), the storage system returns “Reservation Conflict” to the initiator (host A).
SIM = ac9100 is reported when the storage system detects that the initiator (host B) that is the reservation
holder logs out from the storage system without releasing the SCSI-3 reservation for some reason. A
connection configuration example (*1) is shown below.

Host A Host B Host A Host B

Fibre Channel Fibre Channel

connection connection
Port A Port B Port A Port B

Storage System Storage System

LDEV LDEV

: Being logged in : Being logged in

: Reservation holder : Being logged out
: Reservation holder

(a) When the reservation holder is logged in (b) When the reservation holder is logged out
(normal state) (state where SIM = ac9100 is reported)

The host B is the reservation holder. The storage The host B is the reservation holder. The storage
system returns “Reservation Conflict” to the host A. system returns “Reservation Conflict” to the host A.
(Errors occur for I/Os from the host A.) (Errors occur for I/Os from the host A.)
If the host B releases the SCSI-3 reservation during If the host B logs out without releasing the SCSI-
login, I/Os from the host A will be possible. 3 reservation, information about the SCSI-3
reservation by the host B will remain in the storage
system and I/Os from the host A will be impossible.

*1: In the figure, two ports on the storage system are used for connecting to the two hosts. The same
thing applies to a configuration where a FC switch connected to one port on the storage system is
connected to multiple hosts.

TRBL04-1360
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1370

Table 4-4 SIM Information about SCSI-3 Reservation

Byte offset Description
0x40-0x47 WWN of the host (initiator) for which the SCSI-3 reservation was detected
(little endian)
0x48-0x49 LUN of the host that issued the SCSI command
0x4C bit4-7, 0x4D bit0-3 Port number (*2) for the host (initiator) for which the SCSI-3 reservation was
detected
0x4F Host group ID of the host (initiator) for which the SCSI-3 reservation was
detected
0x50-0x57 WWN of the host (initiator) that is the reservation holder
(little endian)
0x5C bit4-7, 0x5D bit0-3 Port number (*2) for the host that is the reservation holder
0x5F Host group ID of the host that is the reservation holder
0x60-0x67 Reservation key of the host that is the reservation holder
0x68-0x6B The time when the host that is the reservation holder secured the reservation
(Time-of-day (TOD))
0x6E bit0-3 Reservation information of the host that is the reservation holder (*3)
• 0x1 : Write Exclusive
• 0x3 : Exclusive Access
• 0x5 : Write Exclusive Registrants Only
• 0x6 : Exclusive Access Registrants Only
• 0x7 : Write Exclusive All Registrants
• 0x8 : Exclusive Access All Registrants
• Others : unused
0x76-0x77 LDEV number for which the SCSI-3 reservation was detected
*2: Red square in the following window. The upper red square is the port number for the host for
which the SCSI-3 reservation was detected, and the lower red square is the port number for
the host that is the reservation holder. For port numbers and CHB locations, see “Table 4-17
Relationship between Cluster # and Channel Port#” in THEORY OF OPERATION SECTION.
*3: Blue square in the following window.

TRBL04-1370
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL04-1380

START

From the “Content – SIM” window, display

the “Content – SSB” window (see “[2]
SIM Log” in “5.3.1 Log Indication” in
MAINTENANCE PC SECTION).

Information about the host (initiator) for

which the SCSI-3 reservation was detected
and the host that is the reservation holder
is included in Internal Data that starts from
byte 0x40 in the “Content-SSB” window.
Check each information according to Table
4-4.…(a) (*1)

Tell the information (a) to the system

administrator and ask him or her whether it
is appropriate for the host that is not logged
in to the storage system to be the reservation
holder.

No
Is it appropriate?

Ask the system administrator to release the

Yes SCSI-3 reservation on the host side.

Can the SCSI-3 reservation No

be released?
On the storage system side, release the
SCSI-3 reservation forcibly (see “raidcom
Yes modify lun” in “Command Control Interface
Set the System Option Mode 1307 to ON to Command Reference”).
prevent the SIM from being output.

Is “Reservation Yes
Conflict” still detected on the
host side?
Collect dumps and contact T.S.D.

No

Complete the SIM.

END
*1: When using CCI (Command Control Interface) version 01-70-03/XX or later, you can get the latest
information on the reservation holder by running the raidcom get ldev command (for details, see
“Command Control Interface Command Reference”).

TRBL04-1380
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-10

5. ShadowImage Error Recovery

5.1 Recovery Procedure for ShadowImage Suspend Pair (SIM = 47dxyy, 7ff102, 47e700)

Recovery for pair suspend

SSB = 21E3 Yes

exists?
No
Primary Volume Error
SSB = 21E4 Yes 1
5 (TRBL05-20)
exists? or
Other Error (TRBL05-30) Secondary Volume Error
No 2
(TRBL05-20)
SSB = 21E7 Yes
5
exists?
Other Error (TRBL05-30)
No

SSB = 21E6 or Yes

6
pinned track exists?
PIN exist (TRBL05-40) This code means that the load on the storage
No system is high.
SSB = 211B Yes Lower the load, resynchronize the pair, and
exists? then do the same operations as you did before
the pair became suspended. (*1)
No

SSB = 211D Yes This code means that TC data which cannot be
exists? copied by ShadowImage exists.
After deleting TC Pair which is related with
No
ShadowImage Pair and resynchronizing the
SSB = 21E1 Yes pair, do the same operations as you did before
5
exists? the pair became suspend. After resynchronizing
Other Error (TRBL05-30) ShadowImage Pair, create the TC Pair. (*1)
No

SSB = 21E2 Yes

5
exists?
Other Error (TRBL05-30)
No

SSB = 21A4 Yes

5
exists?
Other Error (TRBL05-30)
No
These codes indicate that the function of
SSB = 222A or Yes splitting a pair by specifying a consistency
SSB = 222C exists? group failed. Ask users to resynchronize the
pair after removing the cause of error. (*1)
No
OPEN - “Stat & History”.

7 (TRBL05-40)

TRBL05-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-20

Primary Volume Error

1

Check Primary Volume status.

(See MPC04-110)

Primary Volume Yes

is Normal?
No
Restore the Primary Volume status. Temporary error.

RESYNC the Pair. (*1) RESYNC the Pair. (*1)

Secondary Volume Error

2

Check Secondary Volume status.

(See MPC04-110)

Secondary Yes
Volume is Normal?

No
Restore the Secondary Volume status. Temporary error.

RESYNC the Pair. (*1) RESYNC the Pair. (*1)

TRBL05-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-30

Suspend by SM volatile
3

Check SSB

Yes
SSB=001D exists?

No

T.S.D. call RESYNC the Pair. (*1)

Suspend by operation
4

This pair may be suspended.

RESYNC the Pair. (*1)

Other Error
5

Check status.

All Yes
Normal?
No

Restore the Failure Part. May be temporary error.

RESYNC the Pair. (*1) RESYNC the Pair. (*1)

TRBL05-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-40

PIN exist
6

Check PIN.

Does PIN Yes

exist?
No

May be temporary error. Recover the PIN slot.

RESYNC the Pair. (*1) RESYNC the Pair. (*1)

Is there “ALL SP- Yes

PEND SUSPEND BY SM VOLATILE” 3
message? Suspend by SM volatile
(TRBL05-30)
No

Is there “PAIR SUSPEND” Yes

4
message for the Pair?
Suspend by operation
(TRBL05-30)
No

T.S.D. call

*1: If a failure occurs after capacity expansion of one volume of a pair is successful, resynchronizing
the pair is not possible due to capacity inconsistency. Perform capacity expansion so that the
capacities are consistent, and then resynchronize the pair.

TRBL05-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-50

5.2 ShadowImage Initialize procedure

START

(Request to user)
Stop Job/Script to operate the pair
(ShadowImage pair and the other pairs (*1))

Do Thin Image Advanced pairs No

exist?

Yes

Make a note of the volumes of the Thin Image

Advanced pairs.

Is
No there a Thin Image
Advanced pair with snapshot data retention
period enabled? (*2)

Yes

Confirm that the Thin Image Advanced pair with

snapshot data retention period enabled is allowed to
be deleted.

Turn on the mode to forcibly delete a Thin Image

Advanced pair with snapshot data retention period
enabled.

(Request to user)
Confirm that the pairs (ShadowImage and other P.P.
(*1)) are allowed to be deleted.

Click [Apply] button

(Select [Actions] of the main window. Select [Local
Replications]-[Initialize Local Replica Pairs])

Check the following SSB

SSB = 202A, 23FC (SI Initialize Start)
23FD (Normal end)
([Information] [SSB])

1
(TRBL05-51)

TRBL05-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-51

Check the message INITIALIZE START /

INITIALIZE END
(Select [Actions] of main window. Select [Local
Replications]-[View Histories])

Click [Refresh All]

(Storage Navigator [File] -> [Refresh All])

Did the Thin Image No

Advanced pairs exist before the SI
Initialize?

Yes

Is the
No mode to forcibly delete a
Thin Image Advanced pair with snapshot data
retention period enabled on?

Yes

Turn off the mode to forcibly delete a Thin Image

Advanced pair with snapshot data retention period
enabled.

Perform the LDEV formatting on the volumes of the

Thin Image Advanced pairs that you made a note of.
(*3)

(Request to user)
Create ShadowImage pair and the other pairs (*1)

END

There is no problem when the following SSBs occur due to SI initialization:

0b95, 9693, afb2, afb3

*1: When the [Initialize] button is pressed, pairs formed by the following P.P. are also deleted.
[ShadowImage / Volume Migration / Thin Image / Thin Image Advanced]
NOTE1 : Perform the operation only when it is directed by the Technical Support Division.
NOTE2 : For the password, refer to the Technical Support Division.
*2: When SI Initialize is performed, Thin Image Advanced pairs with snapshot data retention period
enabled are also deleted. If there is a Thin Image Advanced pair with snapshot data retention
period enabled, the mode to forcibly delete a Thin Image Advanced pair with snapshot data
retention period enabled must be turned on. If the mode is off, the error code 07005-208607 will
occur. For how to set the mode, ask the Technical Support Division.
TRBL05-51
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-52

*3: For secondary volumes, perform the LDEV formatting on all of them. For primary volumes,
perform the LDEV formatting only on the volumes specified by the Technical Support Division
after backing up them.

TRBL05-52
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL05-60

5.3 Recovery Procedure for Pinned Track

Recovery procedure for pinned track is as follows.

START

Pinned track is ECC/ No

LRC Error?

Yes

Is the volume in No
which the pinned track has
occurred a S-VOL?

Yes
Delete the pair.

Go to pinned track recovery

procedure (TRBL04-160).

If you have deleted the SI pair in this

workflow, create the SI pair.

END

TRBL05-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-10

6. TrueCopy Error Recovery

6.1 TrueCopy Error Recovery Procedure
A TrueCopy pair suspension or a TrueCopy pass blockade may occur owing to hardware errors.
This section explains the recovery procedure against them.
Occurrences of TrueCopy errors can be known through the following.

• TrueCopy error message on the Syslog outputted by RAID Manager (*1)

• Report of a TrueCopy pass blockade occurrence by the SIM
• Report of a TrueCopy pair suspension occurrence by the SIM

Table 6-1 TrueCopy SIM [Link]

SIM REF. CODE Meaning Remarks
d4zxyy TrueCopy pair suspend z : 0 to 2, 4 to 7 or f
x : CU# (see SIMRC02-300 (14))
yy : LDEV#
2180xx Logical path(s) on the remote copy xx : CHB# + Port# in CHB (see SIMRC02-350
connections was logically blocked (27))

When a message indicating that a TrueCopy pair error has occurred is displayed on the Syslog, check the
SIM log of the connected DKC and confirm the conformance of the message on the Syslog with the SIM
logged on the DKC side before starting the recovery using the following flow chart (TRBL06-20).

*1: When the TrueCopy pair is suspended, RAID Manager displays the following message on the
Syslog.

[HORCM_102] Detected a suspending status on this paired volume (Volume: , code: 0x0X).
 : Volume name
0x0X : Pair status (ʻ00ʼ : SMPL, ʻ01ʼ : COPY, ʻ02ʼ: PAIR, ʻ03ʼ/ʼ04ʼ/ʼ07ʼ: PSUS, ʻ05ʼ: SSUS,
Other: PSUE)

TRBL06-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-20

6.1.1 Recovery for TrueCopy Error

START

Yes
SIM = 2180xx? 1
(TRBL06-40)
No
Yes
SIM = d40xyy? 1
(TRBL06-40)
No
Yes
SIM = d41xyy?

No Check the SIM log for the time of

Yes the SIM reported.
SIM = d42xyy? 2
(TRBL06-50)
No SIM = 2180xx Yes
exist?
No 1
(TRBL06-40)
2 (TRBL06-50)

Yes There is no recovery operation. This phenomenon

SIM = d44xyy? occurred by S-VOL PSUS/PSUE operation in RCUʼs Web
Console. (CCI: TC takeover or pairsplit)
No

Yes There is no recovery operation. This phenomenon

SIM = d45xyy? occurred by S-VOL SMPL operation in UCRʼs Web
Console. (CCI: pairsplit)
No
Yes
SIM = d4fxyy? 3
(TRBL06-70)
No

A
(TRBL06-30)

TRBL06-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-30

Yes
SIM = d46xyy?

No

Yes
SIM = d47xyy?

No Check the SIM LOG of MCU.

(Ref. Code = 2180xx)
END
SIM = 2180xx Yes
exist?
No 1
(TRBL06-40)
T.S.D Call

TRBL06-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-40

Select the target path in the Remote Connections window of Web Console. Click
the [View Remote Connection Properties] button to display the View Remote
Connection Properties window. Check the path status in the [Remote Paths] table.

Path Status Yes

Initialization Failed ?
See 6.3 Recovery Action of Path
No Status Error to perform path
recovery operations. (*1)

No Path Status
Communication Time Out?

No Yes
Path Status Normal?

Check MCU failure parts in the

Yes Maintenance Utility window.

4
Yes
(TRBL06-80) Failure part exist?

Repair the failure part.

No

Check RCU failure parts in the Repair the path status by TC or

Maintenance Utility window. GAD Path operation (Refer TC Path
Recovery Procedure: TRBL06-90)
(*1)

Yes
Failure part exist?
Path Status Yes
Normal?
No
Check the connecter, cable and
analyze the failure part. No 4
(TRBL06-80)
T.S.D Call

Yes
Failure part exist?

No

TRBL06-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-50

*1: For the firmware version 88-07-03-x0/xx or later, 88-08-01-x0/xx or later and the firmware version
93-04-01-x0/xx or later, in the configuration that connects VSP G350/G370/G700/G900/F350/
F370/F700/F900/E990 and VSP E590/E790, remote path operations from VSP G350/G370/G700/
G900/F350/F370/F700/F900/E990 by using Storage Navigator (Web Console) are possible.
For the firmware version earlier than 88-07-03-x0/xx, earlier than 88-08-01-x0/xx and the firmware
version earlier than 93-04-01-x0/xx, use RAID Manager (CCI).
For the configuration that connects VSP E1090 and VSP 5000 series, remote path operations
from VSP 5000 series by using Storage Navigator (Web Console) are not possible. So, use RAID
Manager (CCI).

Check the error code in F/M = ʻ8Fʼ SSB log

in time of PSUS/PSUE SIM existing.

Execute a following Recovery Procedure

Repair the pair status by TC Pair operation.

(Refer TC Pair Recovery Operation:
TRBL06-100)

END

TRBL06-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-60

This page is for editorial purpose only.

TRBL06-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-70

Check the SIM Log.

(Ref. Code=2180xy)

Yes
2180xy SIM exist? 1
(TRBL06-40)
No
Check the status display of RCU
and analyze the failure part.

No
Failure part exist?

Yes
Repair the Failure part.

Repair the pair status by TC Pair

operation. (Refer TC Pair Recovery
Operation: TRBL06-100)

Is the Pair status Yes

ʻPAIRʼ or ʻCOPYʼ?

No

T.S.D Call END

TRBL06-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-80

No Is there a failure
SIM of a GAD pair?

Yes
Recover failure of a GAD pair.
(TRBL18-20)

Check the SIM Log and pair status by

the Web Console.
(Is the TC Pair PSUS/PSUE?)

PSUS/PSUE pair No
exist?
Check the pair status of P-VOL and
Yes S-VOL in the “Remote Replication”
Check the pair status in the “Remote window of Web Console for MCU
Replication” window of Web Console. and RCU respectively.

No Pair status Yes

Pair PSUS/PSUE? information of the pair volume
is same?
Yes
No

END
Repair the pair status by TC Pair
operation. (Refer TC Pair Recovery
Operation: TRBL06-100)

Yes Is the Pair status

ʻPAIRʼ or ʻCOPYʼ?

No

END T.S.D Call

TRBL06-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-90

6.1.2 TrueCopy Path Recovery Procedure

START

Check the path status (RCU

Path status) in the “Remote
Connections” window of Web
Console.

Path status Yes

ʻnormalʼ?
The path status has become normal
No automatically by repairing the
Execute Delete path by TC Path failure part.
operation. If the number of logical
path is one, you must execute END
Delete RCU. (*1)

No
Path delete?

Yes
Execute establish path by TC Path
operation. (*1)
(RaidManager: raidcom add rcu)

END T.S.D. Call

*1: For the firmware version 88-07-03-x0/xx or later, 88-08-01-x0/xx or later and the firmware version
93-04-01-x0/xx or later, in the configuration that connects VSP G350/G370/G700/G900/F350/
F370/F700/F900/E990 and VSP E590/E790, remote path operations from VSP G350/G370/G700/
G900/F350/F370/F700/F900/E990 by using Storage Navigator (Web Console) are possible.
For the firmware version earlier than 88-07-03-x0/xx, earlier than 88-08-01-x0/xx and the firmware
version earlier than 93-04-01-x0/xx, use RAID Manager (CCI).
For the configuration that connects VSP E1090 and VSP 5000 series, remote path operations
from VSP 5000 series by using Storage Navigator (Web Console) are not possible. So, use RAID
Manager (CCI).

TRBL06-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-100

6.1.3 TC Pair Recovery Operation

TC Pair Recovery Operation (1/2)

START

Check the pair status in the

“Remote Replication” window
of Web Console.

No No No
Status ʻSMPLʼ? Status ʻPAIRʼ? Status ʻCOPYʼ? A
(TRBL06-110)
Yes Yes Yes
Check the copy operation
No status with Pair status in the
TC Pair? No operation.
“Remote Replication” window
of Web Console.
Yes
Check the S-VOL status in the END
“Remote Replication” window No
Detect error?
of Web Console on RCU.

Yes
Yes
Status ʻSMPLʼ? Execute resync pair after
executing suspend pair by TC
Pair operation. (*2) (*3)
No

Execute delete pair by TC Pair

operation form RCU. [A]
END
(CCI: pairsplit-S)

Execute create pair by TC Pair

operation. (*1) (*3)
(CCI: paircreate)

END

*1: If delete pair operation is executed according to [A], please create pair operation to these TC pairs.
*2: For the CCI, issue the Pairresync command after the Pairsplit command is issued.
*3: If a failure occurs after capacity expansion of one volume of a TC pair is successful, creating or
resynchronizing a TC pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then create or resynchronize the pair.

TRBL06-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-110

TC Pair Recovery Operation (2/2)

No
A Status ʻPSUS/PSUEʼ?

Yes
T.S.D. Call
Execute resync pair by TC Pair
operation. (*2) (*4)
(CCI: pairresync)

Yes Is the Pair status ʻPAIRʼ

or ʻCOPYʼ?

No

Execute create pair after delete pair

by TC Pair operation.
(*1) (*3) (*4)

END

*1: If delete pair operation does not complete, please try force delete pair operation.
*2: If TrueCopy pair detail is ʻSSWS (S-VOL Swapping)ʼ on the CCI (pairdisplay-fc), please execute
resync pair operation (pairresync-swaps).
*3: For the CCI, issue the Paircreate command after the Pairsplit-S command is issued.
*4: If a failure occurs after capacity expansion of one volume of a TC pair is successful, creating or
resynchronizing a TC pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then create or resynchronize the pair.

TRBL06-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-120

6.1.4 Procedure when the host hangs

If a host hangs up while it is writing data in TrueCopy P-VOLs, data difference between paired P-VOL and
S-VOL may occur because of reasons as follows.

1. A write command didnʼt finish normally for some reason in DKC and it reported check condition to the
host, but because of the hang-up, the host didnʼt retry the command.
2. During a process of a write command in DKC, a reset message was issued from the host and stopped the
write command process, but because of the hang-up, the host didnʼt retry the command.

In this case, since write data of the last write command before hang-up was not written on the disk
completely, please restart the job in order to complete the aborted command.

6.1.5 Recovery procedure when an error of TrueCopy pair operation occurs

When either MCU or RCU is in a highly loaded condition, a pair operation (a command for paircreate,
pairsplit, or pairsplit-S) from a CCI to one or multiple TrueCopy pair volume(s) may fail in (EX_CMDRJE
or EX_CMDIOE). In this case, please check the pair status of the volumes that are objects of the operation. If
the status is the same as before the pair operation, please retry the same pair operation.

TRBL06-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-130

6.1.6 Special note of pair recovery procedure when SIM=d4fy-yy is generated

The special note in the recovery procedure from Web Console when this SIM is generated when Paircreate or
the Resync operation is executed, and the state of the pair enters the following states is shown below.

 When this SIM is generated when Resync is operated

It ..state of the pair.. ..following.. explains the deletion of the object pair (make to SMPL) on the RCU
side when becoming P-VOL = SMPL, S-VOL = PAIR or COPY.

Execute the Delete Pairs (pairsplit-S) operation on the S-VOL, and then perform the Create Pairs
operation again.

 When this SIM is generated when Resume is operated

The state of the pair is P-VOL = PSUS/PSUE, S-VOL = PAIR or COPY.

The recovery procedure:

See “6.1.3 TC Pair Recovery Operation” to perform the recovery procedure.
If the pair resynchronization fails, execute the Delete Pairs (pairsplit-S) operation on the P-VOL, and
then perform the Create Pairs operation again.

TRBL06-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-140

6.2 Pinned Track Recovery Procedure for TrueCopy

Pinned track recovery procedure for TrueCopy is as follows.

START

Delete the TC volume pair in which the

pinned track has occurred.

Did the maintenance No

work fail? (*1)

Yes Error type of the ECC/LRC Error

Execute “4.2 Pinned track recovery”.(*1) pinned track?
However, data recovery of the TC pair
is not included. (*2) Write Error
Execute the existing Write Error Check if there is a hardware error
track recovery procedure. on the “Maintenance Utility”
Refer to the Write Error track window and solve the hardware
recovery procedure (start from problem.
ƒ TRBL04-260). However, data
recovery of the TC pair is not
included. (*2)

1 2
(TRBL06-150) (TRBL06-150)

*1: In the recovery from a pinned track, only the LDEV formatting is executed except in the case of
Solaris. For Solaris, only the correction of a pinned track by means of the analyze command is
executed. To recover the data of the TC pair, reconfigure the TC volume pair.
However, the LDEV formatting or the analyze command executing is not required if the pinned
track is a DP volume and out of the user area.
*2: The data of the TC pair is recovered by reconfiguring the TC volume pair.

TRBL06-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-150

2 1

Does Pinned No
track exist outside the userʼs
area? (*3)

Yes

Is the Capacity
Saving setting of the Yes
volume in which the pinned track
has occurred other than
disabled?

No
Perform the Reclaiming the control Execute “4.2 Pinned track recovery”.(*1)
pages inside the DP-VOL. However, data recovery of the TC pair
(Refer to “3.52 Reclaiming the Control is not included. (*2)
Pages Inside the DP-VOL”.)

Reconfigure the TC volume pair.

END

*1: In the recovery from a pinned track, only the LDEV formatting is executed except in the case of
Solaris. For Solaris, only the correction of a pinned track by means of the analyze command is
executed. To recover the data of the TC pair, reconfigure the TC volume pair.
However, the LDEV formatting or the analyze command executing is not required if the pinned
track is a DP volume and out of the user area.
*2: The data of the TC pair is recovered by reconfiguring the TC volume pair.
*3: If MAINTENANCE PC SECTION “5.12.3 Pin Data Indication” does not indicate LBAs of pinned
track, this indicates that a pinned track occurred outside the user area.

TRBL06-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-160

6.3 Recovery Action of Path Status Error

Path Status Factor Recovery Action

“Nothing” Establishing path or deleting Delete the path with “Edit Path” or “Delete
path RCU”, add a new path with “Edit Path” or
“Add RCU”. (*1)
“Initialization Failed” Incorrect the physical Correct the physical path connection
connection between the MCU between the MCU, RCU and the path
and RCU relay equipment.
Incorrect the Port topology Setup the port topology of the both MCU
settings.(Fibre connection) and RCU correctly.
Blockade of the MP or Port on Repair the MP status or Port status on the
the RCU. RCU.
Broken the connection cable Replace the broken cable.
physically.
Incorrect the path relay Correct the path relay equipment settings
equipment settings or the path or repair it.
relay equipment doesn't work.
“Communication Time Out” Blockade of the MP or Port on Repair the MP status or Port status on the
the MCU. MCU.
“Resource Shortage (MCU)” MCU resource over. Too many path in the MCU or the RCU.
“Resource Shortage (RCU)” RCU resource over. Delete the paths and RCUs not currently
in use. (*1)
“Serial Number Mismatch” Incorrect the RCU S/N or Delete the path with “Delete RCU”, add a
Controller ID. new path with the correct RCU S/N and
(Fibre connection) Controller ID with “Add RCU” again. (*1)
Incorrect the physical Correct the physical path connection
connection between the MCU between the MCU, RCU and the path
and RCU. relay equipment.
Incorrect the Port topology Setup the port topology of the both MCU
settings. (Fibre connection) and RCU correctly.
Blockade of the MP or Port on Repair the MP status or Port status on the
the RCU. RCU.
Broken the connection cable Replace the broken cable.
physically.
Incorrect the path relay Correct the path relay equipment settings
equipment settings or the path or repair it.
relay equipment doesnʼt work.
(To be continued)

TRBL06-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-170

(Continued from the preceding page)

Path Status Factor Recovery Action
“Invalid Port” Specified port is not existence Delete the path with “Edit Path” or “Delete
on the MCU. RCU”, add a new path with correct port
on MCU again. (*1)
Incorrect specified port type Delete the path with “Edit Path” or “Delete
“Fibre”. RCU”, add a new path with correct port
type “Fibre” again. (*1)
Specified MCU port type is not Change the channel type of the MCU port
Bidirectional. to Bidirectional.
“RCU Port Number Mismatch” Incorrect the specified RCU Delete the path with “Edit Path” or “Delete
port. RCU”, and add a new path with correct
RCU port again. (*1)
Incorrect the physical Correct the physical path connection
connection between the MCU between the MCU, RCU and the path
and RCU. relay equipment.
Incorrect the Port topology Setup the port topology of the both MCU
settings. (Fibre connection) and RCU correctly.
Blockade of the MP or Port on Repair the MP status or Port status on the
the RCU. RCU.
Broken the connection cable Replace the broken cable.
physically.
Incorrect the path relay Correct the path relay equipment settings
equipment settings or the path or repair it.
relay equipment doesnʼt work.
“Pair-Port Type Mismatch” Incorrect specified RCU port. Delete the path with “Edit Path” or “Delete
RCU”, and add a new path with correct
RCU port again. (*1)
Specified RCU port type is not Change the channel type of the RCU port
Bidirectional. to Bidirectional.
If the port attribute is set to Bidirectional,
perform either of the following:
• Disconnect the cable from the RCU port,
and then reconnect it.
• Disable or Enable the FC switch port
that is connected to the RCU port.
(To be continued)

TRBL06-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-180

(Continued from the preceding page)

Path Status Factor Recovery Action
“Communication Failed” Blockade of the MP or Port on Repair the MP status or Port status on the
the RCU. RCU.
The path relay equipment Repair the path relay equipment.
doesnʼt work.
“Logical Blockade” MCU Port doesnʼt work. Repair the port status on the MCU.
RCU Port doesnʼt work. Repair the port status on the RCU, and
delete the path with “Edit path” or “Delete
RCU” and add the path with “Edit path” or
“Add RCU” again. (*1)
The path relay equipment Repair the path relay equipment, and
doesnʼt work. delete the path with “Edit path” or “Delete
RCU” and add the path with “Edit path” or
“Add RCU” again. (*1)
Broken the connection cable Replace the broken cable, and delete the
physically. path with “Edit path” or “Delete RCU”
and add the path with “Edit path” or “Add
RCU” again. (*1)
“Program Error” Detected program error. Delete the path with “Edit path” or “Delete
RCU”, and add the path with “Edit path”
or “Add RCU” again. (*1)
*1: For the firmware version 88-07-03-x0/xx or later, 88-08-01-x0/xx or later and the firmware version
93-04-01-x0/xx or later, in the configuration that connects VSP G350/G370/G700/G900/F350/
F370/F700/F900/E990 and VSP E590/E790, remote path operations from VSP G350/G370/G700/
G900/F350/F370/F700/F900/E990 by using Storage Navigator (Web Console) are possible.
For the firmware version earlier than 88-07-03-x0/xx, earlier than 88-08-01-x0/xx and the firmware
version earlier than 93-04-01-x0/xx, use RAID Manager (CCI).
For the configuration that connects VSP E1090 and VSP 5000 series, remote path operations
from VSP 5000 series by using Storage Navigator (Web Console) are not possible. So, use RAID
Manager (CCI).

TRBL06-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-190

6.4 Failure Recovery Procedure and Planned Shutdown Procedure of the TC-UR
Configuration (Multi Target/Cascade)
6.4.1  Failure Recovery Procedure of the TC-UR Configuration (Multi Target/Cascade)
The descriptions of the TC-UR delta configuration in the failure recovery procedure and planned shutdown
procedure for the TC-UR configuration are defined as follows:

TC-UR Delta Configuration Definition of the Description

TC between PDKC and LDKC (IDKC (*1)) TC
UR between PDKC and RDKC (multi target configuration), or
UR
UR between IDKC and RDKC (cascade configuration)
UR delta between LDKC and RDKC (multi target configuration) UR delta
*1: Storage system in the intermediate site of IDKC (Intermediate DKC) and UR (Cascade
Configuration)

The following is the table of pair statuses in the event of a single point of failure and the recovery procedure
summary. The UR delta pair status in each table indicates the pair status displayed in RAID Manager. Also,
the value in the parentheses indicates the pair status displayed by Storage Navigator.
This failure recovery procedure is the recovery procedure to maintain the disaster discovery configuration.

1. Multi Target Configuration: Path between DKC

Mirror
No. Item Pair Status Recovery operation
ID
- [Normal 0 PVOL PAIR LVOL PAIR
Operation] (TC PVOL) (TC SVOL)
1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
1 PDKC 0 PVOL PSUE LVOL PAIR 1. TC failure suspension is
→ LDKC (TC PVOL) (TC SVOL) detected in PVOL.
Path failure 1 PVOL PAIR RVOL PAIR (The pair status of SVOL
(UR PVOL) (UR SVOL) does not change.)
2. Failure recovery site
(Recover paths).
3. TC pair resync in PVOL.
2 PDKC 0 PVOL PAIR LVOL PAIR 1. Failure recovery site
→ RDKC (TC PVOL) (TC SVOL) (Recover paths).
Path failure 1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
(To be continued)

TRBL06-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-200

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 RDKC 0 PVOL PAIR LVOL PAIR • SOM448 = ON and
→ PDKC (TC PVOL) (TC SVOL) SOM449 = OFF:
Path failure 1 PVOL PAIR RVOL PAIR If the path is not recovered
(UR PVOL) (UR SVOL) within a minute after a
communication break is
detected, the UR pair will
be suspended by error.
• SOM448 = OFF and
SOM449 = OFF:
If the path is not recovered
within the path watch time
after a communication
break is detected, the UR
pair will be suspended by
error.
Any of the above, the
recovery in the following
procedure.
1. Failure recovery site
(Recover paths).
2. UR pair resync in PVOL.

TRBL06-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-210

2. Multi Target Configuration: Pool Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL pool 0 PVOL PAIR LVOL PAIR 1. UR pair deletion by
full (TC PVOL) (TC SVOL) RVOL.
2. TC pair takeover by
1 PVOL PAIR RVOL PAIR LVOL.
(UR PVOL) (UR SVOL) 3. UR pair (between LVOL
and RVOL) creation by
LVOL.
4. Failure recovery site
(Expand the pool
capacity).
5. TC pair takeover by
PVOL.
6. UR pair (between LVOL
and RVOL) deletion by
LVOL.
NOTE: In the
configuration other than
cascade, delete the UR
pair before performing 5.
7. UR pair (between PVOL
and RVOL) creation by
PVOL.
2 PVOL pool 0 PVOL PAIR LVOL PAIR 1. UR pair deletion by
failure (TC PVOL) (TC SVOL) RVOL.
2. TC pair takeover by
1 PVOL PAIR RVOL PAIR LVOL.
(UR PVOL) (UR SVOL) 3. UR pair (between LVOL
and RVOL) creation by
LVOL.
4. Failure recovery site (see
TRBL10-10)
5. TC pair takeover by
PVOL.
6. UR pair (between LVOL
and RVOL) deletion by
LVOL.
NOTE: In the
configuration other than
cascade, delete the UR
pair before performing 5.
7. UR pair (between PVOL
and RVOL) creation by
PVOL.
3 LVOL pool 0 PVOL PSUE LVOL PSUE 1. TC failure suspension is
full (TC PVOL) (TC SVOL) detected.
2. Failure recovery site
1 PVOL PAIR RVOL PAIR (Expand the pool
(UR PVOL) (UR SVOL) capacity).
3. TC pair recovery in
PVOL.
4 LVOL pool 0 PVOL PSUE LVOL PSUE 1. TC failure suspension is
failure (TC PVOL) (TC SVOL) detected.
2. Failure recovery site (see
1 PVOL PAIR RVOL PAIR TRBL10-10).
(UR PVOL) (UR SVOL) 3. TC pair recovery in
PVOL.
(To be continued)
TRBL06-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-220

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
5 RVOL pool 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
full (TC PVOL) (TC SVOL) detected.
1 PVOL PSUE RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the pool
capacity).
3. UR pair recovery in
PVOL.
6 RVOL pool 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
failure (TC PVOL) (TC SVOL) detected.
1 PVOL PSUE RVOL PSUE 2. Failure recovery site (see
(UR PVOL) (UR SVOL) TRBL10-10).
3. UR pair recovery in
PVOL.

TRBL06-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-230

3. Multi Target Configuration: Journal Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume full (TC PVOL) (TC SVOL) detected.
1 PVOL PFUS RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
3. UR pair resync in PVOL.
2 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume (TC PVOL) (TC SVOL) detected.
failure 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
3 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume full 1 PVOL PFUS RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
3. UR pair resync in PVOL.
4 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.

TRBL06-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-240

4. Multi Target Configuration: Journal Volumes (Pool Volumes) (*1)

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume pool (TC PVOL) (TC SVOL) detected.
full 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume pool (TC PVOL) (TC SVOL) detected.
failure 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
3 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume pool 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
full (UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
4 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume pool 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
*1: Recovery procedures for failure in the pool where virtual volumes of Dynamic Provisioning
(DP-VOLs) which are set as journal volumes exist are described.
The pool full status might occur when the capacity of journal volumes is defined more than that of
all unused pool volumes.

TRBL06-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-250

5. Multi Target Configuration: LDEV

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL failure 0 PVOL PAIR LVOL PAIR 1. UR pair deletion by
(TC PVOL) (TC SVOL) RVOL.
1 PVOL PAIR RVOL PAIR 2. TC pair takeover by
(UR PVOL) (UR SVOL) LVOL.
3. UR pair (between LVOL
and RVOL) creation by
LVOL.
4. Failure recovery site.
5. TC pair takeover by
PVOL.
6. UR pair (between LVOL
and RVOL) deletion by
LVOL.
NOTE: In the
configuration other than
cascade, delete the UR
pair before performing 5.
7. UR pair (between PVOL
and RVOL) creation by
PVOL.
2 LVOL failure 0 PVOL PSUE LVOL PSUE 1. TC failure suspension is
(TC PVOL) (TC SVOL) detected.
1 PVOL PAIR RVOL PAIR 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. TC pair recovery in
PVOL.
3 RVOL failure 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
(TC PVOL) (TC SVOL) detected.
1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair recovery in
PVOL.

TRBL06-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-260

6. Multi Target Configuration: Storage system

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC failure 0 PVOL PAIR LVOL PAIR 1. UR pair deletion by
(SM/CM (TC PVOL) (TC SVOL) RVOL.
Non-Volatile) 1 PVOL PAIR RVOL PAIR 2. TC pair takeover by
(UR PVOL) (*1) (UR SVOL) (*1) LVOL.
3. UR pair (between LVOL
and RVOL) creation by
LVOL.
4. DKC recovery.
5. TC pair takeover by
PVOL.
6. UR pair (between LVOL
and RVOL) deletion by
LVOL.
NOTE: In the
configuration other than
cascade, delete the UR
pair before performing 5.
7. UR pair (between PVOL
and RVOL) creation by
PVOL.
2 LDKC failure 0 PVOL PSUE LVOL PAIR 1. DKC recovery.
(SM/CM (TC PVOL) (TC SVOL) 2. TC pair resync in PVOL.
Non-Volatile) 1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
3 RDKC failure 0 PVOL PAIR LVOL PAIR 1. DKC recovery.
(SM/CM (TC PVOL) (TC SVOL)
Non-Volatile) 1 PVOL PAIR RVOL PAIR
(UR PVOL) (*2) (UR SVOL) (*2)
*1: TC and UR pair information of PDKC (PVOL) is retained, which changes the UR pair state to
PSUE after PDKC (PVOL) PS is on.
*2: If you have SOM 449 = OFF in PDKC, the UR pair status becomes PSUE, and UR pair resync is
required after the DKC recovery.

TRBL06-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-270

7. Cascade Configuration: Path between DKC

Mirror
No. Item Pair Status Recovery operation
ID
- [Normal 0 PVOL PAIR IVOL PAIR
Operation] (TC PVOL) (TC SVOL)
1 IVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
1 PDKC 0 PVOL PSUE IVOL PAIR 1. TC failure suspension is
→ IDKC (TC PVOL) (TC SVOL) detected in PVOL. (The
Path failure 1 IVOL PAIR RVOL PAIR pair status of SVOL does
(UR PVOL) (UR SVOL) not change.)
2. Failure recovery site
(Recover paths).
3. TC pair resync in PVOL.
2 IDKC 0 PVOL PAIR IVOL PAIR 1. Failure recovery site
→ RDKC (TC PVOL) (TC SVOL) (Recover paths).
Path failure 1 IVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
3 RDKC 0 PVOL PAIR IVOL PAIR • SOM448 = ON and
→ IDKC (TC PVOL) (TC SVOL) SOM449 = OFF:
Path failure 1 IVOL PAIR RVOL PAIR If the path is not recovered
(UR PVOL) (UR SVOL) within a minute after a
communication break is
detected, the UR pair will
be suspended by error.
• SOM448 = OFF and
SOM449 = OFF:
If the path is not recovered
within the path watch time
after a communication
break is detected, the UR
pair will be suspended by
error.
Any of the above, the
recovery in the following
procedure.
1. Failure recovery site
(Recover paths).
2. UR pair resync in PVOL.

TRBL06-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-280

8. Cascade Configuration: Pool Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL pool 0 PVOL PAIR IVOL PAIR 1. TC pair takeover by
full (TC PVOL) (TC SVOL) IVOL.
1 IVOL PAIR RVOL PAIR 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the pool
capacity).
3. TC pair takeover by
PVOL.
4. UR pair resync in IVOL.
2 PVOL pool 0 PVOL PAIR IVOL PAIR 1. TC pair takeover by
failure (TC PVOL) (*1) (TC SVOL) (*1) IVOL.
1 IVOL PAIR RVOL PAIR 2. Failure recovery site (see
(UR PVOL) (UR SVOL) TRBL10-10)
3. TC pair takeover by
PVOL.
4. UR pair resync in IVOL.
3 IVOL pool 0 PVOL PSUE IVOL PSUE 1. UR pair deletion by
full (TC PVOL) (TC SVOL) RVOL.
1 IVOL PAIR RVOL PAIR 2. UR pair (between PVOL
(UR PVOL) (UR SVOL) and RVOL) creation by
PVOL.
3. Failure recovery site
(Expand the pool
capacity).
4. TC pair recovery in
PVOL.
5. UR pair deletion by
PVOL.
6. UR pair (between IVOL
and RVOL) creation by
IVOL.
4 IVOL pool 0 PVOL PSUE IVOL PSUE 1. UR pair deletion by
failure (TC PVOL) (TC SVOL) RVOL.
1 IVOL PAIR RVOL PAIR 2. UR pair (between PVOL
(UR PVOL) (UR SVOL) and RVOL) creation by
PVOL.
3. Failure recovery site (see
TRBL10-10)
4. TC pair recovery in
PVOL.
5. UR pair deletion by
PVOL.
6. UR pair (between IVOL
and RVOL) creation by
IVOL.
(To be continued)
*1: The pair status is PSUE during UR pair creation or resynchronization.

TRBL06-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-290

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
5 RVOL pool 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
full (TC PVOL) (TC SVOL) detected.
1 IVOL PSUE RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the pool
capacity).
3. UR pair recovery in
IVOL.
6 RVOL pool 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
failure (TC PVOL) (TC SVOL) detected.
1 IVOL PSUE RVOL PSUE 2. Failure recovery site
(UR PVOL) (UR SVOL) (TRBL10-10)
3. UR pair recovery in
IVOL.

TRBL06-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-300

9. Cascade Configuration: Journal Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 IDKC journal 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
volume full (TC PVOL) (TC SVOL) detected.
1 IVOL PFUS RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
3. UR pair resync in IVOL.
2 IDKC journal 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
volume (TC PVOL) (TC SVOL) detected.
failure 1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in IVOL.
3 RDKC 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume full 1 IVOL PFUS RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
3. UR pair resync in IVOL.
4 RDKC 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume 1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR pair resync in IVOL.

TRBL06-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-310

10. Cascade Configuration: Journal Volumes (Pool Volumes) (*1)

Mirror
No. Item Pair Status Recovery operation
ID
1 IDKC journal 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
volume pool (TC PVOL) (TC SVOL) detected.
full 1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in IVOL.
2 IDKC journal 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
volume pool (TC PVOL) (TC SVOL) detected.
failure 1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in IVOL.
3 RDKC 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume pool 1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
full (UR PVOL) (UR SVOL) 3. UR pair resync in IVOL.
4 RDKC 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume pool 1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR pair resync in IVOL.
*1: Recovery procedures for failure in the pool where virtual volumes of Dynamic Provisioning (DP-
VOLs) which are set as journal volumes exist are described.
The pool full status might occur when the capacity of journal volumes is defined more than that of
all unused pool volumes.

TRBL06-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-320

11. Cascade Configuration: LDEV

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL failure 0 PVOL PAIR IVOL PAIR 1. TC pair takeover by
(TC PVOL) (TC SVOL) IVOL.
1 IVOL PAIR RVOL PAIR 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. TC pair takeover by
PVOL.
4. UR pair resync in IVOL.
2 IVOL failure 0 PVOL PSUE IVOL PSUE 1. UR pair deletion by
(TC PVOL) (TC SVOL) RVOL.
1 IVOL PAIR RVOL PAIR 2. UR pair (between PVOL
(UR PVOL) (*1) (UR SVOL) (*1) and RVOL) creation by
PVOL.
3. Failure recovery site.
4. TC pair recovery in
PVOL.
5. UR pair deletion by
PVOL.
6. UR pair (between IVOL
and RVOL) creation by
IVOL.
3 RVOL failure 0 PVOL PAIR IVOL PAIR 1. UR failure suspension is
(TC PVOL) (TC SVOL) detected.
1 IVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair recovery in
IVOL.
*1: The pair status is PSUE during UR pair creation or resynchronization.

TRBL06-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-330

12. Cascade Configuration: Storage system

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC failure 0 PVOL PAIR IVOL PAIR 1. TC pair takeover by
(SM/CM (TC PVOL) (TC SVOL) IVOL.
Non-Volatile) 1 IVOL PAIR RVOL PAIR 2. DKC recovery.
(UR PVOL) (UR SVOL) 3. TC pair takeover by
PVOL.
4. UR pair resync in IVOL.
2 IDKC failure 0 PVOL PSUE IVOL PAIR 1. UR pair deletion by
(SM/CM (TC PVOL) (TC SVOL) RVOL.
Non-Volatile) 1 IVOL PAIR RVOL PAIR 2. UR pair (between PVOL
(UR PVOL) (*1) (UR SVOL) (*1) and RVOL) creation by
PVOL.
3. DKC recovery.
4. TC pair resync in PVOL.
5. UR pair deletion by
PVOL.
6. UR pair (between IVOL
and RVOL) creation by
IVOL.
3 RDKC failure 0 PVOL PAIR IVOL PAIR 1. DKC recovery.
(SM/CM (TC PVOL) (TC SVOL)
Non-Volatile) 1 IVOL PAIR RVOL PAIR
(UR PVOL) (*2) (UR SVOL) (*2)
*1: TC and UR pair information of IDKC (IVOL) is retained, which changes the UR pair state to
PSUE after IDKC (IVOL) PS is on.
*2: If you have SOM 449 = OFF in IDKC, the UR pair status becomes PSUE, and UR pair resync is
required after the DKC recovery.

TRBL06-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-340

6.5 Failure Recovery Procedure and Planned Shutdown Procedure of the TC-UR Delta
Configuration (Multi Target)
6.5.1  Failure Recovery Procedure of the TC-UR Delta Configuration (Multi Target)
The following is the table of pair statuses in the event of a single point of failure and the recovery procedure
summary. The UR delta pair status in each table indicates the pair status displayed in RAID Manager. Also,
the value in the parentheses indicates the pair status displayed by Storage Navigator.
This failure recovery procedure is the recovery procedure to maintain the disaster discovery configuration.

1. Multi Target Configuration: Path between DKC

Mirror
No. Item Pair Status Recovery operation
ID
- [Normal 0 PVOL PAIR LVOL PAIR
Operation] (TC PVOL) (TC SVOL)
1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
1 PDKC 0 PVOL PSUE LVOL PAIR 1. TC failure suspension is
→ LDKC (TC PVOL) (TC SVOL) detected in PVOL.
Path failure 1 PVOL PAIR RVOL PAIR (The pair status of SVOL
(UR PVOL) (UR SVOL) does not change.)
2. Failure recovery site
2 LVOL PSUS RVOL SSUS (Recover paths).
(UR delta (HOLD) (UR delta (HOLD) 3. TC pair resync in PVOL.
PVOL) SVOL)
2 LDKC 0 PVOL PAIR LVOL PAIR 1. Failure recovery site
→ RDKC (TC PVOL) (TC SVOL) (Recover paths).
Path failure 1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
(To be continued)

TRBL06-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.4.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-350

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 RDKC 0 PVOL PAIR LVOL PAIR 1. Failure recovery site
→ LDKC (TC PVOL) (TC SVOL) (Recover paths).
Path failure 1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
4 PDKC 0 PVOL PAIR LVOL PAIR 1. Failure recovery site
→ RDKC (TC PVOL) (TC SVOL) (Recover paths).
Path failure 1 PVOL PAIR RVOL PAIR
(UR PVOL) (UR SVOL)
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
5 RDKC 0 PVOL PAIR LVOL PAIR • SOM448 = ON and
→ PDKC (TC PVOL) (TC SVOL) SOM449 = OFF:
Path failure 1 PVOL PAIR RVOL PAIR If the path is not recovered
(UR PVOL) (UR SVOL) within a minute after a
communication break is
2 LVOL PSUS RVOL SSUS detected, the UR pair will
(UR delta (HOLD) (UR delta (HOLD) be suspended by error.
PVOL) SVOL) • SOM448 = OFF and
SOM449 = OFF:
If the path is not recovered
within the path watch time
after a communication
break is detected, the UR
pair will be suspended by
error.
Any of the above, the
recovery in the following
procedure.
1. Failure recovery site
(Recover paths).
2. UR pair resync in PVOL.
6 Path failure 0 PVOL PAIR LVOL PAIR 1. Failure recovery site
for remote (TC PVOL) (TC SVOL) (Recover paths).
command 1 PVOL PAIR RVOL PAIR
device (UR PVOL) (UR SVOL)
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)

TRBL06-350
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-360

2. Multi Target Configuration: Pool Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL pool 0 PVOL PAIR LVOL PAIR 1. TC pair swap suspension
full (TC PVOL) (TC SVOL) in LVOL.
1 PVOL PAIR RVOL PAIR 2. Delta resync (UR delta
(UR PVOL) (UR SVOL) resync in LVOL).
3. Failure recovery site
2 LVOL PSUS RVOL SSUS (Expand the pool
(UR delta (HOLD) (UR delta (HOLD) capacity).
PVOL) SVOL) 4. TC and UR pair
recovery. (*1)
2 PVOL pool 0 PVOL PAIR LVOL PAIR 1. TC pair swap suspension
failure (TC PVOL) (TC SVOL) in LVOL.
1 PVOL PAIR RVOL PAIR 2. Delta resync (UR delta
(UR PVOL) (UR SVOL) resync in LVOL).
3. Failure recovery site (see
2 LVOL PSUS RVOL SSUS TRBL10-10)
(UR delta (HOLD) (UR delta (HOLD) 4. TC and UR pair
PVOL) SVOL) recovery. (*1)
3 LVOL pool 0 PVOL PSUE LVOL PSUE 1. TC failure suspension is
full (TC PVOL) (TC SVOL) detected.
1 PVOL PAIR RVOL PAIR 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the pool
capacity).
2 LVOL PSUS RVOL SSUS 3. TC pair recovery in
(UR delta (HOLD) (UR delta (HOLD) PVOL.
PVOL) SVOL)
4 LVOL pool 0 PVOL PSUE LVOL PSUE 1. TC failure suspension is
failure (TC PVOL) (TC SVOL) detected.
1 PVOL PAIR RVOL PAIR 2. Failure recovery site (see
(UR PVOL) (UR SVOL) TRBL10-10)
3. TC pair recovery in
2 LVOL PSUS RVOL SSUS PVOL.
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
5 RVOL pool 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
full (TC PVOL) (TC SVOL) detected.
1 PVOL PSUE RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the pool
capacity).
2 LVOL PSUS RVOL SSUS 3. UR pair recovery in
(UR delta (HOLD) (UR delta (HOLD) PVOL.
PVOL) SVOL)
6 RVOL pool 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
failure (TC PVOL) (TC SVOL) detected.
1 PVOL PSUE RVOL PSUE 2. Failure recovery site (see
(UR PVOL) (UR SVOL) TRBL10-10)
3. UR pair recovery in
2 LVOL PSUS RVOL SSUS PVOL.
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: TC-UR configuration is reconfigured depending on the pair status.
TRBL06-360
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-370

3. Multi Target Configuration: Journal Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume full (TC PVOL) (TC SVOL) detected.
1 PVOL PFUS RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
2 LVOL PSUS/ RVOL SSUS/ 3. UR pair resync in PVOL.
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
2 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume (TC PVOL) (TC SVOL) detected.
failure 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 LVOL PSUS/ RVOL SSUS/
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
3 LDKC 0 PVOL PAIR LVOL PAIR 1. UR delta failure
journal (TC PVOL) (TC SVOL) (PSUE(J)) detected.
volume full 1 PVOL PAIR RVOL PAIR 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
2 LVOL PSUE/ RVOL SSUS/ 3. UR delta pair resync in
(UR delta PJES (UR delta SJNS PVOL.
PVOL) (HLDE) SVOL) (HOLD)
4 LDKC 0 PVOL PAIR LVOL PAIR 1. UR delta failure
journal (TC PVOL) (TC SVOL) (PSUE(J)) detected.
volume 1 PVOL PAIR RVOL PAIR 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR delta pair resync in
PVOL.
2 LVOL PSUE/ RVOL SSUS
(UR delta PJES (UR delta (HOLD)
PVOL) (HLDE) SVOL)
5 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume full 1 PVOL PFUS RVOL PFUS 2. Failure recovery site
(UR PVOL) (UR SVOL) (Expand the journal
volume capacity).
2 LVOL PSUS/ RVOL SSUS/ 3. UR pair resync in PVOL.
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
6 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 LVOL PSUS/ RVOL SSUS/
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)

TRBL06-370
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-380

4. Multi Target Configuration: Journal Volumes (Pool Volumes) (*1)

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume pool (TC PVOL) (TC SVOL) detected.
full 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 LVOL PSUS/ RVOL SSUS/
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
2 PDKC journal 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
volume pool (TC PVOL) (TC SVOL) detected.
failure 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 LVOL PSUS/ RVOL SSUS/
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
3 LDKC 0 PVOL PAIR LVOL PAIR 1. UR delta failure
journal (TC PVOL) (TC SVOL) (PSUE(J)) detected.
volume pool 1 PVOL PAIR RVOL PAIR 2. Failure recovery site.
full (UR PVOL) (UR SVOL) 3. UR delta pair resync in
PVOL.
2 LVOL PSUE/ RVOL SSUS
(UR delta PJES (UR delta (HOLD)
PVOL) (HLDE) SVOL)
4 LDKC 0 PVOL PAIR LVOL PAIR 1. UR delta failure
journal (TC PVOL) (TC SVOL) (PSUE(J)) detected.
volume pool 1 PVOL PAIR RVOL PAIR 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR delta pair resync in
PVOL.
2 LVOL PSUE/ RVOL SSUS
(UR delta PJES (UR delta (HOLD)
PVOL) (HLDE) SVOL)
5 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume pool 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
full (UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 LVOL PSUS/ RVOL SSUS/
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
6 RDKC 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal (TC PVOL) (TC SVOL) detected.
volume pool 1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
failure (UR PVOL) (UR SVOL) 3. UR pair resync in PVOL.
2 LVOL PSUS/ RVOL SSUS/
(UR delta PJNS (UR delta SJNS
PVOL) (HOLD) SVOL) (HOLD)
*1: Recovery procedures for failure in the pool where virtual volumes of Dynamic Provisioning (DP-
VOLs) which are set as journal volumes exist are described.
The pool full status might occur when the capacity of journal volumes is defined more than that of
all unused pool volumes.
TRBL06-380
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-390

5. Multi Target Configuration: LDEV

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL failure 0 PVOL PAIR LVOL PAIR 1. TC pair swap suspension
(TC PVOL) (TC SVOL) in LVOL.
1 PVOL PAIR RVOL PAIR 2. Delta resync (UR delta
(UR PVOL) (UR SVOL) resync in LVOL).
3. Failure recovery site.
2 LVOL PSUS RVOL SSUS 4. TC and UR pair
(UR delta (HOLD) (UR delta (HOLD) recovery. (*1)
PVOL) SVOL)
2 LVOL failure 0 PVOL PSUE LVOL PSUE 1. TC failure suspension is
(TC PVOL) (TC SVOL) detected.
1 PVOL PAIR RVOL PAIR 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. TC pair recovery in
PVOL.
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
3 RVOL failure 0 PVOL PAIR LVOL PAIR 1. UR failure suspension is
(TC PVOL) (TC SVOL) detected.
1 PVOL PSUE RVOL PSUE 2. Failure recovery site.
(UR PVOL) (UR SVOL) 3. UR pair recovery in
PVOL.
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
4 Remote 0 PVOL PAIR LVOL PAIR 1. Failure recovery site.
command (TC PVOL) (TC SVOL)
device failure 1 PVOL PAIR RVOL PAIR * If the remote command
(UR PVOL) (UR SVOL) device settings are
cancelled, make the
2 LVOL PSUS RVOL SSUS settings again.
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: TC-UR configuration is reconfigured depending on the pair status.

TRBL06-390
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-400

6. Multi Target Configuration: Storage system

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC failure 0 PVOL PAIR LVOL PAIR 1. TC pair swap suspension
(SM/CM (TC PVOL) (TC SVOL) in LVOL.
Non-Volatile) 1 PVOL PAIR RVOL PAIR 2. Delta resync (UR delta
(*1) (UR PVOL) (*1) (UR SVOL) (*1) resync in LVOL).
3. DKC recovery.
2 LVOL PSUS RVOL SSUS 4. If the remote command
(UR delta (HOLD) (UR delta (HOLD) device settings are
PVOL) SVOL) cancelled, make the
settings again.
5. TC pair swap resync in
LVOL.
2 LDKC failure 0 PVOL PSUE LVOL PAIR 1. DKC recovery.
(SM/CM (TC PVOL) (TC SVOL) 2. If the remote command
Non-Volatile) 1 PVOL PAIR RVOL PAIR device settings are
(UR PVOL) (UR SVOL) cancelled, make the
settings again.
2 LVOL PSUS RVOL SSUS 3. TC pair resync in PVOL.
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
3 RDKC failure 0 PVOL PAIR LVOL PAIR 1. DKC recovery.
(SM/CM (TC PVOL) (TC SVOL) 2. If the remote command
Non-Volatile) 1 PVOL PAIR RVOL PAIR device settings are
(UR PVOL) (*2) (UR SVOL) (*2) cancelled, make the
settings again.
2 LVOL PSUS RVOL SSUS
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: TC and UR pair information of PDKC (PVOL) is retained, which changes the UR pair state to
PSUE after PDKC (PVOL) PS is on.
*2: If you have SOM 449 = OFF in PDKC, the UR pair status becomes PSUE, and UR pair resync is
required after the DKC recovery.

TRBL06-400
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-410

6.6 DKC Planned Shutdown Procedure of the TC-UR Configuration (Multi Target)
Following is the procedure of the planned shutdown (PS OFF/ON) of the PDKC/LDKC/RDKC in the TC-
UR configuration (multi target). Because suspending all TC and UR pairs related to DKC to be set to PS OFF
is recommended when DKC is set to PS OFF, the procedure that complies with it is shown. (If you stop host
I/O and execute the Flush-specified suspension in advance, the data in the primary volume and the data in the
secondary volume will be the same.)

6.6.1 Planned Shutdown Procedure of the PDKC

Table 6-2 Planned Shutdown Procedure of the PDKC of the TC-UR Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

1 UR pair deletion Execute UR pair deletion on the PDKC. #UR pair deletion
↓ UR pair deletion % pairsplit -g UR -S -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: SMPL

RDKC [PS ON]

UR SVOL: SMPL

2 UR pair creation Execute UR pair creation on the LDKC (between LDKC and RDKC). #UR pair creation
↓ UR pair creation % paircreate -g UR -jp 1
PDKC [PS ON] LDKC [PS ON] -js 2 -IH1
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

3 Stop of host I/O Suspend I/O from host to the PDKC (switch the operation to LDKC).
to the PDKC
(To be continued)

TRBL06-410
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-420

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
4 TC pair takeover Execute TC pair takeover on the LDKC. #TC pair takeover
↓ TC pair takeover % horctakeover -g TC
PDKC [PS ON] LDKC [PS ON] -IH1
TC SVOL: PAIR TC PVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

5 Start of host I/O Consolidate host I/O to the LDKC.

to the LDKC
6 TC pair Execute TC pair suspension in the LDKC. #TC pair suspension
suspension ↓ TC pair suspension % pairsplit -g TC -IH1
PDKC [PS ON] LDKC [PS ON]
TC SVOL: SSUS TC PVOL: PSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

7 PDKC PS OFF Set the PDKC to PS OFF.

↓ PS OFF
PDKC [PS OFF] LDKC [PS ON]
TC SVOL: SSUS TC PVOL: PSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

- During planned
shutdown
8 PDKC PS ON Set the PDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
TC SVOL: SSUS TC PVOL: PSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

9 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
10 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
(To be continued)
TRBL06-420
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-430

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
11 TC pair resync Execute TC pair resync in the LDKC. #TC pair resync
↓ TC pair resync % pairresync -g TC -IH1
PDKC [PS ON] LDKC [PS ON]
TC SVOL: PAIR TC PVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

12 UR pair deletion Execute UR pair deletion on the LDKC. #UR pair deletion
↓ UR pair deletion % pairsplit -g UR -S -IH1
PDKC [PS ON] LDKC [PS ON]
TC SVOL: PAIR TC PVOL: PAIR
UR PVOL: SMPL

RDKC [PS ON]

UR SVOL: SMPL

13 UR pair creation Execute UR pair creation on the PDKC (between PDKC and RDKC). #UR pair creation
↓ UR pair creation % paircreate -g UR -jp 0
PDKC [PS ON] LDKC [PS ON] -js 2 -IH0
TC SVOL: PAIR TC PVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

14 Stop of host I/O Suspend I/O from host to the LDKC (return the operation to PDKC).
to the LDKC
15 TC pair takeover Execute TC pair takeover on the PDKC. #TC pair takeover
↓ TC pair takeover % horctakeover -g TC
PDKC [PS ON] LDKC [PS ON] -IH0
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

16 Start of host I/O Consolidate host I/O to the PDKC.

to the PDKC

TRBL06-430
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-440

6.6.2 Planned Shutdown Procedure of the LDKC

Table 6-3 Planned Shutdown Procedure of the LDKC of the TC-UR Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

1 TC pair Execute TC pair suspension on the PDKC. #TC pair suspension

suspension ↓ TC pair suspension % pairsplit -g TC -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

2 LDKC PS OFF Set the LDKC to PS OFF.

↓ PS OFF
PDKC [PS ON] LDKC [PS OFF]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

- During planned
shutdown
3 LDKC PS ON Set the LDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
(To be continued)
TRBL06-440
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-450

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
6 TC pair resync Execute TC pair resync on the PDKC. #TC pair resync
↓ TC pair resync % pairresync -g TC -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

TRBL06-450
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-460

6.6.3 Planned Shutdown Procedure of the RDKC

Table 6-4 Planned Shutdown Procedure of the RDKC of the TC-UR Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

1 UR pair Execute UR pair suspension on the PDKC. #UR pair suspension

suspension ↓ UR pair suspension % pairsplit -g UR -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS

RDKC [PS ON]

UR SVOL: SSUS

2 RDKC PS OFF Set the RDKC to PS OFF.

PDKC [PS ON] LDKC [PS ON]

TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS
↓ PS OFF
RDKC [PS OFF]
UR SVOL: SSUS

- During planned
shutdown
3 RDKC PS ON Set the RDKC to PS ON.

PDKC [PS ON] LDKC [PS ON]

TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS
↓ PS ON
RDKC [PS ON]
UR SVOL: SSUS

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
(To be continued)
TRBL06-460
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-470

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
6 UR pair resync Execute UR pair resync on the PDKC. #UR pair resync
↓ UR pair resync % pairresync -g UR -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

TRBL06-470
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-480

6.7 DKC Planned Shutdown Procedure of the TC-UR Configuration (Cascade)

Following is the procedure of the planned shutdown (PS OFF/ON) of the PDKC/IDKC/RDKC in the TC-
UR configuration (cascade). Because suspending all TC and UR pairs related to DKC to be set to PS OFF is
recommended when DKC is set to PS OFF, the procedure that complies with it is shown. (If you stop host I/
O and execute the Flush-specified suspension in advance, the data in the primary volume and the data in the
secondary volume will be the same.)

6.7.1 Planned Shutdown Procedure of the PDKC

Table 6-5 Planned Shutdown Procedure of the PDKC of the TC-UR Configuration
(Cascade Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

1 Stop of host I/O Suspend I/O from host to the PDKC (switch the operation to IDKC).
to the PDKC
2 TC pair takeover Execute TC pair takeover on the IDKC. #TC pair takeover
↓ TC pair takeover % horctakeover -g TC
PDKC [PS ON] IDKC [PS ON] -IH1
TC SVOL: PAIR TC PVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

3 Start of host I/O Consolidate host I/O to the IDKC.

to the IDKC
4 TC pair Execute TC pair suspension on the IDKC. #TC pair suspension
suspension ↓ TC pair suspension % pairsplit -g TC -IH1
PDKC [PS ON] IDKC [PS ON]
TC SVOL: SSUS TC PVOL: PSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

(To be continued)

TRBL06-480
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-490

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
5 PDKC PS OFF Set the PDKC to PS OFF.
↓ PS OFF
PDKC [PS OFF] IDKC [PS ON]
TC SVOL: SSUS TC PVOL: PSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

- During planned
shutdown
6 PDKC PS ON Set the PDKC to PS ON.
↓ PS ON
PDKC [PS ON] IDKC [PS ON]
TC SVOL: SSUS TC PVOL: PSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

7 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
8 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
9 TC pair resync Execute TC pair resync on the IDKC. #TC pair resync
↓ TC pair resync % pairresync -g TC -IH1
PDKC [PS ON] IDKC [PS ON]
TC SVOL: PAIR TC PVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

10 Stop of host I/O Suspend I/O from host to the IDKC (return the operation to PDKC).
to the IDKC
11 TC pair takeover Execute TC pair takeover on the PDKC. TC pair takeover
↓ TC pair takeover % horctakeover -g TC
PDKC [PS ON] IDKC [PS ON] -IH0
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS * Executing TC pair
takeover suspends the
RDKC [PS ON] UR pair.
UR SVOL: SSUS

(To be continued)
TRBL06-490
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-500

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
12 Start of host I/O Consolidate host I/O to the PDKC.
to the PDKC
13 UR pair resync Execute UR pair resync on the IDKC. #UR pair resync
↓ UR pair resync % pairresync -g UR -IH1
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

TRBL06-500
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-510

6.7.2 Planned Shutdown Procedure of the IDKC

Table 6-6 Planned Shutdown Procedure of the IDKC of the TC-UR Configuration
(Cascade Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

1 UR pair deletion Execute UR pair deletion on the IDKC. # UR pair deletion

↓ UR pair deletion % pairsplit -g UR -S -IH1
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: SMPL

RDKC [PS ON]

UR SVOL: SMPL

2 UR pair creation Execute UR pair creation on the PDKC (between PDKC and RDKC). #UR pair creation
↓ UR pair creation % paircreate -g UR -jp 0
PDKC [PS ON] IDKC [PS ON] -js 2 -IH0
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

3 TC pair Execute TC pair suspension on the PDKC. #TC pair suspension

suspension ↓ TC pair suspension % pairsplit -g TC -IH0
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

(To be continued)

TRBL06-510
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-520

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
4 IDKC PS OFF Set the IDKC to PS OFF.
↓ PS OFF
PDKC [PS ON] IDKC [PS OFF]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

- During planned
shutdown
5 IDKC PS ON Set the IDKC to PS ON.
↓ PS ON
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

6 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
7 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
8 TC pair resync Execute TC pair resync on the PDKC. #TC pair resync
* For the multi ↓ TC pair resync % pairresync -g TC -IH0
target operation, PDKC [PS ON] IDKC [PS ON]
skip Step 8 and TC PVOL: PAIR TC SVOL: PAIR
Step 9. UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

9 UR pair deletion Execute UR pair deletion on the PDKC. #UR pair deletion
↓ UR pair deletion % pairsplit -g UR -S -IH0
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: SMPL

RDKC [PS ON]

UR SVOL: SMPL

(To be continued)

TRBL06-520
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-530

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
10 UR pair creation Execute UR pair creation on the IDKC (between IDKC and RDKC). #UR pair creation
↓ UR pair creation % paircreate -g UR -jp 1
PDKC [PS ON] IDKC [PS ON] -js 2 -IH1
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

TRBL06-530
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-540

6.7.3 Planned Shutdown Procedure of the RDKC

Table 6-7 Planned Shutdown Procedure of the RDKC of the TC-UR Configuration
(Cascade Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

1 UR pair Execute UR pair suspension on the IDKC. #UR pair suspension

suspension ↓ UR pair suspension % pairsplit -g UR -IH1
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS

RDKC [PS ON]

UR SVOL: SSUS

2 RDKC PS OFF Set the RDKC to PS OFF.

PDKC [PS ON] IDKC [PS ON]

TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS
↓ PS OFF
RDKC [PS OFF]
UR SVOL: SSUS

- During planned
shutdown
3 RDKC PS ON Set the RDKC to PS ON.

PDKC [PS ON] IDKC [PS ON]

TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS
↓ PS ON
RDKC [PS ON]
UR SVOL: SSUS

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
(To be continued)
TRBL06-540
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-550

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
6 UR pair resync Execute UR pair resync on the IDKC. #UR pair resync
↓ UR pair resync % pairresync -g UR -IH1
PDKC [PS ON] IDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR

TRBL06-550
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-560

6.8 DKC Planned Shutdown Procedure of the TC-UR Delta Configuration (Multi Target)
Following is the procedure of the planned shutdown (PS OFF/ON) of the PDKC/LDKC/RDKC in the TC-
UR delta configuration (multi target). Because suspending all TC and UR pairs related to DKC to be set to
PS OFF is recommended when DKC is set to PS OFF, the procedure that complies with it is shown. (If you
stop host I/O and execute the Flush-specified suspension in advance, the data in the primary volume and the
data in the secondary volume will be the same.)
The UR delta pair status in each table indicates the pair status displayed in RAID Manager. Also, the value in
the parentheses indicates the pair status displayed by Storage Navigator. This planned shutdown procedure is
the planned shutdown procedure to maintain the disaster discovery configuration.

6.8.1 Planned Shutdown Procedure of the PDKC

Table 6-8 Planned Shutdown Procedure of the PDKC of the TC-UR Delta Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

1 Stop of host I/O Suspend I/O from host to the PDKC (switch the operation to LDKC).
to the PDKC
2 TC pair swap Execute TC pair swap suspension on the LDKC. #TC pair swap suspension
suspension ↓ TC pair swap suspension % pairsplit -g TC -RS
PDKC [PS ON] LDKC [PS ON] -IH1
TC PVOL: PSUS TC SVOL: SSWS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

3 Delta resync Execute delta resync (UR delta pair resync) on the LDKC. #Delta resync
(UR delta pair ↓ Delta resync % pairresync -g URdelta
resync) PDKC [PS ON] LDKC [PS ON] -IH1
TC PVOL: PSUS TC SVOL: SSWS
UR delta PVOL: PSUS (HOLD) UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL06-560
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-570

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
4 Start of host I/O Consolidate host I/O to the LDKC.
to the LDKC
5 PDKC PS OFF Set the PDKC to PS OFF.
↓ PS OFF
PDKC [PS OFF] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSWS
UR delta PVOL: PSUS (HOLD) UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

- During planned
shutdown
6 PDKC PS ON Set the PDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSWS
UR delta PVOL: PSUS (HOLD) UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

7 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
8 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
9 TC pair swap Execute TC pair swap resync on the LDKC. #TC pair swap resync
resync ↓ TC pair swap resync % pairresync -g TC
PDKC [PS ON] LDKC [PS ON] -swaps -IH1
TC SVOL: PAIR TC PVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR PVOL: PAIR

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

10 Stop of host I/O Suspend I/O from host to the LDKC (return the operation to PDKC).
to the LDKC
(To be continued)

TRBL06-570
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-580

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
11 TC pair swap Execute TC pair swap suspension on the PDKC. #TC pair swap suspension
suspension ↓ TC pair swap suspension % pairsplit -g TC -RS
PDKC [PS ON] LDKC [PS ON] -IH0
TC SVOL: SSWS TC PVOL: PSUS
UR delta PVOL: PSUS (HOLD) UR PVOL: PSUS

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

12 Delta resync Execute delta resync (UR delta pair resync) on the PDKC. #Delta resync
(UR delta pair ↓ Delta resync % pairresync -g UR -IH0
resync) PDKC [PS ON] LDKC [PS ON]
TC SVOL: SSWS TC PVOL: PSUS
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

13 Start of host I/O Consolidate host I/O to the PDKC.

to the PDKC
14 TC pair swap Execute TC pair swap resync on the PDKC. #TC pair swap resync
resync ↓ TC pair swap resync % pairresync -g TC
PDKC [PS ON] LDKC [PS ON] -swaps -IH0
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL06-580
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-590

6.8.2 Planned Shutdown Procedure of the LDKC

Table 6-9 Planned Shutdown Procedure of the LDKC of the TC-UR Delta Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

1 TC pair Execute TC pair suspension on the PDKC. #TC pair suspension

suspension ↓ TC pair suspension % pairsplit -g TC -H0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

2 LDKC PS OFF Set the LDKC to PS OFF.

↓ PS OFF
PDKC [PS ON] LDKC [PS OFF]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

- During planned
shutdown
3 LDKC PS ON Set the LDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
(To be continued)
TRBL06-590
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-600

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
6 TC pair resync Execute TC pair resync on the PDKC. #TC pair resync
↓ TC pair resync % pairresync -g TC -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL06-600
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-610

6.8.3 Planned Shutdown Procedure of the RDKC

Table 6-10 Planned Shutdown Procedure of the RDKC of the TC-UR Delta Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

1 UR pair Execute UR pair suspension on the PDKC. #UR pair suspension

suspension ↓ UR pair suspension % pairsplit -g UR -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

2 RDKC PS OFF Set the RDKC to PS OFF.

PDKC [PS ON] LDKC [PS ON]

TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)
↓ PS OFF
RDKC [PS OFF]
UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

- During planned
shutdown
3 RDKC PS ON Set the RDKC to PS ON.

PDKC [PS ON] LDKC [PS ON]

TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)
↓ PS ON
RDKC [PS ON]
UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
(To be continued)
TRBL06-610
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-620

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
6 UR pair resync Execute UR pair resync on the PDKC. #UR pair resync
↓ UR pair resync % pairresync -g UR -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL06-620
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-630

6.9 Planned Shutdown Procedure of All DKCs in 3DC Configuration

The following is the planned shutdown procedure of all DKCs in the 3DC configuration. The table below
shows the procedure for the TC-UR delta configuration (multi target). The same procedure can be applied to
the TC-UR configuration (multi target/cascade).
*: For the cascade configuration, replace “LDKC” with “IDKC”.

Table 6-11 Planned Shutdown Procedure of All DKCs in TC-UR Delta Configuration
(Multi Target Configuration)
Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
- Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

1 Stop of host I/O Suspend I/O from host to the PDKC.

to the PDKC
2 TC pair Execute TC pair suspension on the PDKC. #TC pair suspension
suspension ↓ TC pair suspension % pairsplit -g TC -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

3 UR pair Execute UR pair suspension on the PDKC. #UR pair suspension

suspension ↓ UR pair suspension % pairsplit -g UR -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL06-630
Hitachi Proprietary DW850/DW900/DW1000
Rev.3.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-640

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
4 PDKC PS OFF Set the PDKC to PS OFF.
↓ PS OFF
PDKC [PS OFF] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

5 LDKC PS OFF Set the LDKC to PS OFF.

↓ PS OFF
PDKC [PS OFF] LDKC [PS OFF]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

6 RDKC PS OFF Set the RDKC to PS OFF.

PDKC [PS OFF] LDKC [PS OFF]

TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)
↓ PS OFF
RDKC [PS OFF]
UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

- During planned
shutdown
7 RDKC PS ON Set the RDKC to PS ON.

PDKC [PS OFF] LDKC [PS OFF]

TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)
↓ PS ON
RDKC [PS ON]
UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL06-640
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL06-650

(Continued from the preceding page)

Procedure Description
No. Note
item (Underlining means a part that changes from the previous status.)
8 LDKC PS ON Set the LDKC to PS ON.
↓ PS ON
PDKC [PS OFF] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

9 PDKC PS ON Set the PDKC to PS ON.

↓ PS ON
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PSUS TC SVOL: SSUS
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

10 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
11 SIM check If SIMs related to the path block are generated in each DKC, complete the
SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary actions).
12 TC pair resync Execute TC pair resync on the PDKC. #TC pair resync
↓ TC pair resync % pairresync -g TC -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PSUS UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

13 Start of host I/O Consolidate host I/O to the PDKC.

to the PDKC
14 UR pair resync Execute UR pair resync on the PDKC. #UR pair resync
↓ UR pair resync % pairresync -g UR -IH0
PDKC [PS ON] LDKC [PS ON]
TC PVOL: PAIR TC SVOL: PAIR
UR PVOL: PAIR UR delta PVOL: PSUS (HOLD)

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL06-650
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-10

7. Recovery from UR Failure

7.1 Recovery Procedure for UR Failure

The UR pair suspension or UR logical path blockade on the remote copy may occur triggered by a hardware
failure.
This section contains explanation of the UR failure and procedures for recovery from the failure. Occurrence
of the UR failure can be known through the following.
• SIM report on occurrence of logical path blockade on the remote copy
• SIM report on occurrence of pair suspension
• UR failure message in the Syslog output by RAID Manager, in the case of the UR (Open)*1

SIM [Link] Meaning Remarks

2180xx Logical path(s) on the remote xx : CHB# + Port# in CHB (see
copy connections was logically SIMRC02-350 (27) )
blocked
dczxyy UR pair suspension z : 0 to 2, 4 to A
x : CU# (See SIMRC02-300 (14))
yy : LDEV#
dcezxx JNL overflow warning x : 0 to 3
zz : JNLG#
dcfzxx Read JNL interruption x : 0 to 3
zz : JNLG#

The UR supports the Force Delete Pair function. When recovery from the failure using an ordinary procedure
is unsuccessful, take a recovery action performing Force Delete Pair operation.

*1: When an UR pair is suspended, RAID Manager displays the following message in the Syslog.

[HORCM_102] Deleted a suspending status on this paired volume (Volume:, code:XXXX).

 : Volume name
XXXX : Factor code

When a message that informs of occurrence of an UR pair failure is displayed in the Syslog, it is
required to check the SIM(s) of the connected DKC and understand correspondence of messages
in the Syslog to SIMs logged on the DKC side before starting the recovery action.

TRBL07-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-20

[Recovery from the UR failure]

START

Yes Take a recovery action referring

SIM = 2180xx
to “6. TrueCopy Error Recovery”.

No

Yes
SIM = dc0xyy 1
(TRBL07-40)
No

Yes
SIM = dc1xyy 2
(TRBL07-50)
No

Yes
SIM = dc2xyy 2
(TRBL07-50)
No

Yes No recovery action is required because this SIM is issued triggered

SIM = dc4xyy
by an S-VOL pairsplit on the secondary site or failure suspension.

No

Yes No recovery action is required because this SIM is issued triggered

SIM = dc5xyy
by an S-VOL pair deletion on the secondary site.

No

Yes Check JNL inflow and lines Is the situation No

SIM = dcezxx
to avoid JNL overflow. getting better?

No Yes T.S.D. Call

Yes The Read JNL from the secondary site is interrupted for one minute
SIM = dcf0xx or longer. No recovery action is required because this SIM is merely
a warning message.
No

Yes
SIM = dcf1xx 1
(TRBL07-40)
No

A
(TRBL07-30)

TRBL07-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-30

Yes
SIM=dc6xyy 3
(TRBL07-60)
No

Yes
SIM=dc7xyy 3
(TRBL07-60)
No

Yes
SIM=dc8xyy

No Turn on the primary site.

Restore the pair status by operating the UR pair.

(Refer to a procedure for recovering an UR pair on
page TRBL07-80)

END

Yes
SIM=dc9xyy
Recover the failed part.
No

On the Resync Mirrors screen of Web Console,

please choose the mirror of a Hold (Failure) state
and perform a resynchronization.

END

Yes
SIM=dcaxyy 4
(TRBL07-70)
No

Yes
SIM=dcf2xx

No The Read JNL from the primary site is interrupted

for one minute or longer. No recovery action is
required because this SIM is merely a warning
message.

Yes
SIM=dcf3xx 1
(TRBL07-40)
No

END

TRBL07-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-40

Check whether a path failure

occurred or not by examining the
SIM log on the secondary site.

Did the failure

occur in the path between Yes
the primary site and the
secondary site?
Take a recovery action referring to “6.
No TrueCopy Error Recovery”. Restore
the pair status after restoring the path
status.

Is a number of the SIM Yes

3
concerned dc7xyy?
(TRBL07-60)
No

Contact the Technical

Support Division.

TRBL07-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-50

Check the SIM log produced in the period

when the reported SIMs were issued.

Was
a SIM whose number Yes
1
was dcf0xx or dcf1xx
issued? (TRBL07-40)

No

Yes
Is there failed part?

Recover the failed part.

No

Restore the pair status by operating the

UR pair. (Refer to “7.2 Procedure for
Recovering UR Pair”.)

END

TRBL07-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-60

Check the SIM log produced in the period

when the reported SIMs were issued.

Was a SIM Yes

whose number was 2180xx
issued?
Take a recovery action referring to
No recovery procedure of SIM REF
CODE 2180xx in “6. TrueCopy Error
Recovery”. Restore the pair status after
restoring the path status.

Does a SIM log

Yes
that precedes the warning SIM
ocncerned exist?
Recover the failed part.
No

Restore the pair status by operating the UR

pair. (“7.2 Procedure for Recovering UR
Pair”)

END

TRBL07-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-70

Make sure of the pair status

of secondary site.

Is the pair status No

PSUx?

Yes Is the pair status No

PAIR, Copy?

Yes Is the pair status No

Suspending?

Make the secondary site Yes Is the pair status No

execute the Suspend Pair that Deleting?
is an operation of the UR
pair. Yes Is the pair status No
SMPL?

Yes

Was the pair status Yes

changed to SMPL?

No Make the primary site

Was the pair status No execute the Delete Pair that
changed to PSUx? is an operation of the UR
pair.

Yes

END
Excute the pairresync that is
an operation of the UR pair.
(*1) After performing the UR
Force Delete Pair operation,
execute the paircreate again. Contact the Technical
(*1) Support Division.
END

END

*1: If a failure occurs after capacity expansion of one volume of a UR pair is successful, creating or
resynchronizing a UR pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then create or resynchronize the pair.

TRBL07-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-80

7.2 Procedure for Recovering UR Pair

START

Make sure of the pair status

through the Web Console.

Is the pair status No Is the pair status No

A
SMPL? PAIR or COPY?
(TRBL07-90)
Yes Yes
B

END
No
Is it an UR pair?

Yes
Make sure of the status of the
SVOL pair through the Web
Console on the secondary
site.

Is the pair status Yes

SMPL?

No
Make the secondary site
execute the Delete Pair that
is an operation of the UR
pair.

END

TRBL07-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-90

Is the pair status No Is the pair status No Is the pair status No

PSUx? Suspending? Deleting?

Yes Yes Yes

D Try to change the pair status Try to change the pair status
to PSUx. to SMPL.
Make sure of the pair status
of secondary site.

Yes Was the pair status Was the pair status Yes
changed to PSUx? changed to SMPL?

No No

Force delete the pair

according to “7.3 Force
Delete Pair Operation”.
B
(TRBL07-80)
Create the pair again.

END
Contact the Technical
Is the pair status No Support Division.
PSUx?
Confirm the restore journal.
Yes

Is the detailed pair No

status PSUS, JNL Cache Overflow? JNL usage has Yes
(*1) decreased?

Yes No
D
Expand the cache, increase the number
of paths between the primary site and the
E
secondary site, enlarge the journal volume
capacity, or reduce the I/O load. (TRBL07-100)

C
(TRBL07-100)

*1: On the Web Console, in the “View Pair Properties” window, see [Status] in the [Pair Detail] table to
check the detailed pair status. To open the “View Pair Properties” window, perform the following
steps:
1. From the [Storage Systems] tree, select [Replication]-[Remote Replication].
2. Select the check box of the UR pair, and then from the [Actions] menu, select [Remote
Replication]-[View Pair Properties].

TRBL07-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-100

Is the journal No
volume blocked or required to
be replaced?

Yes
Restore or replace the journal
volume. (Refer to TRBL07-130)

Is F/M = FB SSB at PSUx Yes

in Table 7-1?

No
Excute the pairresync that is an Execute the Force Delete Pair
operation of the UR pair. (*1) operation

Is the pair status COPY or Yes

PAIR?

No
Execute the Delete Pair that is an
operation of the UR pair, and then
execute the paircreate again. (*1)

END

*1: If a failure occurs after capacity expansion of one volume of a UR pair is successful, creating or
resynchronizing a UR pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then create or resynchronize the pair.

Table 7-1 Force Delete Pair Target F/M = FB SSB

No. F/M Error Code Meaning
1 FB EF60 to EF66 JNL-cache remains with the device of secondary site.

TRBL07-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-110

7.3 Force Delete Pair Operation

The Force Delete Pair operation is a remedy function for the cases where an UR pair is put in the following
abnormal states. Apply this function to both of the primary site and the secondary site.

• The pair was suspended owing to a trouble such as a failure and the pair status did not change but remained
as Suspend.
• Though the Delete Pair or Suspend Pair operation terminated normally, the pair status remained as Deleting
or Suspend.
• Please do not execute the Force Delete operation when all pairs in JNL Group are the pair status of PAIR or
COPY.

• All the data volumes that belong to the group (JNLG) concerned are placed in the Simplex
status because Force Delete Pair operates in the Group mode.
• As a result of performance of Force Delete Pair operation on the primary site, data that has not
been transferred to the secondary site is abandoned.
As a result of performance of Force Delete Pair operation on the secondary site, data that has
not been authorized is abandoned.
• There is a possibility that host I/O to the pair concerned becomes time out when the pair status
of PAIR/COPY exists in JNL Group.

After the Force Delete Pair operations for the primary site and the secondary site are completed, perform the
paircreate operation again in order to make sure that the pair has got out from the abnormal state.
When doing that, specify the JNL Group number as the same value as former one.

If the pair status is not restored in spite of the Force Delete Pair operation, make dummy replacement of all
the Controller Board for the storage system concerned.

TRBL07-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-120

START
Have a service person perform the
following operation.
Execute the pair deletion instructed
by Force Delete Pair.
The following are
Did operations to be
Check statuses of all pairs that No performed by a
belong to the JNL Group concerned. the trouble occur in the
primary site? service person.

Yes
Is the pair status No
A Make the dummy replacement of all
SMPL? the Controller Board.
Yes
Execute the pairsplit instructed by Execute the paircreate in order to
Force Delete Pair. check the result of the recovery
operation. (*1)

Check statuses of all pairs that

belong to the JNL Group concerned. Was
Yes
the recovery operation B
successful?
Is the pair status No No
A
SMPL?

Yes Did
the trouble occur in the No
Execute the paircreate in order to secondary site?
check the result of the recovery
operation. (*1) Yes
Make the dummy replacement of all
Was the Controller Board.
No
the recovery operation
successful? Execute the paircreate in order to
Yes check the result of the recovery
B operation. (*1)

Was
END Yes
the recovery operation
successful?
No
A

Contact the Technical

Support Division.

: Operation on the primary site : Operation on the secondary site

*1: If a failure occurs after capacity expansion of one volume of a UR pair is successful, creating a UR
pair in the procedure is not possible due to capacity inconsistency. Perform capacity expansion so
that the capacities are consistent, and then create the pair.

TRBL07-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-130

7.4 Procedure for UR Pinned Track Recovery and Journal Volume Replacement
Procedure for UR pinned track recovery and journal volume replacement is as follows.
For the UR pair/GAD pair status check and the journal volume check/operation in the following recovery
procedure, ask the customer to do them.

START

Is the volume in
which the pinned track has occurred
No
a UR journal volumes? Or is the volume that is
required to be replaced a journal
volume?

Yes

Is there any No
blocked PDEV?

Yes
Restore the blocked PDEV. Refer to “Recovery
Procedure for LDEV Blockade” (TRBL03-300)

1A 2A

Pinned Track Recovery Pinned Track Recovery Procedure for UR

Procedure for UR Data Volumes Journal Volumes and UR Journal Volume
Replacement Procedure

NOTE: If the pinned track has occurred in both P-VOL and S-VOL, recover the volumes
according to the following sequence.

UR :  P-VOL →  S-VOL
If the pinned track has occurred in both data volumes and journal volumes, recover
the volumes according to the following sequence.
 data volumes →  journal volumes

TRBL07-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-140

Pinned Track Recovery

Procedure for UR Data Volumes

1A

Is the
volume in which the Yes
pinned track has occurred a
P-VOL?

No

Error type of the Write Error

pinned track?

ECC/LRC Error
Delete the UR data volume pair in Execute the existing Write Error Execute “Pinned track recovery
which the pinned track has occurred track recovery procedure. Refer (TRBL04-160)”. (*1)
using Web Console. to the Write Error track recovery However, data recovery of the
procedure (start from  on UR pair is not included. (*2)
Check if there is a hardware error on the TRBL04-260). However, data
“Maintenance Utility” window and solve recovery of the UR pair is not
the hardware problem. included. (*2)

Does Pinned No
track exist outside the userʼs
area? (*3)

Yes

2 1
(TRBL07-160) (TRBL07-160)

*1: In the recovery from a pinned track, only the LDEV formatting is executed except in the case of
Solaris. For Solaris, only the correction of a pinned track by means of the analyze command is
executed. To recover the data of the UR pair, reconfigure the UR volume pair.
However, the LDEV formatting or the analyze command executing is not required if the pinned
track is a DP volume and out of the user area.
*2: The data of the UR pair is recovered by reconfiguring the UR volume pair.
*3: If MAINTENANCE PC SECTION “5.12.3 Pin Data Indication” doesnʼt indicate LBAs of pinned
track, this indicates that a pinned track occurred outside the user area.

TRBL07-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-150

Pinned Track Recovery Procedure for UR

Journal Volumes and UR Journal Volume
Replacement Procedure

2A
Delete the UR data volume pair under the
journal group that includes the journal
volume in which the pinned track has
occurred or the UR data volume pair under
Is there any journal volume No
the journal group that includes the journal
to be newly assigned? volume to be replaced using Web Console.

Yes Delete the journal volume in which the

pinned track has occurred or the journal
Is the journal volume to be replaced using Web Console.
volume in which a failure
occurred in the L site (secondary No
3 (TRBL07-170)
volume of the GAD pair) in
the GAD-UR delta
configuration?

Yes
Are all UR pairs
Swap suspend the GAD pair. under the journal group that Yes
includes the journal volume in which
Swap resynchronize the GAD pair. (*1) the pinned track has occurred
suspended?
Suspend the UR pair in the L site and R site.
No
Register another journal volume that is not
assigned yet. Suspend all UR pairs under the journal group
that includes the journal volume in which the
pinned track has occurred.
Delete the journal volume in which a failure
occurred.

Resynchronize the UR pair in the L site and

R site. (*1) 4 (TRBL07-171)

Swap suspend the GAD pair.

Swap resynchronize the GAD pair. (*1)

END

NOTE: For assign the journal volume, see the “Hitachi Universal Replicator User Guide”.
If the journal volume to be assigned exists, prioritize recovery or replacement of UR
pair. After the recovery of UR pair, format the blocked virtual volume to reduce the
recovery or replacement time.
*1: If a failure occurs after capacity expansion of one volume of a UR/GAD pair is successful,
resynchronizing a UR/GAD pair in the procedure is not possible due to capacity inconsistency.
Perform capacity expansion so that the capacities are consistent, and then resynchronize the pair.

TRBL07-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-160

2 1

Is the Capacity
Saving setting of the Yes
volume in which the pinned track
has occurred other than
disabled?

No
Perform the Reclaiming the control Execute “4.2 Pinned track recovery”.(*1)
pages inside the DP-VOL. However, data recovery of the UR pair
(Refer to “3.52 Reclaiming the Control is not included. (*2)
Pages Inside the DP-VOL”.)

Reconfigure the UR volume pair by

using Web Console. (*3) (*4)

END

*1: In the recovery from a pinned track, only the LDEV formatting is executed except in the case of
Solaris. For Solaris, only the correction of a pinned track by means of the analyze command is
executed. To recover the data of the UR pair, reconfigure the UR volume pair.
However, the LDEV formatting or the analyze command executing is not required if the pinned
track is a DP volume and out of the user area.
*2: The data of the UR pair is recovered by reconfiguring the UR volume pair.
*3: If a failure occurs after capacity expansion of one volume of a UR pair is successful,
resynchronizing a UR pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then resynchronize the pair.
*4: If you have deleted the UR pair in this workflow, recreate the UR pair. If you have not deleted the
UR pair, perform pair resynchronization.

TRBL07-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-170

Pinned track No
recovery?
Format the DP-VOL that was
Yes required to be replaced. (*1)
(See MPC04-370.)
Error type of the Write Error
Register the volume that was
pinned track?
required to be replaced as a journal
volume.
ECC/LRC Error
Check if there is a hardware error on Execute the existing Write Error track
the “Maintenance Utility” window recovery procedure. Refer to the Write
and solve the hardware problem. Error track recovery procedure (start from
ƒ on TRBL04-260). But the data recovery
is not included.

Format the volume which recovered

the pinned track and register it as a
journal volume.

1
(TRBL07-160)

*1: When the DP-pool VOL is blocked, restore the pool and perform LDEV formatting on the DP-
VOL (see “10. Failure recovery of Dynamic Provisioning”).
Register the volume that was required to be replaced as a journal volume after completion of
recovery procedure.

TRBL07-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-171

Does the
journal group that
includes the journal volume
in which the pinned track has occurred No
contain UR delta pairs that form a
multi target configuration
using three UR
sites?

Yes

Delete all UR delta pairs under the journal

group that includes the journal volume in
which the pinned track has occurred.

Newly assign the journal volume which has

not yet been assigned.

Delete the journal volume in which a failure

occurred.

Resynchronize the suspended UR pairs.

Did you delete UR delta pairs No

in this procedure?

Yes
Create the deleted UR delta pairs again. If the
assignment of remote command devices to
mirror IDs has been released at the time of the
UR delta pair deletion, perform the assignment
again.

1
(TRBL07-160)

TRBL07-171
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-180

7.5 Failure Recovery Procedure and Planned Shutdown Procedure of the UR-UR delta
Configuration
Since the UR-UR delta configuration consists of the three Universal Replicators, the description of the UR-
UR delta configuration of the failure recovery procedure and the planned shutdown procedure are defined as
follows.
For the UR-UR delta configuration, see the section related to the 3DC configuration by the three Universal
Replicator sites in “Universal Replicator User Guide”.

UR-UR delta Configuration Definition of the Description

UR between PDKC-LDKC (IDKC (*1) ) UR1
UR between PDKC-RDKC (multi target configuration), or
UR2
UR between IDKC-RDKC (cascade configuration)
UR delta configuration between LDKC-RDKC (multi target configuration),
UR delta
or UR delta (cascade configuration) between PDKC-RDKC.
*1: Storage system in the intermediate site of IDKC (Intermediate DKC) and UR (Cascade
Configuration)

7.5.1  Failure Recovery Procedure of the UR-UR delta Configuration

The following tables describe pair statuses in the event of a single point of failure and recovery operations.
The pair status in each table indicates the pair status displayed in CCI. The UR pair status in parentheses
indicates the pair status displayed in Storage Navigator.
This failure recovery procedure describes the recovery procedure to maintain the disaster discovery
configuration.
If a failure occurs after capacity expansion of one volume of a UR pair is successful, creating or
resynchronizing a UR pair in the recovery procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then create or resynchronize the pair.

TRBL07-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-190

1. Multi Target Configuration: Path between DKC

Mirror
No. Item Pair Status Recovery operation
ID

‒ [Normal PVOL PAIR LVOL PAIR

Operation] 0 (UR1 (UR1
PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
1 PDKC PVOL PAIR LVOL PAIR 1. Failure recovery site
→ LDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
2 LDKC PVOL PAIR LVOL PAIR • SOM448 = ON and SOM449 =
→ PDKC 0 (UR1 (UR1 OFF:
Path failure PVOL) SVOL) After communication break
PVOL PAIR RVOL PAIR detection, immediately UR
1 (UR2 (UR2 pair failure suspend.
PVOL) SVOL) • SOM448 = OFF and SOM449
LVOL SSUS RVOL SSUS = OFF:
(UR delta (HOLD) (UR delta (HOLD) UR pair failure suspend Once
PVOL) SVOL) communication is severed a
certain period of time.
2 Any of the above, the recovery in
the following procedure.
1. Failure recovery site (Recover
paths).
2. UR1 pair resync in PVOL.
(To be continued)

TRBL07-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-200

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 LDKC PVOL PAIR LVOL PAIR 1. Failure recovery site
→ RDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
4 RDKC PVOL PAIR LVOL PAIR 1. Failure recovery site
→ LDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
5 PDKC PVOL PAIR LVOL PAIR 1. Failure recovery site
→ RDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
6 RDKC PVOL PAIR LVOL PAIR • SOM448 = ON and SOM449 =
→ PDKC 0 (UR1 (UR1 OFF:
Path failure PVOL) SVOL) After communication break
PVOL PAIR RVOL PAIR detection, immediately UR
1 (UR2 (UR2 pair failure suspend.
PVOL) SVOL) • SOM448 = OFF and SOM449
LVOL SSUS RVOL SSUS = OFF:
(UR delta (HOLD) (UR delta (HOLD) UR pair failure suspend Once
PVOL) SVOL) communication is severed a
certain period of time.
2 Any of the above, the recovery in
the following procedure.
1. Failure recovery site
(Recover paths).
2. UR2 pair resync in PVOL.
(To be continued)
TRBL07-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-210

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
7 Path failure PVOL PAIR LVOL PAIR 1. Failure recovery site
for remote 0 (UR1 (UR1 (Recover paths).
command PVOL) SVOL)
device PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)

TRBL07-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-220

2. Multi Target Configuration: Pool Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL PVOL PAIR LVOL PAIR 1. UR1 swap suspend in LVOL.
pool full 0 (UR1 (UR1 2. Delta resync (Swap resync the
PVOL) SVOL) UR delta).
PVOL PAIR RVOL PAIR 3. Failure recovery site
1 (UR2 (UR2 (Expand the pool capacity).
PVOL) SVOL) 4. UR1, UR2 pairs recovery.
LVOL SSUS RVOL SSUS (*1)
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
2 PVOL PVOL PAIR LVOL PAIR 1. UR1 swap suspend in LVOL.
pool failure 0 (UR1 (UR1 2. Delta resync (Swap resync the
PVOL) SVOL) UR delta).
PVOL PAIR RVOL PAIR 3. Failure recovery site
1 (UR2 (UR2 (See to TRBL10-10).
PVOL) SVOL) 4. UR1, UR2 pairs recovery.
LVOL SSUS RVOL SSUS (*1)
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
3 LVOL PVOL PSUE LVOL PFUS 1. UR1 failure suspension is
pool full 0 (UR1 (UR1 detected.
PVOL) SVOL) 2. Failure recovery site
PVOL PAIR RVOL PAIR (Expand the pool capacity).
1 (UR2 (UR2 3. UR1 pair recovery. (*1)
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
4 LVOL PVOL PSUE LVOL PSUE 1. UR1 failure suspension is
pool failure 0 (UR1 (UR1 detected.
PVOL) SVOL) 2. Failure recovery site
PVOL PAIR RVOL PAIR (See to TRBL10-10).
1 (UR2 (UR2 3. UR1 pair recovery. (*1)
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
(To be continued)

TRBL07-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-230

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
5 RVOL PVOL PAIR LVOL PAIR 1. UR2 failure suspension is
pool full 0 (UR1 (UR1 detected.
PVOL) SVOL) 2. Failure recovery site
PVOL PSUE RVOL PFUS (Expand the pool capacity).
1 (UR2 (UR2 3. UR2 pair recovery. (*1)
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
6 RVOL PVOL PAIR LVOL PAIR 1. UR2 failure suspension is
pool failure 0 (UR1 (UR1 detected.
PVOL) SVOL) 2. Failure recovery site
PVOL PSUE RVOL PSUE (See TRBL10-10).
1 (UR2 (UR2 3. UR2 pair recovery. (*1)
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: UR-UR configuration is reconfigured depending on the pair status.

TRBL07-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-240

3. Multi Target Configuration: Journal Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal PVOL PFUS LVOL PFUS When there are unused journal
volume full 0 (UR1 (UR1 volumes (*4):
PVOL) SVOL) 1. According to TRBL07-150,
PVOL PFUS RVOL PFUS assign the unused journal
1 (UR2 (UR2 volumes to UR1 and UR2.
PVOL) SVOL) (*3)
LVOL SSUS RVOL SSUS 2. Delete the journal volumes
(UR delta (HOLD) (UR delta (HOLD) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR1, UR2 resync in PVOL.
When there are no unused journal
volumes:
1. UR1, UR2 failure suspensions
are detected. (*1)
2. Failure recovery site (Expand
2
the journal volume capacity).
3. UR1, UR2 resync in PVOL.
If failover occurs:
1. UR1, UR2 failure suspensions
are detected. (*1)
2. UR1 swap suspend in LVOL.
3. Delta resync (Swap resync the
UR delta).
4. Failure recovery site (Expand
the journal volume capacity).
5. UR1 swap resync in LVOL.
(To be continued)

TRBL07-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-241

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
2 PDKC journal PVOL PFUS LVOL PSUE When there are unused journal
volume 0 (UR1 (UR1 volumes (*4):
failure PVOL) SVOL) 1. According to TRBL07-150,
PVOL PSUE RVOL PSUE assign the unused journal
1 (UR2 (UR2 volumes to UR1 and UR2.
PVOL) SVOL) (*3)
LVOL SSUS RVOL SSUS 2. Delete the journal volumes
(UR delta (HOLD) (UR delta (HOLD) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR1, UR2 resync in PVOL.
When there are no unused journal
volumes:
1. UR1, UR2 failure suspensions
2 are detected.
2. UR1 swap suspend in LVOL.
3. Delta resync (Swap resync the
UR delta).
4. Failure recovery site.
5. UR1 swap resync in LVOL.
*: If the UR2 (PVOL-RVOL)
pair status is HLDE, delta
recovery is performed from
PVOL.
3 LDKC PVOL PFUS (*2) LVOL PFUS (*2) 1. For the recovery procedure
journal 0 (UR1 (UR1 when PDKC journal volume
volume full PVOL) SVOL) is full, see the recovery
PVOL PAIR RVOL PAIR operation for #1. (*1)
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
(To be continued)

TRBL07-241
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-250

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
4 LDKC PVOL PSUE LVOL PSUE When there are unused journal
journal 0 (UR1 (UR1 volumes (*4):
volume PVOL) SVOL) 1. According to TRBL07-150,
failure PVOL PAIR RVOL PAIR assign the unused journal
1 (UR2 (UR2 volumes to UR1 and UR
PVOL) SVOL) delta.
LVOL PSUE RVOL SSUS 2. Delete the journal volumes
(UR delta (HLDE) (UR delta (HOLD) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR1 resync in PVOL.
When there are no unused journal
volumes:
2 1. UR1 failure suspension is
detected.
2. Failure recovery site.
3. Delete UR delta.
4. UR1 resync in PVOL.
5. Create UR delta.
6. Assign the remote command
device for the journal mirror
ID in each site.
5 RDKC PVOL PAIR LVOL PAIR 1. For the recovery procedure
journal 0 (UR1 (UR1 when PDKC journal volume
volume full PVOL) SVOL) is full, see the recovery
PVOL PFUS (*2) RVOL PFUS (*2) operation for #1. (*1)
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
(To be continued)

TRBL07-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-251

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
6 RDKC PVOL PAIR LVOL PAIR When there are unused journal
journal 0 (UR1 (UR1 volumes (*4):
volume PVOL) SVOL) 1. According to TRBL07-150,
failure PVOL PSUE RVOL SSUE assign the unused journal
1 (UR2 (UR2 volumes to UR2 and UR
PVOL) SVOL) delta.
LVOL SSUS RVOL PSUE 2. Delete the journal volumes
(UR delta (HOLD) (UR delta (HLDE) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR2 resync in PVOL.
When there are no unused journal
volumes:
2 1. UR2 failure suspension is
detected.
2. Failure recovery site.
3. Delete UR delta.
4. UR2 pair resync in PVOL.
5. Create UR delta.
6. Assign the remote command
device for the journal mirror
ID in each site.
*1: When a communication line error occurs, only UR with the error might have the journal volume
full (in PFUS pair status). If so, recover the failed part, and then resync the UR.
*2: The LDKC or RDKC pair status does not become PFUS until the PDKC journal volume becomes
full. Thus, the LDKC or RDKC journal volume can be expanded until the PDKC journal volume
becomes full.
*3: When assigning a new journal volume, specify the journal volume whose capacity is larger than
the journal volume which is already full.
*4: For cases requiring LDEV formatting due to a 2PDEV failure, you can recover from the failure
or reduce the replacement time by restoring the UR pair according to this procedure and then
resolving the PDEV/LDEV blockade.

TRBL07-251
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-260

4. Multi Target Configuration: Journal Volumes (Pool Volumes) (*1)

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal PVOL PSUE LVOL SSUE 1. UR1, UR2 failure suspensions
volume pool 0 (UR1 (UR1 are detected.
full PVOL) SVOL) 2. UR1 swap suspend in LVOL.
PVOL PSUE RVOL SSUE 3. Delta resync (Swap resync the
1 (UR2 (UR2 UR delta).
PVOL) SVOL) 4. Failure recovery site.
LVOL SSUS RVOL SSUS 5. UR1 swap resync in LVOL.
(UR delta (HOLD) (UR delta (HOLD) *: If the UR (PVOL-RVOL)
2 PVOL) SVOL) pair status is HLDE, delta
recovery is performed from
PVOL.
2 PDKC journal PVOL PSUE LVOL SSUE 1. UR1, UR2 failure suspensions
volume pool 0 (UR1 (UR1 are detected.
failure PVOL) SVOL) 2. UR1 swap suspend in LVOL.
PVOL PSUE RVOL SSUE 3. Delta resync (Swap resync the
1 (UR2 (UR2 UR delta).
PVOL) SVOL) 4. Failure recovery site.
LVOL SSUS RVOL SSUS 5. UR1 swap resync in LVOL.
(UR delta (HOLD) (UR delta (HOLD) *: If the UR (PVOL-RVOL)
2 PVOL) SVOL) pair status is HLDE, delta
recovery is performed from
PVOL.
3 LDKC PVOL PSUE LVOL PSUE 1. UR1 failure suspension is
journal 0 (UR1 (UR1 detected.
volume pool PVOL) SVOL) 2. Failure recovery site.
full PVOL PAIR RVOL PAIR 3. Delete UR delta.
1 (UR2 (UR2 4. UR1 resync in PVOL.
PVOL) SVOL) 5. Create UR delta.
LVOL PSUE RVOL SSUS 6. Assign the remote command
2 (UR delta (HLDE) (UR delta (HOLD) device for the journal mirror
PVOL) SVOL) ID in each site.
(To be continued)

TRBL07-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-270

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
4 LDKC PVOL PSUE LVOL PSUE 1. UR1 failure suspension is
journal 0 (UR1 (UR1 detected.
volume pool PVOL) SVOL) 2. Failure recovery site.
failure PVOL PAIR RVOL PAIR 3. Delete UR delta.
1 (UR2 (UR2 4. UR1 resync in PVOL.
PVOL) SVOL) 5. Create UR delta.
LVOL PSUE RVOL SSUS 6. Assign the remote command
2 (UR delta (HLDE) (UR delta (HOLD) device for the journal mirror
PVOL) SVOL) ID in each site.
5 RDKC PVOL PAIR LVOL PAIR 1. UR2 failure suspension is
journal 0 (UR1 (UR1 detected.
volume pool PVOL) SVOL) 2. Failure recovery site.
full PVOL PSUE RVOL PSUE 3. Delete UR delta.
1 (UR2 (UR2 4. UR2 resync in PVOL.
PVOL) SVOL) 5. Create UR delta.
LVOL SSUS RVOL PSUE 6. Assign the remote command
2 (UR delta (HOLD) (UR delta (HLDE) device for the journal mirror
PVOL) SVOL) ID in each site.
6 RDKC PVOL PAIR LVOL PAIR 1. UR2 failure suspension is
journal 0 (UR1 (UR1 detected.
volume pool PVOL) SVOL) 2. Failure recovery site.
failure PVOL PSUE RVOL PSUE 3. Delete UR delta.
1 (UR2 (UR2 4. UR2 resync in PVOL.
PVOL) SVOL) 5. Create UR delta.
LVOL SSUS RVOL PSUE 6. Assign the remote command
2 (UR delta (HOLD) (UR delta (HLDE) device for the journal mirror
PVOL) SVOL) ID in each site.
*1: Recovery procedures for failure in the pool of DP-VOLs registered as journal volumes are
described. The pool full status might occur when the capacity of journal volumes is defined more
than that of all unused pool volumes.

TRBL07-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-280

5. Multi Target Configuration: LDEV

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL failure PVOL PAIR LVOL PAIR When the recovery by the LDEV
0 (UR1 (UR1 format is necessary:
PVOL) SVOL) 1. UR1 swap suspend.
PVOL PAIR RVOL PAIR 2. Delta resync (Swap resync the
1 (UR2 (UR2 UR delta).
PVOL) SVOL) 3. Delete UR1 and UR2.
LVOL SSUS RVOL SSUS 4. Failure recovery site.
(UR delta (HOLD) (UR delta (HOLD) 5. UR1/UR2 recovery. (*1)
PVOL) SVOL) 6. Assign the remote command
device for the journal mirror
ID in each site.
7. UR1 swap suspend.
8. Delta resync (Swap resync the
UR2).
9. Swap resync the UR1.
2
When the recovery by the LDEV
format is not necessary:
1. UR1 swap suspend in LVOL.
2. Delta resync (Resync the UR
delta pair).
3. Failure recovery site.
4. UR1, UR2 pairs recovery.
(*2)
5. UR delta pair recovery.
2 LVOL failure PVOL PSUE LVOL SSUE When the recovery by the LDEV
0 (UR1 (UR1 format is necessary:
PVOL) SVOL) 1. Detection of UR1 in failure
PVOL PAIR RVOL PAIR suspend status.
1 (UR2 (UR2 2. Delete UR1.
PVOL) SVOL) 3. Failure recovery site.
LVOL SSUS RVOL SSUS 4. UR1 pair recovery. (*2)
(UR delta (HOLD) (UR delta (HOLD) 5. UR delta pair recovery.
PVOL) SVOL) When the recovery by the LDEV
format is not necessary:
2 1. UR1 failure suspension is
detected.
2. Failure recovery site.
3. UR1 pair recovery. (*2)
4. UR delta pair recovery.
(To be continued)

TRBL07-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-281

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 RVOL failure PVOL PAIR LVOL PAIR When the recovery by the LDEV
0 (UR1 (UR1 format is necessary:
PVOL) SVOL) 1. Detection of UR2 in failure
PVOL PSUE RVOL PSUE suspend status.
1 (UR2 (UR2 2. Delete UR2.
PVOL) SVOL) 3. Failure recovery site.
LVOL SSUS RVOL SSUS 4. UR2 recovery.
(UR delta (HOLD) (UR delta (HOLD) 5. UR delta pair recovery.
PVOL) SVOL) When the recovery by the LDEV
format is not necessary:
2 1. UR2 failure suspension is
detected.
2. Failure recovery site.
3. UR2 pair recovery. (*2)
4. UR delta pair recovery.
4 Remote PVOL PAIR LVOL PAIR 1. Failure recovery site.
command 0 (UR1 (UR1
device failure PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: Create UR1 by copying LVOL to PVOL, and UR2 as a delta resync pair.
*2: UR-UR configuration is reconfigured depending on the pair status.

TRBL07-281
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-290

6. Multi Target Configuration: Storage system

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC failure PVOL PAIR (*1) LVOL PAIR (*1) 1. UR1 swap suspend in LVOL.
(SM/CM 0 (UR1 (UR1 2. Delta resync (Swap resync the
Non-Volatile) PVOL) SVOL) UR delta).
PVOL PAIR RVOL PAIR 3. DKC recovery.
1 (UR2 (UR2 4. UR1 swap resync in LVOL.
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
2 LDKC failure PVOL PAIR (*2) LVOL PAIR (*2) 1. DKC recovery.
(SM/CM 0 (UR1 (UR1
Non-Volatile) PVOL) SVOL)
PVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
3 RDKC failure PVOL PAIR LVOL PAIR 1. DKC recovery.
(SM/CM 0 (UR1 (UR1
Non-Volatile) PVOL) SVOL)
PVOL PAIR (*3) RVOL PAIR (*3)
1 (UR2 (UR2
PVOL) SVOL)
LVOL SSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: UR pair information of PDKC (PVOL) is retained, which changes the UR1 pair state to PSUE
after PDKC (PVOL) PS is on.
*2: If you have SOM 449 = OFF in PDKC, the UR1 pair status becomes PSUE, and UR1 resync is
required after the DKC recovery.
*3: If you have SOM 449 = OFF in PDKC, the UR2 pair status becomes PSUE, and UR2 resync is
required after the DKC recovery.

TRBL07-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-300

7. Cascade Configuration: Path between DKC

Mirror
No. Item Pair Status Recovery operation
ID
‒ [Normal PVOL PAIR IVOL PAIR
Operation] 0 (UR1 (UR1
PVOL) SVOL)
IVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
1 PDKC PVOL PAIR IVOL PAIR 1. Failure recovery site
→ IDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
IVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
2 IDKC PVOL PAIR IVOL PAIR • SOM448 = ON and SOM449 =
→ PDKC 0 (UR1 (UR1 OFF:
Path failure PVOL) SVOL) After communication break
IVOL PAIR RVOL PAIR detection, immediately UR
1 (UR2 (UR2 pair failure suspend.
• SOM448 = OFF and SOM449
PVOL) SVOL)
= OFF:
PVOL PSUS RVOL SSUS
UR pair failure suspend Once
(UR delta (HOLD) (UR delta (HOLD) communication is severed a
PVOL) SVOL) certain period of time.
1. Delta resync (Pair resync the
UR delta in PVOL).
2. Failure recovery site
(Recover paths).
3. If UR1 is suspended, pair
resync UR1 in PVOL.
2 When it is for the multi target
operation, the following
recovery procedure is not
required.
4. Delete UR delta and UR2.
5. Create UR2 pair.
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.

(To be continued)
TRBL07-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-310

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 IDKC PVOL PAIR IVOL PAIR 1. Failure recovery site
→ RDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
IVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
4 RDKC PVOL PAIR IVOL PAIR • SOM448 = ON and SOM449 =
→ IDKC 0 (UR1 (UR1 OFF:
Path failure PVOL) SVOL) After communication break
IVOL PAIR RVOL PAIR detection, immediately UR
1 (UR2 (UR2 pair failure suspend.
PVOL) SVOL) • SOM448 = OFF and SOM449
PVOL PSUS RVOL SSUS = OFF:
(UR delta (HOLD) (UR delta (HOLD) UR pair failure suspend Once
PVOL) SVOL) communication is severed a
certain period of time.
2 Any of the above, the recovery in
the following procedure.
1. Failure recovery site
(Recover paths).
2. UR2 pair resync in IVOL.
5 PDKC PVOL PAIR IVOL PAIR 1. Failure recovery site
→ RDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
IVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
6 RDKC PVOL PAIR IVOL PAIR 1. Failure recovery site
→ PDKC 0 (UR1 (UR1 (Recover paths).
Path failure PVOL) SVOL)
IVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
(To be continued)
TRBL07-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-320

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
7 Path failure PVOL PAIR IVOL PAIR 1. Failure recovery site
for remote 0 (UR1 (UR1 (Recover paths).
command PVOL) SVOL)
device IVOL PAIR RVOL PAIR
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)

TRBL07-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-330

8. Cascade Configuration: Pool Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL PVOL PAIR IVOL PAIR 1. UR1 swap suspend in IVOL.
pool full 0 (UR1 (UR1 2. Failure recovery site
PVOL) SVOL) (Expand the pool capacity).
IVOL PAIR RVOL PAIR 3. UR1 pair recovery in IVOL.
1 (UR2 (UR2 4. UR1 swap suspend in PVOL.
PVOL) SVOL) 5. UR1 swap resync in PVOL.
PVOL PSUS RVOL SSUS 6. UR2 pair resync in IVOL.
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
2 PVOL PVOL PAIR (*2) IVOL PAIR (*2) 1. UR1 swap suspend in IVOL.
pool failure 0 (UR1 (UR1 2. Failure recovery site
PVOL) SVOL) (See TRBL10-10).
IVOL PAIR RVOL PAIR 3. UR1 pair recovery in IVOL.
1 (UR2 (UR2 4. UR1 swap suspend in PVOL.
PVOL) SVOL) 5. UR1 swap resync in PVOL.
PVOL PSUS RVOL SSUS 6. UR2 pair resync in IVOL.
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
3 IVOL PVOL PSUE IVOL PFUS 1. Delta resync (Pair resync the
pool full 0 (UR1 (UR1 UR delta in PVOL).
PVOL) SVOL) 2. Failure recovery site
IVOL PAIR RVOL PAIR (Expand the pool capacity).
1 (UR2 (UR2 3. UR1 pair recovery in PVOL.
PVOL) SVOL) *: When it is for the multi
PVOL PSUS RVOL SSUS target operation, the
(UR delta (HOLD) (UR delta (HOLD) following recovery
PVOL) SVOL) procedure is not required.
4. Delete UR delta and UR2.
2 5. Create UR2 pair.
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
(To be continued)

TRBL07-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-340

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
4 IVOL PVOL PSUE IVOL PSUE 1. Delta resync (Pair resync the
pool failure 0 (UR1 (UR1 UR delta in PVOL).
PVOL) SVOL) 2. Failure recovery site
IVOL PAIR (*2) RVOL PAIR (*2) (See TRBL10-10).
1 (UR2 (UR2 3. UR1 pair recovery in PVOL.
PVOL) SVOL) *: When it is for the multi
PVOL PSUS RVOL SSUS target operation, the
(UR delta (HOLD) (UR delta (HOLD) following recovery
PVOL) SVOL) procedure is not required.
4. Delete UR delta and UR2.
2 5. Create UR2 pair.
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
5 RVOL PVOL PAIR IVOL PAIR 1. UR2 failure suspension is
pool full 0 (UR1 (UR1 detected.
PVOL) SVOL) 2. Failure recovery site
IVOL PSUE RVOL PFUS (Expand the pool capacity).
1 (UR2 (UR2 3. UR2 pair recovery in IVOL.
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
6 RVOL PVOL PAIR IVOL PAIR 1. UR2 failure suspension is
pool failure 0 (UR1 (UR1 detected.
PVOL) SVOL) 2. Failure recovery site
IVOL PSUE RVOL PSUE (See TRBL10-10).
1 (UR2 (UR2 3. UR2 pair recovery in IVOL.
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: UR-UR configuration is reconfigured depending on the pair status.
*2: The pair status is PSUE during UR2 pair creation or resynchronization.

TRBL07-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-350

9. Cascade Configuration: Journal Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal PVOL PFUS IVOL PFUS When there are unused journal
volume full 0 (UR1 (UR1 volumes:
PVOL) SVOL) 1. According to TRBL07-150,
IVOL PAIR RVOL PAIR assign the unused journal
1 (UR2 (UR2 volumes to UR1. (*3)
PVOL) SVOL) 2. Delete the journal volumes
PVOL PSUS RVOL SSUS which were already registered
(UR delta (HOLD) (UR delta (HOLD) prior to the assignment of the
PVOL) SVOL) unused journal volumes in
step (1).
3. UR1 resync in PVOL.
When there are no unused journal
volumes:
1. UR1 failure suspension is
detected.
2. Failure recovery site (Expand
the journal volume capacity).
2
3. UR1 pair resync in PVOL.
If failover occurs:
1. UR1 failure suspension is
detected.
2. UR1 swap suspend in IVOL.
3. Failure recovery site (Expand
the journal volume capacity).
4. UR1 swap resync in IVOL.
5. UR1 swap suspend in PVOL.
6. UR1 swap resync in PVOL.
7. UR2 pair resync in IVOL.
(To be continued)

TRBL07-350
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-351

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
2 PDKC journal PVOL PSUE IVOL PSUE When there are unused journal
volume 0 (UR1 (UR1 volumes (*4):
failure PVOL) SVOL) 1. According to TRBL07-150,
IVOL PAIR RVOL PAIR assign the unused journal
1 (UR2 (UR2 volumes to UR1.
PVOL) SVOL) 2. Delete the journal volumes
PVOL PSUE RVOL SSUS which were already registered
(UR delta (HLDE) (UR delta (HOLD) prior to the assignment of the
PVOL) SVOL) unused journal volumes in
step (1).
3. UR1 resync in PVOL.
When there are no unused journal
volumes:
1. UR1 failure suspension is
2
detected.
2. UR1 swap suspend in IVOL.
3. Failure recovery site.
4. UR1 swap resync in IVOL.
5. UR1 swap suspend in PVOL.
6. UR1 swap resync in PVOL.
7. UR2 pair resync in IVOL.
8. UR delta the delta recover.
(To be continued)

TRBL07-351
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-352

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 IDKC journal PVOL PFUS (*1) IVOL PFUS (*1) When there are unused journal
volume full 0 (UR1 (UR1 volumes:
PVOL) SVOL) 1. According to TRBL07-150,
IVOL PFUS RVOL PFUS assign the unused journal
1 (UR2 (UR2 volumes to UR1 and UR2.
PVOL) SVOL) (*3)
PVOL PSUS RVOL SSUS 2. Delete the journal volumes
(UR delta (HOLD) (UR delta (HOLD) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR1 resync in PVOL.
4. UR2 resync in IVOL.
2 When there are no unused journal
volumes:
1. UR1, UR2 failure suspensions
are detected. (*1)
2. Failure recovery site (Expand
the journal volume capacity).
3. UR1 pair resync in PVOL.
4. UR2 pair resync in IVOL.
(To be continued)

TRBL07-352
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-360

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
4 IDKC journal PVOL PSUE IVOL PSUE When there are unused journal
volume 0 (UR1 (UR1 volumes (*4):
failure PVOL) SVOL) 1. According to TRBL07-150,
IVOL PSUE RVOL PSUE assign the unused journal
1 (UR2 (UR2 volumes to UR1 and UR2.
PVOL) SVOL) 2. Delete the journal volumes
PVOL PSUS RVOL SSUS which were already registered
(UR delta (HOLD) (UR delta (HOLD) prior to the assignment of the
PVOL) SVOL) unused journal volumes in
step (1).
3. UR1 resync in PVOL.
4. UR2 resync in IVOL.
When there are no unused journal
volumes:
1. Delta resync (Pair resync the
UR delta in PVOL).
2. Failure recovery site.
2
3. UR1 pair resync in PVOL.
*: When it is for the multi
target operation, the
following recovery
procedure is not required.
4. Delete UR delta and UR2.
5. Create UR2 pair.
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
(To be continued)

TRBL07-360
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-361

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
5 RDKC PVOL PFUS (*2) IVOL PFUS (*2) When there are unused journal
journal 0 (UR1 (UR1 volumes:
volume full PVOL) SVOL) 1. According to TRBL07-150,
IVOL PFUS (*2) RVOL PFUS (*2) assign the unused journal
1 (UR2 (UR2 volumes to UR2 and UR
PVOL) SVOL) delta. (*3)
PVOL PSUS RVOL SSUS 2. Delete the journal volumes
(UR delta (HOLD) (UR delta (HOLD) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR1 resync in PVOL.
4. UR2 resync in IVOL.
2 When there are no unused journal
volumes:
1. UR1, UR2 failure suspensions
are detected. (*2)
2. Failure recovery site (Expand
the journal volume capacity).
3. UR1 pair resync in PVOL.
4. UR2 pair resync in IVOL.
(To be continued)

TRBL07-361
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-362

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
6 RDKC PVOL PAIR IVOL PAIR When there are unused journal
journal 0 (UR1 (UR1 volumes (*4):
volume PVOL) SVOL) 1. According to TRBL07-150,
failure IVOL PSUE RVOL PSUE assign the unused journal
1 (UR2 (UR2 volumes to UR2 and UR
PVOL) SVOL) delta.
PVOL PSUS RVOL PSUE 2. Delete the journal volumes
(UR delta (HOLD) (UR delta (HLDE) which were already registered
PVOL) SVOL) prior to the assignment of the
unused journal volumes in
step (1).
3. UR2 resync in IVOL.
When there are no unused journal
volumes:
2 1. UR2 failure suspension is
detected.
2. Failure recovery site.
3. Delete UR delta.
4. UR2 pair resync in IVOL.
5. Create UR delta.
6. Assign the remote command
device for the journal mirror
ID in each site.
*1: The pair status of IDKC UR1 SVOL does not become PFUS until the PDKC journal volume
becomes full. Thus, the IDKC journal volume can be expanded until the PDKC journal volume
becomes full.
*2: The IDKC or RDKC pair status does not become PFUS until the PDKC journal volume becomes
full. Thus, the IDKC or RDKC journal volume can be expanded until the PDKC journal volume
becomes full.
*3: When assigning a new journal volume, specify the journal volume whose capacity is larger than
the journal volume which is already full.
*4: For cases requiring LDEV formatting due to a 2PDEV failure, you can recover from the failure
or reduce the replacement time by restoring the UR pair according to this procedure and then
resolving the PDEV/LDEV blockade.

TRBL07-362
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-370

10. Cascade Configuration: Journal Volumes (Pool Volumes) (*1)

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC journal PVOL PSUE IVOL PSUE 1. UR1 failure suspension is
volume pool 0 (UR1 (UR1 detected.
full PVOL) SVOL) 2. UR1 swap suspend in IVOL.
IVOL PAIR RVOL PAIR 3. Failure recovery site.
1 (UR2 (UR2 4. UR1 swap resync in IVOL.
PVOL) SVOL) 5. UR1 swap suspend in PVOL.
PVOL PSUE RVOL SSUS 6. UR1 swap resync in PVOL.
2 (UR delta (HLDE) (UR delta (HOLD) 7. UR2 pair resync in IVOL.
PVOL) SVOL) 8. UR delta the delta recover.
2 PDKC journal PVOL PSUE IVOL PSUE 1. UR1 failure suspension is
volume pool 0 (UR1 (UR1 detected.
failure PVOL) SVOL) 2. UR1 swap suspend in IVOL.
IVOL PAIR RVOL PAIR 3. Failure recovery site.
1 (UR2 (UR2 4. UR1 swap resync in IVOL.
PVOL) SVOL) 5. UR1 swap suspend in PVOL.
PVOL PSUE RVOL SSUS 6. UR1 swap resync in PVOL.
2 (UR delta (HLDE) (UR delta (HOLD) 7. UR2 pair resync in IVOL.
PVOL) SVOL) 8. UR delta the delta recover.
3 IDKC journal PVOL PSUE IVOL PSUE 1. Delta resync (Pair resync the
volume pool 0 (UR1 (UR1 UR delta in PVOL).
full PVOL) SVOL) 2. Failure recovery site.
IVOL PAIR RVOL PAIR 3. UR1 pair resync in PVOL.
1 (UR2 (UR2 *: When it is for the multi
PVOL) SVOL) target operation, the
PVOL PSUS RVOL SSUS following recovery
(UR delta (HOLD) (UR delta (HOLD) procedure is not required.
PVOL) SVOL) 4. Delete UR delta and UR2.
5. Create UR2 pair.
2
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
(To be continued)

TRBL07-370
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-380

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
4 IDKC journal PVOL PSUE IVOL PSUE 1. Delta resync (Pair resync the
volume pool 0 (UR1 (UR1 UR delta in PVOL).
failure PVOL) SVOL) 2. Failure recovery site.
IVOL PSUE RVOL PSUE 3. UR1 pair resync in PVOL.
1 (UR2 (UR2 *: When it is for the multi
PVOL) SVOL) target operation, the
PVOL PSUS RVOL SSUS following recovery
(UR delta (HOLD) (UR delta (HOLD) procedure is not required.
PVOL) SVOL) 4. Delete UR delta and UR2.
5. Create UR2 pair.
2
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
5 RDKC PVOL PAIR IVOL PAIR 1. UR2 failure suspension is
journal 0 (UR1 (UR1 detected.
volume pool PVOL) SVOL) 2. Failure recovery site.
full IVOL PSUE RVOL SSUE 3. Delete UR delta.
1 (UR2 (UR2 4. UR2 pair resync in IVOL.
PVOL) SVOL) 5. Create UR delta.
PVOL PSUS RVOL PSUE 6. Assign the remote command
2 (UR delta (HOLD) (UR delta (HLDE) device for the journal mirror
PVOL) SVOL) ID in each site.
6 RDKC PVOL PAIR IVOL PAIR 1. UR2 failure suspension is
journal 0 (UR1 (UR1 detected.
volume pool PVOL) SVOL) 2. Failure recovery site.
failure IVOL PSUE RVOL SSUE 3. Delete UR delta.
1 (UR2 (UR2 4. UR2 pair resync in IVOL.
PVOL) SVOL) 5. Create UR delta.
PVOL PSUS RVOL PSUE 6. Assign the remote command
2 (UR delta (HOLD) (UR delta (HLDE) device for the journal mirror
PVOL) SVOL) ID in each site.
*1: Recovery procedures for failure in the pool of DP-VOLs registered as journal volumes are
described. The pool full status might occur when the capacity of journal volumes is defined more
than that of all unused pool volumes.

TRBL07-380
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-390

11. Cascade Configuration: LDEV

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL failure PVOL PAIR IVOL PAIR When the recovery by the LDEV
0 (UR1 (UR1 format is necessary:
PVOL) SVOL) 1. UR1 swap suspend.
IVOL PAIR RVOL PAIR 2. Delete UR1.
1 (UR2 (UR2 3. Failure recovery site.
PVOL) SVOL)
4. UR1 pair recovery.
PVOL PSUS RVOL SSUS
5. UR1 swap suspend.
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL) 6. Swap resync the UR1.
7. UR2 resync in IVOL.
8. UR delta pair recovery.
When the recovery by the LDEV
2 format is not necessary:
1. UR1 swap suspend in IVOL.
2. Failure recovery site.
3. UR1 pair recovery in IVOL.
4. UR1 swap suspend in PVOL.
5. UR1 swap resync in PVOL.
6. UR2 pair resync in IVOL.
(To be continued)

TRBL07-390
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-391

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
2 IVOL failure PVOL PSUE IVOL PSUE When the recovery by the LDEV
0 (UR1 (UR1 format is necessary:
PVOL) SVOL) 1. Delta resync (Resync the UR
IVOL PAIR (*2) RVOL PAIR (*2) delta in PVOL).
1 (UR2 (UR2 2. Delete UR1 and UR2.
PVOL) SVOL)
3. Failure recovery site.
PVOL PSUS RVOL SSUS
4. UR1 pair recovery in PVOL.
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL) (*1)
5. Delete UR delta.
6. UR2 creation using IVOL
7. Create UR delta.
8. Assign the remote command
device for the journal mirror
ID in each site.
When the recovery by the LDEV
format is not necessary:
1. Delta resync (Pair resync the
UR delta in PVOL).
2 2. Failure recovery site.
3. UR1 pair recovery in PVOL.
(*1)
*: When it is for the multi
target operation, the
following recovery
procedure is not required.
4. Delete UR delta and UR2.
5. Create UR2 pair.
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
(To be continued)

TRBL07-391
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-392

(Continued from the preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 RVOL failure PVOL PAIR IVOL PAIR When the recovery by the LDEV
0 (UR1 (UR1 format is necessary:
PVOL) SVOL) 1. Detection of UR2 in failure
IVOL PSUE RVOL PSUE suspend status
1 (UR2 (UR2 2. Delete UR2.
PVOL) SVOL)
3. Failure recovery site.
PVOL PSUS RVOL SSUS
4. UR2 pair creation using
(UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL) IVOL.
When the recovery by the LDEV
2 format is not necessary:
1. UR2 failure suspension is
detected.
2. Failure recovery site.
3. UR2 pair recovery in IVOL.
4 Remote PVOL PAIR IVOL PAIR 1. Failure recovery site.
command 0 (UR1 (UR1 2. Assign the remote command
device failure PVOL) SVOL) device for the journal mirror
IVOL PAIR RVOL PAIR ID in each site.
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: UR-UR configuration is reconfigured depending on the pair status.
*2: The pair status is PSUE during UR2 pair creation or resynchronization.

TRBL07-392
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-400

12. Cascade Configuration: Storage system

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC failure PVOL PAIR (*1) IVOL PAIR (*1) 1. UR1 swap suspend in LVOL.
(SM/CM 0 (UR1 (UR1 2. DKC recovery.
Non-Volatile) PVOL) SVOL) 3. UR1 swap resync in LVOL.
(*1) IVOL PAIR RVOL PAIR 4. UR1 swap suspend in PVOL.
1 (UR2 (UR2 5. UR1 swap resync in PVOL.
PVOL) SVOL) 6. UR2 pair resync in LVOL.
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
2 IDKC failure PVOL PAIR (*2) IVOL PAIR (*2) 1. Delta resync (Pair resync the
(SM/CM 0 (UR1 (UR1 UR delta in PVOL).
Non-Volatile) PVOL) SVOL) 2. DKC recovery.
IVOL PAIR (*2) RVOL PAIR (*2) 3. UR1 pair resync in PVOL.
1 (UR2 (UR2 *: When it is for the multi
PVOL) SVOL) target operation, the
PVOL PSUS RVOL SSUS following recovery
(UR delta (HOLD) (UR delta (HOLD) procedure is not required.
PVOL) SVOL) 4. Delete UR delta and UR2.
5. Create UR2 pair.
2
6. Create UR delta.
7. Assign the remote command
device for the journal mirror
ID in each site.
3 RDKC failure PVOL PAIR IVOL PAIR 1. DKC recovery.
(SM/CM 0 (UR1 (UR1
Non-Volatile) PVOL) SVOL)
IVOL PAIR (*3) RVOL PAIR (*3)
1 (UR2 (UR2
PVOL) SVOL)
PVOL PSUS RVOL SSUS
2 (UR delta (HOLD) (UR delta (HOLD)
PVOL) SVOL)
*1: UR pair information of PDKC (PVOL) is retained, which changes the UR1 pair state to PSUE
after PDKC (PVOL) PS is on.
*2: UR pair information of IDKC (IVOL) is retained, which changes the UR1, UR2 pair status to
PSUE after IDKC (IVOL) PS is on.
*3: If you have SOM 449 = OFF in IDKC, the UR2 pair status becomes PSUE, and UR2 resync is
required after the DKC recovery.

TRBL07-400
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-410

7.5.2 DKC Planned Shutdown Procedure of the UR-UR delta Configuration

Following is the procedure of the planned shutdown (PS OFF/ON) of the PDKC/LDKC (IDKC)/
RDKC in the UR-UR delta configuration (multi target/cascade).
Because suspending all UR pairs related to DKC to be set to PS OFF is recommended when DKC is set to
PS OFF, the procedure that complies with it is shown.
The UR delta pair status in each table indicates the pair status displayed in CCI. Also, the value in the
parentheses indicates the pair status displayed by Storage Navigator.
This planned shutdown procedure describes the planned shutdown procedure to maintain the disaster
discovery configuration.

[Link] Planned Shutdown Procedure of the PDKC

Table 7-2 Planned Shutdown Procedure of the PDKC of the UR-UR delta Configuration (Multi
Target Configuration)
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
1 Stop of host I/O Suspend I/O from host to the PDKC (switch the operation to LDKC).
to the PDKC
2 UR1 pair swap Execute UR1 pair swap suspension in the LDKC. #UR1 pair swap
suspension ↓ UR1 pair swap suspension suspension
PDKC [PS ON] LDKC [PS ON] % pairsplit -g UR1
UR1 PVOL: PSUS UR1 SVOL: SSWS -RS -IH1
UR2 PVOL: PSUS UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL07-410
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-420

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
3 Delta resync Execute the delta resync in LDKC (Swap resync the UR delta). #Delta resync
(Swap resync ↓ Delta resync % pairresync -g
the UR delta) PDKC [PS ON] LDKC [PS ON] URdelta -swaps -IH1
UR1 PVOL: PSUS UR1 SVOL: SSWS
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
4 Start of host I/O Consolidate host I/O to the LDKC.
to the LDKC
5 PDKC PS OFF Set the PDKC to PS OFF.
↓ PS OFF
PDKC [PS OFF] LDKC [PS ON]
UR1 PVOL: PSUS UR1 SVOL: SSWS
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
‒ During planned
shutdown
6 PDKC PS ON Set the PDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PSUS UR1 SVOL: SSWS
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
7 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
8 SIM check If SIMs related to the logical path blockade on the remote copy are
generated in each DKC, complete the SIMs (for VSP Gx00/Fx00, view the
SIMs and take necessary actions).
(To be continued)

TRBL07-420
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-430

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
9 UR1 pair swap Execute UR1 pair swap resync in the LDKC. #UR1 pair swap resync
resync % pairresync -g UR1
↓ UR1 pair swap resync -swaps -IH1
PDKC [PS ON] LDKC [PS ON]
UR1 SVOL: PAIR UR1 PVOL: PAIR
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

10 Stop of host I/O Suspend I/O from host to the LDKC (return the operation to PDKC).
to the PDKC
11 UR1 pair swap Execute UR1 pair swap suspension in the PDKC. #UR1 pair swap
suspension ↓ UR1 pair swap suspension suspension
PDKC [PS ON] LDKC [PS ON] % pairsplit -g UR1
UR1 SVOL: SSWS UR1 PVOL: PSUS -RS -IH0
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PSUS

RDKC [PS ON]

UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
12 Delta resync Execute the delta resync in PDKC (Swap resync the UR delta). #Delta resync
(Swap resync ↓ Delta resync % pairresync -g UR2
the UR delta) PDKC [PS ON] LDKC [PS ON] -swaps -IH1
UR1 SVOL: SSWS UR1 PVOL: PSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
13 Start of host I/O Consolidate host I/O to the PDKC.
to the PDKC
14 UR1 pair swap Execute UR1 pair swap resync in the PDKC. #UR1 pair swap resync
resync ↓ UR1 pair swap resync % pairresync -g UR1
PDKC [PS ON] LDKC [PS ON] -swaps -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL07-430
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-440

Table 7-3 Planned Shutdown Procedure of the PDKC of the UR-UR delta Configuration
(Cascade Configuration)
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC is under operation.
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
1 Stop of host I/O Suspend I/O from host to the PDKC (switch the operation to IDKC).
to the PDKC
2 UR1 pair swap Execute UR1 pair swap suspension in the IDKC. #UR1 pair swap
suspension ↓ UR1 pair swap suspension suspension
PDKC [PS ON] IDKC [PS ON] % pairsplit -g UR1
UR1 PVOL: PSUS UR1 SVOL: SSWS -RS -IH1
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
3 Start of host I/O Consolidate host I/O to the IDKC.
to the IDKC
4 PDKC PS OFF Set the PDKC to PS OFF.
↓ PS OFF
PDKC [PS OFF] IDKC [PS ON]
UR1 PVOL: PSUS UR1 SVOL: SSWS
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL07-440
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-450

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ During planned
shutdown
5 PDKC PS ON Set the PDKC to PS ON.
↓ PS ON
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PSUS UR1 SVOL: SSWS
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
6 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
7 SIM check If SIMs related to the logical path blockade on the remote copy are
generated in each DKC, complete the SIMs (for VSP Gx00/Fx00, view the
SIMs and take necessary actions).
8 UR1 pair swap Execute UR1 pair swap resync in the IDKC. #UR1 pair swap resync
resync ↓ UR1 pair swap resync % pairresync -g UR1
PDKC [PS ON] IDKC [PS ON] -swaps -IH1
UR1 SVOL: PAIR UR1 PVOL: PAIR
UR delta PVOL: SSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
9 Stop of host I/O Suspend I/O from host to the IDKC (return the operation to PDKC).
to the IDKC
10 UR1 pair swap Execute UR1 pair swap suspension in the PDKC. #UR1 pair swap
suspension ↓ UR1 pair swap suspension suspension
PDKC [PS ON] IDKC [PS ON] % pairsplit -g UR1
UR1 SVOL: SSWS UR1 PVOL: PSUS -RS -IH0
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PSUS

RDKC [PS ON]

UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL07-450
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-460

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
11 Start of host I/O Consolidate host I/O to the PDKC.
to the PDKC
12 UR1 pair swap Execute UR1 pair swap resync in the PDKC. #UR1 pair swap resync
resync ↓ UR1 pair swap resync % pairresync -g UR1
PDKC [PS ON] IDKC [PS ON] -swaps -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PSUS

RDKC [PS ON]

UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
13 UR2 pair Execute UR2 pair resync in the IDKC. #UR2 pair resync
resync ↓ UR2 pair resync % pairresync -g UR2
PDKC [PS ON] IDKC [PS ON] -IH1
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL07-460
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-470

[Link] Planned Shutdown Procedure of the LDKC

Table 7-4 Planned Shutdown Procedure of the LDKC of the UR-UR delta Configuration (Multi
Target Configuration)
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
1 UR1 pair Execute UR1 pair suspension in the PDKC. #UR1 pair suspension
suspension ↓ UR1 pair suspension % pairsplit -g UR1
PDKC [PS ON] LDKC [PS ON] -IH0
UR1 PVOL: PSUS UR1 SVOL: SSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
2 LDKC PS OFF Set the LDKC to PS OFF.
↓ PS OFF
PDKC [PS ON] LDKC [PS OFF]
UR1 PVOL: PSUS UR1 SVOL: SSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
‒ During planned
shutdown
3 LDKC PS ON Set the LDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PSUS UR1 SVOL: SSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
(To be continued)

TRBL07-470
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-480

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
5 SIM check If SIMs related to the logical path blockade on the remote copy are
generated in each DKC, complete the SIMs (for VSP Gx00/Fx00, view the
SIMs and take necessary actions).
6 UR1 pair Execute UR1 pair resync in the PDKC. #UR1 pair resync
resync ↓ UR1 pair resync % pairresync -g UR1
PDKC [PS ON] LDKC [PS ON] -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL07-480
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-490

[Link] Planned Shutdown Procedure of the IDKC

Table 7-5 Planned Shutdown Procedure of the IDKC of the UR-UR delta Configuration
(Cascade Configuration)
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC is under operation.
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
1 Delta resync Execute the delta resync in PDKC (resync the UR delta pair) #Delta resync
(resync the UR ↓ Delta resync % pairresync -g
delta pair) PDKC [PS ON] IDKC [PS ON] URdelta -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
2 UR1 pair Execute UR1 pair suspension in the IDKC. #UR1 pair suspension
suspension ↓ UR1 pair suspension % pairsplit -g UR1
PDKC [PS ON] IDKC [PS ON] -IH0
UR1 PVOL: PSUS UR1 SVOL: SSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
3 IDKC PS OFF Set the IDKC to PS OFF.
↓ PS OFF
PDKC [PS ON] IDKC [PS OFF]
UR1 PVOL: PSUS UR1 SVOL: SSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

(To be continued)

TRBL07-490
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-500

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ During planned
shutdown
4 IDKC PS ON Set the IDKC to PS ON.
↓ PS ON
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PSUS UR1 SVOL: SSUS
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
5 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
6 SIM check If SIMs related to the logical path blockade on the remote copy are
generated in each DKC, complete the SIMs (for VSP Gx00/Fx00, view the
SIMs and take necessary actions).
7 UR1 pair resync Execute UR1 pair resync in the PDKC. #UR1 pair resync
* In the case of ↓ UR1 pair resync % pairresync -g UR1
the multi target PDKC [PS ON] IDKC [PS ON] -IH0
operation, No.8 UR1 PVOL: PAIR UR1 SVOL: PAIR
through No.10 UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)
of the recovery
RDKC [PS ON]
procedure are UR2 SVOL: PAIR
not required. UR delta SVOL: SSUS (HOLD)
8 UR2 pair Delete UR2 pair in PDKC. * UR delta pair is also deleted. #UR2 pair deletion
deletion ↓ UR2 pair deletion % pairsplit -g URdelta
PDKC [PS ON] IDKC [PS ON] -S -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: SMPL UR delta PVOL: SMPL

RDKC [PS ON]

UR2 SVOL: SMPL
UR delta SVOL: SMPL

(To be continued)

TRBL07-500
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-510

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
9 UR2 pair Create UR2 pair in IDKC (between IDKC-RDKC). #UR2 pair creation
creation ↓ UR2 pair creation % paircreate -g UR2
PDKC [PS ON] IDKC [PS ON] -jp 1 -js 2 -IH1
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR

10 UR delta pair Create delta pair in PDKC (between PDKC-RDKC). #UR delta pair creation
creation (*1) ↓ UR delta pair creation % paircreate -g
PDKC [PS ON] IDKC [PS ON] URdelta -jp 0 -js 2
UR1 PVOL: PAIR UR1 SVOL: PAIR -nocsus -IH0
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

*1: Remote command device setting is released by deleting the UR pair. Therefore, the remote
command device must be assigned for the journal mirror ID in each site after creating the UR delta
pair.

TRBL07-510
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-520

[Link] Planned Shutdown Procedure of the RDKC

Table 7-6 Planned Shutdown Procedure of the RDKC of the UR-UR delta Configuration (Multi
Target Configuration)
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC is under operation.
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
1 UR2 pair Execute UR2 pair suspension in the PDKC. #UR2 pair suspension
suspension ↓ UR2 pair suspension % pairsplit -g UR2
PDKC [PS ON] LDKC [PS ON] -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PSUS UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
2 RDKC PS OFF Set the RDKC to PS OFF.
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PSUS UR delta PVOL: SSUS (HOLD)

↓ PS OFF
RDKC [PS OFF]
UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
‒ During planned
shutdown
3 RDKC PS ON Set the RDKC to PS ON.
PDKC [PS ON] LDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PSUS UR delta PVOL: SSUS (HOLD)

↓ PS ON
RDKC [PS ON]
UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
(To be continued)

TRBL07-520
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-530

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
5 SIM check If SIMs related to the logical path blockade on the remote copy are
generated in each DKC, complete the SIMs (for VSP Gx00/Fx00, view the
SIMs and take necessary actions).
6 UR2 pair Execute UR2 pair resync in the PDKC. #UR2 pair resync
resync ↓ UR2 pair resync % pairresync -g UR2
PDKC [PS ON] LDKC [PS ON] -IH0
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR2 PVOL: PAIR UR delta PVOL: SSUS (HOLD)

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL07-530
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-540

Table 7-7 Planned Shutdown Procedure of the RDKC of the UR-UR delta Configuration
(Cascade Configuration)
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC is under operation.
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)
1 UR2 pair Execute UR2 pair suspension in the IDKC. #UR2 pair suspension
suspension ↓ UR2 pair suspension % pairsplit -g UR2
PDKC [PS ON] IDKC [PS ON] -IH1
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PSUS

RDKC [PS ON]

UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
2 RDKC PS OFF Set the RDKC to PS OFF.
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PSUS

↓ PS OFF
RDKC [PS OFF]
UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
‒ During planned
shutdown
3 RDKC PS ON Set the RDKC to PS ON.
PDKC [PS ON] IDKC [PS ON]
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PSUS

↓ PS ON
RDKC [PS ON]
UR2 SVOL: SSUS
UR delta SVOL: SSUS (HOLD)
4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
(To be continued)

TRBL07-540
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL07-550

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
5 SIM check If SIMs related to the logical path blockade on the remote copy are
generated in each DKC, complete the SIMs (for VSP Gx00/Fx00, view the
SIMs and take necessary actions).
6 UR2 pair Execute UR2 pair resync in the IDKC. #UR2 pair resync
resync ↓ UR2 pair resync % pairresync -g UR2
PDKC [PS ON] IDKC [PS ON] -IH1
UR1 PVOL: PAIR UR1 SVOL: PAIR
UR delta PVOL: PSUS (HOLD) UR2 PVOL: PAIR

RDKC [PS ON]

UR2 SVOL: PAIR
UR delta SVOL: SSUS (HOLD)

TRBL07-550
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-10

8. Recovery from Thin Image/Thin Image Advanced Failure

8.1 Recovery Procedure for Thin Image/Thin Image Advanced Failure due to SM
Volatilization (SIM = 47ec00)
The procedure for recovering from a Thin Image/Thin Image Advanced failure when the SM is volatile is as
follows. (*1)

SIM = 47ec00
START

Open “Logical Device” on “Web Console” window on MPC,

and make sure that no pool volumes are blocked. If there are
blocked pool volumes, resume them by LDEV Restore.

Recover the pool.

For the Thin Image pool, see Thin Image User Guide.
For the Dynamic Provisioning pool, see “10.2 Recovery
Procedure for Pool Failure (SIM = 623xxx)”.

Are
there Thin Image/Thin No
Image Advanced pairs before the SM
volatilization? (Ask the
customer.)
Yes

Create the Thin Image/Thin Image Advanced pair again. (*2)

END

*1: Regardless of whether or not there were Thin Image/Thin Image Advanced pairs before restoration
of configuration information (New Installation (Restore Configuration)) or volatilization of SM,
“SIM = 47ec00” might be reported if either of the following pools exists in the storage system:
• Thin Image pool
• Dynamic Provisioning pool
*2: If a failure occurs after capacity expansion of one volume of a pair is successful, creating the pair
is not possible due to capacity inconsistency. Perform capacity expansion so that the capacities are
consistent, and then create the pair.

TRBL08-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-20

8.2 Recovery Procedure for Thin Image/Thin Image Advanced Failure (SIM = 4b3xyy,
7ff104)
The procedure for recovery from a failure occurs in a pair of Thin Image/Thin Image Advanced is explained
below.

SIM = 4b3xyy, 7ff104

START

Yes
SIM = 602xxx exists?

No See 8.3 Recovery Procedure for Pool Failure

(SIM = 602xxx, 604xxx, 605xxx, 606xxx) .

Yes
SIM = 62xxxx exists?

See the table in TRBL02-650 and perform

No the recovery procedure for the reported SIM
(62xxxx).

Yes
Is there a pinned track?

Recover the failure according to Procedure

No for Erasing Pinned Track ( TRBL04-230).

Yes
SSB = 9680 exists?

Check the status of the Primary Volume by

No MPC. (See MPC04-110)

No
Are all statuses normal?
1
Recover from the problem.
(TRBL08-30) Yes

Delete the pair of Thin Image/Thin Image

Advanced, and then create the pair again.
(*1)

END

*1: If a failure occurs after capacity expansion of one volume of a pair is successful, creating the pair
is not possible due to capacity inconsistency. Perform capacity expansion so that the capacities are
consistent, and then create the pair.
TRBL08-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-30

Thin Image/Thin Image Advanced Pair Error

Is there a pair
whose status is ʻPSUSʼ except Yes
for this pair, whose status is
ʻPSUEʼ? Delete the only pair whose status
is ʻPSUEʼ according to the regular
No procedure of deleting the pair.

Is deletion of the Yes

pair successful?

No

Delete all pairs with the Primary Volume or the root

volume in the tree.
[Step.1] Delete the pair whose status is not ʼPSUEʼ.
[Step.2] Delete the pair whose status is ʼPSUEʼ.

Is deletion of all Yes

pairs successful?

No
Ask the user to delete all pairs in the
snapshot tree on Command Control
Interface.

Is deletion of all Yes

pairs successful?
Check the statuses of the Primary
No Volume and Secondary Volume
(see MPC04-110).
T.S.D Call

Is the LDEV Yes

blocked?
Restore the LDEV
No (see MPC04-640).

Delete the pair of Thin Image/Thin Image

Advanced, and then create the pair again. (*1)

END

*1: If a failure occurs after capacity expansion of one volume of a pair is successful, creating the pair
is not possible due to capacity inconsistency. Perform capacity expansion so that the capacities are
consistent, and then create the pair.

TRBL08-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-40

8.3 Recovery Procedure for Pool Failure (SIM = 602xxx, 604xxx, 605xxx, 606xxx)
The procedure for recovery from a failure of a pool used by Thin Image/Thin Image Advanced is explained
below.

SIM = 602xxx, 604xxx, 605xxx, 606xxx

START

SIM = 602xxx No
exists?

Yes
Follow the flow of TRBL08-50.

SIM
= 604xxx, 605xxx or No
606xxx exists?

Yes
Follow the flow of TRBL08-60.

END

TRBL08-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-50

START

Check pool-VOL status on MPC.

Yes
Is pool-VOL Normal?

No

Restore the pool-VOL.

No
Is POOL Blockade?

Yes

Restore the POOL on Storage Navigator.

Perform the “8.7 Recovery Procedure for

Thin Image pool-VOL Failure”.

END

TRBL08-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-60

START

Does the pool

Yes
include a pool VOL whose
Accelerated Compression is
enabled?

No

Does the
Yes Enable Accelerated Compression of
pool include a parity group
the parity group that belongs to the
that can enable Accelerated
pool.
Compression?

No
Yes Is the pool status
exceeding the threshold value?

Requested to the user to perform either of the followings:

• Addition of pool-VOL (*1) No
• Deletion of all Thin Image/Thin Image Advanced pairs with
the Primary volume or root volume of an unnecessary Thin
Image/Thin Image Advanced pair in the tree.

SIM = 4b3xyy No
exist?

Yes

“Resync of the Thin Image pair” is requested

to the user. (*2)

Yes
Is it normal end?

No

“Repeated create after the Thin Image pair is

deleted” is requested to the user. (*2)

Yes
Is it normal end?

No

T.S.D. call END

TRBL08-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-70

*1: To revolve SIM, add a parity group to expand the pool.

The required physical capacity to resolve SIM is calculated by the following formula (1).

Formula (1)
Required physical capacity = (Physical usage of pool / Threshold value of pool) – Physical
capacity of pool before expansion

* Convert the percentage to a fraction for the threshold value of the pool and the reduction ratio.
For example, if the threshold value of the pool is 80 %, handle it as Threshold value of pool =
80/100 in the above formula.
*2: If a failure occurs after capacity expansion of one volume of a pair is successful, creating or
resynchronizing the pair is not possible due to capacity inconsistency. Perform capacity expansion
so that the capacities are consistent, and then create or resynchronize the pair.

TRBL08-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-80

This page is for editorial purpose only.

TRBL08-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-90

8.4 Recovery Procedure for Pool Failure (SIM = 603000)

The procedure for recovery from a failure occurs in the Pool is explained below.

SIM = 603000
START

Requested to the user to perform either of

the followings:
• Deletion of unused POOL
• Deletion of a Thin Image pair
• Deletion of unused V-VOL made with
Dynamic Provisioning or Dynamic
Tiering (*1)
• Shrink of POOL with Dynamic
Provisioning
• Shared Memory Installation

Check ʻSnapshot Estimated Manageable

Capacityʼ on Storage Navigator.

Less than 5%
Yes
of supported capacity of installed
SM?

No

END

*1: For more information about deleting V-VOLs, refer to the procedure described in the “Provisioning
Guide”.

TRBL08-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-100

8.5 Recovery Procedure for Thin Image pool-VOL ECC/LRC Error

When an ECC/LRC error occurs in a pool-VOL in the pool that Thin Image pairs use, perform the following
recovery method because an I/O cannot be issued directly from the HOST for the track concerned.
NOTE1 : In case of a Write Error, perform TRBL04-260 as well as the normal VOL and
recover it.
NOTE2 : The LDEV whose attribute is shown as pool-VOL in the Logical Devices
window of Web Console is a pool-VOL.

START

Delete Thin Image pair of the Thin Image Pool

to which the pool-VOL concerned belongs. (*1)

Can the Thin Image pair be No

deleted?
Check that the Thin Image pair that cannot
Yes be deleted is in the PSUE status, and then
try to delete the Thin Image pair of the
Thin Image pool to which the pool-VOL
concerned belongs again.

Yes Can the Thin Image pair be

deleted?

Delete Thin Image Pool to which the pool-VOL

concerned belongs. No

T.S.D. call
Perform LDEV FORMAT to the LDEV in
which a pinned track is generated.

Create the deleted Thin Image Pool again.

Create the Thin Image pair again. (*2)

END

*1: When deletion of the Thin Image pair where the cascade attribute is enabled fails, delete snapshot
data in all layers of the snapshot tree to which the Thin Image pair where the cascade attribute is
enabled belongs.
*2: If a failure occurs after capacity expansion of one volume of a pair is successful, creating the pair
is not possible due to capacity inconsistency. Perform capacity expansion so that the capacities are
consistent, and then create the pair.

TRBL08-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-110

8.6 Recovery Procedure for Thin Image/Thin Image Advanced Failure (SIM = 670000)
The procedure to recovery from a Thin Image/Thin Image Advanced failure is explained below.

SIM = 670000
START

Ask users to perform the following operations until the condition below is
satisfied: the number of the remaining cache management devices ≥ y.
• Delete unnecessary volumes.
• Delete all Thin Image/Thin Image Advanced pairs with the Primary volume
of an unnecessary Thin Image/Thin Image Advanced pair.
• Delete all Thin Image/Thin Image Advanced pairs related to the root volume
in the tree.
y: 2,048 for VSP G130.
4,096 for VSP G350, G370, G700, G900, VSP F350, F370, F700, F900,
VSP E590, E790, E990, and VSP E1090.

Yes
SIM = 602xxx exists?

“8.3 Recovery Procedure for Pool Failure

No (SIM = 602xxx, 604xxx, 605xxx, 606xxx)”
(See TRBL08-40)

SIM = 4b3xyy, or Yes

7ff104 exists?
“8.2 Recovery Procedure for Thin Image/
No Thin Image Advanced Failure (SIM =
4b3xyy, 7ff104)” (See TRBL08-20)

Yes
SIM = 62xxxx exists?

See the table in TRBL02-650 and perform

No
the recovery procedure for the reported SIM
(62xxxx).

END

TRBL08-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.7.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-120

8.7 Recovery Procedure for Thin Image pool-VOL Failure

The procedure for recovery from a failure occurs in a pool-VOL of Thin Image is explained below.
For the Thin Image pair status check, pool status check, and pool operation in the following recovery
procedure, ask the customer to do them.

START

Delete Thin Image pair of the Thin Image Pool

to which the pool-VOL concerned belongs. (*1)

Can the Thin Image pair be No

deleted?
Check that the Thin Image pair that cannot
Yes be deleted is in the PSUE status, and then
try to delete the Thin Image pair of the
Thin Image pool to which the pool-VOL
concerned belongs again.

Yes Can the Thin Image pair be

deleted?

Delete Thin Image Pool to which the pool-VOL

concerned belongs. No

T.S.D. call
Perform LDEV FORMAT to the blockade
LDEV.

Create the deleted Thin Image Pool again.

Create the Thin Image pair again. (*2)

END

*1: When deletion of the Thin Image pair where the cascade attribute is enabled fails, delete snapshot
data in all layers of the snapshot tree to which the Thin Image pair where the cascade attribute is
enabled belongs.
*2: If a failure occurs after capacity expansion of one volume of a pair is successful, creating the pair
is not possible due to capacity inconsistency. Perform capacity expansion so that the capacities are
consistent, and then create the pair.

TRBL08-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL08-130

8.8 Recovery Procedure for Thin Image I/O Performance Degradation Alert (SIM = 670100)

SIM = 670100
START

Ask the customer to reduce the amount of

data to be written to Thin Image pairs from
the host.

END

TRBL08-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL09-10

9. Recovery from Volume Migration Failure

When it lapses into the state where a system does not expect, volume move processing of Volume Migration
sometimes carries out an unusual end. In this case, the state of Source Volume and Target Volume which was
during movement is not changing from the state before movement. So, there is no necessity of daring carry
out recovery to resume VOL move processing. Please resume processing after checking states, such as a
hard part, with reference to SSB/SIM.
Please carry out recovery procedure with reference to the following flowchart.

Table 9-1 Volume Migration SIM [Link]

SIM REF. CODE meaning comment
47fyxx Volume Migration abnormal end yxx: The lower 12 bits of Target Volume #.
7ff106 y = The lower 4 bits of CU#
xx = LDEV#

TRBL09-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL09-20

9.1 Recovery Procedure for Volume Migration Failure

Recovery for pair suspend

Is there a remaining Yes

migration plan (Volume Migration
(Request to user)
pair)?
Delete the remaining migration
plan (Volume Migration pair).
No

Is there a hardware Yes Perform the recovery procedure

failure SIM? of the SIM.

No

SSB = 21E3 Yes

exists?
Source Volume Error
No 2
(TRBL09-30)
or
SSB = 21E4 Yes Target Volume Error
4 3
exists? (TRBL09-30)
Other Error
No (TRBL09-40)

SSB = 21E7 Yes

4
exists?
Other Error
No (TRBL09-40)

SSB = 21E6 Yes

5
exists?
PIN exist
No (TRBL09-50)

1
(TRBL09-21)

TRBL09-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL09-21

(Request to user)
Yes This code means that the load on the storage
SSB = 211B
system is high.
exists?
Lower the load, and then resume operations
No for Volume Migration.

SSB = 21E1 Yes

4
exists?
Other Error
No (TRBL09-40)

SSB = 21E2 Yes

4
exists?
Other Error
No (TRBL09-40)

T.S.D. Call

TRBL09-21
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL09-30

Source Volume Error

2

Check Source Volume status

(See MPC04-110)

Source Volume is Yes

Normal?

No
Restore the Source Volume status

(Request to user)
Run the failed Volume Migration
operation again

Target Volume Error

3

Check Target Volume status

(See MPC04-110)

Target Volume is Yes

Normal?

No
Restore the Target Volume status

(Request to user)
Run the failed Volume Migration
operation again

TRBL09-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL09-40

Other Error
4

Check status

Yes
ALL Normal?

No
Restore the Failure Part

(Request to user)
Run the failed Volume Migration
operation again

TRBL09-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL09-50

PIN exist
5

Check PIN

No
Does PIN exist?

Yes
Recover the PIN slot

(Request to user)
Run the failed Volume Migration
operation again

TRBL09-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-10

10. Failure recovery of Dynamic Provisioning

10.1 Recovery Procedure for pool-VOL Blockade (When Two (Three in RAID6) or More
Are Blocked in the RAID Gr the pool-VOL Belongs)
Dynamic Provisioning conditions become as shown in the table below.
In some cases, data might not be able to be recovered.
When LDEVs are blocked due to multiple drive blockades (SIM = ef8xxx, ef9xxx, db8xxx, db9xxx, dbaxxx,
dbbxxx, dfaxxx, dfbxxx) and you try to recover data, see “3.13 Recovery Procedure for LDEV Blockade (SIM
= ef8xxx, ef9xxx, db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx, dfbxxx, 46cxxx, 46dxxx)”.
Item Status
DP-VOL status Normal (*1)
POOL status Warning
pool-VOL status Normal + Blocked (only LDEV is blocked in RAID Gr where
two or more (three or more in case of RAID6) are blocked)
I/O access Partially possible
(Access to normal pool-VOL is possible.)
Association with DP-VOL and POOL Yes
*1: When the Capacity Saving is enabled, the DP-VOL status is either Normal or Blocked.

TRBL10-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-20

Recovery method
Perform the recovery processing in the following flow.

Recovery processing at the time of pool-VOL blockade

START Frames surrounding operations show

that the operations are to be performed
by the customer at your request.
Is the pool type
of the pool to which the blocked pool- Yes
1
VOL belongs the DP (data direct
(TRBL10-30)
mapping) pool?
No

Does the pool contain LDEVs with Yes

2
Capacity Saving enabled?
(TRBL10-40)

No

In the Web console main window, select [Logical Devices] from the [Storage
Systems] tree, check all DP-VOLs associated with the pool. (*1)

Please confirm whether DP-VOL to which the Protect attribute of DRU

is added exists. (*14)

When DP-VOL to which the Protect attribute has been added exists,
release the protection attribute of the DP-VOLs using the Data Retention
window of Storage Navigator. (*15)

If necessary, back up all DP-VOLs associated with the pool to which the
pool-VOL belongs.

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage, Volume *: Delete root volumes of Thin Image/
Migration, Thin Image, Thin Image Advanced and global-active device that Thin Image Advanced pairs that
use the DP-VOLs associated with the pool and all Thin Image/Thin Image use the pool and all pairs in the tree
Advanced pairs (the root volume and the pairs in the tree (*)) that use the of the root volume. To identify the
pool. root volumes of Thin Image/Thin
Image Advanced pairs that use the
Block all DP-VOLs associated with the POOL. pool, specify the pool name (ID)
for filtering in the TI Root Volume
tab in the “Local Replication”
Block the failed drive (*10), and then replace it with a new drive.
window of Web Console.

1A
(TRBL10-21)

TRBL10-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-21

1A

Format all of the blocked pool-VOLs in the POOL. (*2) (*5) (*11)

Set System Option Mode 867 to ON.

Perform LDEV FORMAT for all DP-VOLs blocked. (*1)

Set System Option Mode 867 to OFF. (*4)

If there is any backup, restore the data from the backup. (*3)

For the DP-VOLs associated with the pool, create the pairs of TrueCopy,
Universal Replicator, ShadowImage, Volume Migration, Thin Image, Thin
Image Advanced and global-active device and the Thin Image/Thin Image
Advanced pairs that use the pool again. (*12)

END

TRBL10-21
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-30

Please confirm whether DP-VOL to which the Protect

attribute of DRU is added exists. (*14)

When DP-VOL to which the Protect attribute has been

added exists, release the protection attribute of the DP-
VOLs using the Data Retention window of Storage
Navigator. (*15)

Delete the pairs of TrueCopy, Universal Replicator,

ShadowImage, Volume Migration, Thin Image, Thin Image
Advanced and global-active device that use all the DP-VOLs
related to the POOL.

Stop the host I/O for the DP-VOL whose data direct mapping
attribute is enabled.

Delete path definition of all the DP-VOLs whose data direct

mapping attribute is enabled. (*8)

Block all the DP-VOLs whose data direct mapping attribute

is enabled.

Disconnect the external volumes from all the pool-VOLs

whose pool type is the DP (data direct mapping) pool.

Delete all the DP-VOLs whose data direct mapping attribute

is enabled.

Reconnect the external volumes to all the pool-VOLs whose

pool type is the DP (data direct mapping) pool.

Perform the LDEV formatting for the blocked pool-VOL in

the POOL that the LDEV belongs to. (*2) (*5)

Re-create the DP-VOL that was deleted above and perform

path definition again. (*9)

Re-create pairs of TrueCopy, Universal Replicator,

ShadowImage, Volume Migration, Thin Image, Thin Image
Advanced and global-active device for all the DP-VOLs
related to the POOL. (*12)

END

TRBL10-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-40

*: Delete root volumes of Thin Image/Thin Image Advanced

pairs that use the pool and all pairs in the tree of the root
2 volume. To identify the root volumes of Thin Image/Thin
Image Advanced pairs that use the pool, specify the pool
name (ID) for filtering in the TI Root Volume tab in the “Local
Replication” window of Web Console.

Are there deduplication system data No

3
volumes in the pool?
(TRBL10-50)

Yes
In the Web Console main window, select [Logical Devices] from the [Storage Systems] tree, check all
DP-VOLs including the deduplication system data volumes associated with the pool.

Please confirm whether DP-VOL to which the Protect attribute of DRU is added exists.
(*14)

When DP-VOL to which the Protect attribute has been added exists, release the protection
attribute of the DP-VOLs using the Data Retention window of Storage Navigator. (*15)

If necessary, back up all DP-VOLs, excluding deduplication system data volumes, that are associated
with the pool to which the pool-VOL belongs.

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage, Volume Migration, Thin Image, Thin
Image Advanced and global-active device that use the DP-VOLs associated with the pool and all Thin
Image/Thin Image Advanced pairs (the root volume and the pairs in the tree (*)) that use the pool.

Block all DP-VOLs except deduplication system data volumes associated with the pool.

Block all deduplication system data volumes associated with the pool.

Initialize all virtual volumes whose [Deduplication Data] function is [Enabled] in the pool. (In the
[Initialize Duplicated Data] window, click [Apply]. (*7))

Block deduplication system data volumes (fingerprint) associated with the pool.

Block the failed drive (*10), and then replace it with a new drive.

2A
(TRBL10-41)

TRBL10-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-41

2A

Perform the LDEV format on blocked pool-VOLs in the pool to which the pool-VOL belongs. (*5) (*6) (*11)

Initialize all virtual volumes whose [Deduplication Data] function is [Enabled] in the pool. (In the
[Initialize Duplicated Data] window, click [Apply]. (*7))

Set the System Option Mode 1115 to ON. If the System Option Mode 1115 is already set to ON, this
operation is not required. (*13)

Specify all the blocked deduplication system data volumes (data store) in the pool, and then perform the
LDEV format.

Perform the LDEV format on all DP-VOLs except the deduplication system data volumes.

Set the System Option Mode 1115 to OFF. If the mode is not set to ON in this maintenance work, this
operation is not required. (*13)

Perform “20.7 Recovery Procedure When the Compression Acceleration Settings for
Deduplication System Data Volumes Are Invalid after Duplicated Data Initialization”.

If there is any backup, restore the data from the backup.

For the DP-VOLs associated with the pool, create the pairs of TrueCopy, Universal Replicator,
ShadowImage, Volume Migration, Thin Image, Thin Image Advanced and global-active device and the
Thin Image/Thin Image Advanced pairs that use the pool again. (*12)

END

TRBL10-41
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-50

In the Web Console main window, select [Logical Device] from the
[Storage System] tree, check all DP-VOLs associated with the pool.

Please confirm whether DP-VOL to which the Protect attribute of

DRU is added exists. (*14)

When DP-VOL to which the Protect attribute has been added exists,
release the protection attribute of the DP-VOLs using the Data
Retention window of Storage Navigator. (*15)

If necessary, back up all DP-VOLs associated with the pool to which

the pool-VOL belongs.

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage,

Volume Migration, Thin Image, Thin Image Advanced and global-active
device that use the DP-VOLs associated with the pool and all Thin
Image/Thin Image Advanced pairs (the root volume and the pairs in the
tree (*)) that use the pool.

Block all DP-VOLs associated with the pool.

Block the failed drive (*10), and then replace it with a new drive.

Perform the LDEV format on blocked pool-VOLs in the pool to which

the pool-VOL belongs. (*5) (*6) (*11)

Set the System Option Mode 1115 to ON. If the System Option Mode
1115 is already set to ON, this operation is not required. (*13)

Perform the LDEV format on all DP-VOLs.

Set the System Option Mode 1115 to OFF. If the mode is not set to ON
in this maintenance work, this operation is not required. (*13)

If there is any backup, restore the data from the backup.

For the DP-VOLs associated with the pool, create the pairs of TrueCopy,
Universal Replicator, ShadowImage, Volume Migration, Thin Image, Thin
Image Advanced and global-active device and the Thin Image/Thin Image
Advanced pairs that use the pool again. (*12)

END

*: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in the tree of the
root volume. To identify the root volumes of Thin Image/Thin Image Advanced pairs that use the pool, specify
the pool name (ID) for filtering in the TI Root Volume tab in the “Local Replication” window of Web Console.

TRBL10-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-60

*1: Please specify the following two conditions for the filter to display all DP-VOL related to
concerned POOL.
• Please input the concerned pool name (ID) specifying the pool name (ID) for conditional
expression.
• Please select ʻDPʼ specifying the provisioning type for conditional expression.
Please see “System Administrator Guide” about the operating instruction of the filter.
*2: Please specify the following two conditions for the filter to display pool-VOL in POOL that has
been blockaded.
• Please input the concerned pool name (ID) specifying the pool name (ID) for conditional
expression.
• Please select pool-VOL specifying the attribute for conditional expression. Please see “Hitachi
Command Suite User Guide” or “System Administrator Guide” about the operating instruction of
the filter.
*3: Please be careful when restoring from backup as restorations from a VOL can be large contain both
consumed and unconsumed areas and you will need to perform (1) and (2):
(1) Recover the data from the backup.
(2) Reclaim Zero Pages processing.
Therefore you need to perform (1) and (2) each time you restore a whole DP-VOL from a backup.
If you restore data from a backup in the unit of file, you do not need to do “zero page reclaim”
because only consumed area will be restored from the backup.
*4: Turn off System Option Mode 867 only when it is turned on in this recovery procedure. If it has
already been turned on, do not turn it off.
*5: When FMD (NFHAx-QxxxSS) is included in the RAID group to which the pool VOLs belong,
perform the parity group format instead of the LDEV format. (see MAINTENANCE PC SECTION
“[Link] Formatting Parity Group”)
*6: You donʼt have to perform LDEV format on pool-VOLs which have already been recovered by
other operations.
*7: For Command Control Interface, use the [raidcom initialize pool] command.
*8: If the firmware version is earlier than 88-02-01-x0/xx and the DP-VOLs are attached to host
groups/iSCSI targets created automatically through Hitachi Storage Advisor Embedded (HSAE)
(Host Group Name/iSCSI Target Alias starting with “[AutoConfig]”), perform the procedure
through HSAE. For the detailed procedure, see Hitachi Storage Advisor Embedded Guide
“Detaching volumes from a server”. To start HSAE, specify the URL in the Web browser (see the
table in “2.7.3 Starting the Maintenance Utility Window by Specifying IP Address of CTL” in
MAINTENANCE PC SECTION).
*9: To define LU paths for host groups/iSCSI targets created automatically through Hitachi Storage
Advisor Embedded (HSAE) (Host Group Name/iSCSI Target Alias starting with “[AutoConfig]”)
when the firmware version is earlier than 88-02-01-x0/xx, perform the procedure through HSAE.
For the detailed procedure, see Hitachi Storage Advisor Embedded Guide “Attaching volumes
to servers by selecting servers”. To start HSAE, specify the URL in the Web browser (see the
table in “2.7.3 Starting the Maintenance Utility Window by Specifying IP Address of CTL” in
MAINTENANCE PC SECTION).

TRBL10-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-61

*10: If multiple drives whose states are “Failed” exist in the same parity group, you need to forcibly
block the drives and replace them.
When performing the drive replacement operation with Maintenance Utility, select the checkbox
of “Forcibly run without safety checks” in the “Block Drives” window. This checkbox is displayed
only when Maintenance Utility is started from the “Web Console” window or the “MPC” window.
To check the checkbox, start Maintenance Utility from the “Web Console” window or the “MPC”
window.
*11: If you perform the LDEV formatting on the blocked pool-VOLs with Storage Navigator, an alert
message telling that the target volumes for the formatting include pool-VOLs might appear.
That is not an error message but a message encouraging you to perform the LDEV formatting on
the DP-VOLs after completing the formatting on the pool-VOLs.
Perform the LDEV formatting on the DP-VOLs according to the workflow.
*12: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.
*13: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.
*14: Please specify the following condition for the filter using Virtual Volumes tab of Pools: Volume
tabs to display DP-VOL to which the Protect attribute is added in all DP-VOL related to concerned
POOL. (Please make Access Attribute column visible if it is hidden.)
• Please input “protect” specifying the access attribute for conditional expression.
See “System Administrator Guide” for details.
*15: See “Provisioning Guide for Open Systems”.

TRBL10-61
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-70

10.2 Recovery Procedure for Pool Failure (SIM = 623xxx)

The recovery procedure for the failure of the pool used in the Dynamic Provisioning is shown here.

START

Is the POOL No
blockaded?

Yes
In CCI (Command Control Interface) or Web Console,
check the number of DP-VOLs.
In CCI: Execute the “raidcom get pool” command.
In Web Console: Check Number of V-VOLs in the
“Pools” window.

Is the
pool with no DP-VOL Yes
associated with the pool?
(※) In CCI (Command Control Interface) or Web Console,
No delete the target pool.
In CCI: Execute the “raidcom delete pool” command
to delete the target pool.
In Web Console: In the Pools table, select the target
pool, then in the “Delete Pools” window, delete it.

Is the pool deletion No

complete?

Yes
1
(TRBL10-80) END T.S.D. call

※ In CCI: Confirm that SSCNT = 0 is output as a result of the command execution.

In Web Console: Confirm that Number of V-VOLs is 0.

TRBL10-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-80

NOTICE: Only in an unusual case such as cache volatilization in both clusters, perform
the procedures described on this page and later. Do not perform the following
procedures unless the Technical Support Division (T.S.D.) instructs you to do so. If
you perform the following procedures without permission, data in the DP-VOL might
be lost.

Is the parity
group including the pool VOL
Yes
displayed when [Copy...] in the Maintenance
window is opened? (See MPC05-
1050) Suspend the copy process being
executed. (*1)
No

In the Logical Devices window of Web

Console, check the pool-VOL status.

Are the pool Yes

VOLs normal?

No
Restore all pool-VOLs in a normal way.
(See MPC04-640) (*4)

Are pool-VOLs Yes

restored successfully? (*2)

No
Restore all pool-VOLs forcibly.
(See MPC04-680) (*3) (*4) (*5)

2
(TRBL10-81)
*1: In Maintenance Utility, click the [Drives] tab, select the target drive, and then click the [Stop
Copy] button.
*2: If the Shared Memory volatilizes, the normal restoration inevitably fails because the data cannot be
ensured.
*3: Input of the one-time password is required for the forcible restoration.
*4: Do not perform the procedure for restoring the DP-VOLs because performing the procedure for
restoring the pool restores the DP-VOLs.
If you perform the procedure for restoring the DP-VOLs here, the recovery procedure of the DP-
VOLs will fail.
*5: If volatilization of Shared Memory, which causes volatilization of encryption keys, occurs, pool-
VOLs created from encrypted parity groups cannot be restored even by performing the forcible
LDEV restoration operation. Follow the instructions by the Technical Support Division.
TRBL10-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.10.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-81

Yes
Are pools normal?

No T.S.D. call

Are LDEVs No
with Capacity Saving enabled
defined?

Yes

Is the DKC
firmware less than 93- No
03-22-x0/01 or 88-07-02-
x0/00?

Yes
Update the DKC firmware for a
version 93-03-22-x0/01 or 88-07-02-
x0/00 or later. (See FIRM03-10)

7
(TRBL10-82)

TRBL10-81
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-82

Restore all pools. (*1) (*2) (*6)

Yes
Are pools normal? (*3)

No

Did the
Technical Support
Division already check the number No
of SSB = afff reported for the pools that failed
to be recovered and the detailed
byte information of each
SSB = afff?

Yes
Enable System Option Mode 982 (forcible
pool restoration mode).
(See MPC05-880) (*4)

Restore all pools. (*2) (*6)

Disable System Option Mode 982 (forcible

pool restoration mode). (See MPC05-880)
(*5)

No
Are pools normal?

Yes

T.S.D. call
3 (TRBL10-90)

*1: This operation restores the information indicating the location where the DP-VOL data that was
lost due to the Shared Memory volatilization is stored, from the system pool VOL.
*2: You can restore pools by using Web Console or CCI (Command Control Interface).
However, when SIM = 3073xx occurs and MPs are blocked, you cannot use CCI to restore pools.
• Web Console: Use the Pools window to restore pools (see the Provisioning Guide).
• CCI: Execute the following command to restore pools (see the Command Control Interface
Command Reference):
raidcom modify pool -pool pool# -status nml
*3: • If you power on the storage system after a planned shutdown, pools can be restored successfully.
• If you power on the storage system after a power outage, pools cannot be restored.
• After Initialize Pools (MPC04-780), pools cannot be restored.
*4: Ask T.S.D to tell you the password.
*5: Data in the DP-VOLs with Capacity Saving enabled might not be read due to occurrence of SIM =
680001. In such a case, perform 20.1 Recovery Procedure for dedupe and compression Operation
Error (SIM = 680001) .
TRBL10-82
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-83

*6: Recovering multiple pools with large capacity at a time might cause time-out. Therefore, perform
pool recovery for one pool by one, confirm task completion, and then perform the next pool
recovery operation. If Web Console is used, task completion of the pool recovery can be confirmed
in the Tasks window. (Select [Tasks] from the [Storage Systems] tree, display the [Tasks] tab,
and confirm that [Status] of the performed pool recovery task is [Completed].) To use Command
Control Interface for task completion confirmation, run raidcom get command_status. (Confirm
that the raidcom get command_status command ends.)

TRBL10-83
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-90

Is used pool
capacity larger than 0? (Check No
the “Pools” window of Web
Console.)
T.S.D. call
Yes

Is the Copy History

log about the parity group to which the Yes
pool-VOL belongs output, after the output of SIM =
623xxx until this step? (See MPC04-
410)
Locate where the copying destination
PDEV is mounted by ʻContent-Copy
No Historyʼ, and execute dummy-replacement
of the copying destination PDEV.

Yes Replacement
normally ends?

No Replace PDEV with the service

part.

Is LDEV No
blockaded?

Yes
The recovery procedure from LDEV
blockade. (*1) (See to TRBL03-300)

Yes LDEV is
recovered?

No

4 T.S.D. call
(TRBL10-91)

*1: In the flowchart of the recovery procedure on the reference page, be sure to choose “B” for the
action to be taken. If you choose “A”, data recovery will fail.

TRBL10-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-91

Frames surrounding operations show

4
that the operations are to be performed
by the customer at your request.
Are there
one or more DP-VOLs
(*3) for which [Capacity Saving] is set to
No
“Compression” or “Deduplication and Compression”, and/
or one or more deduplication system data
volumes (finger print, data
store)? (*4)

Yes

Is any of the
following true?
・There are one or more DP-VOLs
for which [Capacity Saving Status] is set to
No
“failed” (*6).
・You came here from “Restore Configuration
Procedure” (FIRM05-80).
・There are data reduction 6
shared volumes.
(TRBL10-93)

Yes

Get backups of all the DP-VOLs (*3) for which [Capacity Saving] is
set to “Compression” or “Deduplication and Compression”. (*5)

Delete all pairs of TrueCopy, Universal Replicator,

ShadowImage, Volume Migration and global-active device that
use the DP-VOLs (*3) for which [Capacity Saving] is set to
“Compression” or “Deduplication and Compression” and all Thin
Image/Thin Image Advanced pairs (the root volume and the pairs
in the tree (*1)) that use the pool.

Block all the DP-VOLs (*3) for which [Capacity Saving] is set
to “Compression” or “Deduplication and Compression”.

Block the deduplication system data volumes (finger print, data

store) (*4). (*7)

Initialize all virtual volumes whose deduplication data function

is enabled. (*2) (*7)

5
(TRBL10-92)
TRBL10-91
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-91A

*1: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in
the tree of the root volume. To identify the root volumes of Thin Image/Thin Image Advanced
pairs that use the pool, specify the pool name (ID) for filtering in the TI Root Volume tab in the
“Local Replication” window of Web Console.
*2: For Command Control Interface, use the “raidcom initialize pool” command.
Specify “initialize_deduplication” for the -operation option.
For Web Console, use the [Initialize Duplicated Data] window. For details, see the “Provisioning
Guide”.
*3: You can check them in the [Capacity Saving] column in the “Logical Devices” window of Web
Console.
*4: You can check them in the [Attribute] column in the “Logical Devices” window of Web Console.
*5: Data in the DP-VOLs might not be read due to occurrence of SIM = 680001.
*6: You can check them in the [Capacity Saving status] column in the “Logical Devices” window of
Web Console.
*7: If there is not a deduplication system data volume, the operation is not required.

TRBL10-91A
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-92

Set the System Option Mode 1115 to ON. If the System Option
Mode 1115 is already set to ON, this operation is not required. (*3)

Specify all the blocked deduplication system data volumes (data

store), and then perform the LDEV format. (*4)

Perform the LDEV format on all the DP-VOLs (*2) for which
[Capacity Saving] is set to “Compression” or “Deduplication and
Compression”. (*1)

Set the System Option Mode 1115 to OFF. If the mode is not set to
ON in this maintenance work, this operation is not required. (*3)

Perform “20.7 Recovery Procedure When the Compression

Acceleration Settings for Deduplication System Data Volumes Are
Invalid after Duplicated Data Initialization”.

6
(TRBL10-93)

*1: Do not perform the procedure for LDEV recovery.

*2: You can check them in the [Capacity Saving] column in the “Logical Devices” window of Web
Console.
*3: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.
*4: If there is not a deduplication system data volume, the operation is not required.

TRBL10-92
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-93

6
Frames surrounding operations show
that the operations are to be performed
by the customer at your request.
If you suspend the copy process in TRBL10-80, perform the
copy process again. (*1)

Perform Auto Dump (dump type = Normal) to collect dumps (see

(MPC05-50)).
Then, send the dumps to T.S.D. and go to the next step right
away. You do not have to wait for the results of dump check by
T.S.D.

Ask the customer or SE to perform the following:

• Restoring the DP-VOL data from the backup
• Checking the data closely

For the DP-VOLs and LDEVs, recreate TrueCopy, Universal

Replicator, ShadowImage, Volume Migration and global-active
device pairs, and Thin Image/Thin Image Advanced pairs that
use the pool. (*2)

Perform Auto Dump (dump type = Normal) to collect dumps (see

(MPC05-50)).
Then, send the dumps to T.S.D. and ask them to perform the
health check.

Perform the parity consistency check by setting the parameters as

follows: (See MPC04-820)
• [Auto Correct]=Disable
• [Number of Errors to Stop Process]=16

Is the parity consistency Yes

check unsuccessful?

Perform Auto Dump (dump

No
type = Normal) to collect dumps
(see (MPC05-50)) and contact
END T.S.D.

TRBL10-93
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-94

*1: Set the mode to [Modify Mode], open the Maintenance window, and then click the [Correction
Copy] button in the HDD detail information view (see MPC09-120).
*2: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.

TRBL10-94
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-100

10.3 Recovery Procedure for Pool Failure (SIM = 624000)

The recovery procedure for the failure of the pool used in the Dynamic Provisioning, Thin Image or Thin
Image Advanced is shown here.

START

Requested to the user to perform either of the

followings:
• Deletion of unused POOL
• Deletion of a Thin Image/Thin Image Advanced pair
• Deletion of unused V-VOL made with Dynamic
Provisioning (*1)
• Shrink of POOL with Dynamic Provisioning
• Shared Memory Installation

No
SIM = 4b3xyy exist?

Yes

“Resync of the Snapshot pair/Thin Image

pair” is requested to the user.

Yes
Is it normal end?

No

“Repeated create after the Snapshot pair/

Thin Image pair is deleted” is requested to
the user.

Yes
Is it normal end?

No

T.S.D. call END

*1: For more information about deleting V-VOLs, refer to the procedure described in the “Provisioning
Guide”.

TRBL10-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-110

10.4 Recovery Procedure for Pool Failure (SIM = 62b000)

The recovery procedure for the failure of the pool used in the Dynamic Provisioning is shown here.

START

The system notifies users that the threshold is

exceeded, and asks to increase free space of
the pool.

END

TRBL10-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-120

10.5 Recovery Procedure for pool-VOL Blockade (SIM = 627xxx)

The recovery procedure for blocked pool-VOLs used in Dynamic Provisioning is shown here. (*5)

START

Is SIM = 623xxx also Yes

reported?
Recovery Procedure for Pool Failure
No
(SIM = 623xxx). (See TRBL10-70)

Is only
“External” displayed in END
the [Provisioning Type] column of No
the blocked pool-VOLs in the Logical
Devices window of Web
Console? Is only
“Basic” displayed in the
Yes [Provisioning Type] column of the No
blocked pool-VOLs in the Logical
Are the external Yes Devices window of Web
storage volumes in the Disconnect 1 Console?
status? T.S.D. call
(TRBL10-130)
Yes
No
Recovery Procedure for LDEV Blocking.
Recover the external storage system.
(See TRBL03-300)
(See TRBL11-60)

System
Option Mode 803 or No
“Protect V-VOLs when I/O fails to
Blocked Pool VOL” is
ON? (*3)
Yes (Request to user)
Please confirm whether DP-VOL to which the
Protect attribute of DRU is added exists. (*1)
(Request to user)
When DP-VOL to which the Protect attribute
has been added exists, release the protection
attribute of the DP-VOLs using the “Data
Retention” window of Storage Navigator.
(See the Provisioning Guide.)

END

TRBL10-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-130

Is the data direct mapping No

attribute for the external storage volumes
enabled? (*4)

Yes

Is the migration of the external No

storage volume data complete?

Yes
Delete the DP-VOLs whose data direct mapping Reconnect the external volumes.
attributes are created from the blocked pool- VOLs. (See the “Hitachi Universal Volume
Manager User Guide”.)
Reconnect the external volumes associated with the
deleted DP-VOLs.

Delete the external volumes associated with the

deleted DP-VOLs from the pool.

END

*1: Please specify the following condition for the filter using Virtual Volumes tab of Pools: Volume
tabs to display DP-VOL to which the Protect attribute is added in all DP-VOL related to concerned
POOL. (Please make Access Attribute column visible if it is hidden.)
• Please input “protect” specifying the access attribute for conditional expression.
See “System Administrator Guide” for details.
*2: (Blank)
*3: Check V-VOL protection function settings when the pool-VOL is blocked in [Protect V-VOLs
when I/O fails to Blocked Pool VOL] of the “Pools” window, or the window displayed after
selecting a pool in the “Pools” window of Storage Navigator.
[Yes] indicates that the V-VOL protection function is set to ON.
*4: SIM = 627xxx (“xxx” is a pool number) might be output if a connection to the external volume
group of the migration destination storage system is disconnected.
*5: Performing the firmware update when there are blocked pool-VOLs causes SIM = 627xxx (xxx is
pool#) to be output. If restoration of the blocked pool-VOLs is not necessary, you do not need to
perform Recovery Procedure for pool-VOL Blockade.

TRBL10-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-140

10.6 Procedure for Releasing Protect Attribute of Data Retention Utility (SIM = 628000)
In the pool for which the DP-VOL protection function is enabled, the Protect attribute of Data Retention
Utility might be set for DP-VOLs when the following errors occur:
• The pool-VOL is blocked. (SIM = 627xxx)
• The pool is full. (SIM = 62axxx)
The following is the procedure for releasing the Protect attribute of Data Retention Utility which is set for
DP-VOLs of Dynamic Provisioning, Dynamic Tiering, or active flash.

START

Is SIM = 627xxx also Yes

reported?
Recovery Procedure for pool-VOL Blockade
No (SIM = 627xxx). (See TRBL10-120)

END
Is SIM = 62axxx also Yes
reported?
(Request to user)
No See the Provisioning Guide to perform recovery
procedure for the SIM.
T.S.D. call
(Request to user)
Please confirm whether DP-VOL to which the
Protect attribute of DRU is added exists. (*1)

(Request to user)
When DP-VOL to which the Protect attribute
has been added exists, release the protection
attribute of the DP-VOLs using the Data
Retention window of Storage Navigator.
(See the Provisioning Guide)

END

*1: Please specify the following condition for the filter using Virtual Volumes tab of Pools: Volume
tabs to display DP-VOL to which the Protect attribute is added in all DP-VOL related to concerned
POOL. (Please make Access Attribute column visible if it is hidden.)
• Please input “protect” specifying the access attribute for conditional expression.
See “System Administrator Guide” for details.

TRBL10-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-150

10.7 Deleting Procedure for Pool at the time of pool-VOL Blockade (When External
Volume the pool-VOL Belongs Is Removed)
Recovery method
Perform the recovery by the following flow.

START

Is the
pool type of the pool to No
be deleted the DP (data direct
mapping) pool?

Yes
Set System Option Mode 1083 to ON.

Delete all DP-VOLs (*1) associated with Delete all DP-VOLs (*1) associated with
the pool you want to delete and all Thin the pool you want to delete and all Thin
Image pairs (the root volume and the pairs Image/Thin Image Advanced pairs (the root
in the tree (*2)) that use the pool you want volume and the pairs in the tree (*2)) that
to delete. use the pool you want to delete.

Set System Option Mode 1083 to OFF.

Delete pool.

Was theEND
pool able to No
be deleted?

Yes

END T.S.D. call

*1: For more information about deleting V-VOLs, refer to the procedure described in the “Provisioning
Guide”.
*2: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in
the tree of the root volume. To identify the root volumes of Thin Image/Thin Image Advanced
pairs that use the pool, specify the pool name (ID) for filtering in the TI Root Volume tab in the
“Local Replication” window of Web Console.

TRBL10-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-160

This page is for editorial purpose only.

TRBL10-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-170

10.8 Initialization Procedure for Pool

NOTE 1: When Initialize Pools executed, the pool of all Dynamic Provisioning/Thin Image is blockaded.

NOTE 2: In the case [TrueCopy/Universal Replicator/ShadowImage/Volume Migration/global-

active device] use virtual volumes of Dynamic Provisioning, delete all [TrueCopy/Universal
Replicator/ShadowImage/Volume Migration/global-active device] pairs that use the virtual
volumes before performing Initialize Pools. In addition, delete all the journal volumes of
Universal Replicator that use the virtual volumes. After Initialize Pools completes, create
[TrueCopy/Universal Replicator/ShadowImage/Volume Migration/global-active device] pairs
again. During Initialize Pools, donʼt create [TrueCopy/Universal Replicator/ShadowImage/
Volume Migration/global-active device] pairs with virtual volumes of Dynamic Provisioning. In
the case create those pairs, initialize and paircreate operation may fail.
If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the recovery procedure is not possible due
to capacity inconsistency. Perform capacity expansion so that the capacities are consistent, and
then create the pair.

NOTE 3: Delete all Thin Image/Thin Image Advanced pairs before performing Initialize Pools. After
Initialize Pools completes, create Thin Image/Thin Image Advanced pairs again. During
Initialize Pools, donʼt create Thin Image/Thin Image Advanced pairs. In the case create Thin
Image/Thin Image Advanced pairs, initialize and paircreate operation may fail.

NOTE 4: Stop the LDEV format on the LDEV on which the DP-VOL with [Compression] or the
[Deduplication and Compression] of Capacity Saving enabled exists in the Storage System
before performing Initialize Pools. If Initialize Pools is performed without stopping the LDEV
format, the initialization may fail.

NOTE 5: Do not execute the maintenance of Dynamic Provisioning until the pool is restored to a normal
state after executing Initialize Pools.

NOTE 6: Perform the operation only when it is directed by the Technical Support Division.

NOTE 7: For the password, refer to the Technical Support Division.

NOTICE: Only in an unusual case such as cache volatilization in both clusters, perform
the procedures described on this page and later. Do not perform the following
procedures unless the Technical Support Division (T.S.D.) instructs you to do so. If
you perform the following procedures without permission, data in the DP-VOL might
be lost.

TRBL10-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-180

START

Does any [TrueCopy

pair and others pair (NOTE 2, No
NOTE 3)] pair in the storage system use
virtual volumes of Dynamic
Provisioning?

Yes
(Request to user)
Stop Job / Script to operate the pair.
[TrueCopy pair and the other pairs. (NOTE 2,
NOTE 3)]

(Request to user)
Stop I/O to DP-VOL.

Delete all [TrueCopy pair and the other

pairs. (NOTE 2, NOTE 3)] pairs that use
virtual volumes of Dynamic Provisioning.

Set the System Option Mode 749 and

System Option Mode 755 to ON.

Initialize Pools is executed.

(See MPC04-780)

Set the System Option Mode 749 and

System Option Mode 755 to OFF.

Collect dumps and call T.S.D in order to

know which action “A” or “B” should be
taken.

1
(TRBL10-181)

TRBL10-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-181

action B
A or B?

TRBL10-80 
action A
Enable System Option Mode 982 (forcible
pool restoration mode) (See MPC05-880).
(*1)

Restore all pools. (*2) (*6)

Disable System Option Mode 982 (forcible

pool restoration mode) (See MPC05-880).
(*1)

No
Is the POOL normal?

T.S.D. call
Yes

Is there
any LDEV with
No
[Compression] or [Deduplication and
Compression] of Capacity
Saving enabled?

Yes
Block all DP-VOLs whose [Capacity Saving
Status] is other than Disabled and the
deduplication system data volume in the
pool.

Initialize all virtual volumes whose

[Deduplication Data] function is [Enabled]
in the pool. (In the [Initialize Duplicated
Data] window, click [Apply]. (*3)) (*5)

Specify all the blocked deduplication system

data volumes (data store) in the pool, and
then perform the LDEV format. (*5)

Perform the LDEV format on all blocked

DP-VOLs whose [Capacity Saving Status] is
other than Disabled in the pool. (*4)
(Request to user)
Perform 20.7 Recovery Procedure When Create TrueCopy pair and the other pairs.
the Compression Acceleration Settings for (NOTE 2, NOTE 3)
Deduplication System Data Volumes Are
Invalid after Duplicated Data Initialization .
END

TRBL10-181
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-182

*1: Ask T.S.D to tell you the password.

*2: You can restore pools by using Web Console or CCI (Command Control Interface).
However, when SIM = 3073xx occurs and MPs are blocked, you cannot use CCI to restore pools.
• Web Console: Use the Pools window to restore pools (see the Provisioning Guide).
• CCI: Execute the following command to restore pools (see the Command Control Interface
Command Reference):
raidcom modify pool -pool pool# -status nml
*3: For Command Control Interface, use the [raidcom initialize pool] command.
*4: Do not perform the procedure for LDEV recovery.
*5: If there is not a deduplication system data volume, the operation is not required.
*6: Recovering multiple pools with large capacity at a time might cause time-out. Therefore, perform
pool recovery for one pool by one, confirm task completion, and then perform the next pool
recovery operation. If Web Console is used, task completion of the pool recovery can be confirmed
in the Tasks window. (Select [Tasks] from the [Storage Systems] tree, display the [Tasks] tab,
and confirm that [Status] of the performed pool recovery task is [Completed].) To use Command
Control Interface for task completion confirmation, run raidcom get command_status. (Confirm
that the raidcom get command_status command ends.)

TRBL10-182
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-190

10.9 Recovery Procedure for Dynamic Provisioning by Turning Off the Power and
Volatilizing PS ON

NOTICE: • This operation supposes a special case such as a recovery from a failure unlike
the usual powering off operation. Do not perform this operation without a direction
given by the Technical Support Division.
• When the following procedure is performed, SIM = 680001 might be reported. If
SIM = 680001 is reported, do not perform “20.1 Recovery Procedure for dedupe
and compression Operation Error (SIM = 680001)”, but continue the following
procedure.

START

Collect dumps (see MAINTENANCE PC

SECTION “5.2 Dump”), and contact T.S.D.
Operations to be performed by instructions of the Technical Support Division

Does the pool No

contain LDEVs with Capacity Saving
enabled?

Yes
Set the System Option Modes 1113 and 1148
to ON.

Wait for one hour.

Set the System Option Mode 1112 to ON.

Set the System Option Modes 1113 and 1148

to OFF.

Wait for one hour.

Check for cache write pending data.

Is cache write No
pending data zero in the whole
storage system?

Yes
Wait for one hour.

By using Command Control Interface (CCI),

check whether the function to automatically
add pool volumes for which accelerated
compression is enabled is enabled. (*6)

1 (TRBL10-191)

TRBL10-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-191

1
Operations to be performed by instructions of the Technical Support Division

Is there
a pool for which the
function to automatically add pool Yes
volumes for which accelerated
compression is enabled By using Command Control Interface
is enabled? (CCI), disable the function to automatically
add pool volumes for which accelerated
No compression is enabled. (*7)

Wait for 40 minutes.

Check of SSB = AFB0 reported.

After
the last pool or HDP No
operation, SSB = AFB0 T.S.D. call
reported? (*1)

Yes

Execute “15.3 Forced volatilization (full)

power-off and restarting procedure 1-2”.

Execute the LDEV recovery of blockaded

pool-VOL. (See MPC04-640)

Collect dumps (see MAINTENANCE PC

SECTION “5.2 Dump”), and contact T.S.D.

Are LDEVs No
with Capacity Saving enabled
defined?

Yes

Is the DKC
firmware less than 93-03- No
22-x0/01 or 88-07-02-
x0/00?

Yes
Update the DKC firmware for a
version 93-03-22-x0/01 or 88-07-02-
x0/00 or later. (See FIRM03-10)

3
(TRBL10-192)

TRBL10-191
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-192

Operations to be performed by instructions of the Technical Support Division

Restore all pools. (*10) (*12)

Check of pool recovery result.

The pool recovers Yes

normally?
When the System Option Mode 1112 is ON,
No change it to OFF.

If you have disabled the function to

automatically add pool volumes for which
accelerated compression is enabled, enable
it. (*7)

2
Did the
Technical Support (TRBL10-200)
Division already check the number No
of SSB = afff reported for the pools that failed
to be recovered and the detailed
byte information of each
SSB = afff? T.S.D. call

Yes
Enable System Option Mode 982 (forcible pool
restoration mode). (See MPC05-880) (*9)

Restore all pools. (*10) (*12)

Disable System Option Mode 982 (forcible pool

restoration mode). (See MPC05-880)

TRBL10-192
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-200

Does the pool contain No

LDEVs with Capacity Saving
enabled?

Yes
Back up data as necessary. (*2)

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage, Volume

Migration and global-active device that use the DP-VOLs associated with the pool
and all Thin Image/Thin Image Advanced pairs (the root volume and the pairs in
the tree (*4)) that use the pool.

Block all DP-VOLs whose [Capacity Saving Status] is other than “Disabled” and
the deduplication system data volume in the pool.

Initialize all virtual volumes whose [Deduplication Data] function is [Enabled] in

the pool. (In the [Initialize Duplicated Data] window, click [Apply]. (*3)) (*11)

Specify all the blocked deduplication system data volumes (data store) in the pool,
and then perform the LDEV format. (*11)

Perform the LDEV format on all blocked DP-VOLs whose [Capacity Saving
Status] is other than “Disabled” in the pool. (*5)

Perform “20.7 Recovery Procedure When the Compression Acceleration Settings

for Deduplication System Data Volumes Are Invalid after Duplicated Data
Initialization”.

If there is any backup, restore the data from the backup. (*2)

For the DP-VOLs and LDEVs associated with the pool, recreate TrueCopy,
Universal Replicator, ShadowImage, Volume Migration and global-active device
pairs, and Thin Image/Thin Image Advanced pairs that use the pool. (*8)

END

*1: Please confirm SSB EC = AFB0 was output after the last following operation is executed.
<Operation that should confirm report of SSB EC = AFB0>
• Pool making/pool-VOL addition/pool-VOL deletion/Pool deletion
• DP-VOL making/DP-VOL deletion/DP-VOL capacity expansion
• Quick Restore of ShadowImage using DP-VOL
• Volume Migration using DP-VOL
From the operation to the report of SSB, it usually takes about 40 minutes. However, when the
configuration change is repeated, it might take several hours to do it.
*2: Ask the SE or user to perform the operation.

TRBL10-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-201

*3: For Command Control Interface, use the [raidcom initialize pool] command.
*4: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in
the tree of the root volume. To identify the root volumes of Thin Image/Thin Image Advanced
pairs that use the pool, specify the pool name (ID) for filtering in the TI Root Volume tab in the
Local Replication window of Web Console.
*5: Do not perform the procedure for LDEV recovery.
*6: Use the [raidcom get pool -key opt] command and check [AUTO_ADD_PLV].
*7: Use the [raidcom modify pool -pool] command and the [-auto_add_poolvol] option. Entering a
one-time password is necessary for the operation.
*8: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.
*9: Ask T.S.D to tell you the password.
*10: You can restore pools by using Web Console or CCI (Command Control Interface).
However, when SIM = 3073xx occurs and MPs are blocked, you cannot use CCI to restore pools.
• Web Console: Use the Pools window to restore pools (see the Provisioning Guide).
• CCI: Execute the following command to restore pools (see the Command Control Interface
Command Reference):
raidcom modify pool -pool pool# -status nml
*11: If there is not a deduplication system data volume, the operation is not required.
*12: Recovering multiple pools with large capacity at a time might cause time-out. Therefore, perform
pool recovery for one pool by one, confirm task completion, and then perform the next pool
recovery operation. If Web Console is used, task completion of the pool recovery can be confirmed
in the Tasks window. (Select [Tasks] from the [Storage Systems] tree, display the [Tasks] tab,
and confirm that [Status] of the performed pool recovery task is [Completed].) To use Command
Control Interface for task completion confirmation, run raidcom get command_status. (Confirm
that the raidcom get command_status command ends.)

TRBL10-201
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-210

10.10 Disabling Procedure for Accelerated Compression Setting of Parity Group

Confirm whether the sufficient capacity required for shrinking the pool along with the disabling
Accelerated Compression setting is available before performing this operation.

START

Are there
LDEVs in the accelerated No
compression setting (*4) enabled
parity group? Delete the parity group.
Yes
Create a parity group with the accelerated
compression setting disabled.
Are those LDEVs in the parity No
group used as pool volumes?

END
Yes

Ask the customer to expand the pool. (*2)

Is the sufficient
capacity for shrinking the pool No
of the Accelerated Compression setting (*4)
enabled parity group available?
(*1)

Yes
Ask the customer to shrink the pool for all pool
volumes of the parity group whose Accelerated
Compression setting is enabled.

Ask the customer to format the target parity group.

(*3)

Ask the customer to delete all LDEVs whose

[Expanded Space Used] is [Yes]. (*4)

Ask the customer to change the Accelerated

Compression setting of the target parity group
from enabled to disabled.

END

TRBL10-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-220

*1: Confirm the customer whether the target pool can be shrunk using the following determination
formula.
Determination formula: Pool usage < Pool capacity after shrinking (NOTE) × Depletion threshold
value
NOTE: Pool capacity after shrinking
= Pool capacity before shrinking – Total capacity of pool volumes whose Accelerated
Compression setting is enabled
When the determination formula is met: Yes
When the determination formula is not met: No
*2: Add larger capacity than the total capacity of the pool volumes whose Accelerated Compression
setting is enabled. Add LDEVs whose Accelerated Compression setting is disabled.
*3: Format the drives of the target parity group by specifying the parity group. If incorrect LDEVs are
specified, the Accelerated Compression setting is not disabled.
See MAINTENANCE PC SECTION “[Link] Formatting Parity Group”.
*4: For the Accelerated Compression setting and Expanded Space Used, see “Provisioning Guide”.

TRBL10-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-230

10.11 Recovery Procedures from Failures on Pool Creation, Expansion, and Deletion
The following are the recovery procedures from the failures when SIM = “633xxx” is output. Confirm the
error information by following the procedure shown in Step 1 through Step 3, and then perform the failure
recovery procedure in Step 4.

1. Confirm the error information on SIM = “633xxx” through the Maintenance Utility, and then write down
the POOL ID and the “Concerned Alerts”.

2. Select [View Internal Alerts - DKC] from the [Alerts] tab, and display the “Internal Alerts (DKC)”
window.

TRBL10-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-240

3. In the “Internal Alerts (DKC)” window, select the same Alert ID as the “Concerned Alerts” written down
in Step 1, and display the “Internal Alert Detail” window.

Perform Step 4 by referring to 0x48 byte through 0x7f byte of “Error Data” displayed in the “Internal
Alert Detail” window. Refer to the following figures and table for more details about how to check 0x48
byte through 0x7f byte.

TRBL10-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-250

Byte (HEX) Item Description

48 Operation type Operation types in case of failures
• Pool creation or expansion : 0x01
• Pool deletion : 0x02
49 Recovery Recovery instruction types
instruction • Pool creation or expansion (no DT settings) : 0x01
• Pool creation or expansion (with DT settings) : 0x02
• PG deletion : 0x03
• Pool recreation or deletion : 0x04
• Contact the Technical Support Division : 0xff
4a Pool type Pool types to be performed the operations
• DP pool : 0x01
• TI pool : 0x02
• N/A (only for pool deletion) : 0xff
4b Reserved Unused Unused
4c through 4d Parity Group# Target Parity Group#
0x4c byte: XX (HEX)
0x4d byte: YY (HEX)
If XX/YY is 0x00, it is invalid.
For example, if XX = 0x0c and YY=0x02, the Parity Group# to be
input from the Embedded CCI is “12-2”.
4e through 4f Parity Group# Target Parity Group#
: Consecutive formats just like 0x4c byte through 0x4d byte
7e through 7f

TRBL10-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-260

4. Perform the recovery procedures in accordance with the following flowcharts by referring to the POOL
ID to be recovered that you have checked in Step 1 and the Internal Alert Detail that you have checked in
Step 3.

START

Does SIM = 624000 Yes

occur at the same time?
Take actions for SIM = 624000.
No (See TRBL10-100)

Is the recovery
instruction for 0x49th byte of the Yes
1
SSB the pool creation or expansion?
(TRBL10-270)
(0x01 or 0x02)

No

Is the recovery instruction Yes

for 0x49th byte of the SSB the PG deletion? 2
(0x03) (TRBL10-290)

No

Is the recovery
instruction for 0x49th byte of the Yes
3
SSB the pool recreation or deletion?
(TRBL10-300)
(0x04)

No

T.S.D. call

TRBL10-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-270

In the case that the recovery instruction is the pool creation or expansion
1
(no DT settings), or pool creation or expansion (with DT settings):

Perform the following procedure for each Parity Group#

instructed after 0x4c byte of the SSB.

On the Embedded CCI, execute the following command.

raidcom reset command_status

On the Embedded CCI, execute either of the following pool operation commands
depending on the pool type instructed by 0x4a byte of the SSB.
When the pool type is DP pool (0x01),
raidcom add dp_pool -pool_id <POOL ID> -parity_grp_id <Parity Group#>
When the pool type is TI pool (0x02),
raidcom add snap_pool -pool_id <POOL ID> -parity_grp_id <Parity Group#>
For example, when the POOL ID is 10, the pool type is DP pool
(0x01), and Parity Group# is XX = 0x03 and YY = 0x0a,
raidcom add dp_pool -pool_id 10 -parity_grp_id 3-10

Is the command No
T.S.D. call
normally ended? (*1)
(*1) If ① no error message is displayed, or if ② “raidcom:
Yes [EX_ENOOBJ] No such Object in the RAID” is displayed,
judge it to be normally ended.

On the Embedded CCI, execute the following command.

raidcom get command_status

Is the command No
T.S.D. call
normally ended? (*2)

Yes

Is the procedure
shown above complete for all the No
Parity Group# instructed after 0x4c
byte? (*2) In the case of ERR_CNT = 0 or the following command
execution error, judge the command to be normally ended.
Yes “The specified parity group does not have enough free
capacity to create a pool volume. (SSB1: 2e13 SSB2:0104)”
1-1
(TRBL10-280)

TRBL10-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-280

1-1

Is the recovery
instruction for 0x49th byte of the SSB No
the pool creation or expansion (no DT
settings)? (0x01) Start the Web Console. (See MPC02-10)

Yes Enable the “Multi-Tier Pool” function for the

target <POOL ID> in accordance with”Changing a
Dynamic Tiering or active flash pool to a pool for
Dynamic Provisioning” in Provisioning Guide.

On the Embedded CCI, execute the following command to obtain the

pool information, and check the pool name of the target <POOL ID>.
raidcom get pool -key opt

Does the target No

<POOL ID> exist?

Yes
Notify the user of the checked pool name, and ask the
user to change the pool name if the pool name needs
to be changed.

Has the case of ② Yes

described in (*1) occurred?
Ask the user to perform the pool creation or
No expansion again because no drive is added to the
pool.

END

TRBL10-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-290

2 In the case that the recovery instruction is PG deletion:

On the Embedded CCI, execute the following command.

raidcom get pool

Has the target <POOL Yes

ID> been defined?
Ask the user to delete
No the pool again.
On the Embedded CCI, execute the following command.
raidcom reset command_status

Perform the following procedure for each Parity Group#

instructed after 0x4c byte of the SSB.

On the Embedded CCI, execute the following command to delete the Parity Group.
raidcom delete parity_grp -parity_grp_id <Parity Group#>

For example, when the Parity Group# is XX = 0x03 and YY = 0x0a,

raidcom delete parity_grp -parity_grp_id 3-10

Is the command No
T.S.D. call
normally ended? (*3)
(*3) If no error message is displayed, or if “raidcom:
Yes [EX_ENOOBJ] No such Object in the RAID” is
displayed, judge it to be normally ended.
Is the procedure
shown above complete for all the No
Parity Group# instructed after 0x4c
byte?

Yes
On the Embedded CCI, execute the following command.
raidcom get command_status

Is the command normally No

T.S.D. call
ended? (ERR_CNT = 0)

Yes

END
TRBL10-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-300

3 In the case that the recovery instruction is pool recreation or deletion:

On the Embedded CCI, execute the following command.

raidcom get pool

Has the target <POOL Yes

ID> been defined?
Ask the user to delete
No the pool again.
On the Embedded CCI, execute the following command.
raidcom reset command_status

Perform the following procedure for each Parity Group#

instructed after 0x4c byte of the SSB

On the Embedded CCI, execute the following command to add the Parity Group to the pool.
raidcom add dp_pool-pool_id < POOL ID > -parity_grp_id <Parity Group#>
For example, when the POOL# is 10, and Parity Group# is XX = 0x03 and YY = 0x0a,
raidcom add dp_pool -pool_id 10 -parity_grp_id 3-10

Is the procedure
shown above complete for all the No
Parity Group# instructed after 0x4c
byte?

Yes

3-1 END
(TRBL10-310)

TRBL10-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-310

3-1

On the Embedded CCI, execute the following command.

raidcom get command_status

Is the command normally No

T.S.D. call
ended? (ERR_CNT = 0)

Yes
On the Embedded CCI, provide instruction for the pool deletion of the target pool.
raidcom delete pool -pool < POOL ID > -delete_volume yes
For example, when the POOL ID is 10,
raidcom delete pool -pool 10 -delete_volume yes

On the Embedded CCI, execute the following command.

raidcom get command_status

Is the command normally No

T.S.D. call
ended? (ERR_CNT = 0)

Yes

END

TRBL10-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-320

10.12 Recovery Procedure When Automatic Pool Capacity Expansion Failed due to a
Pool-associated Factor (SIM = 632xxx)
The procedure to recover from an automatic pool capacity expansion failure caused by a factor associated
with a pool is shown below.

START

Do the SIMs
for which actions are not No
taken yet include any of 602xxx/605x
xx/623xxx/624000/627x
xx/628000?

Yes

1 2
(TRBL10-330) (TRBL10-340)

TRBL10-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-330

Yes
SIM = 602xxx?

No

Yes
SIM = 605xxx?

No See “8.3 Recovery Procedure for Pool Failure

(SIM = 602xxx, 604xxx, 605xxx, 606xxx)”.

Yes
SIM = 623xxx?

No See “10.2 Recovery Procedure for Pool Failure

(SIM = 623xxx)”.

Yes
SIM = 624000?

No See “10.3 Recovery Procedure for Pool Failure

(SIM = 624000)”.

Yes
SIM = 627xxx?

No See “10.5 Recovery Procedure for pool-VOL

Blockade (SIM = 627xxx)”.

Yes
SIM = 628000?

No See “10.6 Procedure for Releasing Protect

Attribute of Data Retention Utility (SIM =
628000)”.
END

TRBL10-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL10-340

Is the licensed capacity Yes

insufficient? (*1)
Ask the customer to add the licensed
No capacity.

Are there 1,024 pool- Yes

VOLs in the pool?
Tell the customer that you divide the
No pool into multiple pools because the
pool cannot be expanded.

Is the Shrink Pool Yes

operation in process?
Wait until the Shrink Pool operation
No is complete.

Is the PS OFF Yes

processing in progress?
After completion of the PS OFF
No processing, perform the PS ON
operation.
Collect Dump/Log
(see MAINTENANCE PC
SECTION “5.2 Dump”)
Is SIM =
632xxx reported after
Yes
T.S.D. call 8 hours have passed since the above
procedure was performed?

No

END

*1: When the licensed capacity is smaller than the total capacity of parity groups composing the pool-
VOL, the licensed capacity is insufficient. In such a case, the automatic pool capacity expansion
might fail. The shortage of the licensed capacity can be calculated as follows:
Shortage of licensed capacity = Total capacity of parity groups composing the pool-VOL –
Licensed capacity
• To check the licensed capacity, see [Licensed] of [Licensed Capacity (Used/Licensed)] in the
“Pools” window of Web Console.
• To check the parity group capacity, see [Total] in the [Capacity] column in the “Parity Groups”
window of Web Console.
For details of the windows of Web Console, see “Provisioning Guide”.

TRBL10-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-10

11. External Storage System Maintenance

11.1 Maintenance of External Storage System
The following is a collection of matters to be given considerations when doing maintenance works or failure
recovery actions for the external storage system connected by means of the Universal Volume Manager
function.

11.1.1 Considerations When Performing Maintenance Work on External Storage System

NOTICE: Before changing settings of the external storage system, to release the mapping,
execute [Disconnect External Volumes] and [Delete External Volumes] on the
volumes in the local storage system to which the volumes in the target external
storage system for the settings change are mapped. Then, change the settings on
the external storage system side and map the volumes again. If you do not remap
the volumes, the external volumes cannot be used in the local storage system.
The examples of external storage system settings which require the re-mapping of
external volumes are as follows:
(a) Changing WWN/iSCSI target names of the target ports which connect to the
local storage system
(b) Changing the serial number of the external storage system
(c) Changing LUNs of volumes of the external storage system
(d) Reducing the volume capacity of the external storage system so that the
volume capacity is smaller than when volume mapping was performed
Besides, in the configuration where the external storage system is directly connected
to the host, re-mapping is required after settings change that requires the host
to recognize again the volumes mapped by using Universal Volume Manager is
performed on the external storage system side.
In the above case (a), when changing only the WWN/iSCSI target names of some
target ports connected to the local storage system on the external storage system
side, you do not have to delete the volumes mapped to the local storage system.
The following procedure is the way to change settings of the external storage system
without deleting the external volumes:
1. Changing WWN/iSCSI target names of part of target ports which connect to
the local storage system. After the process, external paths using the target
ports are blocked.
2. Adding new external paths between the target ports and the local storage
system
3. Deleting the external paths blocked in Step 1
Before you delete the external volume mapping, make sure that the volume has no
LU paths, and that the volume is not a component of any pairs (such as TrueCopy
pairs).
For detailed information on deleting the external volume mapping, see section Hitachi
Universal Volume Manager User Guide - Deleting external volume mapping .
For detailed information on mapping external volume, see section Hitachi Universal
Volume Manager User Guide - Mapping an external volume .
TRBL11-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-20

NOTICE: When the following conditions 1 and 2 are met, perform 10.1 Recovery Procedure
for pool-VOL Blockade (When Two (Three in RAID6) or More Are Blocked in the
RAID Gr the pool-VOL Belongs) for the pool-VOLs after recovering the devices of
the external storage system.
1. The devices of the external storage system to be maintained are used as pool-
VOLs.
2. You have performed operations which cannot ensure data consistency (for
example, format) to recover the devices of the external storage system.

When the maintenance work is done on the external storage system side, if external paths are blocked due
to the maintenance work, SIM = 21d0xx (path blockade), SIM = 21d1xx (path recovery), or SIM = efd000
(external storage device blockade) might be issued on the local storage system side. But there is no problem.
After the maintenance work is completed, check that SIMs other than SIM = 21d0xx (path blockade), SIM =
21d1xx (path recovery), or SIM = efd000 (external storage device blockade), which could be caused from the
maintenance work, are not generated, and then set the REMOTE MAINTENANCE switch to ENABLE. If
SIMs other than the above are generated, take actions according to the customerʼs conditions (depending on
the urgency).
Do the maintenance works for the external storage system side following guidelines explained below.

When doing a maintenance work for the external storage system side
1. Make sure that an alternative path (in the Normal status) exists between the local storage system and the
external storage system. (See [Procedure 1] in “11.1.3 Procedure for Operating Storage Navigator”.)
2. When a path blockage occurs due to the maintenance work on the external storage system side, check
whether an alternative path that is not blocked is available. If an alternative path is available, continue the
maintenance work by following the procedure for the external storage system.
3. If no alternative path (in the Normal status) exists, have the customer stop access to the server concerned
and perform the operation (Disconnect External Volume) to disconnect the external storage system
side concerned on the local storage system side. (See [Procedure 2] in “11.1.3 Procedure for Operating
Storage Navigator”.)
4. Do the maintenance work following the procedure for the external storage system side.
5. After the maintenance work for the external storage system side is completed, perform the operation
(Reconnect External Volumes) to reconnect the external storage system side concerned on the local
storage system side. (See [Procedure 3] in “11.1.3 Procedure for Operating Storage Navigator”.)

TRBL11-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-30

NOTE
• Even if the alternative path exists, the SIM (21d0) informing of the path blockade is reported via the local
storage system side when the path is switched to the alternative path. In this case, the path status on the
local storage system side is recovered from the blockade automatically when a factor, which caused the
blockade, on the external storage system side is removed.
• The path recovery SIM (21d1) occurs when at least one of the external paths recovers.
To confirm that all the paths have recovered at the completion of the maintenance, check the path status not
only with the output of the path recovery SIM (21d1) but with the following procedure:
(1) Check the status displayed in the [Status] field of the [External Storage] window that is displayed
when selecting [External Storage] from the [Storage System] tree in the Storage Navigator
window.
(2) Confirm that the status displayed in the [Status] field is “Normal”.
NOTE: If the status displayed in the [Status] field is other than “Normal”, it indicates that at
least one or more external paths are in the maintenance status or in the blocked status.
• When the external storage system is SANRISE9500V series to which the Single path mode is applied, if
a path switch occurs due to the maintenance work, automatic switch back to a primary path occurs after
the maintenance work. In the maintenance work, make sure that the path has been switched back after
the maintenance work for the external storage system side is completed. (See [Procedure 4] in “11.1.3
Procedure for Operating Storage Navigator”.)
• Because the external storage system side is in the Multiple Path mode when it is the SANRISE 2000 series/
SANRISE 9900V series/ AMS2000 series/ HUS/SANRISE USP, NSC/USP V, USP VM/VSP/ HUS VM/
VSP G1000/VSP G1500/VSP F1500, VSP 5000 series, VSP G200/G400/G600/G800, VSP G130/G350/
G370/G700/G900, VSP F400/F600/F800, VSP F350/F370/F700/F900, or VSP E590/E790/E990/E1090/
E590H/E790H/E1090H device, make sure that the path is recovered from the blockade (the path status is
changed to Normal).
Also, after all maintenance work is completed, check if SIM = 21d0xx (path blockade), SIM = 21d1xx
(path recovery), or SIM = efd000 (external storage device blockade), which could be caused from the
maintenance work, is generated. If a SIM other than the above SIMs is generated, perform troubleshooting
according to the SIM.

TRBL11-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-40

11.1.2 Maintenance (Isolation) Procedure for a Failure on External Storage System (SIM =
21d0xx, 21d2xx, efd000, ef5xxx, ff5xxx)
The following SIMs may be reported by the local storage system when a failure occurs in the external storage
system or during a maintenance work. In such a case, specify the maintenance work following the procedure
shown below.

1. In the case of the Hitachi external storage system, check if a remote maintenance report has been sent
from both of the local storage system and the external storage system.
When only a SIM (21d0xx, 21d2xx, efd000, ef5xxx or ff5xxx) informing of a failure in the external
storage system is issued by the local storage system and a failure is also reported by the external storage
system, it is highly possible that the SIM (21d0xx, 21d2xx, efd000, ef5xxx or ff5xxx) is issued by the
local storage system according to the failure that has occurred in the external storage system.
In this case, specify a cause of the failure according to the failure information of the external storage
system.

2. Basically, take actions following instructions given in the TROUBLESHOOTING SECTION according
to the contents of the SIM reported to the local storage system.

3. If you fail to specify the cause or solve the trouble finally, contact the Technical Supports Division (T.S.D.).
In such a case, send dumps / traces of both the local storage system and the external storage system (Hitachi
external storage system only) to the T.S.D.
Procedure for a dump from the local storage system: Refer to MAINTENANCE PC SECTION “5.2
Dump”.

4. When the external storage system is not Hitachi-manufactured, send only the dump from the local storage
system to the T.S.D. Besides, request the customer to make the external storage system recover from the
failure.

Table 11-1
SIM code SSB code Host report Detailed description References
efd0 AD10 Issued Blockade of the external device TRBL11-60
21d0 AD11 Issued Blockade of the path connecting the external TRBL11-60
device TRBL11-80
21d1 AD12 Not issued Recovery of the path connecting the external
device
21d2 AD60 Issued External storage system response delay (*1) TRBL11-110
ef5x 89CB Not issued Abnormal end of Write in External TRBL04-160
storage system
ff5x 89CC Not issued Abnormal end of Read in External TRBL04-160
storage system
*1: The time-out value of response from the external storage system can be changed in the [I/O
Timeout] field of the “Edit External WWNs” window or the “Edit External iSCSI Targets” window.
For details, see Universal Volume Manager User Guide.

TRBL11-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-50

11.1.3 Procedure for Operating Storage Navigator

[Procedure 1] Procedure to make sure of existence of an alternative path between the local storage system
and the external storage system
See “External Paths tab” in “Selected external path group window” in “Hitachi Universal
Volume Manager User Guide”.
For all path groups that use the maintenance target port, make sure that a path in the “Normal”
status exists besides the path to be maintained in the above window.

[Procedure 2] Procedure for disconnecting the external storage system (Disconnect External Volume
operation)
See the chapter on the external volume in “Hitachi Universal Volume Manager User Guide”.

[Procedure 3] Procedure for reconnecting the external storage system (Reconnect External Volumes
Operation)
See the chapter on the external volume in “Hitachi Universal Volume Manager User Guide”.

[Procedure 4] Procedure for making sure that the alternative path has been switched back
See “External Paths tab” in “Selected external path group window” in “Hitachi Universal
Volume Manager User Guide”.
Make sure that the status of the path to be maintained is “Normal” in the above window. If the
status is not “Normal”, close the window once. Wait for a while (about five minutes), and then
display the window again.

TRBL11-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-60

11.2 Recovery Procedure for External Device Failure

The following is the recovery procedure when the External Devices Error (SIM = 21d0xx, efd000) is
occurred.

11.2.1 Recovery Procedure for Path Failure While Device is Blocked (SIM = 21d0xx,
efd000)

External Storage system

devices and path failure

Did you execute No

PS OFF/ON at the Local Storage
System?

Yes

Is the external
volume to which the profile was No
applied by using the profile tool
blocked?

Yes

Does the
DKCMAIN support the Yes
blocked external storage
system?
No
Apply the profile again, then execute
“Reconnect External Volumes”. (*3)

Are the external storage No

system devices recovered?

Yes 1
(TRBL11-61)
END

TRBL11-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-61

Take actions appropriate for the mapping

path status. For how to check the mapping
path status and the recovery actions, see
Hitachi Universal Volume Manager User
Guide.

Is the mapping path status Yes

restored to “Normal”?

No

Is the Optical cable No

connected with External Storage
system and DKC?

Yes
Please execute the maintenance of External Please connect the Optical cable between the
Storage system following its manual. (*1) External Storage system and DKC.

Reconnect external volumes. (*3)

Is there
a path whose status is No
“Unknown”, “Warning”, “Blockade”,
or “Destage Failed”?

Yes Is there an LDEV whose No

status is “Blocked”?
Please follow the path recovery method.
(See TRBL11-80)
Yes

Please examine No
whether path recovery is possible or
not?

Yes
Reconnect external volumes. (*3)

No
Is the device recovered?

Collect dumps (see MAINTENANCE PC

Yes SECTION “5.2 Dump”), and contact T.S.D.

2 (TRBL11-70)

TRBL11-61
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-70

Are the recovered Yes

devices of the external storage system
used as pool-VOLs?
Have
No you performed
operations which cannot ensure No
data consistency (for example, format)
to recover the devices of the
external storage
system?

Yes

Perform “10.1 Recovery Procedure for

pool-VOL Blockade (When Two (Three in
RAID6) or More Are Blocked in the RAID
Gr the pool-VOL Belongs)”

Are there
blocked DP-VOLs
for which Capacity Saving is
No enabled, Deduplication System Data
Volumes (Fingerprint), and Deduplication
System Data Volumes (Data store)
in the pool associated with
the pool-VOL? (*2)

Yes
Restore the blocked LDEVs forcibly (without safety
checks) in the following order.
Ask the Technical Support ------- (See MPC04-695.)
Division about the password. (1) Deduplication System Data Volumes
(Fingerprint) and Deduplication System Data
Volumes (Data store)
(2) DP-VOLs for which Capacity Saving is enabled

END

TRBL11-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.10 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-71

*1: If the data of the blocked device is unnecessary, you can format the device at the external storage
system to recover it.
When the formatted devices of the external storage system are used as pool-VOLs, it meets the
condition to perform “10.1 Recovery Procedure for pool-VOL Blockade (When Two (Three in
RAID6) or More Are Blocked in the RAID Gr the pool-VOL Belongs)”, which is mentioned at the
end of the flowchart.
As the flowchart shows, make sure that you perform it just before the end of the flowchart.
*2: How to check the blockade state of DP-VOLs for which Capacity Saving is enabled, Deduplication
System Data Volumes (Fingerprint), and Deduplication System Data Volumes (Data store):
In the “Logical Devices” window in Web Console, if [Blocked] is displayed in the [Status] column,
the volumes are blocked. For the DP-VOLs for which Capacity Saving is enabled, “Compression”
or “Deduplication and Compression” is displayed in [Capacity Saving]. For the two types of
Deduplication System Data Volumes, “Deduplication System Data Volume (Fingerprint)” or
“Deduplication System Data Volume (Data store)” is displayed in [Attribute].
• The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see “System Administrator Guide”).
• To display only the DP-VOLs for which Capacity Saving is enabled, Deduplication System Data
Volumes (Fingerprint), and Deduplication System Data Volumes (Data store), specify the column
value for the filter. For more details about filtering, refer to “System Administrator Guide”.
*3: See “Hitachi Universal Volume Manager User Guide”.

TRBL11-71
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-80

11.2.2 Recovery Procedure for Path Single Failure (SIM = 21d0xx)

Pass failure

Is the Optical
cable between External No Please connect the Optical cable
Storage system port and DKC between the External Storage system
port connected? and DKC.

Yes
Is the external path Yes
Is the No recovered?
switch connected with DKC
port?
No
Yes Is the Port
LED which the Optical No
2
cable is connected
Is the Port
flashed?
LED which the Optical No Please exchange the Optical cable.
2
cable is connected Yes
flashed?

Yes No Is the external path

recovered?
Please check the External Storage Please confirm the status of the
system or Switch or the Optical External Storage system devices.
cable. If there is the problem, please Yes
maintenance the External Storage
system devices.
1 (TRBL11-90)
If the maintenance of the external
storage system devices has been
performed, reconnect the external
volumes. (*1).

Are the External Yes

Storage system devices
recovered?

No

Replace the SFP in the port connected

to the external storage system.

Are the External Yes

Storage system devices
recovered?

No

Replace the CHB in the port connected

Collect dumps (see to the external storage system.
MAINTENANCE PC SECTION
“5.2 Dump”), and contact T.S.D.
Is the external path Yes
recovered?

END No END

TRBL11-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-90

Is the switch
connected with the No
External Storage system
rightly? Please connect the Optical cable
between the External Storage system
Yes and Switch.

Is the external path Yes

recovered?

No
Please exchange the Optical cable.

No Is the external path

recovered?
Maintain the external storage system
according to the external storage Yes
system manual.

Reconnect external volumes. (*1)

Is the external path Yes

recovered?

No
Replace the SFP in the port connected
to the external storage system.

Are the External Yes

Storage system devices
recovered?

No
Replace the CHB in the port connected
to the external storage system.

Is the external path Yes

recovered?

No
Collect dumps (see
MAINTENANCE PC SECTION
“5.2 Dump”), and contact T.S.D.

END END

*1: See “Hitachi Universal Volume Manager User Guide”.

TRBL11-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-100

This page is for editorial purpose only.

TRBL11-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-110

11.2.3 Recovery Procedure for External storage system response delay (SIM = 21d2xx)

External storage system

response delay

Check the state of the external storage system

and communication paths between the external
storage system and the local storage system
from the local storage system.

Is there any problem

in the external storage system or Yes
the communication paths between the external
storage system and the local
storage system? Remove the problem from the external
storage system or the communication paths
between the external storage system and the
No local storage system.
Check if there is a problem, such as a failure or
overload, in the external storage system.
(Ask the system engineer or user to do so as END
required.)

Is there any problem in the Yes

external storage system?
Remove the problem from the external
No storage system.

Are the END

external storage system and No
the communication paths capable of
withstanding the load applied to
external volumes? Correct the configuration and settings of the
local storage system or the usage of the external
Yes volumes so that the external storage system and
the communication paths can withstand the load
applied to the external volumes.
Collect dumps (see
MAINTENANCE PC SECTION
“5.2 Dump”), and contact T.S.D. END

TRBL11-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-120

11.2.4 Action When External Device and External Volume Are Not Recognized
Check the detailed data of EC=ACF0 (the result of discovery is an unsupported device), and perform the
coping method shown in the table below.
However, since it is deterred for five minutes in units of MP, EC=ACF0 is reported only once, even if there
are two or more factors. When there are two or more factors, remove the factors and execute it again five
minutes later from the previous execution.

Table 11-2 Detailed format of SSB EC=ACF0

0 1 2 3 4 5 6 7 8 9 A B C D E F
0
10
20 9 F A C F 0 Factor code
30 LUN (*)
40 WWN of external storage system (*)
50 WWN
(continued)
60
70
*: The information may not be stored depending on the factor.

Factor code Content Coping Method

0x00000000 • The information of the external • Connect the external storage system supported by
storage system acquired by the Port UVM.
(WWN) discovery is not in the • Apply the firmware version that supports the
profile information. external storage system to the local storage system.
• The external device is the LU for • Install the profile tool supporting the external
storage management. storage system concerned.
• When the LU for storage management (Universal
Xport, etc.) exists, define the LU for data with an
LU number smaller than the LU number of the LU
for storage management. Otherwise, arrange so
that the LU for storage management cannot be seen
from the local storage system or delete the LU for
storage management from the port concerned.
0x00000003 • The remote command device • Do not perform the cascade connection of the
of the external storage system remote command device.
was discovered by the cascade • Make the remote command device invisible from
connection. the local storage system.
0x00000006 • The information of the external • Connect the external storage system supported by
device acquired by the LDEV UVM.
(LU) discovery is not in the profile • Apply the firmware version that supports the
information. external storage system to the local storage system.
• The external device is the LU for • Install the profile tool supporting the external
storage management. storage system concerned.
• Arrange so that the LU for storage management
cannot be seen from the local storage system or
delete the LU for storage management from the port
concerned.
(To be continued)
TRBL11-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-130

(Continued from the preceding page)

Factor code Content Coping Method
0x00000007 • The device concerned is other than • Check the status of the external storage system and
the direct access device. the external device, and make it normal.
0x00000008 • The capacity of the external device • Make the capacity of the external device more than
is less than the supported capacity or equal to the capacity supported by UVM.
of UVM. • Define the device concerned so that it is invisible
from the local storage system.
0x00000009 • The Report LUN information • Check the status of the external storage system and
cannot be acquired. the external device, and make it normal.
• The LU definition is not performed • Perform the LU definition to the connection port of
to the connection port of the the external storage system.
external storage system.
0x0000000A • Login for the external storage • Check the status of the port on the external storage
system failed. system side, and make it normal.
• Perform the WWN registration, etc. on the external
storage system side, and make the login from the
local storage system possible.
0x0000000B • The external device returned • Cancel Reserve of the external device.
RESERVATION CONFLICT.
0x0000000C • An error response was returned • Check the status of the external storage system and
when sending the command to the the external device, and make it normal.
external device.
0x0000000E • The abnormal command response • Check the status of the external storage system and
occurred a total of eight times or the external device, and make it normal.
more for one device.
0x0000000F • Emulation type of the external • Define the device concerned so that it is invisible
device is not supported. from the local storage system.
• Change host mode to any mode except “4C UVM”
at the port of external storage system.
• Change emulation type to any type, which is
supported, at the external device.
0x00000010 • There is no information about valid • Check the status of the external storage system and
LUN at “Report LUN”. the external device, and make it normal.
• The LU definition is not performed • Perform the LU definition to the connection port of
to the connection port of the the external storage system.
external storage system.
0x00000012 • The LU discovery or adding new • Use a path that can be used as an external path.
external path were performed to the
external storage system connected
by using the path (*) that cannot be
used as an external path.
*: Path being used as the I/O path
from the port of the third-party
external storage system to the
port of the local storage system
(To be continued)

TRBL11-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-131

(Continued from the preceding page)

Factor code Content Coping Method
0x00000013 • The [raidcom discover lun] or • Verify that there is no problem even if the
[raidcom add path] command of performance of host I/O or remote copy for the
RAID Manager (CCI) was executed external volume that uses the path is temporarily
for a path used as an external path deteriorated. After that, execute the [raidcom
from the external storage system discover lun] or [raidcom add path] command
to the local storage system in without specifying the [-safety_check enable]
the configuration made by using option.
Universal Volume Manager.
• The [raidcom discover lun] or
[raidcom add path] command of
RAID Manager (CCI) was executed
for a path used as a remote path (the
secondary site is the local storage
system) in the configuration made
by using TrueCopy, Universal
Replicator, or global-active device.
0x00000014 • The [raidcom discover lun] or • Verify that there is no problem even if the
[raidcom add path] command of performance of remote copy for the path is
RAID Manager (CCI) was executed temporarily deteriorated. After that, execute the
for a path used as a remote path [raidcom discover lun] or [raidcom add path]
(the primary site is the local storage command without specifying the [-safety_check
system) in the configuration made enable] option.
by using TrueCopy, Universal
Replicator, or global-active device.
Others • The acquisition of the information • Check the status of the external storage system and
of the external storage system and the external device, and make it normal.
the external device failed.

TRBL11-131
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-140

11.3 Elimination Procedure for Pinned Data on External Storage System

A procedure for eliminating pinned data when it occurs in an external device is shown below.

Pinned data occurs

in an external device.

Is the external device No

one of the Hitachi storage system
products (*2)?

Take recovery actions

Yes
following the maintenance
procedure for the external
Is the displayed device.
No
pinned data problem ECC/LCR error?
(*1)

Replace a drive of the

Yes
external device.

Is it displayed that an
Yes
LU of the local storage system has pinned
data? (*1)

No
On the external storage system, get the
following information:
 Start/End LBA of the LDEV that contains
pinned data
 WWN of the port for which the LDEV that
contains pinned data is defined in the LU
path configuration
 LUN
For how to get the information, refer to
documentation for the external storage system.

END 1 2 END
(TRBL11-150) (TRBL11-150)

*1: For the PIN indication, see MAINTENANCE PC SECTION “5.12.3 Pin Data Indication”.
*2: The following products are not included:
AMS2100/2300/2500, SMS100, and HUS110/130/150

TRBL11-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-150

1 2

On the local storage system, convert the Input information

pinned data to that of the local storage Input the information  Start/End LBA,  WWN, and
system by executing the external device  LUN that have been got manually.
LBA information conversion tool. For
details of the tool, see “11.4 Procedure Output information
for Operating External Device LBA Make notes of the CU:LDEV number and Start/End
Conversion Tool”. LBA manually.

LDEV in the local storage Yes

system is pool-VOL? (Request to user)
Remove the LDEV in the
local storage system from
No
the pool by decreasing the
pool capacity. (*3)

Recover the failed track referring to

“4.2.1 Pinned Tracks”.

END

*3: The LDEV might not be able to be removed from the pool and might remain in the pool depending
on the PIN type in the LDEV. Even when that occurs, go to the next step.

TRBL11-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-160

11.4 Procedure for Operating External Device LBA Conversion Tool

1. On the Maintenance PC, enter “C:\Mapp\wk\xxyyyyzzzzzz\DKC200\mp\pc\[Link]” in the search

box from the [Start] button to start [Link].
NOTE: “xxyyyyzzzzzz” is a directory to be created when creating a Storage System icon.

xx : DKC type
“88” for VSP F350/F370/F700/F900 and VSP G130/G350/G370/G700/G900
“93” for VSP E590/E790/E990/E1090/E590H/E790H/E1090H
yyyy : DKC model name
“8000” for VSP E1090 and VSP E1090H
“6000” for VSP F370/F700/F900, VSP G370/G700/G900, and VSP E990
“4000” for VSP E590/E790/E590H/E790H
“2000” for VSP F350 and VSP G350
“0000” for VSP G130
zzzzzz : Storage system serial number

When the above operation is performed, the following window is displayed.

TRBL11-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-170

2. <Entering the information to be converted>

Enter the WWN, LUN, and Start and End LBA

TRBL11-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-180

3. <Executing the conversion>

When you press the [Execution] button after making sure that the information you have entered is correct,
the converted LDKC#, CULDEV#, start LBA and end LBA for the local storage system is displayed in
the Conversion Info list.

You can also execute the conversion by selecting the [Execution] button from the [Operation] menu bar.

TRBL11-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-190

4. <Verifying the converted information>

Click an item number of the converted information (in the “#” column) and press the [Confirmation]
button.

When the process is completed, the LDKC number and the CULDEV number for the local storage
system, the Start and End LBA for the external device, and the Vender Name, DKC Name, Serial No, and
path information of the external device are displayed.

NOTE: Up to eight (the maximum number of paths) pieces of path information are displayed.
You can also execute this process by selecting the [Confirmation] button from the [Operation] menu bar
besides pressing the [Execution] button.

TRBL11-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-200

5. <Displaying the Pin Slot>

Click an item number of the converted information (in the “#” column) and press the [Pin Slot] button.

When the process is completed, the Start and End LBA of the slot concerning the converted LBA is
displayed. (Display of the Start/End LBA in the case where the Pin Erasure Tool is used: The display is
done for each slot.)

NOTE: • Up to 128 pieces of information can be displayed.

• When the terminal slot is displayed, it may be displayed as smaller than one slot
size.
You can also execute this process by selecting the [Pin Slot] button from the [Operation] menu bar
besides pressing the [Execution] button.

TRBL11-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-210

6. <Procedure for erasing information displayed in the main window>

When you press the [Clear] button in the main window, information displayed in the window is erased.

TRBL11-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-220

7. <Procedure for quitting the tool>

To quit the tool, press the [Exit] button in the main window.

You can also execute this process by selecting the [Exit] button from the [Operation] menu bar besides
pressing the [Execution] button.

TRBL11-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-230

8. <Warning and error dialog boxes>

Warning and error dialog boxes are shown below.

(1) Warning about start of the tool

When the following dialog box is displayed, the tool has already been started.

(2) Input error

When the following dialog box is displayed, the data that has been entered is incorrect.
Check the data that you entered.

(3) WWN error

When the following dialog box is displayed, the WWN that has been entered does not exist. Check
the WWN that you entered.

TRBL11-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-240

(4) External device error

When the following dialog box is displayed, the external device corresponding to the WWN and
LUN that have been specified does not exist.
Check the WWN and LUN that you entered.

(5) LBA specification error

When the following dialog box is displayed, the value of the specified LBA exceeds the maximum
LBA value of the device.
Check the LBA value that you entered.

(6) Memory reservation error

When the following dialog box is displayed, the memory failed to be reserved.

TRBL11-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-250

(7) Config error

When the following dialog box is displayed, the configuration information could not be got
correctly.

(8) Device error

When the following dialog box is displayed, the LDEV corresponding to the specified LBA does
not exist.

(9) Item specification error

When the following dialog box is displayed, the item was not specified at the time of the
verification and the Pin Slot display.

TRBL11-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-260

(10) Internal logical error

When the following dialog box is displayed, an error occurred in the internal logic.

(11) Control area specification error

The specified LBA is a control area.

(12) Error of maximum number of displayed items

The number of displayed items in the PINSLOT window exceeded the allowable maximum value.

TRBL11-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL11-270

11.5 Considerations When Performing Data Recovery on External Volume

Because write data to an external LDEV is stored in the cache of the local storage system once and then
written to an LU of the external device by means of the asynchronous destaging operation, it is possible that
Write Pending Data remains in the cache of the local storage system when a failure occurs in the external
device.
Therefore, it is required to make data restoration being conscious of the Write Pending Data.

1. When making restoration using backup data of a host

(1) Restore an LU of the external device.
(2) Restore a virtual LDEV of the local storage system.
(3) Restore the data using backup data of a host.

2. When making restoration using backup data of the local storage system function
(1) Restore an LU of the external device.
(2) Restore a virtual LDEV of the local storage system.
(3) Restore the data using the local storage system function.

3. When making restoration using backup data of the external device

(1) Restore an LU of the external device.
(2) Restore a virtual LDEV of the local storage system.
(3) Make the local storage system execute the “Disconnect External Volumes” for the LU concerned.
(The Write Pending Data is written to the external device.)
(4) Make the external device restore the LU data of the external device using the backup data.
(5) Restore the virtual LDEV by making the local storage system execute the “Reconnect External
Volumes” for the virtual LDEV.

TRBL11-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL12-10

12. Recovery from SNMP Failure

A procedure for coping with a trouble occurs during a check to be done after installation of a P.P. of the
SNMP is shown below.

12.1 Recovery Procedure for SNMP Test

START

Make sure of the specifications of the LAN to be connected.

Make sure of details of the setting.

IP address
Netmask
Gateway

Was a Yes
wrong setting made?

No
Check the connection between the GUM and the Hub.
Check the straight and cross cables. Correct the settings and execute the
Check the connection of the Hub. trap report test.

Is
Yes
there any problem in the
connection?
No
Reboot the GUM.
Correct the LAN connection
between the GUM and the Hub and
Execute the trap report test.
execute the trap report test.

Is
the SNMP trap Yes
reported normally?

No

Check over customerʼs environment. END

TRBL12-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL12-20

12.2 When Trap Cannot Be Received While Ping Reaches Manager PC Prepared by
Customer
1. Check the settings of Enable in the “SNMP Setting” window on the confirmation GUM.
(1) Check if “ENABLE” is selected
à If not, it choose.

(2) Check if the Community name has been added.

à If not, add it.

(3) Check if the setting of the Enable is that in which the Manager PC concerned is specified as a
receiver of the trap.
à If it is wrongly specified, make the trap receiver to be added with or changed to the IP address
of the Manager PC.

(4) In the case of the cold start trap at the time when the GUM is rebooted
Check if the setting on the Manager side is that in which the trap of the cold start can be received.
à Check if the setting is not the one in which only the failure trap is received by means of a
masking.

2. When the Firewall/Gateway exists in the network between the GUM and the PC prepared by a customer,
check if the UDPs of the Ports #161 and #162 allow the passing.
à Ask the customer to change the setting to allow the passing.

3. Check the customer's Manager for the setting of the trap reception.
à Ask the customer to check if the setting is correct.

TRBL12-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.14.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL12-30

12.3 SNMP Trap Information

Failure information supported by the SNMP is shown below.

1. Specifications of the extended trap

Item Specification Remarks
SNMP Community Community name that is set
PDU Type Trap PDU
Enterprise ID Agent identifier
Agent IP Address Agent IP address
Generic Trap Code Enterprise Specific
Specific Trap Code See the following “2. Specific trap codes”.
Extended Trap PDU See the following “3. Extended trap PDU”.

2. Specific trap codes

Each of these codes is shown as the Kind in a trace file.
Code Name Meaning
1 RaidEventAcute Report on failure occurrence: Storage system shut off completely.
2 RaidEventUserSerious Report on failure occurrence: Operation of a failed part shut off.
3 RaidEventUserModerate Report on failure occurrence: A partial failure occurred.
4 RaidEventUserService Report on failure occurrence: A slight failure occurred.

3. Extended trap PDU

The following is information notified to the Manager as the trap.
Name Type Description
EventTrapSerialNumber Integer Serial number of the Controller Chassis in which a failure
occurred.
EventTrapNickname DisplayString Nickname of the storage system in which a failure
occurred.
EventTrapREFCODE DisplayString Reference code of a failure: See SIM RC SECTION
(SIMRC00-00).
EventTrapPartsID Object IDENTIFIER Part in which a failure occurred.

TRBL12-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL13-10

13. Failure recovery of Encryption License Key

13.1 Recovery procedure when acquisition failure from key management server
(SIM = 661000, 661001)
Key encryption key (used for encryption key decoding) or encryption key acquisition from the external key
server (key management server) at the time of DKC start fails and no volumes can be accessed.
The following are the statuses of drives and LDEVs when the error occurs.
All drives: Failed
All LDEVs other than DP-VOLs for which Capacity Saving is disabled: Blocked
Communication re-establishment with the key management server, PS OFF and PS ON are necessary for
restoration.
Please restore the communication with the key management server and the volumes according to the
Recovery procedure (TRBL13-11).

NOTICE: If the firmware version is 88-02-04-x0/xx or later, the following volumes are blocked:
• DP-VOL for which Capacity Saving is enabled
• Deduplication system data volume (finger print)
• Deduplication system data volume (data store)
These volumes are automatically recovered from the blockade by performing the
Recovery procedure (TRBL13-11).

NOTICE: If the firmware version is earlier than 88-02-04-x0/xx, check whether there is a DP-
VOL for which Capacity Saving is enabled according to the instruction below. If such
a volume exists, contact the Technical Support Division.

[Procedure for checking for DP-VOLs with Capacity Saving enabled]

The volume whose [Capacity Saving] is shown as Compression or Deduplication
and Compression in the Logical Devices window of Web Console is the DP-VOL
with Capacity Saving enabled.
• The [Capacity Saving] column is not displayed by default. Display the [Capacity
Saving] column by using the [Column Settings] button (for details, see “System
Administrator Guide”).
• To display only the DP-VOLs with Capacity Saving enabled, specify the column
value for the filter. For more details about filtering, refer to “System Administrator
Guide”.

NOTICE: When key encryption key or encryption key acquisition at the time of DKC start is
failed, DKB/ENC/HDD replacement, CEK Rekey, enabling/disabling data encryption
at parity group, initializing encryption environmental settings will be failed. Please
restore the DKC before replacement according to the Recovery procedures
(TRBL13-11).

TRBL13-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL13-10A

NOTICE: Be sure to restore the connection to the external key server with which the storage
system communicated last time. If the external key server is in a cluster configuration,
restore the connection when the primary server is not switched to the secondary
server (the same condition as the last time the storage system communicated).

TRBL13-10A
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL13-11

Recovery procedure
(1) Checking the connection with the key management server
Check that the LAN cable between the SVP and the key management server is properly connected.
Then, ask a user who has the Security Administrator role (View & Modify) to click [Sever
Configuration Test: Check] of Edit Encryption Environmental Settings of Web Console or Storage
Navigator.
• When the check result of the server configuration test shows a normal state, go to Step (4).
• When the check result of the server configuration test shows an error message, go to Step (2).

(2) Restoring the connection with the external key management server
The SVP fails in acquiring the key from the key management server when the DKC is started.
Ask the customer to check and restore the connection between the SVP and the key management
server according to the error message shown in the server configuration test and the following table
that shows major causes of the key acquisition failure.
Category Cause of failure Action
Problem of network The key management server is not Run the key management server.
running.
There is a problem in a Perform recovery actions appropriate
communication path between the for cause of failure.
SVP and the key management server. * When editing the encryption
Examples: environmental settings to recover
• The LAN cable is disconnected or the connection between the SVP
damaged. and the key management server, do
• Firewall blocks communications. not change the host name and port
• The network circuit is overloaded. number of the key management
• Network devices are damaged or server. If they are changed, data
not running. in the storage system might not be
able to be decoded.
Problem of client The client certificate of the SVP is Update the certificates to the
certificate expired. appropriate ones.
The client certificate of the key
management server is expired.
The client certificate of the SVP is
invalid .
The client certificate of the key
management server is invalid .
The client certificate of the SVP is
updated and the Common Name in
the client certificate after the update
is different from the Common Name
of the client certificate before the
update.
Other The key encryption key and If the deleted keys cannot be
encryption key are deleted from the restored, contact the Technical
key management server. Support Division.

TRBL13-11
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL13-12

(3) Checking the connection with the key management server

Perform the server configuration test using the same procedure as Step (1) to check that the
connection between the SVP and the key management server is established.

(4) Restoring the DKC

Power off the DKC, and then power on the DKC. Then, check that all volumes are restored.
If the DKC is not restored, contact the Technical Support Division.

TRBL13-12
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL13-20

13.2 Recovery procedure for Encryption key threshold warning and depletion (SIM =
660100, 660200)
The rest of Encryption Keys are less than threshold warning level or zero. If there is no free encryption key,
drive installation, drive replacement and DKB/DKBN/CTL replacement fails. Please give notice to customer
and ask them to create encryption keys.

The following SIMs are reported:

SIM = 660100 : This SIM is reported when there is no free encryption key.
SIM = 660200 : This SIM is reported when the rest of free encryption key is less than warning threshold
level (*1).
*1: The threshold level is variable number that depends on the number of installed spare drives and the
number of installed DKBs/DKBNs/CTLs. (Refer to the following table.)
VSP E590 VSP E990 VSP E1090 VSP G350/F350 VSP G700/F700
VSP E790 VSP G370/F370 VSP G900/F900

Spare Drive 1 encryption key 1 encryption key 1 encryption key 1 encryption key 1 encryption key
per drive per drive per drive per drive per drive
CTL 6 encryption keys 0 encryption key 0 encryption key 3 encryption keys 0 encryption key
per CTL per CTL per CTL per CTL per CTL
DKB 3 encryption keys 3 encryption keys 3 encryption keys
per DKB per DKB per DKB
DKBN 3 encryption keys 3 encryption keys
per DKBN per DKBN
Eg.) When one spare drive, two CTSs, and two DKBs are installed in VSP E790, the threshold
level is 19 (= 1+6x2+3x2).

The recovery procedure is as follows.

When this SIM occurs at the time of Initialize Encryption Environmental Settings, this recovery procedure is
not necessary.
1. Give notice to customer
• If there is no free encryption key, drive installation, drive replacement and DKB/DKBN/CTL
replacement fails. Please give notice to customer and ask them to create encryption keys. The creation
of the maximum number of keys is recommended.
If operations using Encryption License Key (see Encryption License Key User Guide) are performed
without creating encryption keys, the SIM will be reported again.
• A user who have Security Administrator (View & Modify) role can create encryption keys.
• The following number of keys are needed
Drive installation, drive replacement : 1 encryption key per drive
DKB replacement : 3 encryption keys per DKB
DKBN replacement : 2 encryption keys per DKBN
CTL replacement : 4 encryption keys per CTL (for VSP E590/E790)
: 3 encryption keys per CTL (for VSP G350/F350)
: 3 encryption keys per CTL (for VSP G370/F370)
: 0 encryption key per CTL (for other models)

TRBL13-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL13-30

13.3 Recovery procedure of DKB failure when restoring Encryption Keys

If the latest Encryption Keys have not been restored for the reason that Certificate Encryption Keys have
been rekeyed after the backup, encryption DKB may be blocked.
Please execute not the dummy replacement but the replacement all encryption DKBs under technical support
divisionʼs guidance, even if not all encryption DKBs are blocked.

TRBL13-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL14-10

14. MP Blockade Reset Function

1. Usage Guideline
• This is a special function to recover a MP blockade operation without the need to self-replace the card
under certain conditions specified below.
• To use this function, please open a case with your Technical Support Division and proceed under their
guidance.

2. Usage Conditions
• To recover a MP in which WCHK1 occurred due to a Firmware.
Eg.) Cache of WCHK1 is EC = 1644.
• Requested as a recovery procedure for an issue notified by an Early Notice/Alert.
• Requested by following the procedure described in Maintenance Manual.

Not to be used to recover hardware failures.

3. MP Reset Procedure Flowchart

START

Are Usage No
Conditions in 2 satisfied?

Yes
Refer Restoring Failed MP (MPC05-
1240) and execute restoring failed MP
procedures.

Are
restoring failed MP No
procedures finished?
Execute replace or self-replace under
Yes technical support divisionʼs guidance.

END

TRBL14-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-10

15. Forced Outage and Restart of DKC/DB

• This operation supposes a special case such as a recovery from a failure unlike the usual
powering off operation. Do not perform this operation without a direction given by the T.S.D.
because a system down may be caused if it is performed without due notice.

There are four ways of Forced Powering Off. Please refer to a way which is appropriate for your work.

Storing data Turning off

Volatilizing data in SM/
No. Section Title in SM/CM in DB Page
CM
CFMs (*1) breakers
1 Forced Outage and Restarting Non-volatilization Yes Yes TRBL15-20
Procedure for Non-Volatile (Data in SM/CM is (*2)
restored from CFMs.)
2 Forced volatilization (full) Volatilization No Yes TRBL15-80
power-off and restarting (All data in SM/CM is (*4)
procedure 1-1 deleted.)
3 Forced volatilization (full) Volatilization No Yes TRBL15-100
power-off and restarting (All data in SM/CM is
procedure 1-2 deleted.)
5 Forced volatilization (part) Volatilization Yes No TRBL15-130
power-off and restarting (Only specific data (*3) (*5)
procedure 2-1 in SM/CM is restored
from CFMs.)
6 Forced volatilization (part) Volatilization Yes Yes TRBL15-150
power-off and restarting (Only specific data (*3) (*2)
procedure 2-2 in SM/CM is restored
from CFMs.)
*1: When data in SM/CM is stored in CFMs, batteries are used. Therefore, energy in batteries is
consumed.
*2: If data in SM/CM cannot be stored in CFMs, No.1 and No.5 ways are not available.
Check that Battery/CFM is normal in advance.
*3: Only management information of both Quick Format and HDP is restored from CFMs. The other
data in SM/CM is deleted.
*4: Forced volatilization (full) procedure 1-2 is a procedure when the system parameter editing is
impossible.
When the editing is possible, use Procedure 1-1 in accordance with the instructions by the
Technical Support Division.
*5: Forced volatilization (part) procedure 2-2 is a procedure when PSOFF is impossible. To execute
PSOFF, use Procedure 2-1 in accordance with the instructions by the Technical Support Division.

TRBL15-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-20

15.1 Non volatilization power-off and restarting procedure

When this procedure is executed, the AC input of the power supply of the DKC and the DB is compulsorily
cut off, and the power supply is turned off immediately. The data in the CM is stored to the CFM, and is
restored to the cache memory after restart.
To restart system of SM/CM volatilizing, refer to “15.2 Forced volatilization (full) power-off and restarting
procedure 1-1” and “15.3 Forced volatilization (full) power-off and restarting procedure 1-2”.

• This operation supposes a special case such as a recovery from a failure unlike the usual
powering off operation. Do not perform this operation without a direction given by the T.S.D.
because a system down may be caused if it is performed without due notice.
• Check that A jumper used for cache memory volatilization is not Enable before performing the
operation. If you perform it in the Enable status, a customer data loss may be caused.

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

TRBL15-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-30

3. Turn off the PDU breakers that are connected to the DKC.

4. Turn off the PDU breakers that are connected to the CHBB if it is installed.

Figure 15-1 Turning Off PDU Breaker

PDU
Breaker

CB200

PDU
OFF

CB100
PDU

Rear view of rack frame Front view of PDU

For information about the Hitachi Universal V2 rack used with HDS VSP storage systems, refer to the
Hitachi Universal V2 Rack Reference Guide, MK-97RK000-00.

TRBL15-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-40

5. Turn off the PDU breakers that are connected to the DB.

Figure 15-2 Turning Off PDU Breaker

PDU
Breaker

CB200

PDU
OFF

CB100
PDU

Rear view of rack frame Front view of PDU

TRBL15-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-50

6. Wait for 30 seconds or more until the BACKUP STS LED in off state starts blinking at low speed (On
and off are repeated at 0.5-second intervals).

CBLH1/CBLH2/CBLHN/CBLMH4
Controller Board
BACKUP STS LED

Front of CBLH1/CBLH2/CBLHN/CBLMH4

CBSS/CBSL
Controller Board BACKUP STS LED

Rear of CBSS/CBSL

CBXSS/CBXSL
Controller Board

BACKUP STS LED

Rear of CBXSS/CBXSL

TRBL15-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.9 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-60

CBSN
Controller Board
BACKUP STS LED

Rear of CBSN

7. Turn on the PDU breakers that are connected to the DB.

8. Turn on the PDU breakers that are connected to the CHBB if it is installed.

Figure 15-3 Turning On PDU Breaker

PDU
Breaker

CB200

PDU
ON

CB100
PDU

Rear view of rack frame Front view of PDU

TRBL15-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-70

9. Turn on the PDU breakers that are connected to the DKC.

Figure 15-4 Turning On PDU Breaker

PDU
Breaker

CB200

PDU
ON

CB100
PDU

Rear view of rack frame Front view of PDU

10. After the Backup LED changes from blinking (low-speed) to going out, the Storage System power turns
on automatically.

TRBL15-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-80

15.2 Forced volatilization (full) power-off and restarting procedure 1-1

When this procedure is executed, the AC input of the power supply of the DKC and the DB is compulsorily
cut off, and the power supply is turned off immediately. Using this procedure, the data in the CM is not
stored to the CFM. Therefore, when you restart the system the SM/CM is volatile.
To restart the system and not to volatilize the SM/CM, refer to “15.1 Non volatilization power-off and
restarting procedure” (TRBL15-20).

• This operation supposes a special case such as a recovery from a failure unlike the usual
powering off operation. Do not perform this operation without a direction given by the T.S.D.
because a system down, loss of user data or loss of configuration information may be caused if
it is performed without due notice.
• The DKC processor failure forcible volatile warning (fffe0x) may occur during this work.
• The forced volatilization procedures have four types. Since the SM volatilization ranges differ,
follow the instructions by the Technical Support Division for which to work on.
• After this Operation was completed, please refer the FIRMWARE SECTION 5. Configuration
Information Restore/Initialization Procedure , and re-perform Config Version Up with the media
of the version same as Config on the device by all means.
• After completion of this procedure, if there is a parity group composed of Flash Module Drives
(FMD (NFHAx-QxxxSS)) in which LDEVs are not created, perform MAINTENANCE PC
SECTION [Link] Deleting Parity Group , INSTALLATION SECTION 4.3 Removing Drives ,
INSTALLATION SECTION 3.3 Adding Drives , and MAINTENANCE PC SECTION [Link]
Creating Parity Group .

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Enable.

4. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

5. Turn off the PDU breakers that are connected to the CHBB if it is installed.
à Refer to Figure 15-1 (TRBL15-30).

TRBL15-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-90

6. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

7. Wait for 30 seconds or more until the BACKUP STS LED goes out.

8. Turn on the PDU breakers that are connected to the DB.

à Refer to Figure 15-3 (TRBL15-60).

9. Turn on the PDU breakers that are connected to the CHBB if it is installed.
à Refer to Figure 15-3 (TRBL15-60).

10. Turn on the PDU breakers that are connected to the DKC.
à Refer to Figure 15-4 (TRBL15-70).

11. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and check that A
jumper used for cache memory volatilization is Disable. Turning off/on the Storage System changes A
jumper used for cache memory volatilization to Disable automatically. Be sure to confirm that the status
is Disable.
When using it in the Enable status, turning off the Storage System due to power outage or others may
cause a loss of the customer data.

TRBL15-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-100

15.3 Forced volatilization (full) power-off and restarting procedure 1-2

When this procedure is executed, the AC input of the power supply of the DKC and the DB is compulsorily
cut off, and the power supply is turned off immediately. Using this procedure, the data in the CM is not
stored to the CFM. Therefore, when you restart the system the SM/CM is volatile.
To restart the system and not to volatilize the SM/CM, refer to “15.1 Non volatilization power-off and
restarting procedure” (TRBL15-20).

• This operation supposes a special case such as a recovery from a failure unlike the usual
powering off operation. Do not perform this operation without a direction given by the T.S.D.
because a system down, loss of user data or loss of configuration information may be caused if
it is performed without due notice.
• The forced volatilization procedures have four types. Since the SM volatilization ranges differ,
follow the instructions by the Technical Support Division for which to work on.
• After this Operation was completed, please refer the FIRMWARE SECTION 5. Configuration
Information Restore/Initialization Procedure , and re-perform Config Version Up with the media
of the version same as Config on the device by all means.
• Do not change location of the Controller Board, Cache Memory or CFM after turning off the
PDU breakers because loss of user data or configuration information may be caused.
• After completion of this procedure, if there is a parity group composed of Flash Module Drives
(FMD (NFHAx-QxxxSS)) in which LDEVs are not created, perform MAINTENANCE PC
SECTION [Link] Deleting Parity Group , INSTALLATION SECTION 4.3 Removing Drives ,
INSTALLATION SECTION 3.3 Adding Drives , and MAINTENANCE PC SECTION [Link]
Creating Parity Group .

For CBSS/CBSL/CBLH1/CBLH2/CBLHN/CBLMH4

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

TRBL15-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-110

3. Remove the BKM or BKMF

When they are CBSS or CBSL, refer to LOCATION SECTION “[Link] BKM” to remove BKM-1 and
BKM-2.
When they are CBLH1, CBLH2, CBLHN, or CBLMH4, refer to LOCATION SECTION “[Link] BKMF”
to remove BKMF-13 and BKMF-23.

CBSS/CBSL CBLH1/CBLH2/CBLHN/CBLMH4

4. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

5. Turn off the PDU breakers that are connected to the CHBB if it is installed.
à Refer to Figure 15-1 (TRBL15-30).

6. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

7. Wait for 30 seconds or more until the BACKUP STS LED goes out.

TRBL15-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-111

8. Attach the BKM or BKMF

When they are CBSS or CBSL, refer to LOCATION SECTION “[Link] BKM” to attach BKM-1 and
BKM-2.
When they are CBLH1, CBLH2, CBLHN, or CBLMH4, refer to LOCATION SECTION “[Link] BKMF”
to attach BKMF-13 and BKMF-23.

CBSS/CBSL CBLH1/CBLH2/CBLHN/CBLMH4

9. Turn on the PDU breakers that are connected to the DB.

à Refer to Figure 15-3 (TRBL15-60).

10. Turn on the PDU breakers that are connected to the CHBB if it is installed.
à Refer to Figure 15-3 (TRBL15-60).

TRBL15-111
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-120

11. Turn on the PDU breakers that are connected to the DKC.
à Refer to Figure 15-4 (TRBL15-70).

12. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On”, and turn on the main switch.

For CBXSS/CBXSL

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

4. Wait for 30 seconds or more until the BACKUP STS LED blinks.

5. While the BACKUP STS LED is blinking, remove the Controller Board 1 and Controller Board 2 (see
LOCATION SECTION “2.4.3 Parts Location of CBXSS/CBXSL”).

6. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

7. Install the Controller Board 1 and Controller Board 2 (see LOCATION SECTION “2.4.3 Parts Location
of CBXSS/CBXSL”).

8. Turn on the PDU breakers that are connected to the DB.

à Refer to Figure 15-3 (TRBL15-60).

9. Turn on the PDU breakers that are connected to the DKC.

à Refer to Figure 15-4 (TRBL15-70).

10. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On”, and turn on the main switch.

TRBL15-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-121

For CBSN

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

4. Wait for 30 seconds or more until the BACKUP STS LED blinks.

5. While the BACKUP STS LED is blinking, remove the Controller Board 1 and Controller Board 2 (see
LOCATION SECTION “2.4.4 Parts Location of CBSN”).

6. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

7. Install the Controller Board 1 and Controller Board 2 (see LOCATION SECTION “2.4.4 Parts Location
of CBSN”).

8. Turn on the PDU breakers that are connected to the DB.

à Refer to Figure 15-3 (TRBL15-60).

9. Turn on the PDU breakers that are connected to the DKC.

à Refer to Figure 15-4 (TRBL15-70).

10. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On”, and turn on the main switch.

TRBL15-121
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-130

15.4 Forced volatilization (part) power-off and restarting procedure 2-1

Performing this work forcibly disconnects the AC input of DKC and DB power. It does not only turn off the
power immediately but also does not recover the save data on the Cache SSD on the SM/CM. Therefore, the
SM/CM volatilizes after restarting.

• This operation supposes a special case such as a recovery from a failure unlike the usual
powering off operation. Do not perform this operation without a direction given by the T.S.D.
because a system down, loss of user data or loss of configuration information may be caused if
it is performed without due notice.
• The DKC processor failure forcible volatile warning (fffe0x) may occur during this work.
• The forced volatilization procedures have four types. Since the SM volatilization ranges differ,
follow the instructions by the Technical Support Division for which to work on.
• After this Operation was completed, please refer the FIRMWARE SECTION 5. Configuration
Information Restore/Initialization Procedure , and re-perform Config Version Up with the media
of the version same as Config on the device by all means.
• Do not change location of Cache Memory and CFM after turning off the PDU breakers because
loss of user data or configuration information may be caused.

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Refer to INSTALLATION SECTION “1.5.2 Storage System Power Off (Planned Shutdown)” and turn
off the main switch. Press the main switch on the front of the Controller Chassis for about three seconds
to turn it off.

4. Check that the POWER LED on the front of the Storage System changes from green to amber.
It takes about 10 minutes at a maximum to change the LED to amber. After the POWER LED lights up in
amber, the ACT LED (green) on the Drive may be blinking, but it is not a problem.

5. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Enable.

TRBL15-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-140

6. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On” and turn on the main switch.

7. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Disable.

TRBL15-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-150

15.5 Forced volatilization (part) power-off and restarting procedure 2-2

Performing this work forcibly disconnects the AC input of DKC and DB power. It does not only turn off the
power immediately but also does not recover the save data on the Cache SSD on the SM/CM. Therefore, the
SM/CM volatilizes after restarting.

• This operation supposes a special case such as a recovery from a failure unlike the usual
powering off operation. Do not perform this operation without a direction given by the T.S.D.
because a system down, loss of user data or loss of configuration information may be caused if
it is performed without due notice.
• The DKC processor failure forcible volatile warning (fffe0x) may occur during this work.
• The forced volatilization procedures have four types. Since the SM volatilization ranges differ,
follow the instructions by the Technical Support Division for which to work on.
• After this Operation was completed, please refer the FIRMWARE SECTION 5. Configuration
Information Restore/Initialization Procedure , and re-perform Config Version Up with the media
of the version same as Config on the device by all means.
• Do not change location of the Controller Board, Cache Memory or CFM after turning off the
PDU breakers because loss of user data or configuration information may be caused.

For CBSS/CBSL/CBLH1/CBLH2/CBLHN/CBLMH4

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

4. Turn off the PDU breakers that are connected to the CHBB if it is installed.
à Refer to Figure 15-1 (TRBL15-30).

5. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

6. Wait until the BACKUP STS LED changes from blinking (low-speed) to going out.
Note that it takes about 20 minutes at a maximum until all LEDs go out.

TRBL15-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-160

7. Remove the CFM.

When they are CBSS or CBSL, refer to LOCATION SECTION “2.4.1 Parts Location of CBSS/CBSL” to
remove CFM-1 and CFM-2.
When they are CBLH1, CBLH2, CBLHN, or CBLMH4, refer to LOCATION SECTION “2.4.2 Parts
Location of CBLH1/CBLH2/CBLHN/CBLMH4” to remove CFM-10 and CFM-20.

8. Turn on the PDU breakers that are connected to the DB.

à Refer to Figure 15-3 (TRBL15-60).

9. Turn on the PDU breakers that are connected to the CHBB if it is installed.
à Refer to Figure 15-3 (TRBL15-60).

10. Turn on the PDU breakers that are connected to the DKC.
à Refer to Figure 15-4 (TRBL15-70).

11. Take an interval of 30 seconds or more.

12. Attach the CFM.

When they are CBSS or CBSL, refer to LOCATION SECTION “2.4.1 Parts Location of CBSS/CBSL” to
attach CFM-1 and CFM-2.
When they are CBLH1, CBLH2, CBLHN, or CBLMH4, refer to LOCATION SECTION “2.4.2 Parts
Location of CBLH1/CBLH2/CBLHN/CBLMH4” to attach CFM-10 and CFM-20.

13. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Enable.

14. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On”, and turn on the POWER ON/
OFF switch.

15. Wait until it becomes READY.

16. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Disable.

TRBL15-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-170

For CBXSS/CBXSL

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

4. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

5. Wait until the BACKUP STS LED changes from blinking (low-speed) to going out.
Note that it takes about 20 minutes at a maximum until all LEDs go out.

6. Remove the Controller Board 1 and Controller Board 2 (see LOCATION SECTION “2.4.3 Parts Location
of CBXSS/CBXSL”).

7. Remove the CFM-1 and CFM-2 (see LOCATION SECTION “2.4.3 Parts Location of CBXSS/CBXSL”).

8. Install the Controller Board 1 and Controller Board 2 (see LOCATION SECTION “2.4.3 Parts Location
of CBXSS/CBXSL”).

9. Turn on the PDU breakers that are connected to the DKC.

à Refer to Figure 15-4 (TRBL15-70).

10. Take an interval of 30 seconds or more.

11. Turn off the PDU breakers that are connected to the DKC.
à Refer to Figure 15-1 (TRBL15-30).

12. Remove the Controller Board 1 and Controller Board 2 (see LOCATION SECTION “2.4.3 Parts Location
of CBXSS/CBXSL”).

13. Install the CFM-1 and CFM-2 (see LOCATION SECTION “2.4.3 Parts Location of CBXSS/CBXSL”).

14. Install the Controller Board 1 and Controller Board 2 (see LOCATION SECTION “2.4.3 Parts Location
of CBXSS/CBXSL”).

TRBL15-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-180

15. Turn on the PDU breakers that are connected to the DB.
à Refer to Figure 15-3 (TRBL15-60).

16. Turn on the PDU breakers that are connected to the DKC.
à Refer to Figure 15-4 (TRBL15-70).

17. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Enable.

18. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On”, and turn on the POWER ON/
OFF switch.

19. Wait until it becomes READY.

20. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Disable.

TRBL15-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL15-190

For CBSN

1. Display “Maintenance Utility” window.

2. Check all CFMs and batteries in the storage system for failures.

<When any of the parts have failures>

Remove the failures from the parts, and then go back to Step 1, unless otherwise instructed by T.S.D.

<When none of the parts has any failure or when all failures are already removed from the parts>
Close the “Maintenance Utility” window, and then go to the next step.

3. Turn off the PDU breakers that are connected to the DKC.

à Refer to Figure 15-1 (TRBL15-30).

4. Turn off the PDU breakers that are connected to the DB.

à Refer to Figure 15-2 (TRBL15-40).

5. Wait until the BACKUP STS LED changes from blinking (low-speed) to going out.
Note that it takes about 20 minutes at a maximum until all LEDs go out.

6. Remove the CFM-1 and CFM-2 (see LOCATION SECTION “2.4.4 Parts Location of CBSN”).

7. Turn on the PDU breakers that are connected to the DB.

à Refer to Figure 15-3 (TRBL15-60).

8. Turn on the PDU breakers that are connected to the DKC.

à Refer to Figure 15-4 (TRBL15-70).

9. Take an interval of 30 seconds or more.

10. Install the CFM-1 and CFM-2 (see LOCATION SECTION “2.4.4 Parts Location of CBSN”).

11. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Enable.

12. Refer to INSTALLATION SECTION “1.5.1 Storage System Power On”, and turn on the main switch.

13. Wait until it becomes READY.

14. Refer to MAINTENANCE PC SECTION “3.16 Edit or Confirm System Parameters” and change A
jumper used for cache memory volatilization to Disable.

TRBL15-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL16-10

16. Recovery Procedure for GUM Information Recover Failure (SIM =

7d08xx)
SIM = 7d08xx

START

Are SIMs Yes

reported at the time of CTL
replacement?
Is SIM
= 7d0axx reported at Yes
No
the same time as SIM =
7d08xx? If you check and find that the alert
No settings are initialized, make the
settings again (see 26. Procedure
Open the [CFM] tab in the Controller When Alert Settings Are Initialized
Chassis window of Maintenance Utility and due to a Failure At the Time of CTL
check the status of all displayed CFMs. Replacement ).

Is the status No END

of all the displayed CFMs
Normal? Replace the CFM that indicates
the error. (See REPLACEMENT
Yes
SECTION 2.10 Replacing a Cache
Perform [GUM reboot] from Flash Memory (CFM) )
Maintenance Utility of the CTL that
output SIM. (See MAINTENANCE
PC SECTION 3.18 Reboot GUM )
END
Is
the [GUM reboot] No
processing completed
normally? Press the [LAN-RST] switch of
the CTL indicated by SIM to reset
Yes GUM. (See MAINTENANCE PC
SECTION 3.26 Resetting GUM )

Wait for about five minutes, and then

log into Maintenance Utility of the
CTL that output SIM again. (*1)

Does SIM = 7d08xx Yes

occur again?

No T.S.D Call

END

*1: If you cannot log in, wait for about one to two minutes to log in again. It might take a maximum of
20 minutes to be able to log in.
If you still cannot log in Maintenance Utility, login as the maintenance user by the customer
might fail repeatedly. Ask the customer whether that is occurring. After the customer can log in
successfully, try to log in again.
TRBL16-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL17-10

17. Recovery Procedure for GUM Version Warning (SIM = 7d0axx)

SIM = 7d0axx

START

Does SIM occur by No

replacing the CTL?

Yes

Is SIM
= 7d08xx reported at Yes
the same time as SIM =
7d0axx? If you check and find that the alert
No settings are initialized, make the
settings again (see 26. Procedure
Select [Firmware] from the When Alert Settings Are Initialized
Administration menu of Maintenance due to a Failure At the Time of CTL
Utility to display firmware versions. Replacement ).

Is
the GUM
firmware version
displayed in the following format? No
CTL1: <GUM firmware version>
CTL2: <GUM firmware
version> END

Yes
By using the Maintenance
Utility window that is opened for
maintenance operation of the CTL Does SIM occur by Yes
replacement, release the system lock updating the firmware?
(*) (TRBL02-530), and then reboot Perform [Recovery procedure when
the GUM (see MAINTENANCE PC No these conditions (Upload files is
SECTION 3.18 Reboot GUM ). 100%, the progress (xx%) of Update
*: Regardless of whether [System firmware has not changed for over
Locked] or [System Unlocked] 2 30 minutes, and the GUM status is
is displayed as the system lock Updating ) are met during the firmware
(TRBL17-20)
status, release the system lock update] (FIRM04-81) in FIRMWARE
forcibly. SECTION 4.1 Recovery Procedure in
Online Menu Was Selected .
Retry the CTL replacement by using
the same CTL.
END

See 2.2.1 Error Recovery Procedure

when Removing/Inserting CTL .
Is the CTL No
replacement completed
normally?

Yes

1 (TRBL17-20)

TRBL17-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL17-20

1
Retry the CTL replacement by using
a new CTL.
Perform [GUM reboot] from
Maintenance Utility of the CTL that
output SIM. (See MAINTENANCE
PC SECTION 3.18 Reboot GUM ) Is the CTL Yes
replacement completed
normally?
Wait for about five minutes, and then
log into Maintenance Utility of the END
CTL that output SIM again. (*1) No
Select [Firmware] in the 2
Administration menu to display the
firmware version.
Use the installation media for the SVP, which comes with the Storage
System and is owned by the customer, to update only the GUM firmware
online from Maintenance Utility. (*2) (See FIRMWARE SECTION
Is the GUM 3.3.1 Updating Firmware of the Storage System .)
firmware version • Even when the GUM firmware update downgrades its version because
displayed in the following the GUM firmware version on the replaced CTL is new, Warning is
Yes not displayed, and the Password window does not appear.
format?
CTL1: <GUM firmware version> • Since this is the update to the same version of the firmware running
CTL2: <GUM firmware in the Storage System, a performance is not affected by rebooting MP
version> described in FIRM03-150 (Table 3-3 ).
• Set the Update Type to Online (default) and the Reboot pattern to By
1/4 (default).
No • Check the checkbox for Forcibly upload the firmware. in Step 5 in
FIRMWARE SECTION 3.3.1 Updating Firmware of the Storage
END System .

No See FIRMWARE SECTION 4.1

Did [online firmware
Recovery Procedure in Online Menu
exchange] success?
Was Selected .

Yes

Display the
firmware version again.
Is GUM version displayed as the Yes
following format?
CTL1: xx-xx-xx/xx
CTL2: xx-xx-xx/xx
T.S.D Call

No

END

*1: If you cannot log in, wait for about one to two minutes to log in again. It might take a maximum of
20 minutes to be able to log in.
*2: You can update only the GUM firmware regardless of whether you use Maintenance Utility or
[Link] in the installation media when performing the firmware update.
To update only the GUM firmware, check only the checkbox of GUM when confirming the
updated contents of the firmware.

TRBL17-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.15 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-10

18. Recovery from Global-active Device Functions Failure

18.1 Recovery Procedure for Global-active Device Functions Failure
Failure suspension of a GAD pair, path block between a GAD pair, and Quorum Disk block may occur
triggered by hardware failure and so on. This chapter shows explanation and recovery procedures of failure
in GAD functions.
Failure occurrence in GAD functions can be detected by the following.
• SIM report of failure suspension of a GAD pair
• SIM report of path block between a GAD pair
• SIM report of Quorum Disk block

Table 18-1 GAD SIM [Link]

SIM [Link] Meaning Remarks
ddxyzz Failure suspension of a GAD pair X: Failure suspension type (0 to 3)
Y: The lowest digit of CU number
ZZ: LDEV number
2180-xy Path block between a GAD pair X: CHB PCB #
Y: Port# in PCB
dee0xx Quorum Disk recovery XX: Quorum Disk ID
def0xx Quorum Disk block XX: Quorum Disk ID

The following flow charts describe recovery procedures for each type of failure in GAD.
When a failure occurs during data migration by using GAD pairs in the environment where GAD pairs
are already being operated (there are GAD pairs created by using one LDEV for two mirrors), follow the
troubleshooting procedures described in Global-Active Device User Guide.
Additionally, the failure recovery procedure at path block occurrence between a GAD pair is identical with
the failure recovery procedure in TrueCopy function, and the procedure is described in TRBL06-40.

TRBL18-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-20

18.1.1 Recovery Procedure at Failure Suspension of a GAD Pair (SIM = ddxyzz)

NOTE: • In the following procedure, ask SE or the customer to check the pair status and I/O mode of the
GAD pair. For the procedure, see “How to check pair status and I/O mode of GAD pair”.
• If you contact the Technical Support Division in the following procedure, see “Dump collection in
this recovery procedure” to collect dumps.

START

Is there
Yes
Quorum failure? SIM =
def0xx
Recover Quorum failure.
No (See “18.1.5 Recovery Procedure
at Quorum Disk Failure (SIM =
def0xx)”.)

Is there path
Yes
failure between DKC?
SIM=2180xy
Recover path failure between
No DKC. (See TRBL06-40)

If any parts other than the above

failed, recover the failed parts
according to the respective
recovery procedures. (*1)

Check pair status and I/O mode of

the GAD PVOL/SVOL from the
Web Console.

I/O mode of the No

2
PVOL = Local?
(TRBL18-40)

Yes

1
(TRBL18-30)

TRBL18-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-30

Yes Pair status of the SVOL

= PSUE?

No

Pair status of the SVOL No

= PAIR?

Yes

I/O mode of the SVOL No

= Block?

Yes
Designate the GAD SVOL to
suspend (swap suspend). (*6)

Pair status of the SVOL No

= PSUE?
Delete the path from servers to the
Yes GAD SVOL. (*5)

Designate the GAD PVOL to Forced deletion (Disable) from

resynchronize. (*4) (*7) the Web Console or the Command
Control Interface (CCI) of the GAD
SVOL. (*2)

Is it normally No
Forced deletion (Enable) from the
resynchronized?
Web Console or the Command
Control Interface (CCI) of the GAD
Yes PVOL. (*3)
Recover the path from servers to the
GAD SVOL. (*4) Designate the GAD PVOL to create
a pair. (*4) (*7)

END
No
Is it normally created?

T.S.D. call Yes

Add a path from servers to the GAD
SVOL. (*4)

END

TRBL18-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-40

I/O mode of the SVOL No

3
= Local?
(TRBL18-50)

Yes

Pair status of the PVOL No

= PSUE?
Delete the path from servers to the
Yes GAD PVOL. (*5)
Designate the GAD SVOL to
resynchronize (swap resync). (*4) (*7) Forced deletion (Disable) from
the Web Console or the Command
Control Interface (CCI) of the GAD
PVOL. (*2)
Is it normally No
resynchronized?
Forced deletion (Enable) from the
Web Console or the Command
Yes T.S.D. call Control Interface (CCI) of the GAD
Recover the path from servers to the SVOL. (*3)
former PVOL. (*4)
Designate the GAD SVOL to create
Swap the GAD PVOL/SVOL. (*4) a pair. (*4) (*7)

END No
Is it normally created?

Yes T.S.D. call

Add a path from servers to the GAD
SVOL. (*4)

Swap the GAD PVOL/SVOL. (*4)

END

TRBL18-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-50

I/O mode of the PVOL No

= Block?

Yes

I/O mode of the SVOL No

= Block?

Yes T.S.D. call

Is the firmware version No

93-05-02-x0-xx or later or 88-08-05-x0/
xx or later?
Forced deletion (Enable) from the
Web Console or the Command
Yes Control Interface (CCI) of the GAD
PVOL (*3)
With Web Console or RAID Manager,
change the I/O mode of the volumes
for which you want to resume the Recover the path from servers to the
operation to Local. (*4) GAD PVOL. (*4)

Examine data in the GAD PVOL.

Resynchronize the pair of the volumes
(*4)
for which you changed the I/O mode
to Local. (*4)

Is the resynchronization No (TRBL18-60)

successful?

Yes

END T.S.D. call

TRBL18-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-60

No
PVOL data is the latest?

Delete the path from servers to the

Yes GAD PVOL. (*5)
Delete the path from servers to the
GAD SVOL. (*5) Forced deletion (Enable) from the
Web Console or the Command
Forced deletion (Disable) from Control Interface (CCI) of the GAD
the Web Console or the Command SVOL. (*3)
Control Interface (CCI) of the GAD
SVOL. (*2) Recover the path from servers to the
GAD SVOL. (*4)
Create a pair from the GAD PVOL.
(*4) (*7) Examine data in the GAD SVOL.
(*4)

No
Is it normally created?
No
SVOL data is the latest?

Yes
Add a path from servers to the GAD Yes
SVOL. (*4) Delete virtual ID of the GAD PVOL.
(*4)

END Create a pair from the GAD SVOL.

(*4) (*7)

No
Is it normally created?

Yes
T.S.D. call Add a path from servers to the GAD
PVOL. (*4)

Swap the GAD PVOL/SVOL. (*4)

END

TRBL18-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-61

*1: When an LDEV is blocked in a GAD pair, recover in accordance with the recover procedure at
LDEV block occurrence (TRBL18-80).
*2: When pair status of the GAD pair is released and it is the status of the GAD reserved volume,
forced deletion (Disable) is unnecessary.
*3: When pair status of the GAD pair is released and it is the status of the GAD reserved volume, ask
the customer to configure virtual LDEV ID instead of forced deletion (Enable).
*4: Ask the customer to perform operation.
*5: Ask the customer to perform operation. When the path cannot be deleted, perform the next step.
*6: Ask the customer to perform operation. Even if using consistency group, perform suspend
operation for each pair.
*7: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD pair is successful,
creating or resynchronizing a TC/UR/GAD pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create or
resynchronize the pair.

TRBL18-61
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-70

How to check pair status and I/O mode of GAD pair

1. For Web Console
Expand the Storage Systems tree, click [Replication]-[Remote Replication], and then select the [GAD
Pairs] tab.
In the displayed list of GAD pairs, see [Status] to check the pair status, and [I/O Mode] in the [Local
Storage System] table to check the I/O mode.

2. For RAID Manager

Execute the pairdisplay command. The following is a command example:
pairdisplay -g oraHA -fcxe -IH1
“oraHA” indicates the group name defined in the configuration definition file, and “-IH1” indicates the
instance number 1.
In the execution result, the “Status” column shows the pair status, and the “R/W” column shows the I/O
mode.

3. I/O mode terms displayed in Web Console and RAID Manager

The following table lists the I/O mode terms described in this procedure and those displayed in the Web
Console and the RAID Manager.

Term in this procedure Term in Web Console Term in RAID Manager

Mirror Mirror (Read Local) L/M
Local Local L/L
Block Block B/B

Dump collection in this recovery procedure

Before contacting the Technical Support Division, collect dumps from both MCU and RCU by
performing Auto Dump.
For the procedure, see MAINTENANCE PC SECTION “5.2 Dump”.
When performing Auto Dump, specify “Normal” for the dump type.
However, if the performance of the storage system is deteriorated when the error occurs, specify “Monitor”
for the dump type.

TRBL18-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-80

18.1.2 Recovery Procedure at LDEV Block in the GAD Pair (SIM = 3a0xyy, db8xxx,
db9xxx, dbaxxx, dbbxxx, dfaxxx, dfbxxx, ef8xxx, ef9xxx)

NOTE: • In the following procedure, ask SE or the customer to check the pair status and I/O mode of the
GAD pair. For the procedure, see “How to check pair status and I/O mode of GAD pair”.
• If you contact the Technical Support Division in the following procedure, see “Dump collection in
this recovery procedure” to collect dumps.

START

LDEV
is blocked in the
PVOL? No
SIM = 3a0xyy/db8xxx/db9xxx/dbaxxx/ 1
dbbxxx/dfaxxx/dfbxxx/ (TRBL18-90)
ef8xxx/ef9xxx

Yes

I/O mode of the SVOL No

2
= Local or Mirror?
(TRBL18-81)
Yes
Delete the path from servers to the GAD
PVOL. (*4)

Delete the pair from the Web Console of the

GAD SVOL. (*3)

Recover in accordance with the recovery

procedure of LDEV block.
• 3a0xyy : TRBL03-140
• db8xxx, db9xxx, dbaxxx, dbbxxx, dfaxxx,
dfbxxx, ef8xxx, ef9xxx : TRBL03-300

Create a pair from the GAD SVOL. (*3) (*6)

Is it normally No
created?

Yes
T.S.D. call
Add a path from servers to the GAD PVOL.
(*3)

Swap the GAD PVOL/SVOL. (*3)

END

TRBL18-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-81

No I/O mode of the

SVOL = Block?

Yes
Find the failure factor in the Web
Console. (*5)

Suspended
No
factor is other than Initial
Copy Failed?

Yes

Delete the path from servers to the

GAD PVOL. (*4)

Forced deletion (Disable) from

the Web Console or the Command
Control Interface (CCI) of the GAD
PVOL. (*1)

Forced deletion (Enable) from the

Web Console or the Command
Control Interface (CCI) of the GAD
SVOL. (*2)

Recover the path from servers to the

GAD SVOL. (*3)

SVOL data is the No

latest?
Recover data from backup data.
Yes (TRBL18-100)

3
(TRBL18-80) END

TRBL18-81
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-90

I/O No
mode of the PVOL = Local or
Mirror?
Delete the path from servers to the GAD
Yes
SVOL. (*4)
Delete the path from servers to the GAD
SVOL. (*4)
Forced deletion (Disable) from the Web
Console or the Command Control
Delete the pair from the Web Console of Interface (CCI) of the GAD SVOL. (*1)
the GAD PVOL. (*3)

Forced deletion (Enable) from the Web

Console or the Command Control
Recover in accordance with the recovery Interface (CCI) of the GAD PVOL. (*2)
procedure of LDEV block.
• 3a0xyy : TRBL03-140
• db8xxx, db9xxx, dbaxxx, dbbxxx, Recover the path from servers to the
dfaxxx, dfbxxx, ef8xxx, ef9xxx : GAD PVOL. (*3)
TRBL03-300
Examine data in the GAD PVOL. (*3)
Create a pair from the GAD PVOL.
(*3) (*6)
PVOL data is the No
latest?

Yes
Is it normally No
created? Recover data from backup data.
(TRBL18-100)
Yes
Recover the path from servers to the T.S.D. call
GAD SVOL. (*3)

END
*1: When pair status of the GAD pair is released and it is the status of the GAD reserved volume,
forced deletion (Disable) is unnecessary.
*2: When pair status of the GAD pair is released and it is the status of the GAD reserved volume, ask
the customer to configure virtual LDEV ID instead of forced deletion (Enable).
*3: Ask the customer to perform operation.
*4: Ask the customer to perform operation. When the path cannot be deleted, perform the next step.
*5: Ask SE or the customer to perform operation.
In the Web Console, expand the Storage Systems tree, click [Replication]-[Remote Replication],
select the [GAD Pairs] tab, and then click [More Actions]-[View Pair Properties]. Check [Failure
Factor] of [Pair Detail].
*6: If a failure occurs after capacity expansion of one volume of a GAD pair is successful, creating
a GAD pair in the procedure is not possible due to capacity inconsistency. Perform capacity
expansion so that the capacities are consistent, and then create the pair.

TRBL18-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-91

How to check pair status and I/O mode of GAD pair

1. For Web Console
Expand the Storage Systems tree, click [Replication]-[Remote Replication], and then select the [GAD
Pairs] tab.
In the displayed list of GAD pairs, see [Status] to check the pair status, and [I/O Mode] in the [Local
Storage System] table to check the I/O mode.

2. For RAID Manager

Execute the pairdisplay command. The following is a command example:
pairdisplay -g oraHA -fcxe -IH1
“oraHA” indicates the group name defined in the configuration definition file, and “-IH1” indicates the
instance number 1.
In the execution result, the “Status” column shows the pair status, and the “R/W” column shows the I/O
mode.

3. I/O mode terms displayed in Web Console and RAID Manager

The following table lists the I/O mode terms described in this procedure and those displayed in the Web
Console and the RAID Manager.

Term in this procedure Term in Web Console Term in RAID Manager

Mirror Mirror (Read Local) L/M
Local Local L/L
Block Block B/B

Dump collection in this recovery procedure

Before contacting the Technical Support Division, collect dumps from both MCU and RCU by
performing Auto Dump.
For the procedure, see MAINTENANCE PC SECTION “5.2 Dump”.
When performing Auto Dump, specify “Normal” for the dump type.
However, if the performance of the storage system is deteriorated when the error occurs, specify “Monitor”
for the dump type.

TRBL18-91
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-100

18.1.3 Procedure to Recover Data from Backup Data at LDEV Failure in the GAD
Environment

START

Recover in the No
1
PVOL?
(TRBL18-110)
Yes

Delete the path from servers to the GAD

SVOL. (*4)

Forced deletion (Disable) from the Web

Console or the Command Control
Interface (CCI) of the GAD SVOL. (*1)

Forced deletion (Enable) from the Web

Console or the Command Control
Interface (CCI) of the GAD PVOL. (*2)

Recover in accordance with the recovery

procedure of LDEV block.
• 3a0xyy : TRBL03-140
• db8xxx, db9xxx, dbaxxx, dbbxxx,
dfaxxx, dfbxxx, ef8xxx, ef9xxx :
TRBL03-300

Recover data in the PVOL from backup

data. (*3)

Recover the path from servers to the

GAD PVOL. (*3)

Create a pair from the Web Console of

the GAD PVOL. (*3) (*6)

Is it normally No
created?

Yes
Add a path from servers to the GAD T.S.D. call (*5)
SVOL. (*3)

END

TRBL18-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-101

*1: When pair status of the GAD pair is released and it is the status of the GAD reserved volume,
forced deletion (Disable) is unnecessary.
*2: When pair status of the GAD pair is released and it is the status of the GAD reserved volume, ask
the customer to configure virtual LDEV ID instead of forced deletion (Enable).
*3: Ask the customer to perform operation.
*4: Ask the customer to perform operation. When the path cannot be deleted, perform the next step.
*5: Before contacting the Technical Support Division, collect dumps from both MCU and RCU by
performing Auto Dump. For the procedure, see MAINTENANCE PC SECTION “5.2 Dump”.
When performing Auto Dump, specify “Normal” for the dump type.
However, if the performance of the storage system is deteriorated when the error occurs, specify
“Monitor” for the dump type.
*6: If a failure occurs after capacity expansion of one volume of a GAD pair is successful, creating
a GAD pair in the procedure is not possible due to capacity inconsistency. Perform capacity
expansion so that the capacities are consistent, and then create the pair.

TRBL18-101
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-110

Delete the path from servers to the GAD

PVOL. (*4)

Forced deletion (Disable) from the Recover data in the SVOL from backup
Web Console or the Command Control data. (*3)
Interface (CCI) of the GAD PVOL. (*1)
Recover the path from servers to the
Forced deletion (Enable) from the GAD SVOL. (*3)
Web Console or the Command Control
Interface (CCI) of the GAD SVOL. (*2)
Create a pair from the Web Console of
the GAD SVOL. (*3) (*6)
Recover in accordance with the recovery
procedure of LDEV block.
• 3a0xyy : TRBL03-140 Is it normally No
• db8xxx, db9xxx, dbaxxx, dbbxxx, created?
dfaxxx, dfbxxx, ef8xxx, ef9xxx :
TRBL03-300 Yes
T.S.D. call (*5)
Add a path from servers to the GAD
PVOL. (*3)

Swap the GAD PVOL/SVOL. (*3)

END

*1: When pair status of the GAD pair is released and it is the status of the GAD reserved volume,
forced deletion (Disable) is unnecessary.
*2: When pair status of the GAD pair is released and it is the status of the GAD reserved volume, ask
the customer to configure virtual LDEV ID instead of forced deletion (Enable).
*3: Ask the customer to perform operation.
*4: Ask the customer to perform operation. When the path cannot be deleted, perform the next step.
*5: Before contacting the Technical Support Division, collect dumps from both MCU and RCU by
performing Auto Dump. For the procedure, see MAINTENANCE PC SECTION “5.2 Dump”.
When performing Auto Dump, specify “Normal” for the dump type.
However, if the performance of the storage system is deteriorated when the error occurs, specify
“Monitor” for the dump type.
*6: If a failure occurs after capacity expansion of one volume of a GAD pair is successful, creating
a GAD pair in the procedure is not possible due to capacity inconsistency. Perform capacity
expansion so that the capacities are consistent, and then create the pair.

TRBL18-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-120

18.1.4 Recovery Procedure of the Pinned Track in the GAD Environment

NOTE: • In the following procedure, ask SE or the customer to check the pair status and I/O mode of the
GAD pair. For the procedure, see “How to check pair status and I/O mode of GAD pair”.
• If you contact the Technical Support Division in the following procedure, see “Dump collection in
this recovery procedure” to collect dumps.

START

Confirm the volume, in which the pinned

track occurs, from the Web Console.

Does it occur in No
the GAD pair?

Yes The No
failure occurs in Quorum
Disk?
Yes
Recover the error track.
(TRBL04-160)
2

No (TRBL18-140)
Is the volume a
GAD volume?

Yes

Does Pinned track exist No

outside the userʼs area? (*1)

Yes

Is the Capacity Saving setting of

Yes
the volume in which the pinned track has occurred
other than disabled?

No

Perform the Reclaiming the control Execute “4.2 Pinned track recovery”.(*2)
pages inside the DP-VOL. However, data recovery of the GAD pair is
(Refer to “3.52 Reclaiming the not included. (*3)
Control Pages Inside the DP-VOL”.)

1
(TRBL18-130)

TRBL18-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-121

*1: Indicates that a PIN event occurred in the management area if the CC (Cylinder) information or the
HH (Head) information of the PIN data displayed on the Maintenance PC was outside the userʼs
area. (The number of user cylinders can be referred on the ʻCustomized Volume Size Defineʼ of the
MPC Refer Configuration.)
*2: In the recovery from a pinned track, only the LDEV formatting is executed except in the case of
Solaris. For Solaris, only the correction of a pinned track by means of the analyze command is
executed. To recover the data of the GAD pair, reconfigure the GAD pair.
However, the LDEV formatting or the analyze command executing is not required if the pinned
track is a DP volume and out of the user area.
*3: The data of the GAD pair is recovered by reconfiguring the GAD pair.

TRBL18-121
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-130

Type of the ECC/LRC Error

pinned track?

Write Error Delete the GAD pair in which

the pinned track occurs.
Pair status = No
COPY?
Recover the Write error track
Yes according to “[Link] Write
Error”.
Suspend a pair from the Web
Console of the GAD PVOL. (*1)
When failure suspension
(SIM = dd0xyy/dd1xyy/
dd2xyy/dd3xyy) of a GAD
pair occurs, recover the GAD
pair in accordance with the
procedure of TRBL18-20.
Is it normally No Recover the ECC/LRC Error
suspended? track according to “[Link] ECC/
LRC Error”.
Yes However, data recovery of the
Recover the Write error track GAD pair is not included. (*3)
according to “[Link] Write
Error”.
If the GAD pair is deleted in the
workflow, reconfigure the GAD
Resynchronize from the Web pair. (*4)
Console of the GAD PVOL. (*1)
(*2)

Is it normally No
resynchronized?

Yes T.S.D. call

Recover the path from
servers to the GAD SVOL.
(*1)

END

*1: Ask the customer to perform operation.

*2: If a failure occurs after capacity expansion of one volume of a GAD pair is successful,
resynchronizing a GAD pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then resynchronize the pair.
*3: The data of the GAD pair is recovered by reconfiguring the GAD pair.
*4: If the GAD pair is deleted in the workflow, reconfigure the GAD pair. If the GAD pair is not
deleted, perform resynchronization.

TRBL18-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-140

External VOL External VOL

Write Error or Read Error
Type of the pinned
track?

ECC/LRC Error

Pair status = PAIR/ No Pair status = PAIR/ No

COPY? COPY?

Yes No Pair status Yes No Pair status

= PSUS/SSUS/SSWS/ = PSUS/SSUS/SSWS/
Delete the path from servers to PSUE? Delete the path from servers to PSUE?
the GAD SVOL. (*2) the GAD SVOL. (*2)
Yes Yes

Suspend a pair from the Web Format the externally connected Suspend a pair from the Web Recover the pinned track
Console of the GAD PVOL. (*1) volume that is used as Quorum Console of the GAD PVOL. (*1) according to “[Link] External
Disk after blocking the volume. VOL Write Error”.
(*1)

When failure suspension (SIM = When failure suspension (SIM =

dd0xyy/dd1xyy/dd2xyy/dd3xyy) dd0xyy/dd1xyy/dd2xyy/dd3xyy)
of a GAD pair occurs, recover of a GAD pair occurs, recover
the GAD pair in accordance with the GAD pair in accordance with
the procedure of TRBL18-20.
the procedure of TRBL18-20.

Is it normally No
No
suspended? Is it normally
suspended?
Yes
Yes
Format the externally connected
volume that is used as Quorum Recover the pinned track
Disk after blocking the volume. according to “[Link] External
(*1) VOL Write Error”.

Resynchronize from the Web Resynchronize from the Web

Console of the GAD PVOL. (*1) Console of the GAD PVOL. (*1)
(*3) (*3)

Is No Is No
it normally it normally
resynchronized? resynchronized?

Yes T.S.D. call Yes T.S.D. call

Add a path from servers to the Add a path from servers to the
GAD SVOL. (*1) GAD SVOL. (*1)

END

*1: Ask the customer to perform operation.

*2: Ask the customer to perform operation. When the path cannot be deleted, perform the next step.
*3: If a failure occurs after capacity expansion of one volume of a GAD pair is successful,
resynchronizing a GAD pair in the procedure is not possible due to capacity inconsistency. Perform
capacity expansion so that the capacities are consistent, and then resynchronize the pair.

TRBL18-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-141

How to check pair status and I/O mode of GAD pair

1. For Web Console
Expand the Storage Systems tree, click [Replication]-[Remote Replication], and then select the [GAD
Pairs] tab.
In the displayed list of GAD pairs, see [Status] to check the pair status, and [I/O Mode] in the [Local
Storage System] table to check the I/O mode.

2. For RAID Manager

Execute the pairdisplay command. The following is a command example:
pairdisplay -g oraHA -fcxe -IH1
“oraHA” indicates the group name defined in the configuration definition file, and “-IH1” indicates the
instance number 1.
In the execution result, the “Status” column shows the pair status, and the “R/W” column shows the I/O
mode.

3. I/O mode terms displayed in Web Console and RAID Manager

The following table lists the I/O mode terms described in this procedure and those displayed in the Web
Console and the RAID Manager.

Term in this procedure Term in Web Console Term in RAID Manager

Mirror Mirror (Read Local) L/M
Local Local L/L
Block Block B/B

Dump collection in this recovery procedure

Before contacting the Technical Support Division, collect dumps from both MCU and RCU by
performing Auto Dump.
For the procedure, see MAINTENANCE PC SECTION “5.2 Dump”.
When performing Auto Dump, specify “Normal” for the dump type.
However, if the performance of the storage system is deteriorated when the error occurs, specify “Monitor”
for the dump type.

TRBL18-141
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-150

18.1.5 Recovery Procedure at Quorum Disk Failure (SIM = def0xx)

NOTE: • In the following procedure, ask SE or the customer to check the pair status and I/O mode of the
GAD pair. For the procedure, see “How to check pair status and I/O mode of GAD pair”.
• If you contact the Technical Support Division in the following procedure, see “Dump collection in
this recovery procedure” to collect dumps.

START

The external device

No
failure occurs?
(SIM = 21d0xx/efd000)

Yes
From the Web Console, confirm
the pair status of all the GAD PVOLs/
SVOLs that use Quorum Disk ID in which
failure occurred.

No
Pair status = COPY?

Yes
Suspend a pair from the Web Console of the
GAD PVOL. (*1)

No Is it normally
suspended?

Yes

Maintain in accordance with “11.2 Recovery

Procedure for External Device Failure”. (*2)

The external volume Yes

needs re-mapping?
Prepare an external volume and perform the
No
quorum disk replacement using Command
Control Interface. (Refer to Global-Active
No The device in the external Device User Guide)
storage system is recovered?
END
Yes
When failure suspension (SIM = dd0xyy/
dd1xyy/dd2xyy/dd3xyy) of a GAD pair
occurs, recover the GAD pair in accordance
with the procedure of TRBL18-20.

T.S.D. call 1 (TRBL18-151)

TRBL18-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-151

If you suspended a pair, resynchronize a pair

from the Web Console of the GAD PVOL.
(*1)

No
Is it normally resynchronized?

T.S.D. call
Yes

END

*1: Ask the customer to perform operation.

*2: When the recovery procedure in “11.2 Recovery Procedure for External Device Failure” requires
re-mapping operation of the external volume, after deleting all the GAD pairs that use Quorum
Disk in which failure occurred, delete the Quorum Disk in which failure occurred and then recover
the external volume.
However, you can perform the recovery procedure for the external volume without deleting GAD
pairs by preparing a new external volume and then performing the quorum disk replacement (CCI
[raidcom replace quorum] command).

TRBL18-151
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-160

How to check pair status and I/O mode of GAD pair

1. For Web Console
Expand the Storage Systems tree, click [Replication]-[Remote Replication], and then select the [GAD
Pairs] tab.
In the displayed list of GAD pairs, see [Status] to check the pair status, and [I/O Mode] in the [Local
Storage System] table to check the I/O mode.

2. For RAID Manager

Execute the pairdisplay command. The following is a command example:
pairdisplay -g oraHA -fcxe -IH1
“oraHA” indicates the group name defined in the configuration definition file, and “-IH1” indicates the
instance number 1.
In the execution result, the “Status” column shows the pair status, and the “R/W” column shows the I/O
mode.

3. I/O mode terms displayed in Web Console and RAID Manager

The following table lists the I/O mode terms described in this procedure and those displayed in the Web
Console and the RAID Manager.

Term in this procedure Term in Web Console Term in RAID Manager

Mirror Mirror (Read Local) L/M
Local Local L/L
Block Block B/B

Dump collection in this recovery procedure

Before contacting the Technical Support Division, collect dumps from both MCU and RCU by
performing Auto Dump.
For the procedure, see MAINTENANCE PC SECTION “5.2 Dump”.
When performing Auto Dump, specify “Normal” for the dump type.
However, if the performance of the storage system is deteriorated when the error occurs, specify “Monitor”
for the dump type.

TRBL18-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-170

18.1.6 Recover Path Failure Between a GAD Pair in the GAD Environment
Path Status Factor Recovery Action
“Nothing” Establishing path or deleting path Delete the path with “Edit Path” or “Delete
RCU”.
Add a new path with “Edit Path” or “Add
RCU”. (*1)
“Initialization Failed” Incorrect the physical connection Correct the physical path connection between
between the MCU and RCU the MCU, RCU and the path relay equipment.
Incorrect the Port topology Setup the port topology of the both MCU and
settings.(Fibre connection) RCU correctly.
Blockade of the MP or Port on the Repair the MP status or Port status on the
RCU. RCU.
Broken the connection cable Replace the broken cable.
physically.
Incorrect the path relay equipment Correct the path relay equipment settings or
settings or the path relay repair it.
equipment doesn't work.
“Communication Time Blockade of the MP or Port on the Repair the MP status or Port status on the
Out” MCU. MCU.
“Resource Shortage MCU resource over. Too many path in the MCU or the RCU.
(MCU)” Delete the paths and RCUs not currently in
“Resource Shortage RCU resource over. use. (*1)
(RCU)”
“Serial Number Incorrect the RCU S/N or Delete the path with “Delete RCU”.
Mismatch” Controller ID. (Fibre connection) Add a new path with the correct RCU S/N and
Controller ID with “Add RCU” again. (*1)
Incorrect the physical connection Correct the physical path connection between
between the MCU and RCU. the MCU, RCU and the path relay equipment.
Incorrect the Port topology Setup the port topology of the both MCU and
settings. (Fibre connection) RCU correctly.
Blockade of the MP or Port on the Repair the MP status or Port status on the
RCU. RCU.
Broken the connection cable Replace the broken cable.
physically.
Incorrect the path relay equipment Correct the path relay equipment settings or
settings or the path relay repair it.
equipment doesnʼt work.
(To be continued)

TRBL18-170
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-180

(Continued from the preceding page)

Path Status Factor Recovery Action
“Invalid Port” Specified port is not existence on Delete the path with “Edit Path” or “Delete
the MCU. RCU”.
And add a new path with correct port on MCU
again. (*1)
Incorrect specified port type Delete the path with “Edit Path” or “Delete
“Fibre”. RCU”.
And add a new path with correct port type
“Serial/Fibre” again. (*1)
Specified MCU port type is not Change the channel type of the MCU port to
Bidirectional. Bidirectional.
“RCU Port Number Incorrect the specified RCU port. Delete the path with “Edit Path” or “Delete
Mismatch” RCU”.
And add a new path with correct RCU port
again. (*1)
Incorrect the physical connection Correct the physical path connection between
between the MCU and RCU. the MCU, RCU and the path relay equipment.
Incorrect the Port topology Setup the port topology of the both MCU and
settings. (Fibre connection) RCU correctly.
Blockade of the MP or Port on the Repair the MP status or Port status on the
RCU. RCU.
Broken the connection cable Replace the broken cable.
physically.
Incorrect the path relay equipment Correct the path relay equipment settings or
settings or the path relay repair it.
equipment doesn't work.
(To be continued)

TRBL18-180
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-190

(Continued from the preceding page)

Path Status Factor Recovery Action
“RCU Port type is not Incorrect specified RCU port. Delete the path with “Edit Path” or “Delete
RCU Target” RCU”.
And add a new path with correct RCU port
again. (*1)
Specified RCU port type is not Change the channel type of the RCU port to
Bidirectional. Bidirectional.
“Communication Blockade of the MP or Port on the Repair the MP status or Port status on the
Failed” RCU. RCU.
The path relay equipment doesnʼt Repair the path relay equipment
work.
“Logical Blockade” MCU Port doesnʼt work. Repair the port status on the MCU.
RCU Port doesnʼt work. Repair the port status on the RCU.
And delete the path with “Edit path” or “Delete
RCU”.
Add the path with “Edit path” or “Add RCU”
again. (*1)
The path relay equipment doesnʼt Repair the path relay equipment.
work. And delete the path with “Edit path” or “Delete
RCU”.
And add the path with “Edit path” or “Add
RCU” again. (*1)
Broken the connection cable Replace the broken cable.
physically. And delete the path with “Edit path” or “Delete
RCU”.
Add the path with “Edit path” or “Add RCU”
again. (*1)
“Program Error” Detected program error. Delete the path with “Edit path” or “Delete
RCU”.
And add the path with “Edit path” or “Add
RCU” again. (*1)
*1: For the firmware version 88-07-03-x0/xx or later, 88-08-01-x0/xx or later and the firmware version
93-04-01-x0/xx or later, in the configuration that connects VSP G350/G370/G700/G900/F350/
F370/F700/F900/E990 and VSP E590/E790, remote path operations from VSP G350/G370/G700/
G900/F350/F370/F700/F900/E990 by using Storage Navigator (Web Console) are possible.
For the firmware version earlier than 88-07-03-x0/xx, earlier than 88-08-01-x0/xx and the firmware
version earlier than 93-04-01-x0/xx, use RAID Manager (CCI).
For the configuration that connects VSP E1090 and VSP 5000 series, remote path operations
from VSP 5000 series by using Storage Navigator (Web Console) are not possible. So, use RAID
Manager (CCI).

TRBL18-190
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-200

18.2 Recovery Procedure When a Failure Occurred While Creating/Resynchronizing a

GAD Pair
The following are recovery procedures when an operation fails due to occurrence of a failure etc. while
creating or resynchronizing a GAD pair and the pair status of the P-VOL and S-VOL is the following status.

■ When a GAD pair creation operation fails

• If the pair status is “PVOL = SMPL”, “SVOL ≠ SMPL”;

Recovery procedure:
From the Web Console or the Command Control Interface (CCI), perform forced deletion (Disable)
operation to the SVOL and retry pair creation operation.

• If pair creation operation is performed from the RM/CLI and is failed by SSB = D004, FA03;
• If pair creation operation is performed from the web console and is failed by 06205-008704 (W) in the
Storage Navigator message;

Recovery procedure 1:
1. A failure may occur in a path between the MCU and RCU. Check the path status between the MCU and
RCU.

2. When checking the path status finds a failure, remove the failure factors and then confirm the path status
is normal.

3. After recovering the normal path status, perform pair creation operation again to the pair where pair
creation failed.

Additionally, when pair creation operation cannot be performed or fails due to factors such as an
unrecoverable path failure, follow the recovery procedure 2 below to perform forced deletion operation
of the pair.

Recovery procedure 2:
1. Identifying the pair that needs forced deletion operation
• When performing pair creation operation from the web console;
The pair that is found to be an error by confirming the task status where pair creation operation is
performed from the task window.
• When pair creation operation is performed from the RM/CLI;
The foremost pair among the pairs where the pair status of both PVOL and SVOL is “SMPL”
by confirming the pair status of the GAD pairs defined in the configuration definition file, by the
pairdisplay command.

2. Forced deletion operation

From the logical device list of the web console, select the VOL designated as “SVOL”, and then perform
[More Actions] – [Force Delete Pairs (GAD Pairs)].

TRBL18-200
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-210

■ When a resynchronization operation fails

The recovery procedure is as follows when the pair status is P-VOL = PSUx, S-VOL = COPY.

From the web console, perform resynchronization again.

TRBL18-210
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-220

18.3 Failure Recovery Procedure and Maintenance Procedure of the GAD-UR delta
Configuration
18.3.1 Failure Recovery Procedure of the GAD-UR delta Configuration
The reference codes reported in the GAD-UR delta configuration are the same as the reference codes of the
TC + UR configuration and GAD configuration.

Table 18-2 Reference codes that are reported at the time of the journal volume failure of UR
delta pair
REF code
Error description Error level Host report
22 23
Detection of DP pool failure
62 3x Moderate YES
(The journal volume also fails.)
DP pool VOL failure
62 7x Moderate YES
(The journal volume also fails.)
The journal volume failure
dc ex Moderate No
(The UR journal is full.)
Pair volume failure (P-VOL suspension) YES
dc 1x Serious
A failure is detected in the PDKC. (Repeated report)

The following is the table of pair statuses in the event of a single point of failure and the recovery procedure
summary. In each table, the value in the parentheses for GAD pair status indicates I/O mode and the value
in the parentheses for UR delta pair status indicates pair status displayed in CCI or journal volumeʼs mirror
status. To complete the delta resync operation, keep updating I/O from the host for about two minutes.
If a failure occurs after capacity expansion of one volume of a UR/GAD pair is successful, creating or
resynchronizing a UR/GAD pair in the recovery procedure is not possible due to capacity inconsistency.
Perform capacity expansion so that the capacities are consistent, and then create or resynchronize the pair.

No. Failure Recovery Procedure Reference page

1 “1. Path between DKC” TRBL18-230
2 “2. Pool Volumes” TRBL18-260
3 “3. Journal Volumes” TRBL18-280
4 “5. LDEV (LDEV Blockade)” TRBL18-320
5 “6. Storage system” TRBL18-330

TRBL18-220
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-230

1. Path between DKC

Mirror
No. Item Pair Status Recovery operation
ID
‒ [Normal PVOL PAIR LVOL PAIR
Operation] 0 (GAD (Mirror (GAD (Mirror
PVOL) (RL)) SVOL) (RL))
PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
1 PDKC PVOL PSUE LVOL PSUE 1. GAD failure suspension is
→ LDKC 0 (GAD (Local) (GAD (Block) detected.
Path failure PVOL) SVOL) 2. Failure recovery site.
PVOL PAIR RVOL PAIR (Recover paths)
1
(UR PVOL) (UR SVOL) 3. GAD resync by PVOL.
LVOL HOLDING RVOL HOLD (*1)
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
2 LDKC PVOL PSUE LVOL SSWS 1. GAD failure suspension is
→ PDKC 0 (GAD (Block) (GAD (Local) detected.
Path failure PVOL) SVOL) 2. Delta resync.
PVOL HOLDING RVOL HOLD 3. Failure recovery site.
1 (UR delta (PSUE/ (UR delta (SSUS/ (Recover paths)
PVOL) PJNS) SVOL) SJNS) 4. GAD swap resync. (*1)
LVOL PAIR RVOL PAIR
5. GAD swap suspend.
2 (UR PVOL) (UR SVOL) 6. Delta resync.
7. GAD swap resync. (*1)
3 LDKC PVOL PAIR LVOL PAIR 1. Failure recovery site.
→ RDKC 0 (GAD (Mirror (GAD (Mirror (Recover paths)
Path failure PVOL) (RL)) SVOL) (RL))
PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
4 RDKC PVOL PAIR LVOL PAIR 1. Failure recovery site.
→ LDKC 0 (GAD (Mirror (GAD (Mirror (Recover paths)
Path failure PVOL) (RL)) SVOL) (RL))
PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
(To be continued)

TRBL18-230
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-240

(Continued from preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
5 PDKC PVOL PAIR LVOL PAIR 1. Failure recovery site.
→ RDKC 0 (GAD (Mirror (GAD (Mirror (Recover paths)
Path failure PVOL) (RL)) SVOL) (RL))
PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
6 RDKC PVOL PAIR LVOL PAIR • SOM448 = ON and SOM449
→ PDKC 0 (GAD (Mirror (GAD (Mirror = OFF:
Path failure PVOL) (RL)) SVOL) (RL)) After communication break
PVOL PAIR RVOL PAIR detection, immediately UR
1 (UR PVOL) (UR SVOL) pair failure suspend.
• SOM448 = OFF and
LVOL HOLD RVOL HOLD
SOM449 = OFF:
(UR delta (PSUS/ (UR delta (SSUS/
UR pair failure suspend Once
PVOL) PJNS) SVOL) SJNS)
communication is severed a
certain period of time.
2 Any of the above, the recovery
in the following procedure.
1. Failure recovery site.
(Recover paths)
2. UR resync by PVOL. (*1)
7 PDKC - PVOL PAIR LVOL PAIR Failure recovery site.
External 0 (GAD (Mirror (GAD (Mirror (Recover paths)
storage PVOL) (RL)) SVOL) (RL))
Path failure PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
8 LDKC - PVOL PAIR LVOL PAIR Failure recovery site.
External 0 (GAD (Mirror (GAD (Mirror (Recover paths)
storage PVOL) (RL)) SVOL) (RL))
Path failure PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)

TRBL18-240
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-250

*1: Perform the following operation.

1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.

TRBL18-250
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-260

2. Pool Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL PVOL PSUE LVOL SSWS 1. GAD failure suspension is
pool full 0 (GAD (Block)
(GAD (Local) detected.
PVOL) SVOL) 2. Delta resync.
PVOL HOLDING RVOL HOLD 3. Failure recovery site.
1 (UR delta (PSUE/ (UR delta (SSUS/ 4. GAD swap resync. (*1)
PVOL) PJNS) SVOL) SJNS) 5. GAD swap suspend.
LVOL PAIR RVOL PAIR 6. Delta resync.
2
(UR PVOL) (UR SVOL) 7. GAD swap resync. (*1)
2 PVOL PVOL PSUE LVOL SSWS 1. GAD failure suspension is
pool failure 0 (GAD (Block) (GAD (Local) detected.
PVOL) SVOL) 2. Delta resync.
PVOL HOLDING RVOL HOLD 3. Failure recovery site.
1 (UR delta (PSUE/ (UR delta (SSUS/ 4. GAD swap resync. (*1)
PVOL) PJNS) SVOL) SJNS) 5. GAD swap suspend.
LVOL PAIR RVOL PAIR 6. Delta resync.
2
(UR PVOL) (UR SVOL) 7. GAD swap resync. (*1)
3 LVOL PVOL PSUE LVOL PSUE 1. GAD failure suspension is
pool full 0 (GAD (Local) (GAD (Block) detected.
PVOL) SVOL) 2. Failure recovery site.
PVOL PAIR RVOL PAIR 3. GAD pair resync by PVOL.
1
(UR PVOL) (UR SVOL) (*1)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
4 LVOL PVOL PSUE LVOL PSUE 1. GAD failure suspension is
pool failure 0 (GAD (Local) (GAD (Block) detected.
PVOL) SVOL) 2. Failure recovery site.
PVOL PAIR RVOL PAIR 3. GAD pair resync by PVOL.
1
(UR PVOL) (UR SVOL) (*1)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
5 RVOL PVOL PAIR LVOL PAIR 1. UR failure suspension is
pool full 0 (GAD (Mirror (GAD (Mirror detected.
PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
PVOL PSUE RVOL PFUS 3. UR pair resync by PVOL.
1
(UR PVOL) (UR SVOL) (*1)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
(To be continued)

TRBL18-260
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-270

(Continued from preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
6 RVOL PVOL PAIR LVOL PAIR 1. UR failure suspension is
pool failure 0 (GAD (Mirror (GAD (Mirror detected.
PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
PVOL PSUE RVOL PSUE 3. UR pair resync by PVOL.
1
(UR PVOL) (UR SVOL) (*1)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
*1: Perform the following operation.
1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.

TRBL18-270
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-280

3. Journal Volumes

Mirror
No. Item Pair Status Recovery operation
ID
1 Primary PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume full PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
PVOL PFUS RVOL PFUS 3. UR resync by PVOL. (*1)
1 (UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
2 Primary PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
failure PVOL PSUE RVOL PSUE 3. UR resync by PVOL. (*1)
1 (UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
3 Local PVOL PAIR LVOL PAIR 1. UR delta failure
journal 0 (GAD (Mirror (GAD (Mirror (PSUE(J)) detected.
volume full PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
PVOL PAIR RVOL PAIR 3. UR delta the mirror resync.
1
(UR PVOL) (UR SVOL) (*1) (*3)
LVOL HLDE RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJES) SVOL) SJNS)
4 Local PVOL PAIR LVOL PAIR 1. UR delta failure
journal 0 (GAD (Mirror (GAD (Mirror (PSUE(J)) detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
failure PVOL PAIR RVOL PAIR 3. UR delta the mirror resync.
1
(UR PVOL) (UR SVOL) (*1) (*3)
LVOL HLDE RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJES) SVOL) SJNS)
5 Remote PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume full PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
PVOL PFUS (*2) RVOL PFUS (*2) 3. UR resync by PVOL. (*1)
1
(UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
(To be continued)

TRBL18-280
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-290

(Continued from preceding page)

Mirror
No/ Item Pair Status Recovery operation
ID
6 Remote PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
failure PVOL PSUE RVOL PSUE 3. UR resync by PVOL. (*1)
1
(UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
*1: Perform the following operation.
1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.
*2: The pair status of RDKC does not become PFUS until the PDKC journal volume becomes full.
Thus, the RDKC journal volume can be expanded until the PDKC journal becomes full.
*3: This operation cannot be executed by RAID Manager. Execute from Storage Navigator.

TRBL18-290
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-300

4. Journal Volumes (Pool Volumes) (*1)

Mirror
No. Item Pair Status Recovery operation
ID
1 Primary PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
pool full PVOL PSUE RVOL PSUE 3. UR resync by PVOL. (*2)
1 (UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
2 Primary PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
pool failure PVOL PSUE RVOL PSUE 3. UR resync by PVOL. (*2)
1 (UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
3 Local PVOL PAIR LVOL PAIR 1. UR delta failure
journal 0 (GAD (Mirror (GAD (Mirror (PSUE(J)) detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
pool full PVOL PAIR RVOL PAIR 3. UR delta the mirror resync.
1
(UR PVOL) (UR SVOL) (*2) (*3)
LVOL HLDE RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJES) SVOL) SJNS)
4 Local PVOL PAIR LVOL PAIR 1. UR delta failure
journal 0 (GAD (Mirror (GAD (Mirror (PSUE(J)) detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
pool failure PVOL PAIR RVOL PAIR 3. UR delta the mirror resync.
1
(UR PVOL) (UR SVOL) (*2) (*3)
LVOL HLDE RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJES) SVOL) SJNS)
5 Remote PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
pool full PVOL PSUE RVOL PSUE 3. UR resync by PVOL. (*2)
1
(UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
(To be continued)

TRBL18-300
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-310

(Continued from preceding page)

Mirror
No/ Item Pair Status Recovery operation
ID
6 Remote PVOL PAIR LVOL PAIR 1. UR failure suspension is
journal 0 (GAD (Mirror (GAD (Mirror detected.
volume PVOL) (RL)) SVOL) (RL)) 2. Failure recovery site.
pool failure PVOL PSUE RVOL PSUE 3. UR resync by PVOL. (*2)
1
(UR PVOL) (UR SVOL)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
*1: Recovery procedures for failure in the pool of DP-VOLs registered as journal volumes are
described. The pool full status might occur when the capacity of journal volumes is defined more
than that of all unused pool volumes.
*2: Perform the following operation.
1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.
*3: This operation cannot be executed by RAID Manager. Execute from Storage Navigator.

TRBL18-310
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-320

5. LDEV (LDEV Blockade)

Mirror
No. Item Pair Status Recovery operation
ID
1 PVOL PVOL PSUE LVOL SSWS When the recovery by the
failure 0 (GAD (Block) (GAD (Local) LDEV format is necessary:
PVOL) SVOL) 1. UR pair deletion.
PVOL HOLDING RVOL HOLD 2. UR delta resync pair
1 (UR delta (PSUE/ (UR delta (SSUS/ deletion.
3. GAD pair deletion. (SVOL
PVOL) PJNS) SVOL) SJNS)
side first)
LVOL PAIR RVOL PAIR
4. Failure recovery site.
(UR PVOL) (UR SVOL) 5. GAD pair creation. (SVOL
side first)
6. Exchange PVOL for
SVOL in the GAD pair as
required.
7. UR delta resync pair
creation.
8. UR pair creation. (*1)
2 When the recovery by the
LDEV format is not necessary:
1. GAD failure suspension is
detected.
2. Delta resync.
3. Failure recovery site.
4. GAD pair swap resync.
(*1)
5. GAD swap suspend.
6. Delta resync.
7. GAD swap resync. (*1)
2 LVOL PVOL PSUE LVOL PSUE When the recovery by the
failure 0 (GAD (Local) (GAD (Block) LDEV format is necessary:
PVOL) SVOL) 1. UR pair deletion.
PVOL PAIR RVOL PAIR 2. UR delta resync pair
1 deletion.
(UR PVOL) (UR SVOL)
HOLDING RVOL 3. GAD pair deletion.
LVOL HOLD
4. Failure recovery site.
(UR delta (PSUE/ (UR delta (SSUS/
5. GAD pair creation.
PVOL) PJNS) SVOL) SJNS) 6. UR delta resync pair
creation.
7. UR pair creation. (*1)
2 When the recovery by the
LDEV format is not necessary:
1. GAD failure suspension is
detected.
2. Failure recovery site.
3. GAD pair resync by PVOL.
(*1)
(To be continued)
TRBL18-320
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-321

(Continued from preceding page)

Mirror
No. Item Pair Status Recovery operation
ID
3 RVOL PVOL PAIR LVOL PAIR When the recovery by the
failure 0 (GAD (Mirror (GAD (Mirror LDEV format is necessary:
PVOL) (RL)) SVOL) (RL)) 1. UR pair deletion.
PVOL PSUE RVOL PSUE 2. UR delta resync pair
1 deletion.
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD 3. Failure recovery site.
(UR delta (PSUS/ (UR delta (SSUS/ 4. UR delta resync pair
PVOL) PJNS) SVOL) SJNS) creation.
5. UR pair creation. (*1)
When the recovery by the
2 LDEV format is not necessary:
1. UR failure suspension is
detected.
2. Failure recovery site.
3. UR pair resync by PVOL.
(*1)
4 Quorum PVOL PAIR LVOL PAIR Failure recovery site.
Disk 0 (GAD (Mirror (GAD (Mirror (Quorum Disk)
volume PVOL) (RL)) SVOL) (RL))
failure PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
*1: Perform the following operation.
1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.

TRBL18-321
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-330

6. Storage system

Mirror
No. Item Pair Status Recovery operation
ID
1 PDKC PVOL PSUE LVOL SSWS 1. GAD failure suspension is
failure 0 (GAD (Block) (GAD (Local) detected.
(SM/CM PVOL) SVOL) 2. Delta resync.
Non- PVOL PSUE (*1) RVOL HOLD 3. DKC recovery.
Volatile) 1 (UR PVOL) (UR delta (SSUS/ 4. UR pair (Mirror ID 1)
(*1) (*1) SVOL) SJNS) deletion (*4)
LVOL PAIR RVOL PAIR 5. Creation of UR delta
(UR PVOL) (UR SVOL) resync pair (Mirror ID 1)
(*4)
2 6. GAD swap resync. (*2)
7. GAD swap suspend.
8. Delta resync.
9. GAD swap resync. (*2)
2 LDKC PVOL PSUE LVOL PSUE 1. GAD failure suspension is
failure 0 (GAD (Local) (GAD (Block) detected.
(SM/CM PVOL) SVOL) 2. DKC recovery.
Non- PVOL PAIR RVOL PAIR 3. GAD resync by PVOL.
1
Volatile) (UR PVOL) (UR SVOL) (*2)
LVOL HOLDING RVOL HOLD
2 (UR delta (PSUE/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)
3 RDKC PVOL PAIR LVOL PAIR 1. DKC recovery.
failure 0 (GAD (Mirror (GAD (Mirror 2. UR failure suspension is
(SM/CM PVOL) (RL)) SVOL) (RL)) detected.
Non- PVOL PAIR (*3) RVOL PAIR (*3) 3. UR resync by PVOL. (*2)
1
Volatile) (UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) (*3) SVOL) SJNS)
4 External PVOL PAIR LVOL PAIR Failure recovery site.
storage 0 (GAD (Mirror (GAD (Mirror
failure PVOL) (RL)) SVOL) (RL))
PVOL PAIR RVOL PAIR
1
(UR PVOL) (UR SVOL)
LVOL HOLD RVOL HOLD
2 (UR delta (PSUS/ (UR delta (SSUS/
PVOL) PJNS) SVOL) SJNS)

TRBL18-330
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-340

*1: The UR pair information of PDKC (PVOL) remains and the UR pair status changes to failure
suspension after PS ON of PDKC (PVOL). For firmware versions 93-05-xx-xx/xx or later and
88-08-05-x0/xx or later, confirm that the UR pair status changes to HOLDING after PS ON of
PDKC (PVOL).
*2: Perform the following operation.
1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.
*3: If you have a SOM449 = OFF in PDKC, UR pair status PSUE, LVOL of UR delta pair state
changes to HOLDING.
*4: When the UR pair status of PDKC (PVOL) is HOLDING, skip the steps for UR pair deletion and
creation of UR delta resync pair for Mirror ID 1.

TRBL18-340
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-350

18.3.2 GAD-UR delta Configuration Maintenance Procedure

As a basic principle of maintenance, downgrade micro-programs, and then operate in accordance with the
maintenance procedure.
When only host is to be maintained, no operation of storage is needed.
For planned shutdown of the DKC of the GAD-UR delta configuration, see “[Link] Planned Shutdown
Procedure of the DKC of the GAD-UR delta Configuration”.

[Link] Maintenance Procedure

The following maintenance procedure lists a procedure including recovery operation on the host side.

No. Maintenance part Procedure Note

1 P Site 1. Execute GAD Swap suspension.
(DKC + Host) 2. [Automatic] Delta Resync.
3. Perform maintenance.
4. Execute GAD Swap Resync. (*1)
5. Execute GAD Swap suspension.
6. [Automatic] Delta Resync.
7. Execute GAD Swap Resync. (*1)
2 PDKC ↑
3 P Host No storage operation is needed. Because I/O is available in the
PDKC/LDKC, no storage operation
is needed.
4 L Site 1. Suspend GAD.
(DKC + Host) 2. erform maintenance.
3. Resync GAD. (*1)
5 LDKC ↑
6 L Host No storage operation is needed. Because I/O is available in the
PDKC/LDKC, no storage operation
is needed.
7 R Site 1. Suspend UR.
(DKC + Host) 2. Perform maintenance.
3. Resync UR. (*1)
8 RDKC ↑
9 R Host No storage operation is needed. Because I/O is available in the
PDKC/LDKC, no storage operation
is needed.
(To be continued)

TRBL18-350
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-360

(Continued from preceding page)

No. Maintenance part Procedure Note
10 P/L Site simultaneous 1. Suspend GAD.
maintenance 2. Execute UR Swap suspension.
(DKC + Host) 3. Perform maintenance.
4. Execute UR Swap resync.
5. Execute UR Swap suspension.
6. Execute UR swap resync.
7. Resync GAD. (*1)
*1: Perform the following operation.
1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.

TRBL18-360
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-370

[Link] Planned Shutdown Procedure of the DKC of the GAD-UR delta Configuration

No. Planned Shutdown Procedure Reference page

1 “1. Planned Shutdown Procedure of the PDKC” TRBL18-370
2 “2. Planned Shutdown Procedure of the LDKC” TRBL18-400
3 “3. Planned Shutdown Procedure of the RDKC” TRBL18-430
4 “4. Planned Shutdown Procedure of External Storage” TRBL18-450

Following is the procedure of the planned shutdown (PS OFF/ON) of the PDKC/LDKC/RDKC/ external
storage for Quorum in the GAD-UR delta configuration.
Because it is recommended to suspend all GAD pairs or UR pairs related to the DKCs that are to be set to PS
OFF when the DKCs are set to PS OFF, the procedure to comply with it is shown.

1. Planned Shutdown Procedure of the PDKC

Table 18-3 Planned Shutdown Procedure of the PDKC of the GAD-UR delta Configuration
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC/LDKC are under operation, and the RDKC is stand-by. (*1)
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLD

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

1 Stop of host I/O Stop I/O from host to the PDKC, and consolidate host I/O to the LDKC.
to the PDKC
2 GAD pair swap Execute GAD pair swap suspension in the LDKC. #GAD pair swap
suspension ↓ GAD pair swap suspension suspension
PDKC [PS ON] LDKC [PS ON] % pairsplit -g
GAD PVOL: PSUS (Block) GAD SVOL: SSWS (Local) GRPMirror0 -RS -IH1
UR delta PVOL: HOLDING UR PVOL: PAIR

External storage [PS ON]

RDKC [PS ON]

UR delta SVOL: HOLD
UR SVOL: PAIR

(To be continued)

TRBL18-370
Hitachi Proprietary DW850/DW900/DW1000
Rev.6 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-380

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
3 PDKC PS OFF Set the PDKC to PS OFF.
↓ PS OFF
PDKC [PS OFF] LDKC [PS ON]
GAD PVOL: PSUS (Block) GAD SVOL: SSWS (Local)
UR delta PVOL: HOLDING UR PVOL: PAIR

External storage [PS ON]

RDKC [PS ON]

UR delta SVOL: HOLD
UR SVOL: PAIR

‒ During planned
shutdown
4 PDKC PS ON Set the PDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
GAD SVOL: PSUS (Block) GAD SVOL: SSWS (Local)
UR delta PVOL: HOLDING UR PVOL: PAIR

External storage [PS ON]

RDKC [PS ON]

UR delta SVOL: HOLD
UR SVOL: PAIR

5 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
6 SIM check If SIMs related to the path block are generated in each DKC, complete
the SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary
actions).
7 GAD pair swap Execute GAD pair swap resync in the LDKC. #GAD pair swap
resync ↓ GAD pair swap resync resync
PDKC [PS ON] LDKC [PS ON] % pairresync -g
GAD SVOL: PAIR (Mirror (RL)) GAD PVOL: PAIR (Mirror (RL)) GRPMirror0 -swaps
UR delta PVOL: HOLDING UR PVOL: PAIR -IH1

External storage [PS ON]

RDKC [PS ON]

UR delta SVOL: HOLD
UR SVOL: PAIR

8 Restart of host Restart I/O from host to the PDKC. (*1)

I/O to the
PDKC
(To be continued)

TRBL18-380
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-390

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
9 UR delta pair (*2)
configuration PDKC [PS ON] LDKC [PS ON]
construction GAD SVOL: PAIR (Mirror (RL)) GAD PVOL: PAIR (Mirror (RL))
completed UR delta PVOL: HOLD UR PVOL: PAIR
status
External storage [PS ON]

RDKC [PS ON]

UR delta SVOL: HOLD
UR SVOL: PAIR

*1: Perform the following operation.

1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.
*2: To resume the operation in the primary site, see the description of replacing the primary volume
and secondary volume of the GAD pair in “Global-Active Device User Guide”.

TRBL18-390
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-400

2. Planned Shutdown Procedure of the LDKC

Table 18-4 Planned Shutdown Procedure of the LDKC of the GAD-UR delta Configuration
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC/LDKC are under operation, and the RDKC is stand-by. (*1)
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLD

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

1 Stop of host I/O Stop I/O from host to the LDKC, and consolidate host I/O to the PDKC.
to the LDKC
2 GAD pair Suspend the GAD pairs in the PDKC. #GAD pair suspension
suspension ↓ GAD pair suspension % pairsplit -g
PDKC [PS ON] LDKC [PS ON] GRPMirror0 -IH0
GAD PVOL: PSUS (Local) GAD SVOL: PSUS (Block)
UR PVOL: PAIR UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

3 LDKC PS OFF Set the LDKC to PS OFF.

↓ PS OFF
PDKC [PS ON] LDKC [PS OFF]
GAD PVOL: PSUS (Local) GAD SVOL: PSUS (Block)
UR PVOL: PAIR UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

(To be continued)

TRBL18-400
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-410

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ During planned
shutdown
4 LDKC PS ON Set the LDKC to PS ON.
↓ PS ON
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PSUS (Local) GAD SVOL: PSUS (Block)
UR PVOL: PAIR UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

5 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
6 SIM check If SIMs related to the path block are generated in each DKC, complete
the SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary
actions).
7 GAD pair Resync the GAD pairs in the PDKC. #GAD pair resync
resync ↓ GAD pair resync % pairresync -g
PDKC [PS ON] LDKC [PS ON] GRPMirror0 -IH0
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

8 Restart of Restart I/O from host to the LDKC. (*1)

host I/O to the
LDKC
9 UR delta pair
configuration PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
construction
UR PVOL: PAIR UR delta PVOL: HOLD
completed
status External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

TRBL18-410
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-420

*1: Perform the following operation.

1. Continue to issue I/O for about two minutes from the server to the primary volume or secondary
of the GAD pair.
2. Check the pair status.
• To check the pair status from CCI, confirm that the primary volume status of the UR delta
resync pair changes from “PSUE” to “PSUS”. At the same time, confirm that the mirror status
of the journal volume in the primary site of the UR delta resync pair is “PJNS”.
• To check the pair status from Storage Navigator, confirm that the primary volume status of
the UR delta resync pair changes from “HOLDING” to “HOLD”.

TRBL18-420
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-430

3. Planned Shutdown Procedure of the RDKC

Table 18-5 Planned Shutdown Procedure of the RDKC of the GAD-UR delta Configuration
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC/LDKC are under operation, and the RDKC is stand-by.
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLD

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

1 UR pair Suspend the UR pairs in the PDKC. #UR pair suspension

suspension ↓ UR pair suspension % pairsplit -g
PDKC [PS ON] LDKC [PS ON] GRPMirror1 -IH0
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PSUS UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PSUS
UR delta SVOL: HOLD

2 RDKC PS OFF Set the RDKC to PS OFF.

PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PSUS UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS OFF]

UR SVOL: PSUS
UR delta SVOL: HOLD
↑ PS OFF

(To be continued)

TRBL18-430
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-440

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ During planned
shutdown
3 RDKC PS ON Set the RDKC to PS ON.
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PSUS UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PSUS
UR delta SVOL: HOLD
↑ PS ON

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete
the SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary
actions).
6 UR pair resync Resync the UR pairs in the PDKC. #UR pair resync
% pairresync -g
↓ UR pair resync GRPMirror1 -IH0
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLDING

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

7 UR delta pair
configuration
PDKC [PS ON] LDKC [PS ON]
construction
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
completed UR PVOL: PAIR UR delta PVOL: HOLD
status
External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

TRBL18-440
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-450

4. Planned Shutdown Procedure of External Storage

NOTE: For the configuration (*) where volumes are not set as quorum disks, skip the steps
related to GAD or quorum disks when performing the planned shutdown of the
external storage because the external storage for quorum disks is not used.
If none of the volumes is set as a quorum disk, perform only PS OFF/ON of the
external storage.
*: Execute the [raidcom get quorum] command with Command Control Interface to
check the configuration. (For details, see Command Control Interface Command
Reference.)

Table 18-6 Planned Shutdown Procedure of External Storage of the GAD-UR delta
Configuration
Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
‒ Initial status The PDKC/LDKC are under operation, and the RDKC is stand-by.
PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLD

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

(To be continued)

TRBL18-450
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-460

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
1 Disconnection Disconnect Quorum disk (external volume) connection in the PDKC and #External volume
of Quorum disk RDKC. disconnection
↓ Disconnection of Quorum disk ↓ Disconnection of Quorum disk % raidcom disconnect
PDKC [PS ON] LDKC [PS ON] external_grp -ldev_id
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL)) <quorum ldev#>
UR PVOL: PAIR UR delta PVOL: HOLD -IH0 (or -IH1)

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

2 External storage Set external storage to PS OFF.

PS OFF PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLD
↓ PS OFF
External storage [PS OFF]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

‒ During planned
shutdown
3 External storage Set external storage to PS ON.
PS ON PDKC [PS ON] LDKC [PS ON]
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL))
UR PVOL: PAIR UR delta PVOL: HOLD
↓ PS ON
External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

4 Check of the Confirm each DKC has no block part. If there are block parts, recover them.
block part
5 SIM check If SIMs related to the path block are generated in each DKC, complete
the SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary
actions).
(To be continued)

TRBL18-460
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL18-470

(Continued from the preceding page)

Description Note
No. Procedure item
(Underlining means a part that changes from the previous status.) (RM command, etc.)
6 Reconnection Reconnect Quorum disk (external volume) in the PDKC and RDKC. #External volume
of Quorum disk ↓ Reconnection of Quorum disk ↓ Reconnection of Quorum disk reconnection
PDKC [PS ON] LDKC [PS ON] % raidcom check_
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL)) ext_storage external_
UR PVOL: PAIR UR delta PVOL: HOLD grp -ldev_id <quorum
ldev#>
External storage [PS ON]
-IH0 (or -IH1)
RDKC [PS ON]
UR SVOL: PAIR
UR delta SVOL: HOLD

7 Confirmation Confirm connection from the PDKC and RDKC to Quorum disk. #Confirmation of
of Quorum disk ↓ Confirmation of Quorum disk ↓ Confirmation of Quorum disk external volume
connection connection connection connection
PDKC [PS ON] LDKC [PS ON] % raidcom get
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL)) external_grp
UR PVOL: PAIR UR delta PVOL: HOLD -external_grp_id
<quorum external
External storage [PS ON]
group id>
RDKC [PS ON] -IH0 (or -IH1)
UR SVOL: PAIR
UR delta SVOL: HOLD

8 Confirmation Confirm external volumes of the PDKC and RDKC are recognized as #Confirmation
of Quorum disk Quorum disk. of Quorum disk
recognition ↓ Confirmation of Quorum disk ↓ Confirmation of Quorum disk recognition
recognition recognition % raidcom get ldev
PDKC [PS ON] LDKC [PS ON] -ldev_id <quorum
GAD PVOL: PAIR (Mirror (RL)) GAD SVOL: PAIR (Mirror (RL)) ldev#> -IH0 (or -IH1)
UR PVOL: PAIR UR delta PVOL: HOLD

External storage [PS ON]

RDKC [PS ON]

UR SVOL: PAIR
UR delta SVOL: HOLD

9 SIM check If SIMs related to the path block are generated in each DKC, complete
the SIMs (for VSP Gx00/Fx00/Ex90, view the SIMs and take necessary
actions).

TRBL18-470
Hitachi Proprietary DW850/DW900/DW1000
Rev.0 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL19-10

19. Recovery Procedure when the Maintenance Utility from Hitachi Device
Manager (Storage Navigator) Fails to Start or a Communication Error
Occurs between SVP and DKC
Example: An error message example displayed when the Maintenance Utility fails to start.

In the case that an IP address of the user LAN is default value (CTL1: [Link]/CTL2: [Link]),
this failure may occur. If this failure occurs, take the following recovery procedure.

1. Connect the Maintenance PC and the Maintenance LAN of the CTL1 with a LAN cable.

2. Set IPv4 address and subnet mask of the Maintenance PC to [Link] and [Link], respectively.
Default value of the Maintenance LAN at a factory shipment is [Link] (CTL1). If the IP address of
the Maintenance LAN was modified, set the IPv4 address and subnet mask values of the Maintenance PC
according to the modified value.

3. Start up the Web browser on the Maintenance PC and input the IP address of the Maintenance LAN.
CTL1: [Link]
If modified, input the modified IP address.

4. When the “Maintenance Utility” window opens, input a user name and a password and then, press the
“Login“ button.

5. Click the “Network Settings” button on the “Set Up Network Settings” menu on the “Maintenance Utility”
window and then, change the “IPv4 Address” for both CTL1 and CTL2 to the following IP address.
CTL1: [Link] (provisional value)
CTL2: [Link] (provisional value)

6. After changing the IP addresses, the Maintenance Utility will automatically reboot to apply its setting.
Wait for about five minutes.

7. Execute the aforementioned procedure from Step 3 to Step 6 again to change the “IPv4 Addresses” for
both CTL1 and CTL2 to the following IP address (default value).
CTL1: [Link] (default value)
CTL2: [Link] (default value)
TRBL19-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-10

20. dedupe and compression Error Recovery

20.1 Recovery Procedure for dedupe and compression Operation Error (SIM = 680001)

NOTICE: If operations without data guarantee, such as formatting, have been performed on a
volume used as a pool-VOL on the external storage system, perform 10.1 Recovery
Procedure for pool-VOL Blockade (When Two (Three in RAID6) or More Are Blocked
in the RAID Gr the pool-VOL Belongs) instead of the following procedure.

The following describes a procedure for restoring a dedupe and compression operation error.

SIM = 680001

START
6

Are Yes
there any blocked pool-
VOLs? Follow the pool-VOL Blockade procedure to
No restore an error. (TRBL10-120)

Yes
Does PIN exist?
Follow the pinned track recovery procedure
No to restore an error. (TRBL04-230)

Is Error Code of the No

related SSB 01d0 to 01d4, 01d6, 01f9, 01fe
or 0168?

Yes Is Error Code of the Yes

related SSB 01d5?

Is the Location item No END

displayed in the format of LDEV = Yes
xx:xx:xx (x: hexadecimal) in the Alert Detail
T.S.D. call
window of Maintenance Utility (see
MPC03-1130)? [A]

Identify DP-VOLs where errors

No are detected by seeing Logical
Identify DP-VOLs where errors Identify DP-VOLs where errors are Device in the window of MPC (see
are detected referring to the related detected by the displayed LDEV#. MAINTENANCE PC SECTION
SSBs. (*4) 5.12.3 Pin Data Indication ).

Are there
deduplication system data No
volumes in the pool to which the DP-VOLs
where errors are detected
belong?
2
Yes
(TRBL20-30)
1
(TRBL20-20)

TRBL20-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-11

[B] is the flowchart for MICRO-FC SECTION “Restoring Configuration Information”.

[B]

List all DP-VOLs with Capacity Saving enabled and

deduplication system data volumes as “DP-VOLs
where errors are detected”.

Are there
deduplication system data No
volumes in the pool to which the “DP-VOLs
where errors are detected”
belong?
2
Yes
(TRBL20-30)

3
(TRBL20-20)

TRBL20-11
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-20

Frames surrounding operations show that

1 the operations are to be performed by the
customer at your request.

Is “the DPVOL
where an error is detected” a No
2
deduplication system data volume
(data store)? (TRBL20-30)

Yes
3

Did you click

[Apply] in the “Initialize
Duplicated Data” window (*1) for the Yes
4
pool associated with “DP-VOLs where
errors are detected” in this (TRBL20-31)
maintenance work?

No
In the Web Console main window, select [Logical Devices] from the [Storage Systems] tree, check all DP-VOLs
including the deduplication system data volume associated with the pool.

Back up all DP-VOLs whose [Deduplication Data] is “Enabled” in the pool.

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage, Volume Migration and global-active device that
use the DP-VOLs associated with the pool and all Thin Image/Thin Image Advanced pairs (the root volume and the
pairs in the tree (*2)) that use the pool.

Block all DP-VOLs whose [Deduplication Data] is “Enabled” and the deduplication system data volumes in the
pool.

Initialize all virtual volumes whose [Deduplication Data] function is [Enabled] in the pool. (In the [Initialize
Duplicated Data] window, click [Apply]. (*1))

Set the System Option Mode 1115 to ON. If the System Option Mode 1115 is already set to ON, this operation is
not required. (*6)

Specify all the blocked deduplication system data volumes (data store) in the pool, and then perform the LDEV
format.

Perform the LDEV format on all blocked DP-VOLs whose [Deduplication Data] is “Enabled” in the pool. (*3)

Set the System Option Mode 1115 to OFF. If the mode is not set to ON in this maintenance work, this operation is
not required. (*6)

Perform “20.7 Recovery Procedure When the Compression Acceleration Settings for Deduplication System Data
Volumes Are Invalid after Duplicated Data Initialization”.

Recover the data from the backup.

For the DP-VOLs and LDEVs associated with the pool, recreate TrueCopy, Universal Replicator, ShadowImage,
Volume Migration and global-active device pairs, and Thin Image/Thin Image Advanced pairs that use the pool. (*5)

4 (TRBL20-31)

TRBL20-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-30

Frames surrounding operations show that

2 the operations are to be performed by the
customer at your request.

Did you perform

the LDEV format for “DP-VOLs Yes
5
where errors are detected” in this
maintenance work? (TRBL20-31)

No

Back up the “DP-VOLs where errors are detected”.

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage,

Volume Migration, global-active device, Thin Image and Thin Image
Advanced that use the “DP-VOLs where errors are detected”.

Block the “DP-VOLs where errors are detected”.

Set the System Option Mode 1115 to ON. If the System Option
Mode 1115 is already set to ON, this operation is not required. (*6)

Perform the LDEV formatting on the “DP-VOLs where errors are

detected”.

Set the System Option Mode 1115 to OFF. If the mode is not set to
ON in this maintenance work, this operation is not required. (*6)

Recover the data from the backup.

Recreate the deleted pairs of TrueCopy, Universal Replicator,

ShadowImage, Volume Migration, global-active device, Thin Image
and Thin Image Advanced. (*5)

5
(TRBL20-31)

TRBL20-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-31

Does the
DKCMAIN firmware Yes
version on the storage system support
the health check function?
(*7)
Did you perform No
No the health check in this maintenance
work?

Yes Is there a DP-

VOL for which [Capacity
No Saving] (*8) is set to [Compression]
in the pool to which “DP-VOLs
where errors are detected”
END belong?

Yes

Does the
DKCMAIN firmware Yes
version on the storage system support
the health check function?
(*7)
Did you perform No
No the health check in this maintenance
work?

Yes Perform the health check. (*9)

Yes
Is SIM = 680001 reported?

No 6
(TRBL20-10)

END

TRBL20-31
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.4 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-40

*1: For Command Control Interface, use the [raidcom initialize pool] command.
*2: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in
the tree of the root volume. To identify the root volumes of Thin Image/Thin Image Advanced
pairs that use the pool, specify the pool name (ID) for filtering in the TI Root Volume tab in the
Local Replication window of Web Console.
*3: Do not perform the procedure for LDEV recovery.
*4: For a DP-VOL#, refer to SSB: 01d0 to 01d4, 01d6, 01f9, 01fe or 0168 (byte 0x46 to 0x47).

In this case, the DP-VOL# is

0x8002.

*5: If a failure occurs after capacity expansion of one volume of a TC/UR/GAD/SI/TI/TIA pair is
successful, creating a TC/UR/GAD/SI/TI/TIA pair in the procedure is not possible due to capacity
inconsistency. Perform capacity expansion so that the capacities are consistent, and then create the
pair.
*6: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.
*7: The storage systems with the following DKCMAIN firmware versions support the health check
function.
Storage System DKCMAIN firmware version
VSP E series 93-05-22-xx/xx or later
93-05-04-xx/xx or later and less than 93-05-1x-xx/xx
93-04-04-xx/xx or later and less than 93-04-xx-xx/xx
Other than VSP E series 88-08-02-xx/xx
*8: You can view the Capacity Saving settings in the Logical Devices window of Web Console.
The [Capacity Saving] column is not displayed by default. Display the [Capacity Saving] column
by using the [Column Settings] button (for details, see System Administrator Guide).
*9: See Provisioning Guide .

TRBL20-40
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-50

20.2 Recovery Procedure for Operation Error in Deleting Capacity-Saving-Enabled DP-

VOLs (without blocking/formatting) (SIM = 680002)

NOTICE: • If SIM = 623xxx is reported, perform “10.2 Recovery Procedure for Pool Failure (SIM
= 623xxx)” before starting the following procedure.
• If SIM = 627xxx is reported, perform “10.5 Recovery Procedure for pool-VOL
Blockade (SIM = 627xxx)” before starting the following procedure.
• If you are performing “10.8 Initialization Procedure for Pool”, complete the
procedure, and then perform the following procedure.

The following is the recovery procedure when SIM “680002” is output.

SIM = 680002
START

Check the status of all DP-VOLs in [Capacity

Saving Status] in the “Logical Devices”
window with Storage Navigator. (*1)

Are there DP-VOLs No

whose [Capacity Saving Status] is
“Failed”?

T.S.D. call
Yes
List all of the DP-VOLs whose [Capacity
Saving Status] is “Failed”.

Do the listed
DP-VOLs include one or more No
deduplication system data volumes
(data store)?

Yes

1 2
(TRBL20-60) (TRBL20-70)

TRBL20-50
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-60

Block the deduplication system data volumes (data store).

Initialize all virtual volumes whose [Deduplication Data] function is [Enabled] in

the pool. (In the [Initialize Duplicated Data] window, click [Apply]. (*2))

Perform the Delete LDEVs operation on the deduplication system data volumes
(data store) by using the [raidcom delete ldev] command of RAID Manager.

END

TRBL20-60
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-70

If blocked pool-VOLs exist in the pool to which the listed DP-VOLs

belong, perform the Format LDEVs operation on the pool-VOLs.

Perform the Format LDEVs operation on the listed DP-VOLs. (*3)

Perform “20.7 Recovery Procedure When the Compression Acceleration

Settings for Deduplication System Data Volumes Are Invalid after
Duplicated Data Initialization”.

Perform the Delete LDEVs (*4) operation on the listed DP-VOLs.

END

*1: This item does not appear in the default state. To display the item, change the setting in the “Column
Settings” window. For details about the “Column Settings” window, see “System Administrator
Guide”
*2: For Command Control Interface, use the [raidcom initialize pool] command.
*3: Do not perform the procedure for LDEV recovery.
*4: If the firmware version is earlier than 88-02-01-x0/xx and the LDEVs are attached to the server
through Hitachi Storage Advisor Embedded (HSAE), perform the procedure through HSAE. For
the detailed procedure, see Hitachi Storage Advisor Embedded Guide “Deleting a volume”. To
start HSAE, specify the URL in the Web browser (see the table in “2.7.3 Starting the Maintenance
Utility Window by Specifying IP Address of CTL” in MAINTENANCE PC SECTION).

TRBL20-70
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-80

20.3 Recovery Procedure when Operation Error of Deduplication System Data Volume
Automatic Deletion is Detected (SIM = 681xxx)
The following is the recovery procedure when SIM “681xxx” is output.

SIM = 681xxx

START

Identify a POOL by the SIM code.

Block all of deduplication system data volumes

that are associated with the identified POOL.

Initialize the deduplication system data volumes.

For Command Control Interface, run the [raidcom initialize pool -pool xx -operation initialize_
deduplication] command.
For more information about initializing the deduplication system data volumes through the Web
Console, refer to the “Provisioning Guide”.

Perform the LDEV format on the blocked

deduplication system data volumes.

Perform “20.7 Recovery Procedure When

the Compression Acceleration Settings for
Deduplication System Data Volumes Are
Invalid after Duplicated Data Initialization”.

Force delete the deduplication system data

volumes from Command Control Interface.
Use the [raidcom modify pool -pool xx -delete
dsd_volumes] command.

Are there no
deduplication system data volumes No
or is [Capacity Saving Status]
[DeletingVolume]?

Yes
Wait until the deduplication system data T.S.D. call
volumes are deleted.

END

TRBL20-80
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-90

20.4 Recovery Procedure when Deduplication System Data Volumes are Suspended (SIM
= 682000)
SIM “682000” is output to indicate that the deduplication system data volume automatic deletion cannot
operate in the storage system.
The deduplication system data volume automatic deletion is resumed by performing the following procedure.

SIM = 682000

START

Is other Yes
maintenance or provisioning in
process? (*2)
Complete the maintenance or provisioning
No operation.

Is
there any blocked part Yes
in the “Maintenance Utility”
window? Recover the blocked part according to the
No related SIM. (TRBL02-640)

Has an abnormality Yes

occurred during LDEV creation or
deletion? (*3)
Direct the LDEV creation or deletion (*1)
again to complete the process.
No

In the
“Logical Devices”
window of Storage
Navigator, check the following: Yes
Is [Capacity Saving Status] of deduplication
system data volumes [Deleting
Volume] and is the progress
not advanced?

No Refer to Provisioning Guide.

The automatic deletion is operable. Wait for the

deletion of deduplication system data volumes
to be complete.

END

TRBL20-90
Hitachi Proprietary DW850/DW900/DW1000
Rev.13 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-100

*1: If the firmware version is earlier than 88-02-01-x0/xx and the LDEVs are attached to the server
through Hitachi Storage Advisor Embedded (HSAE), perform the procedure through HSAE. For
the detailed procedure, see Hitachi Storage Advisor Embedded Guide “Creating a volume” and
“Deleting a volume”. To start HSAE, specify the URL in the Web browser (see the table in “2.7.3
Starting the Maintenance Utility Window by Specifying IP Address of CTL” in MAINTENANCE
PC SECTION).
*2: Check if there is any maintenance work being done with Maintenance Utility and view the “Tasks”
window of Storage Navigator to check if there is any provisioning operation being executed.
*3: In the “Tasks” window of Storage Navigator, check if there is any task that is in the failed status.
And use Command Control Interface to get error information of asynchronous commands (see
Command Control Interface Command Reference “raidcom get command_status”).

TRBL20-100
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-110

20.5 Procedure for Initializing All DP-VOLs for Which Capacity Saving Is Enabled,
Deduplication System Data Volumes (Fingerprint), and Deduplication System Data
Volumes (Data Store) in a Pool

START Ask the customer to do the operation.

In the Web Console main window, select [Logical Devices] from the [Storage Systems] tree, check all DP-VOLs
including the deduplication system data volume associated with the pool.

Back up all DP-VOLs for which Capacity Saving is enabled in the pool. If they are already backed up, this
operation is not required.

Delete all pairs of TrueCopy, Universal Replicator, ShadowImage, Volume Migration and global-active device that
use the DP-VOLs associated with the pool and all Thin Image/Thin Image Advanced pairs (the root volume and the
pairs in the tree (*2)) that use the pool.

Block all the DP-VOLs for which Capacity Saving is enabled in the pool, and then block deduplication system data
volumes.

Initialize all virtual volumes for which Deduplication Data is enabled in the pool. (In the Web Console main
window, select the target pool from the [Pools] tree, select the [Virtual Volumes] tab and [More Actions], and then,
in the “Initialize Duplicated Data” window, click [Apply]. (*1))

Set the System Option Mode 1115 to ON. If the System Option Mode 1115 is already set to ON, this operation is
not required. (*4)

Specify all the blocked deduplication system data volumes (data store) in the pool, and then perform the LDEV
formatting.

Perform the LDEV formatting on all the blocked DP-VOLs for which Capacity Saving is enabled in the pool. (*3)

Set the System Option Mode 1115 to OFF. If the mode is not set to ON in this workflow this operation is not
required. (*4)

Perform “20.7 Recovery Procedure When the Compression Acceleration Settings for Deduplication
System Data Volumes Are Invalid after Duplicated Data Initialization”.

Restore the data from the backup.

For the DP-VOLs and LDEVs associated with the pool, recreate TrueCopy, Universal Replicator, ShadowImage,
Volume Migration and global-active device pairs, and Thin Image/Thin Image Advanced pairs that use the pool.

END

TRBL20-110
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-120

*1: For Command Control Interface, use the [raidcom initialize pool] command.
*2: Delete root volumes of Thin Image/Thin Image Advanced pairs that use the pool and all pairs in
the tree of the root volumes. To identify the root volumes of Thin Image/Thin Image Advanced
pairs that use the pool, specify the pool name (ID) for filtering in the TI Root Volume tab in the
“Local Replication” window of Web Console.
The [Pool Name (ID)] column is not displayed by default. Display it by using the [Column
Settings] button (see System Administrator Guide).
*3: Do not perform the procedure for LDEV recovery.
*4: Perform only when the DKCMAIN firmware version is less than 88-06-03-x0/xx, or less than 93-
02-04-x0/xx.

TRBL20-120
Hitachi Proprietary DW850/DW900/DW1000
Rev.14 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-130

20.6 Recovery Procedure When an Operation Error Is Detected While the Compression
Acceleration Settings for Deduplication System Data Volumes Are Changed (SIM =
689xxx)
The following is the recovery procedure when SIM “689xxx” is output.

SIM = 689xxx

START

Identify a POOL by the SIM code. (xxx: POOL#)

Run the [raidcom get ldev -ldev_list dp_volume

-pool_id xxx] command of Command Control
Interface to check the compression acceleration
status of the deduplication system data volumes (data
store) associated with the identified POOL.

Is the compression
acceleration status of all the deduplication Yes
system data volumes (data store) the
same as expectation (*1) ?
END

No
Remove the factors that prevent the compression
acceleration settings from being changed by performing
troubleshooting for the following SIMs.
• DP Pool LDEV blockade (SIM = 627xxx) (TRBL10-120)
• ACLF error (SIM = 21e0xx) (TRBL02-640)

Change the compression acceleration settings of

the deduplication system data volumes (data store)
by running the [raidcom modify ldev -ldev_id
yyy -compression_acceleration {enable|disable}
-request_id auto] command of Command Control
Interface.

Are the compression acceleration No

settings changed successfully?

Yes T.S.D. call

END

*1: “COMPRESSION_ACCELERATION_STATUS : ENABLED” is displayed when the POOL

contains one or more DP-VOLs for which the compression acceleration is enabled.
“COMPRESSION_ACCELERATION_STATUS : DISABLED” is displayed when the POOL does
not contain a DP-VOL for which the compression acceleration is enabled.
(“COMPRESSION_ACCELERATION_STATUS : HYBRID” might be displayed during update
depending on the timing.)
TRBL20-130
Hitachi Proprietary DW850/DW900/DW1000
Rev.12.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-140

20.7 Recovery Procedure When the Compression Acceleration Settings for Deduplication
System Data Volumes Are Invalid after Duplicated Data Initialization

START

In the main window of the Web Console, select [Logical

Devices] from the [Storage Systems] tree, and check
Compression Acceleration of the virtual volumes for which
Compression and Deduplication is set that are associated
with the initialized POOL and Compression Acceleration
Status of the deduplication system data volumes (data store)
that are associated with the initialized POOL.

Is the compression
acceleration status of all the deduplication Yes
system data volumes (data store) the
same as expectation (*1) ?
END

No

Ask the customer to do the following:

Change the compression acceleration settings of the
deduplication system data volumes (data store) by running
the [raidcom modify ldev -ldev_id yyy -compression_
acceleration {enable|disable} -request_id auto] command of
Command Control Interface.

Are the compression acceleration No

settings changed successfully?

Yes T.S.D. call

END

*1: When Compression Acceleration is set to Enabled for one or more virtual volumes for which
Compression and Deduplication is set, confirm that Compression Acceleration Status is set to
Enabled for all the deduplication system data volumes (data store). If Compression Acceleration
Status is set to Disabled, there is a problem.
When Compression Acceleration is not set to Enabled for any virtual volumes for which
Compression and Deduplication is set, confirm that Compression Acceleration Status is set to
Disabled for all the deduplication system data volumes (data store). If Compression Acceleration
Status is set to Enabled, there is a problem.

TRBL20-140
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-150

20.8 Recovery Procedure When Access to Metadata for dedupe and compression Fails
(SIM = 68bxxx)

START

Are
there blocked
Yes
LDEVs in the pool for which
SIM = 68bxxx is
reported?
Do the blocked LDEVs No
No
include a pool-VOL?

Perform “3.13 Recovery Procedure

Yes for LDEV Blockade (SIM = ef8xxx,
Perform “10.5 Recovery Procedure ef9xxx, db8xxx, db9xxx, dbaxxx,
for pool-VOL Blockade (SIM = dbbxxx, dfaxxx, dfbxxx, 46cxxx,
627xxx)”. 46dxxx)”.

Are there pinned

tracks in LDEVs in the
Yes
pool for which SIM = 68bxxx is
reported?
(See MPC05-1170) Perform “4.2 Pinned track recovery”.

No

END

TRBL20-150
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL20-160

20.9 Recovery Procedure When Inline Deduplication Process by dedupe and

compression Is Delayed (SIM = 68a000)

START

Are there Yes

blocked parts in the storage
system?
Restore the blocked parts.
No

Is the END
firmware version 93-
06-84-x0/00 or later, 93-07-03- Yes
x0/00 or later, 93-07-22-x0/00 or
later, or 88-08-12-xx/00
or later? T.S.D. call

No

Is the System Option Yes

Mode 1191 set to ON?

T.S.D. call
No
Set the System Option Mode 1191 to
ON. (*1)

END

*1: When the System Option Mode 1191 is set to ON, used pool capacity might be temporarily
increased. For details, see “Provisioning Guide”.

TRBL20-160
Hitachi Proprietary DW850/DW900/DW1000
Rev.13.1 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL21-10

21. Dump Collection Troubleshooting

How to deal with a trouble in dump collection

No. Trouble Action

1 An error occurs during the dump The dump collection of DKC might be impossible due to a
collection of DKC and GUM. temporary error of communication. When the dump of DKC is
not stored, retry the dump collection operation.
Refer to MAINTENANCE PC SECTION “5.2 Dump” to check
the dump collection procedure.
2 The “Dump of the following Refer to MAINTENANCE PC SECTION “5.2 Dump” (3)
processors could not be done.” dialog DUMP Gather (b) When an error occurs.
is displayed.
3 DKC dump is not stored. All MPs in DKC might be down.
Confirm with the Technical Support Division and perform the
operation.

The installation status of Maintenance PC or SVP might be

abnormal. Collect the dump manually through the command
line using Maintenance PC (See MAINTENANCE PC
SECTION “5.2 Dump”) or SVP (customer PC) and send it.
(To be continued)

TRBL21-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.11 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL21-20

(Continued from the preceding page)

No. Trouble Action
4 GUM dump is not stored. Because user ID and password are wrong, GUM cannot be
accessed.
When collecting dump, user ID and password are required.
Check them.

[Collecting dump using Maintenance PC]

1. Check the user ID and password that are required for
connecting to DKC on Maintenance PC.
2. Confirm that you can log in to Maintenance Utility with the
user ID and password you checked
3. Collect the dump from Maintenance PC again.

[Collecting dump using SVP]

1. When registering a storage system to Storage Device List,
check if the entered user ID and the password are entered
correctly, and confirm that SN starts.
2. If SN does not start, check that you can log in to
Maintenance Utility with the user ID and password you
entered
3. Collect the dump using SVP again

[Collecting dump using GUM (Maintenance Utility)]

The dump collection from GUM is performed after the login
to Maintenance Utility, so a dump collection failure due to
the incorrect user ID and password does not occur. Therefore,
when you successfully collect the dump from GUM, you can
exclude the possibility of a failure due to the incorrect user ID
and password.
5 GUM Warning might occur, or GUM might be down. reboot
GUM and try dump collection again.
For GUM reboot operations, see MAINTENANCE PC
SECTION “3.18 Reboot GUM”.

TRBL21-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.8 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL22-10

22. Procedure to Be Performed before Downgrading Firmware Version under

the Configuration that Uses Veeam Backup & Replication

When version downgrade of the firmware is suppressed by the function ID = 06:18, ask the customer to
perform the procedure shown below. After completion of the procedure, retry the firmware update.

1. Delete all snapshots (storage snapshots) created by using Veeam Backup & Replication in the storage
system. To identify such snapshots, perform the following:

<How to identify snapshots created by using Veeam Backup & Replication>

A TI snapshot pair that meets all the following conditions contains a TI snapshot (storage snapshot)
created by using Veeam Backup & Replication. Run the raidcom commands to identify a TI snapshot pair
that meets all the following conditions.

Conditions
(1) An S-VOL of a TI snapshot pair belongs to a resource group that has a name starting with “VBR_”.
(2) With the raidcom get snapshot -key opt command, “E” (the Read Only attribute is enabled) is
output in the “R” column.

Identify an LDEV that meets the conditions above by performing the following steps.

Steps
(1) Run the raidcom get resource command to identify an ID of a resource group that has a name
starting with “VBR_”.
(2) Run the raidcom get ldev -ldev_list defined -key front_end -resource <resource ID> command
to identify an LDEV# that belongs to the resource group identified in Step (1). In <resource ID>,
enter the resource group ID identified in Step (1).
(3) Run the raidcom get snapshot -key opt -ldev_id <ldev#> command to identify a pair with the Read
Only attribute enabled. In <ldev#>, enter the LDEV# identified in Step (2). If “E” (the Read Only
attribute is enabled) is output in the “R” column, the TI snapshot is a snapshot created by using
Veeam Backup & Replication.

TRBL22-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.8 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL22-20

The following is an example when running the commands shown in Steps (1) through (3) together with the
rmawk command.

raidcom get resource | rmawk @1-eq:VBR_* | rmawk exe="raidcom get ldev -ldev_
list defined -key front_end -resource @2" | rmawk @L-ne:1 exe="raidcom get snapshot
-ldev_id @2 -key opt" | rmawk @15-eq:E -o @L-eq:1

Output example
In the following example, the snapshots of MU#3 of P-LDEV#1 (LDEV#1) and MU#3 of P-LDEV#4
(LDEV#4) are TI snapshots (storage snapshots) created by using Veeam Backup & Replication.

SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME SLU C_LDEV# P R
Veeam_1 S-VOL SSUS 400007 2 3 1 0 100 ---A 5f0c9458 N - N E
Veeam_2 S-VOL SSUS 400007 5 3 4 0 100 ---A 5f0c946a N - N E

TRBL22-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.12 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL23-10

23. Recovery Procedure for Corruption of GUM Configuration Information

(SIM 7d0d0x)
The corruption of the GUM configuration information is detected, and the user account information needs to
be restored. Ask the customer if there are backups of the user account information.

• When there are backups, ask the customer to restore the user account information from the backups (see
“System Administrator Guide”).

• When there are no backups, all user account information needs to be registered again. Ask the customer to
perform the steps below.

NOTICE: During the registration work of the information on a user account, a login to the
storage system with the user account is not possible. Therefore, perform the
registration work when host management products including Storage Navigator are
less affected.

(1) Set the current password again for the password of the built-in user (user name: maintenance) (see
“System Administrator Guide”).
(2) Delete all created user accounts other than the built-in user (user name: maintenance), and then
create the same user accounts again (see “System Administrator Guide”).

TRBL23-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.16 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL24-10

24. Procedure When Warning Threshold for Cache Write Pending Rate Is
Exceeded (SIM = 493xyy)
The SIM is issued when the state where the Cache Write Pending rate is 73% or higher continues for one
minute in any CLPR#.
Take action according to the following workflow.

START

No
Are businesses affected?

Yes
Contact the Technical Support Division.

Were dumps collected No

by the automatic log dump collection
function? (*1)
Collect the Detail dump by performing Auto
Dump.
Yes
Retrieve Storage system serial number_
[Link]
collected by the automatic log dump
collection function (see MAINTENANCE
PC SECTION “[Link] Copying
Collected Dumps”).

Check whether a blocked part exists or not.

The system configuration and the operating

state might cause the SIM. Check the items
in Table 24-1 as much as possible by asking
the SE or user about them and report the
check results to the Technical Support
Division.

END

*1: SIM = 7c0800 (Dump collection start)

SIM = 7c0900 (Dump collection ends normally)

TRBL24-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL24-20

Table 24-1 Items to Check

No. Item Description
1 I/O The Cache Write Pending rate might be high due to increase of I/Os.
Ask the SE or user to check the following:
Check the usage rates of drives by using Performance Monitor of Performance
Manager. (see Performance Guide).
2 Copy functions The Cache Pending Rate might be high due to copy processing regardless of I/Os.
Ask the SE or user to check the following:
 When the following program products are used, check -1 and -2 with Storage
Navigator.
-1 : global-active device
-2 : ShadowImage
-3 : Thin Image/Thin Image Advanced
-4 : TrueCopy
-5 : Universal Replicator
-6 : Volume Migration
-1 : Whether copy operations are in process in related volumes
-2 : Copy speed of related volumes (other than -6)
3 Configuration The Cache Pending Rate might be high due to changes in the storage system
change configuration and business activities that change the state of internal resources.
Ask the SE or user whether he or she has recently changed the storage system
configuration (MP unit assignment and CLPR capacity) and business activities.

TRBL24-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.17 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL25-10

25. Procedure When Overload of Cache Occurs (SIM = 491000)

The SIM = 491000 is reported if overload of cache (cache write pending rate: 65%) is detected in any MPU
when the System Option Mode 318 is set to ON. To detect cache overload state (where data input from the
host exceeds the destage capacity), set the System Option Mode 318 to ON on the storage system.
The SIM is reported at intervals of one hour during the cache overload state (once the SIM is reported, it will
not be reported for one hour).
When the SIM is reported, collect the Detail dump by performing Auto Dump and contact the Technical
Support Division. The Detail dump includes operational information in addition to the information collected
for the Normal dump. Operational information is necessary for investigating the cause of cache overload in
detail. So, you need to collect the Detail dump.

TRBL25-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL26-10

26. Procedure When Alert Settings Are Initialized due to a Failure At the
Time of CTL Replacement
If both SIM = 7d0axx and SIM = 7d08xx occur when CTL replacement is performed, do the following
workflow because the alert settings might be initialized.

START

Is the GUM
version displayed
with ? in the Firmware window Yes
opened from the Administration
menu of Maintenance
Utility?

No

Is GUM
version displayed in the
No
following format?
CTL1: xx-xx-xx/xx
CTL2: xx-xx-xx/xx
T.S.D. call
Yes

Is either of the following true?

GUM of CTL1 is less than 88-08-10/00 and GUM of CTL2 is
88-08-10/00 or later.
No
GUM of CTL1 is 88-08-10/00 or later and GUM of CTL2 is less than 88-08-10/00.
GUM of CTL1 is less than 93-06-43/00 and GUM of CTL2 is 93-06-43/00 or later.
GUM of CTL1 is 93-06-43/00 or later and GUM of CTL2 is less
than 93-06-43/00. 2
(TRBL26-20)

Yes
Make a note (*1: You will use the note when
you make the settings again) of the following
alert notification settings of the other CTL
than the one for which the replacement
operation failed.
• Email notification setting (3.4.1)
• SNMP setting (3.4.3)
• System group information (3.4.3)
(See MAINTENANCE PC SECTION 3.4
Alert Notifications .)

Perform the dummy replacement of the CTL

for which the replacement operation failed
(see REP02-04-10).

1 (TRBL26-20)

TRBL26-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.2 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL26-20

1 2

Perform the dummy replacement of the CTL

Is the dummy replacement No for which the replacement operation failed
completed normally? (see REP02-04-10).

Yes
No Is the dummy replacement
completed normally?
Display the
firmware version again. Is No
GUM version displayed in the following Yes
format?
CTL: xx-xx-xx/xx
Display the
No firmware version again. Is
Yes GUM version displayed in the following
Make the alert notification settings again format?
according to the values (*1: You made a note CTL: xx-xx-xx/xx
of) set for the other CTL than the one for
which the replacement operation failed (see Yes
MAINTENANCE PC SECTION 3.4 Alert
Notifications ).
* Even when the values in the note are Yes Is SIM = 7d08xx reported
the same as default values, make the alert again?
notification settings again.
No
Reboot GUMs by using Maintenance Utility
of both CTLs (see MAINTENANCE PC END
SECTION 3.18 Reboot GUM ).

Is SIM = 7d08xx reported Yes

again?

No T.S.D. call

END

TRBL26-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL27-10

27. Procedure for Checking the Snapshot Data Retention Period Setting for
Thin Image Advanced Pairs
The snapshot data retention period for Thin Image Advanced pairs functions to protect snapshot data of the
customer.
If the snapshot data retention period setting for Thin Image Advanced pairs is enabled, operations such as
deletion of snapshot data are suppressed.

The following describes how to check the snapshot data retention period setting for Thin Image Advanced
pairs.

• Procedure for viewing the snapshot data retention period setting of a specific Thin Image Advanced pair
(LDEV (volume))

<Method by using the Embedded CLI>

1. Connect to the Embedded CLI according to MAINTENANCE PC SECTION 2.16 Connecting to
Embedded CCI .
2. Run the following command to view the snapshot data retention period setting:
raidcom get snapshot -ldev_id <ldev#> -key details
If S is displayed in the MODE column of the command output, the snapshot data retention period
setting is enabled for the pair.
If S is not displayed in the MODE column of the command output, the snapshot data retention period
setting is disabled for the pair.
For details about how to use the command, see Command Control Interface Command Reference.

TRBL27-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL27-20

• Procedure for viewing the snapshot data retention period setting of all Thin Image Advanced pairs in the
storage system
The following two methods are available.
If you can use RAID Manager installed in the client PC, Maintenance PC, or server, we recommend that
you use it.

<Method by using the Embedded CLI>

1. Connect to the Embedded CLI according to MAINTENANCE PC SECTION 2.16 Connecting to
Embedded CCI .
2. Run the following command to get the list of snapshot groups:
raidcom get snapshot
Command example:
c:\HORCM\etc>raidcom get snapshot
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME
test - - 800089 - - - - - ---- -
test2 - - 800089 - - - - - ---- -

3. For each snapshot group got in Step 2, run the following command to get the list of Thin Image Advanced
pairs:
raidcom get snapshot -snapshotgroup <name> -key details
For <name>, specify a snapshot group name displayed in the SnapShot_name column in the list got in
Step 2.
Command example:
c:\HORCM\etc>raidcom get snapshot -snapshotgroup test -key details
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME SLU C_LDEV# P R D_STAT RETENTION(H)
test P-VOL PSUS 800089 2000 3 - 1 - ---ARS------ 65a6e8c1 - - N D PSUS 1
test P-VOL PSUS 800089 2000 4 2001 1 - ---ARS------ 65a6e8c6 - - N D PSUS 1
test P-VOL PAIR 800089 2000 5 - 1 - ---AR------- - - - N D PAIR -

c:\HORCM\etc>raidcom get snapshot -snapshotgroup test2 -key details

SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME SLU C_LDEV# P R D_STAT RETENTION(H)
test2 P-VOL PSUS 800089 5000 3 - 1 100 ---A-------- 65b63270 - - N D PSUS -

4. If S is displayed in the MODE column of the command output, the snapshot data retention period
setting is enabled for the pair.
If S is not displayed in the MODE column of the command output, the snapshot data retention period
setting is disabled for the pair.
For details about how to use the command, see Command Control Interface Command Reference.
In the command example of Step 3, the snapshot data retention period setting is enabled for the Thin
Image Advanced pair with LDEV#2000 and mirror IDs (MU#) 3 and 4.

TRBL27-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL27-30

<Method by using RAID Manager installed in the client PC, Maintenance PC, or server>
1. Run the following command:
raidcom get snapshot | rmawk @L-ne:1 exe="raidcom get snapshot -snapshotgroup @1 -key details"
Command example:
c:\HORCM\etc>raidcom get snapshot | rmawk @L-ne:1 exe="raidcom get snapshot -snapshotgroup @1 -key details"
SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME SLU C_LDEV# P R D_STAT RETENTION(H)
test P-VOL PSUS 800089 2000 3 - 1 - ---ARS------ 65a6e8c1 - - N D PSUS 1
test P-VOL PSUS 800089 2000 4 2001 1 - ---ARS------ 65a6e8c6 - - N D PSUS 1
test P-VOL PAIR 800089 2000 5 - 1 - ---AR------- - - - N D PAIR -

SnapShot_name P/S STAT Serial# LDEV# MU# P-LDEV# PID % MODE SPLT-TIME SLU C_LDEV# P R D_STAT RETENTION(H)
test2 P-VOL PSUS 800089 5000 3 - 1 100 ---A-------- 65b63270 - - N D PSUS -

2. If S is displayed in the MODE column of the command output, the snapshot data retention period
setting is enabled for the pair.
If S is not displayed in the MODE column of the command output, the snapshot data retention period
setting is disabled for the pair.
For details about how to use the command, see Command Control Interface Command Reference.
In the command example of Step 1, the snapshot data retention period setting is enabled for the Thin
Image Advanced pair with LDEV#2000 and mirror IDs (MU#) 3 and 4.
NOTE: You can run the command without rmawk also with RAID Manager installed in
the client PC, Maintenance PC, or server in the same way as <Method by using the
Embedded CLI>.

TRBL27-30
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL28-10

28. Procedure for Disabling the Snapshot Data Retention Period Setting for
Thin Image Advanced Pairs
The following describes how to disable the snapshot data retention period setting for Thin Image Advanced
pairs. For example, when you downgrade the firmware to the version that does not support the snapshot data
retention period in an environment where there is a Thin Image Advanced pair for which the snapshot data
retention period setting is enabled, you need to disable the snapshot data retention period setting.

• Procedure for disabling the snapshot data retention period setting of a specific Thin Image Advanced pair
1. Contact and ask the Technical Support Division about the settings that you need to make in advance
before disabling the snapshot data retention period setting for Thin Image Advanced pairs.
When you contact the Technical Support Division, tell the following information to them.
• Serial number of the target storage system
• Scheduled time of disabling the snapshot data retention period setting
2. Do the settings that you need to make in advance (see Step 1).
3. Ask the customer to perform the following action.

<Action>
(1) Run the following command to disable the snapshot data retention period setting of the target Thin
Image Advanced pair with its P-VOLs LDEV# and mirror ID specified:
raidcom modify snapshot -ldev_id <ldev#> -mirror_id <mu#> -snapshot_data renew_retention
-retention 0

• Procedure for disabling the snapshot data retention period setting of all Thin Image Advanced pairs in the
storage system
1. Contact and ask the Technical Support Division about the settings that you need to make in advance
before disabling the snapshot data retention period setting.
When you contact the Technical Support Division, tell the following information to them.
• Serial number of the target storage system
• Scheduled time of disabling the snapshot data retention period setting
2. Do the settings that you need to make in advance (see Step 1).
3. Ask the customer to perform the following operations by using either method below. We recommend the
method by using RAID Manager installed in the client PC, Maintenance PC, or server if possible.

TRBL28-10
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL28-20

<Method by using the Embedded CLI>

(1) Identify all Thin Image Advanced pairs for which the snapshot data retention period setting is
enabled in the storage system by performing performing <Method by using the Embedded CLI>
in Procedure for viewing the snapshot data retention period setting of all Thin Image Advanced
pairs in the storage system in 27. Procedure for Checking the Snapshot Data Retention Period
Setting for Thin Image Advanced Pairs .
(2) Disable the snapshot data retention period setting of all the Thin Image Advanced pairs identified
in Step (1) by running the following command:
raidcom modify snapshot -ldev_id <ldev#> -mirror_id <mu#> -snapshot_data renew_retention
-retention 0
For <ldev#>, specify the LDEV# displayed in the "LDEV#" column. For <mu#>, specify the
mirror ID displayed in the MU# column.
Command example:
c:\HORCM\etc>raidcom modify snapshot -ldev_id 2000 -mirror_id 3 -snapshot_data
renew_retention -retention 0

<Method by using RAID Manager installed in the client PC, Maintenance PC, or server>
(1) Run the following command to disable the snapshot data retention period setting of all Thin Image
Advanced pairs in the storage system:
raidcom get snapshot | rmawk @L-ne:1 exe="raidcom get snapshot -snapshotgroup @1 -key
details" | rmawk @10-eq:S* exe="raidcom modify snapshot -ldev_id @5 -mirror_id @6
-snapshot_data renew_retention -retention 0"
Command example:
c:\HORCM\etc>raidcom get snapshot | rmawk @L-ne:1 exe="raidcom get snapshot
-snapshotgroup @1 -key details" | rmawk @10-eq:S* exe="raidcom modify snapshot
-ldev_id @5 -mirror_id @6 -snapshot_data renew_retention -retention 0"

NOTE: You can run the command without rmawk also with RAID Manager installed in
the client PC, Maintenance PC, or server in the same way as <Method by using the
Embedded CLI>.

TRBL28-20
Hitachi Proprietary DW850/DW900/DW1000
Rev.18.3 Copyright © 2018, 2024, Hitachi, Ltd.
TRBL29-10

29. Procedure for Downgrading Firmware When the Configuration Includes

a Thin Image Advanced Pair for Which the Snapshot Data Retention
Period Setting Is Enabled
If downgrading the firmware version is suppressed by the function ID = 10 : 00, perform the following, and
then retry the firmware update.

1. Perform Procedure for disabling the snapshot data retention period setting of all Thin Image Advanced
pairs in the storage system in 28. Procedure for Disabling the Snapshot Data Retention Period Setting
for Thin Image Advanced Pairs .

TRBL29-10