Avamar: How to address Avamar Dial Home cases

Summary: This article provides a list to other articles on how to address Avamar Dial Home cases for various symptom codes.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Software Events:

Symptom Code Issue: Description: Article to address the issue:
Symptom: 15                   node offline node 0.n was online, changing Avamar: Troubleshooting Node Offline or GSAN Degraded Issues on an Avamar System (Resolution Path)  
Symptom: 4004 hfscheck hfscheck of cp.2025nnnnn failed on error: MSG_ERR_DDR_ERROR Avamar: Data Domain Integration: Troubleshooting hfscheck failures with MSG_ERR_DDR_ERROR (Resolution Path)
hfscheck of cp.2025nnnnn failed on error: MSG_ERR_CGSAN_FAILED Avamar: Troubleshooting HFSCHECK failures due to MSG_ERR_CGSAN_FAILED (Resolution Path)
hfscheck of cp.2025nnnnn failed on error: MSG_ERR_HFSCHECKERRORS  Avamar: Troubleshooting HFSCHECK Failures (Resolution Path)
hfscheck of cp.2025nnnnn failed on error: MSG_ERR_TIMEOUT Avamar: Troubleshooting HFSCHECK Failures due to MSG_ERR_TIMEOUT (Resolution Path)
hfscheck of cp.2025nnnnn failed on error: MSG_ERR_NODE_DOWN Avamar: Troubleshooting HFSCHECK failures due to MSG_ERR_NODE_DOWN
failed hfscheck maintenance with error MSG_ERR_NO_CHECKPOINT Avamar: Troubleshooting HFSCHECK failures due to MSG_ERR_NO_CHECKPOINT
failed hfscheck maintenance with error MSG_ERR_INPROGRESS Avamar: Troubleshooting HFSCHECK failures due to MSG_ERR_INPROGRESS
hfscheck of cp.2025nnnnn failed on error: MSG_ERR_CMD_FAIL Avamar: Troubleshooting HFSCHECK failures due to MSG_ERR_CMD_FAIL
failed hfscheck maintenance with error MSG_ERR_ROLLING_CHECK Avamar: HFSCHECK fails with MSG_ERR_ROLLING_CHECK due to an Avamar Server time shift
Symptom: 4202 garbage collection failed garbage collection with error MSG_ERR_NOPARITY Avamar: Troubleshooting Garbage Collection (GC) Failures (Resolution Path)
failed garbage collection with error MSG_ERR_DISKFULL Avamar: Operating System (OS) Capacity (Resolution Path)
failed garbage collection with error MSG_ERR_DDR_ERROR Avamar: Data Domain Integration: Troubleshooting Connectivity issues/All Avamar maintenance activities fail with MSG_ERR_DDR_ERROR (Resolution Path)
failed garbage collection with error MSG_ERR_BADTIMESYNC Avamar: Checkpoint failed with result "MSG_ERR_BADTIMESYNC."
failed garbage collection with error MSG_ERR_IO_ERROR Avamar: Troubleshooting failed garbage collection with error MSG_ERR_IO_ERROR (Resolution Path)
failed garbage collection with error MSG_ERR_MISC Avamar: Troubleshooting Garbage Collection Failing with MSG_ERR_MISC (Resolution Path)
failed garbage collection with error MSG_ERR_MISMATCH Avamar: Troubleshooting Garbage Collection (GC) Failures (Resolution Path)
Symptom: 4302  checkpoint failed checkpoint maintenance with error MSG_ERR_DDR_ERROR Avamar: Data Domain Integration: Troubleshooting Connectivity issues/All Avamar maintenance activities fail with MSG_ERR_DDR_ERROR (Resolution Path)
failed checkpoint maintenance with error MSG_ERR_ACCESSMODE Avamar: Checkpoint fails with MSG_ERR_ACCESSMODE due to an incomplete GSAN index stripe splitting operation
failed checkpoint maintenance with error MSG_ERR_DISKFULL Avamar: Maintenance tasks fail with MSG_ERR_DISKFULL due to the Operating System capacity of one or more data partition operating system capacity exceeding 89 percent
failed checkpoint maintenance with error MSG_ERR_TIMEOUT Avamar: Checkpoint fails with MSG_ERR_TIMEOUT
failed checkpoint maintenance with error MSG_ERR_BADTIMESYNC Avamar: Checkpoint failed with result "MSG_ERR_BADTIMESYNC."
failed checkpoint maintenance with error MSG_ERR_EXCEPTION Avamar: Checkpoint failed with result MSG_ERR_EXCEPTION and Unix exception "Too many links" due to File System Corruption
failed checkpoint maintenance with error MSG_ERR_OFFLINE Avamar: Troubleshooting Checkpoint Failures (Resolution Path)
Symptom: 22407  MC flush Flush of Administrator Server data to server is overdue  Avamar: Flush of Administrator Server data to server is overdue
Symptom: 22409 hfscheck A checkpoint validation (hfscheck) of server checkpoint data is overdue  Avamar: Symptom Code 22409 - A checkpoint validation (hfscheck) of server checkpoint data is overdue (Resolution Path)
Symptom: 22416 Capacity The server storage has exceeded maximum operating capacity Avamar: Capacity Troubleshooting, Issues, and Questions - All Capacity (Resolution Path)
Symptom: 22632 Partition suspended  A server disk has become suspended Avamar: Suspended Partitions, Stripes, and Hfscheck Failures on Avamar
 
 

