Resolving A Problem; Bad Block Errors - IBM Storwize V7000 Unified Problem Determination Manual

It is possible that the tables that are used to record bad block locations can fill up.
The table can fill either on an MDisk or on the system as a whole. If a table does
fill up, the migration or replication that was creating the bad block fails because it
was not possible to create an exact image of the source volume.
The system creates alerts in the event log for the following situations:
v When it detects medium errors and creates a bad block
v When the bad block tables fill up
The following errors are identified:
The recommended actions for these alerts guide you in correcting the situation.
Clear bad blocks by deallocating the volume disk extent, by deleting the volume or
by issuing write I/O to the block. It is good practice to correct bad blocks as soon
as they are detected. This action prevents the bad block from being propagated
when the volume is replicated or migrated. It is possible, however, for the bad
block to be on part of the volume that is not used by the application. For example,
it can be in part of a database that has not been initialized. These bad blocks are
corrected when the application writes data to these areas. Before the correction
happens, the bad block records continue to use up the available bad block space.

Resolving a problem

Described here are some procedures to help resolve fault conditions that might
exist on your system and which assume a basic understanding of the Storwize
V7000 Unified system concepts.
The following procedures are often used to find and resolve problems:
v Procedures that involve data collection and system configuration
v Procedures that are used for hardware replacement.
Always use the recommended actions on the Events panel of the management GUI
as the starting point to diagnose and resolve a problem.
The following topics describe a type of problem that you might experience, that is
not resolved by using the management GUI. In those situations, review the
symptoms and follow the actions that are provided here.
The Start here: Use the management GUI recommended actions topic gives the
starting point for any service action. The situations covered in this section are the
200
Storwize V7000 Unified: Problem Determination Guide Version
Table 37. Bad block errors
Error code
1840
1226
1225
Description
The managed disk has bad blocks. On an
external controller, this can only be a copied
medium error.
The system has failed to create a bad block
because the MDisk already has the
maximum number of allowed bad blocks.
The system has failed to create a bad block
because the system already has the
maximum number of allowed bad blocks.