Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Nov 13, 2026

Enclosure names for ESS6000 are inconsistent with pdisk names

On an ESS6000 and ESS3500 hybrid systems, the enclosure names are inconsistent with the names generated by the system.

Assume you have a systems with nine enclosures, the bottom enclosure is named enclosure 1, the next one up is enclosure 2, and so on up to enclosure 9 located directly under the ESS6000 head node.

The ESS6000 head node contains between 4 and 48 NVMe drives.

The pdisks however get named e1s## for the head node, e2s## for enclosure 1, up to e10s## for enclosure 9.  ( Also notice the lack of leading zeros make the pdisk names different lengths. )

This is confusing to both customers and the CSR when a disk replacement occurs, pdisk e8s24 implies that slot 24 in enclosure 8 needs to be replaced, but really it is enclosure 7.

Solution, start by numbering the headnode drives as enclosure 0.

Idea priority Medium