Hardware Events:

Symptom: Description Article to address the issue:
Symptom: 52600 ipmiutil: igetevent: 021f <mm/dd/yy hh:mm:ss> CRT BMC  Processor #80 CATERR Proc Config Error 03 [a1 01 01] Contact Dell Technologies Avamar Support.
Symptom: 52600 ipmiutil: igetevent: 00a5 <mm/dd/yy hh:mm:ss> CRT BMC  Critical Interrupt #05 FP NMI Diag Int FP NMI   6f [00 ff ff]/code> Avamar: Gen4s Hardware: Symptom Code 52600 - ipmiutil: igetevent: CRT BMC Critical Interrupt
Symptom: 52601 ipmiutil: igetevent: 006d <mm/dd/yy hh:mm:ss> MAJ EFI  System Firmware #06 POST Err Sensor POST Code 8190 6f [a0 90 81] Contact Dell Technologies Avamar Support
Symptom: 52607 ipmiutil: igetevent: 00fd <mm/dd/yy hh:mm:ss> MAJ BMC  Fan #32 System Fan 2 Lo Crit thresh actual=1666.00 RPM, threshold=1715.00 RPM Avamar: Gen4s Hardware: Fan Low Threshold (Lo Crit thresh) Errors
Symptom: 52617 <MRMON113> Controller ID:  0   Unexpected sense:   PD       =   Port 0 - 3:2:2Hardware impending failure general hard drive Avamar: Gen4S Hardware: How to address various disk events and errors
<MRMON113> Controller ID:  0   Unexpected sense:   PD       =   Port 0 - 3:2:0Write protected,   CDB   =    0x2e 0x0 Avamar: Gen4s Hardware: Symptom Code 52617 - Unexpected sense: PD = Port 0 - 3:2:n. Write protected
Avamar: Gen4s Hardware: Symptom Code 52617 - Unexpected sense: PD = Port 0 - 3:2:12. Write protected (SSD)
<MRMON113> Controller ID:  0   Unexpected sense:   PD  #012    =   Port 0 - 3:2:8Internal target failure,   CDB   = Contact Dell Technologies Avamar Support
<MRMON113> Controller ID:  0   Unexpected sense:   PD       =   Port 0 - 3:2:12Information unit CRC error detected,   CDB Avamar: Gen4S Hardware: How to address various disk events and errors
<MRMON113> Controller ID:  0   Unexpected sense:   PD  #012    =   -:-:0Write error - recommend reassignment,   CDB   =    0 Avamar: Gen4s Hardware: Symptom Code 52617 - Unexpected sense: PD = Port 0 - 3:2:12. Write protected (SSD)
Symptom: 52618 <MRMON096> Controller ID:  0   PD Predictive failure:  #012    Port 0 - 3:2:4 Avamar: Gen4S Hardware: How to address various disk events and errors
Symptom: 52619 <MRMON015> Controller ID:  0   Fatal firmware error:       Line 866 in ../../raid/2108vI2o.c Event ID:15 Contact Dell Technologies Avamar Support
Symptom: 52620 <MRMON145> Controller ID:  0   Battery temperature is high Avamar - Gen4s Hardware >> Symptom Code 52620 - Controller ID: 0 Battery temperature is high
Symptom: 52621 <MRMON195> Controller ID:  0   BBU disabled; changing WB logical drives to WT, Forced WB VDs are not affected Avamar : Gen4s Hardware >> Symptom Code 52621 - BBU disabled; changing WB logical drives to WT, Forced
Symptom: 52622 <MRMON087> Controller ID:  0   Error:   Port 0 - 3:2:0      ( Error   250)  Contact Dell Technologies Avamar Support
<MRMON268> Controller ID:  0  PD Reset:   PD  #012    =   Port 0 - 3:2:0,   Error  #012    =   3,   Path   =#012      0 Avamar: Gen4S Hardware: How to address various disk events and errors
Symptom: 52623 HARDWARE:  <date> <node> <MRMON113> Controller ID:  0   Unexpected sense:   PD  #012    =   Port 0 - 3:2:11Power on, reset, or bus device reset Avamar: Gen4S Hardware: How to address various disk events and errors
Symptom: 52626 <MRMON267> Controller ID:  0  Command timeout on PD:   PD       =   Port 0 - 3:2:12No addtional sense informatio Avamar: Gen4S Hardware: How to address various disk events and errors
Symptom: 52627 ipmiutil: igetevent: 0044 01/01/05 00:00:24 MAJ BMC  Voltage #de BB +3.3V Vbat Lo Crit thresh actual=0.89 V, threshold=2.14 V Avamar Gen4S Hardware >> Symptom Code 52601/52627 - MAJ BMC Voltage #de BB +3.3V Vbat Lo Crit thresh actual=2.05 V, threshold=2.14 V
Symptom: 52628 <MRMON202> Controller ID:  0   Single-bit ECC error; critical threshold#012    exceeded:   ECAR  #012    =   959688528 Avamar: Gen4S Hardware: Single-bit ECC error; critical threshold exceeded
Symptom: 52630 ipmiutil: igetevent: 009e 01/15/22 14:34:27 CRT Bios Critical Interrupt #04 PCIe Fat Sensor PCIe Fatal Surprise Link Down (00:02.0) 70 [a1 Avamar Gen4s Hardware >> Symptom Code 52600/52630 - CRT Bios Critical Interrupt PCIe Fat Sensor PCIe Fatal Surprise Link Down
ipmiutil: igetevent: 0199 02/09/22 12:58:48 MAJ Bios Critical Interrupt #05 PCIe Cor Sensor PCIe Warn Receiver Error (00:01.1) 71 [a0 0 Avamar Gen4s Hardware >> Symptom Code 52601/52630 - MAJ Bios Critical Interrupt #05 PCIe Cor Sensor PCIe Warn Receiver Error
Symptom: 52633 <MRMON150> Controller ID:  0   Battery has failed and cannot support data retention. Please replace the battery Event Gen4s Hardware >> Symptom Code 52619/52633 - Controller ID: 0 Battery has failed and cannot support data retention. Please replace the battery Event ID:150
Symptom: 52700  ipmiutil: igetevent-gen4t: 00c4 <mm/dd/yy hh:mm:ss> CRT BMC Shutdown In Progress #f4 Delayed Reb Reason Code: 0x0e 6f [81 0e ff] Avamar : Gen4T Hardware >> Symptom Code 52700 - HW_CRIT_BMC_ERR_G4T
Symptom: 52701  ipmiutil: igetevent-gen4t: 011c <mm/dd/yy hh:mm:ss> MAJ BMC CMD Status #d2 Power Good (deasserted) 6f [00 ff ff] Avamar : Gen4T Hardware >> Symptom Code 52701 - HW_MAJOR_BMC_ERR_G4T
Symptom: 52704  ipmiutil: igetevent-gen4t: 014c <mm/dd/yy hh:mm:ss> MAJ BMC  Temperature #31 DIMM_Bank1 Hi Crit thresh actual=127.00 C, threshold=90.00 C Contact Dell Technologies Avamar Support
Symptom: 52706  ipmiutil: igetevent-gen4t: 0158 <mm/dd/yy hh:mm:ss> MIN BMC  Temperature #5f Ambient_Temp Hi Noncrit thresh actual=48.00 C, threshold=48. Contact Dell Technologies Avamar Support
Symptom: 52710  A fan sensor detected a fan speed that has exceeded the non-critical rpm threshold within the Gen4T system. Contact Dell Technologies Avamar Support 
Symptom: 52712 ipmiutil: igetevent-gen4t: 0003 <mm/dd/yy hh:mm:ss> MAJ BMC  Voltage #d8 CMOS_Voltage Lo Crit thresh actual=0.96 V, threshold=2.20 V Contact Dell Technologies Avamar Support
Symptom: 52714 hwfaultd: DIMM N Fault Contact Dell Technologies Avamar Support
Symptom: 52716 HARDWARE:<date> <node> hwfaultd: SLIC N Fault Contact Dell Technologies Avamar Support
Symptom: 52717 hwfaultd: PS N Fault Contact Dell Technologies Avamar Support
Symptom: 52718 hwfaultd: Fan N Fault Contact Dell Technologies Avamar Support
Symptom: 52719 hwfaultd: I2C 7 Fault Contact Dell Technologies Avamar Support
Symptom: 52722 hwfaultd: CPU Module Fault Contact Dell Technologies Avamar Support
Symptom: 52723  hwfaultd: Expander Unrecoverable Error Avamar Server: Gen4T M2400 storage nodes became unresponsive and reported "hwfaultd: Expander Unrecoverable Error" & spontaneous expander reset
Symptom: 52724 hwfaultd: Expander Critical Error Contact Dell Technologies Avamar Support
Symptom: 52725 hwfaultd: Expander Non-Critical Error Avamar Gen4T: hwfaultd: Expander Non-Critical Error
Symptom: 52726 resume_updater: libplatform failed to initialize. Avamar - libplatform failed to initialize
Symptom: 52728 resume_updater: Chassis resume settings cannot be read. Avamar : Gen4T Hardware >> Symptom Code 52728 - HW_RESUPD_CHASSIS_ERR_G4T
resume_updater: The chassis is not an Avamar system, and there is no saved resume settings. It needs to be manually set up. Avamar Gen4T: Error "The chassis is not an Avamar system, and there is no saved resume settings" after SP replacement
resume_updater: Chassis resume settings do not match saved values. Need examination. Avamar - Gen4T: Chassis resume settings do not match saved values
Symptom: 52750 Adaptec Event Monitor: [10001] :ERR: A controller has been removed from the system: controller 1 Contact Dell Technologies Avamar Support
Symptom: 52751 Adaptec Event Monitor: [11003] :WRN: One or more logical devices contain a bad stripe: controller 1 ( PM8060-RAID #00192603647 Physical Slo Contact Dell Technologies Avamar Support
Symptom: 52755 Adaptec Event Monitor: [12000] :WRN: Logical device is degraded: controller 1 ( PM8060-RAID #FFFFFF00 Physical Slot: 0 ), logical dev Avamar : Gen4T Hardware >> Symptom Code 52755 - HW_VDISK_LOST_REDUND_G4T
Symptom: 52756 Adaptec Event Monitor: [12005] :ERR: Rebuild failed: controller 1 ( PM8060-RAID #BD162100991 Physical Slot: 0 ), logical device 0 (vd0 Contact Dell Technologies Avamar Support
Symptom: 52759 Adaptec Event Monitor: [13000] :ERR: Failed drive: controller: 1 ( PM8060-RAID #FFFFFF00 Physical Slot: 0 ), channel: 0, deviceID: 11, encl Contact Dell Technologies Avamar Support 
Symptom: 52764 Adaptec Event Monitor: [13016] :WRN: Bad Block discovered: controller: 1 Avamar : Gen4T Hardware >> Symptom Code 52764 - HW_PHYS_DISK_BAD_BLOCK_G4T
Symptom: 52766 The wearout threshold was reach on an SSD drive. Contact Dell Technologies Avamar Support 
Symptom: 52768 Adaptec Event Monitor: [14006] :WRN: Backup unit temperature exceeded the over-heat threshold: controller 1 ( PM8060-RAID #00190136942 Ph Contact Dell Technologies Avamar Support 
Symptom: 52769 Adaptec Event Monitor: [14009] :ERR: Backup unit encountered a fatal condition: controller 1 Contact Dell Technologies Avamar Support 
Symptom: 52805 hardware_monitor[55820]: MessageID:MEM9072,  Created:2023-06-21T18:00:57-05:00,  Severity:Critical,  Message Avamar ADS Gen5: Event code=52804 A memory device error occurred
Symptom: 29.AAA1.902  High Incoming Box - Symptom: 29.AAA1.902 Troubleshooting SYR HIB Service Requests (Resolution Path)

Affected Products

Avamar, Avamar Server
Article Properties
Article Number: 000216088
Article Type: How To
Last Modified: 21 May 2025
Version:  33
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.