KB 000183486 — No-spare-drive alert in dynamic pools
KB 000014913 — Understanding dynamic pools
KB 000081354 lists our drive part number, but our firmware is newer than the affected revisions. DTA 542005 also appears inapplicable based on its OE and part-number requirements.
Our main questions:
Given that this is a non-system drive in a dynamic pool, is it preferable to insert a new compatible SSD into an empty DPE slot and allow Unity to consume it automatically, or should we remove Disk 4 and replace it directly in the same slot?
If we insert the new SSD into an empty slot, should Unity automatically resume the copy process or replenish the consumed distributed spare extents? What behavior should we expect?
What specific Unisphere or CLI indicators should we verify to confirm that the original drive is safe to remove and that RAID protection/spare capacity has been restored?
Does the 01/5D/28 predictive-failure indication suggest that physical replacement is appropriate even though the drive reports substantial remaining endurance?
Is there any known requirement to update Unity OE before replacing this drive under the current 5.5.0 release?
We have obtained a compatible replacement SSD and would like to complete remediation during a controlled maintenance window.
We would prefer to avoid an unnecessary full-array OE upgrade, particularly because this system provides VMware production storage.
Any guidance from Dell engineering or administrators who have handled this exact scenario would be greatly appreciated. A reference to the relevant customer replacement procedure would be especially helpful.
It is best to power down the drive in slot 4 then replace it with a SSD drive from the support matrix in slot 4.
You don't want to put a drive into an empty slot as then you will need to configure the slot as part of the pool in order for the drive to be seen by the pool and useable.
When in unisphere or CLI you will want to confirm that the slot4 is powered down prior to removal of the drive. Once that is confirmed then you can remove the current drive and insert the replacement drive. You can then confirm that the replacement drive is seen and is part of the disk pool. You should then see that the data is copying to the replacement drive, which you can monitor till it is complete.
The error is letting you know that the drive is showing signs that it needs to be replaced soon. Now you can wait and replace the drive later if you want when the drive endurance is lower as that is your call.
There is not any reason to upgrade your Unity OE prior to replacing the drive in slot 4. the reason that you would need to upgrade your Unity OE prior to a drive replacement is that your OE would not support the replacement drive without an OE upgrade.
We're still receiving 14:60342 approximately every 24 hours. Dell KB 000183486 indicates this can continue even after data has been moved into distributed spare extents. We also have 14:60284, a paco done event, and zero degraded RAID extents.
Can you confirm whether these indicators establish that Disk 4 has been fully evacuated? What exact Unisphere or CLI status should we use to verify that slot 4 is powered down and safe to remove before the in-place replacement?
If you look in Unisphere at the drive slot is should state that the slot is online or offline. As long as your slot4 is offline, then the drive is ready for replacement. Once the replacement drive has been inserted then the slot will power on and check the drive to make sure that it will work with your unity system.
The drive is still seemingly in an online state, its not failed or faulted. The lights on the from panel are the normal blue color, not orange/amber.
Unity is complaining that its degraded and EOL even though there are a reported 1,752 days expected left on the disk itself [over 4 years]. This number hasn't changed since last week.
Is there any way to safely clear that flag? It seems like a bug. We are on the latest drive firmware available.
Should we add a new spare somehow or wait until this drive actually fails ?
Is there a way to manually fail/offline the drive in order to replace it?
Here is the output from the most recent
Full Error Log=[/nas/log/check_health.261029-215039.log]
file, after we ran a failover SP command.
22:19:27 service@Unity spb:~/user# cat /nas/log/check_health.261029-215039.log
Check Command: /EMC/Platform/bin/check_health
Reporting SP: SPB
hardware: EMCHW platform:OBERON
nas_version:5.5
nas_release:0.0
-------------------------------------Checks-------------------------------------
2026-10-29T21:50:46+00:00 check_user_boot_counter: (Pass)
2026-10-29T21:50:47+00:00 check_peer_management_port_link: (Pass)
2026-10-29T21:50:47+00:00 check_peer_SP: (Pass)
2026-10-29T21:50:47+00:00 check_for_hardware_faults: (Pass)
2026-10-29T21:50:59+00:00 check_for_dae_cable_missing: (Pass)
2026-10-29T21:50:59+00:00 check_for_SSD_faults: (Pass)
2026-10-29T21:50:59+00:00 check_for_enclosure_faults: (Pass)
2026-10-29T21:50:59+00:00 check_for_corrupt_rpm_db: (Pass)
2026-10-29T21:50:59+00:00 check_if_mirror_is_mountable: (Pass)
2026-10-29T21:50:59+00:00 check_for_mirror_rebuild: (Pass)
platform::check_LCC_firmware_versions: Undefined, Skipped
2026-10-29T21:51:00+00:00 check_drive_firmware_version: (Pass)
2026-10-29T21:51:04+00:00 check_boot_control_status: (Pass)
2026-10-29T21:51:04+00:00 check_CPU_utilization: (Pass)
2026-10-29T21:51:04+00:00 check_suspended_job: (Pass)
2026-10-29T21:51:04+00:00 check_replication_health: (Pass)
2026-10-29T21:51:11+00:00 check_import_connection_health: (Pass)
2026-10-29T21:51:11+00:00 check_msm_not_running: (N/A)
2026-10-29T21:51:11+00:00 check_import_session_exists: (Pass)
2026-10-29T21:51:11+00:00 check_sancopy_session_exists: (Pass)
2026-10-29T21:51:11+00:00 check_components_allowable_on_SPs: (Pass)
2026-10-29T21:51:12+00:00 check_kmip_client_certificate: (Pass)
2026-10-29T21:51:14+00:00 check_metrics_db: (Pass)
2026-10-29T21:51:14+00:00 check_cp_db: (Pass)
2026-10-29T21:51:14+00:00 check_management_port: (Pass)
2026-10-29T21:51:15+00:00 check_space_usage_of_backend_directory: (Pass)
2026-10-29T21:51:15+00:00 check_if_nbsnas_is_mounted: (Pass)
2026-10-29T21:51:15+00:00 check_observability_partition_status: (Pass)
2026-10-29T21:51:15+00:00 check_filesystem_state: (Pass)
2026-10-29T21:51:15+00:00 check_if_root_filesystem_has_enough_free_space: (Pass Pass)
2026-10-29T21:51:15+00:00 check_if_user_root_fs_has_enough_space: (Pass)
2026-10-29T21:51:16+00:00 check_network_connectivity: (Pass Pass)
2026-10-29T21:51:20+00:00 check_status: (Pass)
2026-10-29T21:51:26+00:00 check_if_cic_is_configured: (Pass)
2026-10-29T21:51:26+00:00 check_filesystems_health: (Pass)
2026-10-29T21:51:30+00:00 check_nas_servers_health: ()
2026-10-29T21:51:30+00:00 check_fsn_health: (N/A)
2026-10-29T21:51:30+00:00 check_server_connectivity: (Pass Pass Pass)
2026-10-29T21:51:30+00:00 check_if_storage_pool_recovery_is_required: (Fail)
2026-10-29T21:51:30+00:00 check_if_lun_recovery_is_required: ()
2026-10-29T21:51:30+00:00 check_FASTCache_status: (Pass Pass)
2026-10-29T21:51:31+00:00 check_for_cache_lost_faulted_luns: (Pass)
2026-10-29T21:51:34+00:00 check_for_disk_transitions: (Pass)
2026-10-29T21:51:34+00:00 check_for_faulted_disks: (Fail)
2026-10-29T21:51:34+00:00 check_for_no_pulled_disks: (Pass)
2026-10-29T21:51:34+00:00 check_movesession_exists: (Pass)
--------------------------------------------------------------------------------
One or more warnings have occurred. It is recommended that you follow the
instructions provided to correct the problem then try again.
Upgrade cannot proceed.
------------------------------------Warnings------------------------------------
Flare: Check if storage pool recovery is required
The following pools do not appear to be in a healthy state:
* Pool_0 - The system could not start an automatic copy of data from
one or more drives in the pool to replace a drive that is wearing
out, because spare drives are not available. Add drives to the pool.
Action : Upgrade may continue, but the recommended course of action is
to escalate this issue through your support organization. Provide this
output with the escalation.
ERROR_CODE=flr::check_if_storage_pool_recovery_is_required_3|Warning|Pool_0 - The system could not start an automatic copy of data from one or more drives in the pool to replace a drive that is wearing out, because spare drives are not available. Add drives to the pool.
Flare: Check for faulted disks
The following disks are End of life
* Encl. 0: Disk 4
Action : Upgrade may continue, but the recommended course of action is
to escalate this issue through your support organization. Provide this
output with the escalation.
ERROR_CODE=flr::check_for_faulted_disks_2|Warning|Encl. 0: Disk 4
--------------------------------------------------------------------------------
Check Result: Warning22:20:58 service@Unity spb:~/user#
Just to confirm you haven't done any OE upgrades to your Unity350F recently? You are correct that the days listed is over 4 years. I noticed that when you posted the output that it was from SPB. If you look at the logs from SPA are they the same?
No we have not updated our Unity 350F in months, not since back in June of this year. It is out of support and we are planning to replace it soon. Last time we updated it, the process had disrupted our underlying storage; it did not go smoothly as it should have compared to previous experiences.
The logs from SPB have a gap in time compared to when it was either last rebooted or the SP changed.
The check_health logs on SPA are not technically the same [just because of dates and source] - it has a most recent date of 2026-10-21 = check_health.261021-182646.log
Other than the obvious differences, yes these logs are exactly the same.
Seeing as the logs are not matching fully I would like to ask you if you can reboot your unity system during your next maintenance window? The reason being is that the dates, times, error, & warning messages should match from both sp's. Since the don't match 100% it is best to reboot your system to ensure that the error messages are correct.
Just for clarification, are you saying that /nas/log/ content should match on both SP's? or just the check_health files?
That path appears to be on local storage to each SP's and not shared between them.
The path: /EMC/backend/log_shared/ is a different case that IS shared across both SP's, which includes the EMCSystemLogFile.log file. [ for example via mtab: /dev/c4loga1 /EMC/backend/log_shared ext3 rw,sync,nosuid,noatime 0 0 ]
For a unity system you will have a log for each SP, and you will also have a shared or merged log which will have all events from both SP's. So when support looks at the logs we review both SP's logs first but we also review the merger or shared logs to make sure that no messages are getting missed by either sp.
DELL-Sam L
Community Manager
•
8147 Posts
•
34706 Points
4
0
Posted October 28th, 2026 13:12
Hello itadminEA,