Customer device RE0 reports the "ssd Error" as below and this error can be cleared by itself.
user@PTX10008-re0> show chassis alarms
0 alarms currently active
user@PTX10008-re0> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 25 degrees C / 77 degrees F
CPU temperature 25 degrees C / 77 degrees F
DRAM 117097 MB (131072 MB installed)
Memory utilization 10 percent
5 sec CPU utilization:
==========================
####################
user@PTX10008-re0> show log messages | match "ssd Error"
<11>1 2025-06-03T15:14:53.333Z PTX10008-re0 emfd-fpa 12484 - - EMF_FPA_FAULT_REP: createFault: Fault(Location: /Chassis[0]/Re[0] Module: platform Object: ssd Error: 14) reported
<11>1 2025-06-03T15:14:53.333Z PTX10008-re0 emfd-fpa 12484 - - EMF_FPA_ALARM_REP: RaiseAlarm: Alarm(Location: /Chassis[0]/Re[0] Module: platform Object: ssd Error: 14) reported
user@PTX10008-re0:
--------------------------------------------------------------------------
Filesystem Size Used Avail Capacity Mounted on
/dev/root 36M 36M 0 100% /run/initramfs
/dev/sda2 32G 5.3G 25G 18% /soft
/dev/sda5 3.0G 578M 2.2G 21% /data
/dev/sda7 145G 118G 21G 86% /var
/dev/loop0 15G 38M 14G 1% /data/var/external
devtmpfs 63G 0 63G 0% /dev
/tmp 63G 0 63G 0% /run/initramfs/uswitch/tmp
------------------------------------------------
<11>1 2025-06-03T15:14:53.333Z user@PTX10008-re0 emfd-fpa 12484 - - EMF_FPA_FAULT_REP: createFault: Fault(Location: /Chassis[0]/Re[0] Module: platform Object: ssd Error: 14) reported
<13>1 2025-06-03T15:14:53.333Z user@PTX10008-re0 emfd-fpa 12484 - - EMF_EVO_ALARM_SET: Alarm set: RE color=yellow, class=CHASSIS, reason=Host 0 Active Disk Usage Exceeded
<11>1 2025-06-03T15:14:53.333Z user@PTX10008-re0 emfd-fpa 12484 - - EMF_FPA_ALARM_REP: RaiseAlarm: Alarm(Location: /Chassis[0]/Re[0] Module: platform Object: ssd Error: 14) reported
<10>1 2025-06-03T15:14:53.338Z user@PTX10008-re0 - 13194 - - 2025-06-03 15:14:53 CRITICAL: disk_mgmt_tool.py:424 syslog(): alarm raised for high disk usage on /var
<10>1 2025-06-03T16:55:26.344Z user@PTX10008-re0 - 6984 - - 2025-06-03 16:55:26 CRITICAL: disk_mgmt_tool.py:424 syslog(): Starts cleaning for /vardisk usage hit critical limit
<13>1 2025-06-03T16:55:32.086Z user@PTX10008-re0 platform-monitor 7268 - - disk usage below 90% on var
<13>1 2025-06-03T16:55:32.170Z user@PTX10008-re0 emfd-fpa 12484 - - EMF_EVO_ALARM_CLR: Alarm cleared: RE color=yellow, class=CHASSIS, reason=Host 0 Active Disk Usage Exceeded
<11>1 2025-06-03T16:55:32.171Z user@PTX10008-re0 emfd-fpa 12484 - - EMF_FPA_ALARM_CLR: ClearAlarm: Alarm(Location: /Chassis[0]/Re[0] Module: platform Object: ssd Error: 14) cleared
<11>1 2025-06-03T16:55:32.171Z user@PTX10008-re0 emfd-fpa 12484 - - EMF_FPA_FAULT_CLR: destroyFault: Fault(Location: /Chassis[0]/Re[0] Module: platform Object: ssd Error: 14) cleared
<10>1 2025-06-03T16:55:33.530Z user@PTX10008-re0 - 7373 - - 2025-06-03 16:55:33 CRITICAL: disk_mgmt_tool.py:424 syslog(): alarm cleared for high disk usage on /var
The logs are related to DISKUSEREXCEEDERR, which gets cleared since disk_mgmt_tool kicks in and clears the files post which the alarm gets cleared. This is expected behavior and per design.