Skip to Main Content
IBM Power Ideas Portal

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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - https://ideas.ibm.com/ - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Status Is a defect
Workspace IBM i
Categories Storage
Created by Guest
Created on Aug 2, 2019

Improved behavior of IBM i when bad sectors of external storage occur

There was an incident that bad blocks on an external storage connected to an IBM i partition resulted in recursive SRC A6xx0266 for hours and performance of the IBM i partition significantly slowed down. It was hard for the customer to determine what was happening and what to do to recover from this situation.
In order to shorten the time for the problem determination and the system recovery, we request the following enhancements of error handling when reads do not complete due to bad blocks on pages (sectors) of an external storage.

- SRC A6xx0266 should not be repeatedly logged for hours. Instead, we expect IBM i to stop reading and return with appropriate failure or alert messages for easier PD from customers' point of view for bad blocks on an external storage
- For example, we expect IBM i to return with Page-read-error instead of recursive SRC A6xx0266 for bad blocks on an external storage


Use Case:

IBM i connecting to external storage


Idea priority High
  • Guest
    Aug 15, 2019

    .After reviewing, there isn't anything new to enhance. The current design should do exactly what is being requested. If IBM i gets a medium error from the storage controller, it should present a data check which marks the block bad. The the object would then either be marked damaged or the application would re-drive a write that would be relocated to a good sector in the storage array. If this is not the behavior then it would be considered a defect. This behavior has been enhanced over the last few years and in the PMR example it was unclear if all the fixes were on the system.

  • Guest
    Aug 7, 2019

    The design is already there to cause a data check which marks the block as damaged and allows the IBM i lpar to continue to run. If the error code from the storage box does not return what is expected, this situation can occur or if the block is part of the operating system itself. To understand this further to see if an enhancement is required or if it is a defect somewhere in the stack, more detail is required. on this unique case. The PMR mentioned does not mention the error that caused the A6XX0255.