System reporting fewer unconfigured disks - Unity XT 380

Hello Wambua-iv,

Were there any new drives added to your unity 380 XT, or were all 144 installed when your system was first installed? What is your current OE on Your Unity 380XT system?

All disks were installed when the system was first deployed, the firmware version currently is 5.4.1.0.5.006

Do they show different amounts of available storage?

The systems are showing same capacity volumes.

You should be able to add more storage

To use these disks:

1. Go to Unisphere → Storage → Pools
2. Either:
• Create a new pool using the unconfigured drives in dg_24, or
• Expand an existing pool if it was originally created from the same drive group
3. Unity does not automatically rebalance or add unconfigured drives to existing pools.

Expanding the pool or creating a new one shows 89 disks available, that is the 91 disk minus the 2 hot spares, is there anything I can do in order to locate the 8 disks that seem to be missing ( there is a failed disk that I am awaiting the shipment of the new one for replacement)

For tranditional pool, unconfied disk means spare. For dynamic pool, unconfigured disks means that not enough to assemble a smaller group

I was going through the output of 'svc_diag --state all' and found the following output, does the 'broken or non-redundant' state after the number of drives show as configured?

13:39:53 0x41680120 Permanent spare request for 0_6_4,serial num:WBN72J35 denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_3,serial num:WBN724XA denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_5,serial num:WBN72JJW denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_2,serial num:WBN7266F denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_1,serial num:WBN724DX denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_6,serial num:WBN729FN denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_0,serial num:WBN726XC denied. RAID Group unconsumed, broken or non-redundant

13:39:53 0x41680120 Permanent spare request for 0_6_7,serial num:WBN7281J denied. RAID Group unconsumed, broken or non-redundant

Permanent spare request for 0_6_4, serial num: WBN72J35 denied. RAID Group unconsumed, broken or non-redundant

The system detected a failure (or impending failure) on the disk at slot 0_6_4 (Bus 0, Enclosure 6, Slot 4) The array attempted to automatically assign a permanent hot spare. The request was denied because the underlying RAID group is already in a broken or non-redundant state. This typically indicates a multiple drive failure — a second drive likely failed before the first drive's rebuild completed, making a spare rebuild mathematically impossible Unity actively blocks pool modifications (capacity expansion, tier additions, etc.) when any underlying RAID group is faulted, broken, or in a degraded/non-redundant state.

1. Check Pool and RAID Group Health:
2. uemcli /stor/config/pool show -detail
3. uemcli /stor/config/rg show -detail
4. uemcli /env/disk show -detail

Hello @DELL-Josh Cr I ran the commands, I was not able to get the rg command output, 
I have discovered a discrepancy; there are SAS and SAS Flash disks that have a status of 'Bound' in the svc_diag_--state_spinfo.txt file but the output of 'uemcli /env/disk show -detail' shows the disks as 'unconfigured'. 

Understanding the Discrepancy

What "Bound" in svc_diag_--state_spinfo.txt Means

The svc_diag service command pulls real-time hardware and physical storage states directly from the Storage Processor's low-level Operating Environment (OE). When disks show as 'Bound', it means they are physically and logically tied to a RAID Group or storage pool at the core storage level.

What "Unconfigured" in uemcli /env/disk show -detail Means

The uemcli command queries the Unisphere management database (UEMDB). When it reports those same disks as 'Unconfigured', it tells us that the management database has fallen out of sync with the underlying physical storage state.

Why the rg Command Returned No Output

The RAID Group (rg) command likely failed because the management layer cannot query or display a RAID Group that it currently believes does not exist — since, from its perspective, the drives populating it are "unconfigured."

What Typically Causes This

This "Bound/Unconfigured" mismatch condition can occur after:

• An abrupt power loss or unexpected reboot
• An improperly replaced or reseated drive
• A software bug in the OE causing a ghost drive state

Recommended Next Steps

1. Restart Management Services — In some cases, restarting the management software on the primary Storage Processor (SP) can force the management database to re-poll the hardware and resynchronize the states. However, proceed with caution and only if guided by support.
2. Generate a Data Collection Bundle — Please run the svc_dc command to collect a full diagnostic bundle from the array. This will capture all the information Dell Engineering needs to assess the situation.
3. Contact Dell Technical Support — This is strongly recommended. Resolving this mismatch requires internal engineer-level tools to safely sync the management database back to the physical array's actual state without risking Data Unavailable (DU) or Data Loss (DL) scenarios. This is not something that can be safely resolved through standard user-accessible commands.

Important: Please do not attempt to manually reconfigure, unbind, or manipulate these disks through any available commands, as doing so could result in data loss. Let Dell Technical Support handle the database-to-hardware resynchronization.