Unity Rescue Reason Codes

Table of Contents:
Rescue Codes: Page 1 - 6
Rescue Reasons: Page 7 - 11
All Reason Codes: Page 11 - 19

This spreadsheet details all the possible reasons why an SP could go into service mode. There are three possible counters/checks that could trigger a code,
and these roll up into a single "Rescue Reason" that shows up on the service page(Flex GUI) and service tasks page(HTML GUI)
For some codes, we also now register "Service Codes" which provide service folks with a little more detail about which component has failed and triggered the SP to enter service mode.
Note: RRCHC and RRC share the same code format and code range. Please check both sheets for RRC/RRCHC registration.

Rescue Reason
Code Fault Description Text in rrc.txt Reason Text Description Action Code in Flex GUI Action Text Description

Boot Control Counters

0x0000 Invalid / No Error No faults detected. Go to the System Health SERVICE_ACTION_0 No action is required.
page to view the health of this 0
Storage Processor (SP).

0x0100 SYSTEM There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (SYSTEM). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor Collection, and then try the
in order: Check all cables, reboot each SP, and reimage (SYSTEM). following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x0204 SSD Not defined in rrc.txt
0x0304 MIRROR Not defined in rrc.txt
0x0402 CCSX There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (CCSX). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor (CCSX). Collection, and then try the
in order: Check all cables, reboot each SP, and reimage following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x0502 CDX Not defined in rrc.txt
0x0602 LOG There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (LOG). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor ((LOG). Collection, and then try the
in order: Check all cables, reboot each SP, and reimage following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x0702 CP CS Not defined in rrc.txt
0x0802 CP ECOM There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (CP ECOM). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor (CP Collection, and then try the
in order: Check all cables, reboot each SP, and reimage ECOM). following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x0905 USER A user has placed this Storage Processor into Service A user has placed this SERVICE_ACTION_2 To return this SP to Normal
Mode (USER). Storage Processor (SP) into 2 Mode, reboot it.
Service Mode.
0x0a00 POST No need to defined in rrc.txt because it's caused by Post
Faults Code
0x0b00 BOOTFL There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (BOOTFL). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor (SP). Collection, and then try the
in order: Check all cables, reboot each SP, and reimage following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x0c00 PLTFORM There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (PLTFORM). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor (SP). Collection, and then try the
in order: Check all cables, reboot each SP, and reimage following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x0d06 (IGNORE) CDX2 Should not cause sp goes to service mode
0x0e06 (IGNORE) CDX3 Should not cause sp goes to service mode
0x0f06 (IGNORE) CDX4 Should not cause sp goes to service mode
0x1000 HLD RST No need to defined in rrc.txt because it's powered off
0x1102 ADMIN There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (ADMIN). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor (SP). Collection, and then try the
in order: Check all cables, reboot each SP, and reimage following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x1200 APPINIT There is a problem with the system software on this There is a problem with the SERVICE_ACTION_1 To attempt to correct this
Storage Processor (APPINIT). To attempt to correct this system software on this 2 problem, first run Data
problem, first run Data Collection, and then try the following Storage Processor (SP). Collection, and then try the
in order: Check all cables, reboot each SP, and reimage following in order: Check all
each Storage Processor (SP). If this does not resolve the cables, reboot each SP, and
issue, contact your service provider. reimage each Storage
Processor (SP). If this does not
resolve the issue, contact your
service provider.
0x1306 (IGNORE) SVCREBOOT Should not cause sp goes to service mode
0x1400 UPGRADE There is a problem with the hardware configuration on this There is a problem with the SERVICE_ACTION_3 Verify that the number of
machine. To correct this problem, Verify that the number of hardware configuration on 1 Storage Processors (SPs) and
Storage Processors and the installed amount of memory is this system. the installed amount of memory
correct. is correct.
0x1506 (IGNORE) SVCREIMAGE Should not cause sp goes to service mode
0x1606 (IGNORE) SVCHALT Should not cause sp goes to service mode
0x1706 (IGNORE) SVCMODE Should not cause sp goes to service mode
0x1800 AUTOPWROFF No need to defined in rrc.txt because it's powered off
0x1900 MANPWROFF This Storage Processor (SP) is ready to be manually shut There was a problem shutting SERVICE_ACTION_3 Pull the power cables from the
(If there is a down. Pull the power cables from the device to complete down the Storage Processor. 2 device to complete the shutdown
issue disabling the shutdown sequence. sequence.
write cache
during system
shutdown, or if
write cache is
already
disabled, SPs
reboot into
service mode)
0x1a00 FW There is a problem with upgrading the firmware There is a problem with SERVICE_ACTION_3 Please run Data Collection and
(BIOS/POST/BMC/FWBN/BROADCOM) on this Storage upgrading the firmware 7 then contact your service
Processor. Please run Data Collection and then contact (BIOS/POST/BMC/FWBN/BR provider.
your service provider. OADCOM) on this Storage
Processor.
0x1b00 SOFTWARE There is a problem with the system software on this N/A N/A N/A
(Note: there are Storage Processor (SOFTWARE). To attempt to correct
some related this problem, first run Data Collection, and then try the
RRCHC codes following in order: Check all cables, reboot each SP, and
for this boot reimage each Storage Processor (SP). If this does not
counter fault. resolve the issue, contact your service provider.
See RRCHC
sheet.)

POST Fault Code

0x8001 Fault detected in This Storage Processor (SP) has failed. Replace this SP. This Storage Processor (SP) SERVICE_ACTION_0 Replace this SP.
CPU has failed. 1
0x8002 Fault detected in I/O module 0 in this Storage Processor (SP) has failed. I/O module 0 in this Storage SERVICE_ACTION_0 Replace I/O module 0 in this SP.
SLIC0 Replace I/O module 0 in this SP. Processor (SP) has failed. 2

0x8003 Fault detected in I/O module 1 in this Storage Processor (SP) has failed. I/O module 1 in this Storage SERVICE_ACTION_0 Replace I/O module 1 in this SP.
SLIC1 Replace I/O module 1 in this SP. Processor (SP) has failed. 3

0x8004 Faulted detected This Storage Processor (SP) and I/O module 0 have failed. This Storage Processor (SP) SERVICE_ACTION_0 Replace this SP and I/O module
in CPU and Replace this SP and I/O module 0. and I/O module 0 have failed. 4 0.
SLIC0

0x8005 Faulted detected This Storage Processor (SP) and I/O module 1 have failed. This Storage Processor (SP) SERVICE_ACTION_0 Replace this SP and I/O module
in CPU and Replace this SP and I/O module 1. and I/O module 1 have failed. 5 1.
SLIC1

0x8006 Faulted detected This Storage Processor (SP) and all of its memory This Storage Processor (SP) SERVICE_ACTION_0 Replace this SP and replace all
in CPU and modules (DIMMs) have failed. Replace this SP and replace and all of its memory 6 of its memory modules (DIMMs).
memory DIMMS all of its memory modules (DIMMs). modules (DIMMs) have failed.

0x8007 Fault detected in All memory modules (DIMMs) in this Storage Processor All memory modules (DIMMs) SERVICE_ACTION_0 Replace all memory modules
DIMMs (SP) have failed. Replace all memory modules (DIMMs) in in this Storage Processor 6a (DIMMs) in this SP.
this SP. (SP) have failed.
0x8008 Fault detected in Memory module 0 (DIMM 0) in this Storage Processor (SP) Memory module 0 (DIMM 0) SERVICE_ACTION_0 Replace memory module 0
DIMM 0 has failed. Replace memory module 0 (DIMM 0) in this SP. in this Storage Processor 6b (DIMM 0) in this SP.
(SP) has failed.
0x8009 Fault detected in Memory module 1 (DIMM 1) in this Storage Processor (SP) Memory module 1 (DIMM 1) SERVICE_ACTION_0 Replace memory module 1
DIMM 1 has failed. Replace memory module 1 (DIMM 1) in this SP. in this Storage Processor 6c (DIMM 1) in this SP.
(SP) has failed.
0x800A Fault detected in Memory module 2 (DIMM 2) in this Storage Processor (SP) Memory module 2 (DIMM 2) SERVICE_ACTION_0 Replace memory module 2
DIMM 2 (Sentry has failed. Replace memory module 2 (DIMM 2) in this SP. in this Storage Processor 6d (DIMM 2) in this SP.
only) (SP) has failed.

0x800C Fault detected in Memory module 1 (DIMM 1) and memory module 2 (DIMM Memory module 1 (DIMM 1) SERVICE_ACTION_0 Replace memory module 0
DIMMs 0 & 1 2) in this Storage Processor (SP) have failed. Replace and memory module 2 (DIMM 6e (DIMM 0) and memory module 1
(TBD) memory module 0 (DIMM 0) and memory module 1 (DIMM 2) in this Storage Processor (DIMM 1) in this SP.
1) in this SP. (SP) have failed.
0x800E Fault detected in The solid state disk (SSD) in this Storage Processor (SP) The solid state disk (SSD) in SERVICE_ACTION_0 Replace the solid state disk
SSD has failed. Replace the solid state disk (SSD) in this SP. this Storage Processor (SP) 7 (SSD) in this SP.
has failed.
0x800F Faulted detected This Storage Processor (SP) has failed. Replace this SP This Storage Processor (SP) SERVICE_ACTION_0 Replace this SP and all of its
in entire blade and all of its components (memory modules, I/O module, has failed. 8 components (memory modules,
solid state disk, etc.). I/O module, solid state disk,
etc.).
0x8010 Faulted detected The SAS cable connected to this Storage Processor (SP) The SAS cable connected to SERVICE_ACTION_0 Check that the cable is not
in Fibre Cable is missing or damaged. Check that the cable is not this Storage Processor (SP) 9 damaged and is connected
Connection damaged and is connected securely to this SP. If the cable is missing or damaged. securely to this SP. If the cable
is missing or damaged, order a replacement. is missing or damaged, order a
replacement.
0x8011 Faulted detect in Fault detected in the DPE chassis. Power-cycle the DPE. If Fault detected in the DPE SERVICE_ACTION_1 Power-cycle the DPE. If the
the DPE the problem persists, contact service to replace the DPE. chassis. 0 problem persists, contact
Enclosure service to replace the DPE.

0x8013 Fault detected in This Storage Processor (SP) has a hardware mismatch. This Storage Processor (SP) SERVICE_ACTION_2 Contact your service provider to
the SP Contact your service provider to replace the mismatched has a hardware mismatch. 3 replace the mismatched
hardware components. hardware components.

BE Check Code
0x80b0 An unexpected An unexpected error has occurred. Power-cycle this SP. If An unexpected error has SERVICE_ACTION_1 Power-cycle this SP. If problem
error has problem persists, power-cycle the SP and all DAE occurred. 3 persists, power-cycle the SP and
occurred. enclosures. all DAE enclosures.
0x80b4 Detected at Detected at least one missing disk in the first 4 disks in the Detected at least one missing SERVICE_ACTION_1 Insert the missing disk(s). If disk
least one DPE. Insert missing DPE disk(s). If disk is already disk in the first 4 disks in the 6 is already inserted, replace it.
missing disk in inserted, replace it. The Service Code below should DPE. The service code below should
the first 4 disks indicate which disks are causing the problem. indicate which disks are causing
in the DPE, and the problem.
becheck is
checking for
install-blocking
errors. This
error is also
returned when
two or more
disks out the
first four DPE
disks are
missing in all
modes.

0x80b7 No SAS Cannot detect a SAS port on this Storage Processor (SP). Cannot detect a SAS port on SERVICE_ACTION_1 Replace this SP.
Controller found Replace this SP. this Storage Processor (SP). 7
0x80b8 Invalid Disk Invalid disk type detected. Replace unsupported disk type Invalid disk type detected. SERVICE_ACTION_2 Replace unsupported disk type
type. For with appropriate type (SAS or EFD). The Service Code 5 with appropriate type (SAS or
example if SATA below should indicate which disks are causing the problem. EFD). The Service Code below
disk is plugged should indicate which disks are
into the one of causing the problem.
the first 4 slots
in the DPE.

0x80b9 No I/O between No I/O between the SP SAS Controller and the disks. No I/O between the SAS SERVICE_ACTION_2 Reboot this SP. If the problem
SP SAS Reboot this SP. If the problem persists, power-cycle the controller on this Storage 6 persists, power-cycle the DPE. If
Controller and DPE. Processor (SP) and the disks. the problem still persists, the SP
disks. is faulted and needs
replacement.
0x80bd Detected at Detected at least one faulted disk in the first 4 disks in the One or more disks in the first SERVICE_ACTION_2 Replace the faulted disk(s) in the
least one faulted DPE. Replace the faulted disk(s) in the DPE. The Service 4 disk slots of the disk- 7 DPE. The Service Code below
disk in the first 4 Code below should indicate which disks are causing the processor enclosure (DPE) should indicate which disks are
disks in the problem. have faulted. causing the problem.
DPE, and
becheck is
checking for
install-blocking
errors.
0x80be Failed to run Unable to communicate with backend, disk status is Cannot get the status of disks SERVICE_ACTION_2 Reboot this SP. If the problem
backend check. unknown. Reboot this SP. If the problem persists, power-used by this Storage 6 persists, power-cycle the DPE. If
Disk status is cycle the DPE. If the problem still persists, the SP is Processor (SP). the problem still persists, the SP
not known. faulted and needs replacement. is faulted and needs
replacement.
0x80bf The first 4 disks The first 4 disks in the DPE have mismatched types. The first 4 disks in the DPE SERVICE_ACTION_2 Ensure that the first 4 disks in
in the DPE have Ensure that the first 4 disks in the DPE have indentical size have mismatched types. 8 the DPE have identical size and
mismatched and type. The Service Code below should indicate which type. The Service Code below
types disks are causing the problem. should indicate which disks are
causing the problem.
0x80c0 Invalid Disk Disk detected with an invalid block size. Replace the Disk detected with an invalid SERVICE_ACTION_2 Replace the disk(s) with ones
block size. For disk(s) with ones that have a sector size of 520. The block size. 9 that have a sector size of 520.
example if disk Service Code below should indicate which disks are The Service Code below should
formatted with causing the problem. indicate which disks are causing
block size other the problem.
than 520 (i.e.
512) is plugged
into the one of
the first 4 slots
in the DPE.
0x80c1 The first 4 disks The first 4 disks in the DPE have mismatched sizes. The disk in the first 4 disk SERVICE_ACTION_2 Ensure that the first 4 disks in
in the DPE have Ensure that the first 4 disks in the DPE have indentical size slots in the disk-processor 8 the DPE have identical size and
mismatched and type. The Service Code below should indicate which enclosure (DPE) have type. The Service Code below
sizes disks are causing the problem. mismatched sizes. should indicate which disks are
causing the problem.
0x80c2 The DPE The DPE resume is missing the EMC Product Serial The disk-processor enclosure SERVICE_ACTION_3 Contact your service provider to
resume is Number. Contact your service provider, the correct serial (DPE) resume is missing the 0 have the Product ID / SN
missing EMC number needs to be programmed. EMC Product ID / SN. programmed on your system.
Product Serial
Number.
 Unity Rescue Reasons Hint Codes

This spreadsheet details all the possible Rescue Reason Code Hint Codes (RRCHC) which provide more specific reasons why an SP could go into service mode.
The RRCHC is usually used together with Rescue Reason Code. RRC may only describe generic rescue reason, and RRCHC can provide more specific hint.
Note: RRCHC and RRC share the same code format and code range. Please check both sheets for RRC/RRCHC registration.

Rescue Reason
Code Hint Code Fault Description Text in rrc.txt Reason GUI Code Reason Text Description Action GUI Code Action Text Description

0x1b01 MCR degraded mode There is a problem with the SERVICE_ERR_0x1b01 There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - The database system software on this Storage the system software on _12 Collection, and then try the following in order:
configuration could not Processor. To attempt to correct this Storage Processor. Check all cables, reboot each SP, and reimage
be loaded or data has this problem, first run Data each Storage Processor (SP). If this does not
been corrupted. Collection, and then try the resolve the issue, contact your service provider.
following in order: Check all
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.

0x1b02 MCR degraded mode The chassis WWN Seed and SERVICE_ERR_0x1b02 The chassis WWN SERVICE_ACTION Please put the original chassis back and follow
reason System Drives WWN Seed do Seed and System _33 the correct chassis replacement procedure.
not match. Please put the Drives WWN Seed do
original chassis back and follow not match.
the correct chassis replacement
procedure.

0x1b03 MCR degraded mode System drive(s) are in the SERVICE_ERR_0x1b03 System drive(s) are in SERVICE_ACTION If any of the system drives was moved, put it
reason incorrect slot(s). If any of the the incorrect slot(s). _34 back in the original slot or contact your service
system drives was moved, put it provider.
back in the original slot or
contact your service provider.

0x1b04 MCR degraded mode Two or more system drives are in SERVICE_ERR_0x1b04 Two or more system SERVICE_ACTION To attempt to correct this problem, first run Data
reason an invalid state. To attempt to drives are in an invalid _12 Collection, and then try the following in order:
correct this problem, first run state. Check all cables, reboot each SP, and reimage
Data Collection, and then try the each Storage Processor (SP). If this does not
following in order: Check all resolve the issue, contact your service provider.
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.
0x1b05 MCR degraded mode Two non-system drives have SERVICE_ERR_0x1b05 Two non-system drives SERVICE_ACTION If drives were moved put the drives back in their
reason been detected in system drive have been detected in _35 original slots or contact your service provider.
slots, and at least one of the system drive slots, and
system drives is in a user slot. If at least one of the
drives were moved put the drives system drives is in a
back in their original slots or user slot.
contact your service provider.

0x1b06 MCR degraded mode There is a problem with the SERVICE_ERR_0x1b06 There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - The chassis system software on this Storage the system software on _12 Collection, and then try the following in order:
replacement flag and Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
the user-modified flag this problem, first run Data (code 0x1b06). each Storage Processor (SP). If this does not
for the WWN seed are Collection, and then try the resolve the issue, contact your service provider.
mutually exclusive, but following in order: Check all
in this case both are cables, reboot each SP, and
set which is not reimage each Storage Processor
allowed. (SP). If this does not resolve the
issue, contact your service
provider.

0x1b07 MCR degraded mode There is a problem with the SERVICE_ERR_0x1b07 There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - Failed to read system software on this Storage the system software on _12 Collection, and then try the following in order:
the system database Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
header. this problem, first run Data (code 0x1b07). each Storage Processor (SP). If this does not
Collection, and then try the resolve the issue, contact your service provider.
following in order: Check all
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.

0x1b08 MCR degraded mode There is a problem with the SERVICE_ERR_0x1b08 There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - The system system software on this Storage the system software on _12 Collection, and then try the following in order:
header which was read Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
from the drive is this problem, first run Data (code 0x1b08). each Storage Processor (SP). If this does not
greater than the Collection, and then try the resolve the issue, contact your service provider.
expected size. The following in order: Check all
header size was cables, reboot each SP, and
changed without reimage each Storage Processor
initializing the (SP). If this does not resolve the
persistent storage. issue, contact your service
provider.
0x1b09 MCR degraded mode There is a problem with the SERVICE_ERR_0x1b09 There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - The System system software on this Storage the system software on _12 Collection and then try the following in order:
DB Magic number was Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
not what was expected this problem, first run Data (code 0x1b09). each Storage Processor (SP). If none of these
and so the DB Data Collection, and then try the resolve the issue, contact your service provider.
may not be correct. following in order: Check all
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.

0x1b0a MCR degraded mode There is a problem with the SERVICE_ERR_0x1b0a There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - An invalid system software on this Storage the system software on _12 Collection and then try the following in order:
memory configuration Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
was detected by the this problem, first run Data (code 0x1b0a). each Storage Processor (SP). If none of these
database service. Collection, and then try the resolve the issue, contact your service provider.
following in order: Check all
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.

0x1b0b MCR degraded mode There is a problem with the SERVICE_ERR_0x1b0b There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - This SP’s system software on this Storage the system software on _12 Collection, and then try the following in order:
database version is Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
inconsistent with its this problem, first run Data (code 0x1b0b). each Storage Processor (SP). If this does not
Peer’s database Collection, and then try the resolve the issue, contact your service provider.
version. following in order: Check all
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.

0x1b0c MCR degraded mode The system drive size is smaller SERVICE_ERR_0x1b0c The system drive size is SERVICE_ACTION Replace the system drive with a supported drive
reason than the minimum required size. smaller than the _36 size.
Replace the system drive with a minimum required size.
supported drive size.
0x1b0d MCR degraded mode There is a problem with the SERVICE_ERR_0x1b0d There is a problem with SERVICE_ACTION To attempt to correct this problem, first run Data
reason - Initialization system software on this Storage the system software on _12 Collection, and then try the following in order:
flag is not set on all the Processor. To attempt to correct this Storage Processor Check all cables, reboot each SP, and reimage
required drives. this problem, first run Data (code 0x1b0d). each Storage Processor (SP). If this does not
Collection, and then try the resolve the issue, contact your service provider.
following in order: Check all
cables, reboot each SP, and
reimage each Storage Processor
(SP). If this does not resolve the
issue, contact your service
provider.

0x1b20 MCF/MCC degraded There is a problem with the SERVICE_ERR_0x1b20 There is a problem with SERVICE_ACTION Please run Data Collection and then contact
mode reason - FCT system software on this Storage the system software on _37 your service provider.
faulted, MCC cache Processor. Please run Data this Storage Processor
lost, or MCC cache not Collection and then contact your (code 0x1b20).
recoverable service provider.

0x1b30 vVNX - unsupported Virtual hardware configuration

configuration of virtual doesn't match supported profiles.
hardware. Please fix configuration via Virtual hardware
hypervisor hosting the virtual configuration doesn't
machine. match supported SERVICE_ACTION Please fix configuration via hypervisor hosting
SERVICE_ERR_0x1b30 profiles (code 0x1b30). _38 the virtual machine.
0x1b10 Keystore corrupt Keystore on this Storage SERVICE_ERR_0x1b10 Keystore on this SERVICE_ACTION Please use svc_restore_keys command to
Processor (SP) has been Storage Processor (SP) _39 restore the keystore from the keystore backup
corrupted. Use is corrupted (code copy.
svc_restore_keys command to 0x1b10)
restore the keystore from the
keystore backup copy.
 Unity Rescue Service Codes - All Codes

This spreadsheet details all the possible Service Codes that could get registered by various components to make it easier
for service and engineering to detect why an SP is in service mode.

Boot Ctrl Counter Hint Code Text in hints.txt Reason & Action

PLTFORM 0xFC0C5001 Failed to determine platform, sptool failure. Failed to determine platform, sptool failure.

PLTFORM 0xFC0C5002 Failed to start CSX environment. c4-csx-env.sh has failed. Failed to start CSX environment. c4-csx-env.sh has failed.

PLTFORM 0xFC0C5003 Cminet has failed. Cminet has failed.

PLTFORM 0xFC0C5004 c4-flare.sh has failed, SAFE stopped/panicked, newSP c4-flare.sh has failed, SAFE stopped/panicked, newSP
reboot/failure, mirror has failed to mount. See reboot/failure, mirror has failed to mount. See
/EMC/C4Core/log/start_c4.log. /EMC/C4Core/log/start_c4.log.

PLTFORM 0xFC0C5005 c4-configdb has failed. c4-configdb has failed.

PLTFORM 0xFC0C5006 c4-heartbeat had failed. c4-heartbeat had failed.
PLTFORM 0xFC0C5007 rom-device had failed. rom-device had failed.

PLTFORM 0xFC0C5008 Failed to start driver software because c4-flare.sh has failed. Failed to start driver software because c4-flare.sh has failed.
A driver in the system has set a “degraded” state bit in A driver in the system has set a “degraded” state bit in
NVRAM and wants to put the local SP into service mode due NVRAM and wants to put the local SP into service mode
to a fault in that driver that will prevent the rest of the due to a fault in that driver that will prevent the rest of the
software on the SP to load and run properly. To determine software on the SP to load and run properly. To determine
the affected driver run ‘nvramutil --get deg_drv’. the affected driver run ‘nvramutil --get deg_drv’.

PLTFORM 0xFC0C5009 GMS service has failed. GMS service has failed.

PLTFORM 0xFC0C500A CSX display support, if set, has failed. CSX display support, if set, has failed.

PLTFORM 0xFC0C500B CSX Helper, which controls registry access, has failed. CSX Helper, which controls registry access, has failed.
Registry is likely offline. Registry validation is required. Registry is likely offline. Registry validation is required.

PLTFORM 0xFC0C500C Ndu service has failed. Likely causes are failure to determine Ndu service has failed. Likely causes are failure to
if performing an "auto-commit" of the SAFE container is safe determine if performing an "auto-commit" of the SAFE
to do. See /EMC/C4Core/log/ndu_commit.log and container is safe to do. See
/EMC/C4Core/log/start_c4.log to determine real cause. /EMC/C4Core/log/ndu_commit.log and
/EMC/C4Core/log/start_c4.log to determine real cause.

PLTFORM 0xFC0C500D Init private luns script failure. Unable to correctly init the Init private luns script failure. Unable to correctly init the
private luns needed by the system or unable to determine if private luns needed by the system or unable to determine if
the init is required. This verification is required for proper the init is required. This verification is required for proper
function of the SP. function of the SP.
PLTFORM 0xFC0C500E The TLDListener( c4-flare-admin.sh) has failed all of its The TLDListener( c4-flare-admin.sh) has failed all of its
retries. This service is required for all administrative retries. This service is required for all administrative
operations and cannot start. operations and cannot start.

PLTFORM 0xFC0C500F Iscsi zones Daemon(c4-flare-izdaemon.sh) has failed all of Iscsi zones Daemon(c4-flare-izdaemon.sh) has failed all of
its retries. This affects all ability of this SP to import FLUs its retries. This affects all ability of this SP to import FLUs
from external sources; example RPSplitter FLUs. from external sources; example RPSplitter FLUs.

PLTFORM 0xFC0C5010 PEServixe(c4-flare-peservice.sh) has failed all of its retries. PEServixe(c4-flare-peservice.sh) has failed all of its retries.
This affect all ability of performing auto-tiering. This affect all ability of performing auto-tiering.

PLTFORM 0xFC0C5011 Remote Agent(c4-flare-remoteagent.sh) has failed all of its Remote Agent(c4-flare-remoteagent.sh) has failed all of its
retries. Inernal to EMC only. This affect all ability to perform retries. Inernal to EMC only. This affect all ability to perform
DAQ testing externally. (This service is disabled for DAQ testing externally. (This service is disabled for
customer rigs but is critical to EMC arrays.) customer rigs but is critical to EMC arrays.)

PLTFORM 0xFC0C5012 C4-detect-degrade.sh has failed to access the NVRAM to C4-detect-degrade.sh has failed to access the NVRAM to
determine if the software is degraded or not. determine if the software is degraded or not.

PLTFORM 0xFC0C5013 DedupDirectorService(c4-flare-dedupdirectorservice.sh) has DedupDirectorService(c4-flare-dedupdirectorservice.sh) has

failed its retries. This affects the ability of performing all of failed its retries. This affects the ability of performing all of
deduplication functionality. deduplication functionality.

PLTFORM 0xFC0C5014 Pool Service process to manage Feature Storage LUN to Pool Service process to manage Feature storage LUN to
store metadata for services like deduplication (c4-flare- store metadata for services like deduplication (c4-flare-
poolservice.sh) has failed its retries. This affects the ability of poolservice.sh) has failed its retries. This affects the ability
run deduplication pass. of run deduplication pass.

PLTFORM 0xFC0C5015 Automigrator daemon(c4-flare-automigd.sh) has failed all its Automigrator daemon(c4-flare-automigd.sh) has failed all its
retries. This service is required for Migration TLD poll retries to load. This service is required for Migration TLD
operations to update job cache which is looked up by poll operations to update job cache which is looked up by
components of Automigrator to track the progress of components of Automigrator to track the progress of
migration. migration.

ADMIN 0xFC115004 (not in hints.txt. is this code still used?) Failure to start c4-flare-admin. SW issues or configuration
issues - check backend health/reboot both
SPs/reimage/reinit

APPINIT 0xFC12CDD1 Dart root LUNs are cache dirty, escalate to fix cache dirty dart root luns cache dirty, fix cache dirty (manual
procedure), or reinit

APPINIT 0xFC12CDF1 nasdb/c4loga are cache dirty, escalate to fix cache dirty nasdb/c4loga cache dirty, fix cache dirty (manual
procedure), or reinit

CDX2 0xFC0D6003 Dart 2 failed, possibly backend connectivity issues or config Dart 2 failed, possibly backend connectivity issues or config
issues issues
CDX4 0xFC0F6003 Dart 4 failed, possibly backend connectivity issues or config Dart 4 failed, possibly backend connectivity issues or config
issues issues
CP ECOM 0xFC086002 Try to fix up the management IP info (ip, mask, gateway, try Try to fix up the management IP info (ip, mask, gateway, try
changing - may be SSL certificate will eb regenerated). If changing - may be SSL certificate will eb regenerated). If
doesn't help - same as 0xFC066001 doesn't help - same as 0xfc066001

LOG 0xFC066001 Probably a data corruption on the service LUN - reinit only Probably a data corruption on the service LUN - reinit only
(but does not hurt to try to reimage) (but does not hurt to try to reimage)

BOOTFL 0xFC0B0100 MBR write to bootflash failed MBR write to bootflash failed; could try bootflash
replacement; check if /dev/bootflash exists; collect udevadm
info –p –a /sys/class/sdb ; escalate

BOOTFL 0xFC0B0101 Bootflash device not found Bootflash device not found; could try bootflash replacement;
check if /dev/bootflash exists; collect udevadm info –p –a
/sys/class/sdb ; escalate
BOOTFL 0xFC0B0120 Could not reinitialize backend Could not reinitialize backend; lab/mfg-only ; escalate if
found in the field
BOOTFL 0xFC0B0121 Could not put down PMP structure Could not put down PMP structure; collect logs, show ls
/dev/ssd* /dev/sd*, escalate
BOOTFL 0xFC0B0122 Could not partition SSD for temporary storage Could not partition SSD for temporary storage; collect logs,
show ls /dev/ssd* /dev/sd*, escalate
BOOTFL 0xFC0B0123 Could not start internal network Could not start internal network

BOOTFL 0xFC0B0130 Could not upgrade Broadcom firmware Could not upgrade Broadcom firmware

BOOTFL 0xFC0B0140 Minimum BIOS/POST requirements not met Minimum BIOS/POST requirements not met

BOOTFL 0xFC0B0141 Failed to write firmware images to backend Failed to write firmware images to backend

BOOTFL 0xFC0B0200 Could not bring up CSX Could not bring up CSX; collect logs ; check for bad disks ;
escalate
BOOTFL 0xFC0B0201 Could not start platform container Could not start platform container; collect logs ; check for
bad disks ; escalate
BOOTFL 0xFC0B0202 Could not load asidc driver Could not load asidc driver; collect logs ; check for bad disks
; escalate
BOOTFL 0xFC0B0203 Could not load mirror driver Could not load mirror driver; collect logs ; check for bad
disks ; escalate
BOOTFL 0xFC0B0204 C4 Mirror device not available C4 Mirror device not availabl; collect logs ; check for bad
disks ; escalate
BOOTFL 0xFC0B0205 C4 Mirror device partitions not available C4 Mirror device partitions not available; collect logs ; check
for bad disks ; escalate
BOOTFL 0xFC0B0206 Could not setup registry for Platform container; could be One of "featurestate --update" or "setup_flare_env.pl" scripts
caused by configuration script internal error failed; collect logs ; escalate
BOOTFL 0xFC0B0220 Could not get HW Platform type Could not get HW Platform type; collect logs, escalate
BOOTFL 0xFC0B0221 Could not bring up CSX Could not bring up CSX; lab/mfg-only ; escalate if found in
the field
BOOTFL 0xFC0B0222 Could not start platform container Could not start platform container; lab/mfg-only ; escalate if
found in the field
BOOTFL 0xFC0B0223 Could not load asidc driver Could not load asidc driver; lab/mfg-only ; escalate if found
in the field
BOOTFL 0xFC0B0224 Could not get HW Family type Could not get HW Family type

BOOTFL 0xFC0B0225 Could not load ntmirror driver. Wrong slot for vault drives Could not load ntmirror driver. Wrong slot for vault drives

BOOTFL 0xFC0B0226 Could not get HW Model name Could not get HW Model name

BOOTFL 0xFC0B0227 Could not get HW internal name Could not get HW internal name

BOOTFL 0xFC0B0230 (not in hints.txt. This code is not likely to be seen at a Could not figure out memory amount; escalate to dev
customer site)
BOOTFL 0xFC0B0231 (not in hints.txt. This code is not likely to be seen at a Could not create system_rcr ; escalate to dev ; this would
customer site) generally mean a software bug

BOOTFL 0xFC0B0232 (not in hints.txt. This code is not likely to be seen at a Could not store new system_rcr to the backend; could be a
customer site) safe crash. It should try again on a reboot, but that’ll likely
fail too. reimage won’t help. OS install without –reinit may or
may not help. Escalate otherwise
BOOTFL 0xFC0B0300 Could not retrieve image from peer Could not retrieve image from peer; if peer is up and
running, escalate; otherwise you can try bringing the peer up
first and try again
BOOTFL 0xFC0B0301 Could not link image to /tmp location Could not link image to /tmp location; collect logs; do an ls
of /tmp and the image location, do a df, try a touch in /tmp;
escalate
BOOTFL 0xFC0B0302 Could not make image executable Could not make image executable; collect logs; do an ls of
/tmp and the image location, do a df, try a touch in /tmp;
escalate
BOOTFL 0xFC0B0303 0-byte image detected 0-byte image detected; if a dual-SP system and the other
SP is ok, boot with neo.invalidateir=1; if that doesn’t help,
escalate
BOOTFL 0xFC0B0304 Image failed integrity check Image failed integrity check; if a dual-SP system and the
other SP is ok, boot with neo.invalidateir=1; if that doesn’t
help, escalate
BOOTFL 0xFC0B0305 Could not prepare backend mirror device for image Could not prepare backend mirror device for image
repository use repository use; collect logs, check existence of
/dev/mirror{a,b}, escalate
BOOTFL 0xFC0B0306 Could not put image on image repository Could not put image on image repository

BOOTFL 0xFC0B0307 Could not mount image repository Could not mount image repository; if a dual-SP system and
the other SP is ok, boot with neo.invalidateir=1; if that
doesn’t help, escalate
BOOTFL 0xFC0B0308 Could not retrieve backend config file Could not retrieve backend config file; if a dual-SP system
and the other SP is ok, boot with neo.invalidateir=1; if that
doesn’t help, escalate
BOOTFL 0xFC0B0309 The mirror has failed to validate properly The mirror has failed to validate properly after
<$VAL_MAX_TRIES> tries; collect logs, escalate
BOOTFL 0xFC0B030A Failure during image installation Failure during image installation; collect logs, escalate

BOOTFL 0xFC0B030B Error while validating main runtime copy Error while validating main runtime copy; could try corrupting
the mirror but would prefer straight escalate

BOOTFL 0xFC0B030C Could not mount root partition on backend. World collapsing Could not mount root partition on backend. World
collapsing; could try corrupting the mirror but would prefer
straight escalate
BOOTFL 0xFC0B030D Could not retrieve install.config file Could not retrieve backend.config or boot.config file; if a
dual-SP system and the other SP is ok, boot with
neo.invalidateir=1; if that doesn’t help, escalate
BOOTFL 0xFC0B030E Could not find root device Could not find root device; collect logs, ls /dev/ssd*,
escalate
BOOTFL 0xFC0B030F could not exec run-init could not exec run-init; try svc_reimage, otherwise escalate

BOOTFL 0xFC0B0310 OS Image revision mismatch OS Image revision mismatch

BOOTFL 0xFC0B0311 Could not communicate with peer SP during reinit-dual

execution
BOOTFL 0xFC0B0312 Could not sync with peer SP during reinit-dual execution

BOOTFL 0xFC0B0313 Unable to create encrypted device Unable to create encrypted device; lab/mfg-only; escalate if
found in the field
BOOTFL 0xFC0B0320 Could not invalidate existing config Could not invalidate existing config

BOOTFL 0xFC0B0321 Could not determine SP ID Could not determine SP ID

BOOTFL 0xFC0B0330 Could not mount temporary storage partition on SSD Could not mount temporary storage partition on SSD; collect
logs, show ls /dev/ssd* /dev/sd*, escalate
BOOTFL 0xFC0B0400 Failed to check or install hotfixes Failed to check or install hotfixes

BOOTFL 0xFC0B0401 Failed to check or apply upgrades Failed to check or apply upgrades

BOOTFL 0xFC0B0402 Failed to create runtime boot partition Failed to create runtime boot partition

BOOTFL 0xFC0B0403 Failed to create runtime root partition Failed to create runtime root partition

BOOTFL 0xFC0B0404 Failed to make sim substs Failed to make sim substs

BOOTFL 0xFC0B0450 Failed to create boot partition Failed to create boot partition
BOOTFL 0xFC0B0451 Failed to create peer boot partition Failed to create peer boot partition

BOOTFL 0xFC0B0452 Failed to create root partition Failed to create root partition

BOOTFL 0xFC0B0453 Failed to configure network Failed to configure network

BOOTFL 0xFC0B0800 Failed to mount root partition, try rebooting. If the problem Could not mount the root partition in order to generate disk
persists the recommended action is to reinitialize the system files; try power cycle of VM, if on first boot try redeploy of
using svc_reinit. Note: If this is the first boot of the system, VM template
reinitializing may not work and it's recommended to redeploy
the VM.

BOOTFL 0xFC0B0801 Failed to mount system disk partition, try rebooting. If the Count not mount partition that holds disk files; try power
problem persists the recommended action is to reinitialize cycle of VM, if on first boot try redeploy of VM template
the system using svc_reinit. Note: If this is the first boot of
the system, reinitializing may not work and it's recommended
to redeploy the VM.

BOOTFL 0xFC0B0802 0B0 Could not create new disk files; try power cycle of VM, if on
first boot try redeploy of VM template
BOOTFL 0xFC0B0803 Failed to mount root install partition, try rebooting. If the Could not root install partition (backup copy); try power cycle
problem persists the recommended action is to reinitialize of VM, if on first boot try redeploy of VM template
the system using svc_reinit. Note: If this is the first boot of
the system, reinitializing may not work and it's recommended
to redeploy the VM.

BOOTFL 0xFC0B0804 Failed to generate serial number, try rebooting. If the Could not generate serial number for the virtual system; try
problem persists the recommended action is to reinitialize power cycle of VM, if on first boot try redeploy of VM
the system using svc_reinit. Note: If this is the first boot of template
the system, reinitializing may not work and it's recommended
to redeploy the VM.
BOOTFL 0xFC0B0805 Failed to copy system config to root copy, try rebooting. If Could not copy the virtual configuration file to the root
the problem persists the recommended action is to partition; try power cycle of VM, if on first boot try redeploy
reinitialize the system using svc_reinit. Note: If this is the of VM template
first boot of the system, reinitializing may not work and it's
recommended to redeploy the VM.

BOOTFL 0xFC0B0806 Failed to generate WWN seed, try rebooting. If the problem Could not generate a wwn seed for the virtual system; try
persists the recommended action is to reinitialize the system power cycle of VM, if on first boot try redeploy of VM
using svc_reinit. Note: If this is the first boot of the system, template
reinitializing may not work and it's recommended to redeploy
the VM.
BOOTFL 0xFC0B0807 Failed to mount image repository, try rebooting. If the Could not mount the image repository to backup the friendly
problem persists the recommended action is to reinitialize hostname; try power cycle of VM, if on first boot try redeploy
the system using svc_reinit. Note: If this is the first boot of of VM template
the system, reinitializing may not work and it's recommended
to redeploy the VM.
BOOTFL 0xFC0B0808 Failed to unmount image repository, try rebooting. If the Could not unmount image repository; try power cycle of VM,
problem persists the recommended action is to reinitialize if on first boot try redeploy of VM template
the system using svc_reinit. Note: If this is the first boot of
the system, reinitializing may not work and it's recommended
to redeploy the VM.
BOOTFL 0xFC0B0809 Failed to unmount system disk partition, try rebooting. If the Could not unmount partition that holds disk file; try power
problem persists the recommended action is to reinitialize cycle of VM, if on first boot try redeploy of VM template
the system using svc_reinit. Note: If this is the first boot of
the system, reinitializing may not work and it's recommended
to redeploy the VM.
BOOTFL 0xFC0B0810 Failed to clean system disk partition, try rebooting. If the Could not clean filesystem on partition that holds disk files;
problem persists the recommended action is to reinitialize try power cycle of VM, if on first boot try redeploy of VM
the system using svc_reinit. Note: If this is the first boot of template
the system, reinitializing may not work and it's recommended
to redeploy the VM.

BOOTFL 0xFC0B0811 Failed to unmount root copy, try rebooting. If the problem Could not unmount root install partition (backup copy); try
persists the recommended action is to reinitialize the system power cycle of VM, if on first boot try redeploy of VM
using svc_reinit. Note: If this is the first boot of the system, template
reinitializing may not work and it's recommended to redeploy
the VM.

BOOTFL 0xFC0B0812 Failed to unmount root partition, try rebooting. If the problem Could not unmount root partition; try power cycle of VM, if
persists the recommended action is to reinitialize the system on first boot try redeploy of VM template
using svc_reinit. Note: If this is the first boot of the system,
reinitializing may not work and it's recommended to redeploy
the VM.
BOOTFL 0xFC0B0813 Failed to generate DUID, try rebooting. If the problem
persists the recommended action is to reinitialize the system
using svc_reinit. Note: If this is the first boot of the system,
reinitializing may not work and it's recommended to redeploy
the VM.

BOOTFL 0xFC0B0820 Persisted SP ID does not match current hypervisor reported

Bios UUID.

BOOTFL 0xFC0B0900 Could not register MAC addresses Could not register MAC addresses; lab/mfg-only ; escalate if
found in the field
BOOTFL 0xFC0B0901 Could not reboot after registering MAC addresses Could not reboot after registering MAC addresses; lab/mfg-
only ; escalate if found in the field
BOOTFL 0xFC0B0902 Could not retrieve config file from network Could not retrieve config file from network; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B0903 Could not retrieve image file from network Could not retrieve image file from network; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B0904 Could not retrieve customize file from network Could not retrieve customize file from network; lab/mfg-only
; escalate if found in the field
BOOTFL 0xFC0B0905 Could not unpack bootflash image Could not unpack bootflash image; lab/mfg-only ; escalate if
found in the field
BOOTFL 0xFC0B0906 Could not install bootflash image for boot to SSPG mode Could not install bootflash image for boot to SSPG mode;
lab/mfg-only ; escalate if found in the field
BOOTFL 0xFC0B0907 Could not unmount bootflash or remove bootflash image Could not unmount bootflash or remove bootflash image;
lab/mfg-only ; escalate if found in the field
BOOTFL 0xFC0B0908 Could not mount device with OS.tgz.bin at /boot Could not mount device with OS.tgz.bin at /boot; lab/mfg-
only ; escalate if found in the field
BOOTFL 0xFC0B0909 Could not set new kernel parameters Could not set new kernel parameters; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B090A Could not set new root device Could not set new root device; lab/mfg-only ; escalate if
found in the field
BOOTFL 0xFC0B090B Could not install grub to SSD for SSPG boot Could not install grub to SSD for SSPG boot; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B090C Could not change system type to SSPG Could not change system type to SSPG; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B090D Could not mount local device to retrieve image Could not mount local device to retrieve image; lab/mfg-only
; escalate if found in the field
BOOTFL 0xFC0B090E Could not copy config file from local device Could not copy config file from local device; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B090F Could not retrieve config file from network Could not retrieve config file from network; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B0910 Could not retrieve image file from network Could not retrieve image file from network; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B0911 Could not retrieve customize file from network Could not retrieve customize file from network; lab/mfg-only
; escalate if found in the field
BOOTFL 0xFC0B0912 Main device does not appear to exist Main device does not appear to exist; lab/mfg-only ;
escalate if found in the field
BOOTFL 0xFC0B0913 Persisted System UUID does not match current hypervisor Persisted System UUID does not match current hypervisor
reported Bios UUID. reported Bios UUID. Possible causes are converted, cloned
VMs or a manually manipulated uuid.bios setting. Fix the
Bios UUID to match the system’s persisted UUID or
escalate to support.

BOOTFL 0xFC0B0914 Could not fix filesystem errors on one of the mirror partitions Tried to fix filesystem errors on a mirror partition but a
reboot required and after 3 reboots the problems are still
there.
BOOTFL 0xFC0B0915 Could not mount boot recovery partition

BOOTFL 0xFC0B0916 Unable to create SP Model entry in config repo

BOOTFL 0xFC0B0917 SP Model HW mismatch detected

UPGRADE 0xFC140100 (not in hints.txt. is this code still used?) Installed RAM size does not match RCR size

UPGRADE 0xFC140101 (not in hints.txt. is this code still used?) Number of SPs does not match expected configuration

UPGRADE 0xFC140102 (not in hints.txt. is this code still used?) Number of SPs does not match expected configuration
UPGRADE 0xFC140103 (not in hints.txt. is this code still used?) Platform/RAM/SP_count combination not valid; expected in
lab/mfg only; escalate if found in the field

SOFTWARE 0xFC1B0001 FCT disabled faulted MCF driver is in a disabled faulted state; clear dirty LUNs (if
any) and destroy fast cache
SOFTWARE 0xFC1B0002 FCT cache faulted MCF has a faulted LUN; clear dirty cache condition

SOFTWARE 0xFC1B0003 MCC cache lost MCC is cache lost and must be cleared

SOFTWARE 0xFC1B0004 MCC cache was not recovered MCC cache can't be recovered, need to force cache lost,
then clear cache lost
SOFTWARE 0xFC1B0005 c4admintool command execution failed within A call to c4admintool within cache_health.sh script has
cache_health.sh script failed for some unknown reason. Set Hint Code and go into
service mode.

SOFTWARE 0xFC1B3001 Virtual hardware configuration doesn't match supported Encountered unsupported virtual hardware configuration
profiles which needs to be fixed before the system can boot.

SOFTWARE 0xFC1B3002 Wrong virtual disk sizes order Please contact support.