MAP 3250

Use this MAP to perform SAS fabric problem isolation for a PCIe2 or a PCIe3 controller.

Considerations:

Remove power from the system before connecting and disconnecting cables or devices, as appropriate, to prevent hardware damage or erroneous diagnostic results.
Some systems have the disk enclosure or the removable media enclosure integrated in the system with no cables. For these configurations, the SAS connections are integrated onto the system boards and a failed connection can be the result of a failed system board or integrated device enclosure.

Attention: When SAS fabric problems exist, obtain assistance from your hardware service provider before performing any of the following actions:

Obtain assistance before you replace a RAID adapter; because the adapter might contain nonvolatile write cache data and configuration data for the attached disk arrays, and additional problems might be created by replacing an adapter.
Obtain assistance before you remove functioning disks in a disk array; because the disk array might become degraded or might fail, and additional problems might be created if functioning disks are removed from a disk array.

Attention: Removing functioning disks in a disk array is not recommended without assistance from your hardware service support organization. A disk array might become degraded or might fail if functioning disks are removed, and additional problems might be created.

Step 3250-1

Was the SRN nnnn-3020?

No: Go to Step 3250-3.
Yes: Go to Step 3250-2.

Step 3250-2

The possible causes follow:

More devices are connected to the adapter than the adapter supports. Change the configuration to reduce the number of devices below what is supported by the adapter.
A SAS device has been incorrectly moved from one location to another. Either return the device to its original location or move the device while the adapter is powered off or unconfigured.
A SAS device has been incorrectly replaced by a SATA device. A SAS device must be used to replace a SAS device.

When the problem is resolved, see the removal and replacement procedures topic for the system unit on which you are working and do the "Verifying the repair" procedure.

Step 3250-3

Determine whether any of the disk arrays on the adapter are in a Degraded state as follows:

Start the IBM® SAS Disk Array Manager.
1. Start Diagnostics and select Task Selection on the Function Selection display.
2. Select RAID Array Manager.
3. Select IBM SAS Disk Array Manager.
Select List SAS Disk Array Configuration.
Select the IBM SAS RAID controller that was identified in the hardware error log.

Does any disk array have a state of Degraded?

No: Go to Step 3250-5.
Yes: Go to Step 3250-4.

Step 3250-4

Other errors should have occurred related to the disk array being in a Degraded state. Take action on these errors to replace the failed disk and to restore the disk array to an Optimal state.

When the problem is resolved, see the removal and replacement procedures topic for the system unit on which you are working and do the "Verifying the repair" procedure.

Step 3250-5

Was the SRN nnnn-FFFD?

No: Go to Step 3250-7.
Yes: Go to Step 3250-6.

Step 3250-6

Identify the device that is associated with the problem by examining the hardware error log. To view the hardware error log, complete the following steps:

Follow the steps in Examining the hardware error log and return here.

Obtain the Resource field from the Detail Data / ADDITIONAL HEX DATA section as illustrated in the following example:

Detail Data



ADDTIONAL HEX DATA



0001 0800 1910 00F0 0110 A100 0101 0000 0150 0000 0000 00FF 57B5 FFFD 0000 0000



0008 17FF FFFF FFFF 5000 00E1 1751 B410 0000 0000 0000 0000 0000 0000 0000 A030

          ^

          |

      Resource is 000817FF

Replace the device.
If replacing the device does not resolve the issue, contact your hardware service provider.

Go to Step 3250-16.

Step 3250-7

Have other errors occurred at the same time as this error?

No: Go to Step 3250-9.
Yes: Go to Step 3250-8.

Step 3250-8

Take action on the other errors that have occurred at the same time as this error.

When the problem is resolved, see the removal and replacement procedures topic for the system unit on which you are working and do the "Verifying the repair" procedure.

Step 3250-9

Was the SRN nnnn-FFFE?

No: Go to Step 3250-12.
Yes: Go to Step 3250-10.

Step 3250-10

Ensure that the device, the device enclosure, and the adapter microcode levels are up to date.

Did you update to newer microcode levels?

No: Go to Step 3250-12.
Yes: Go to Step 3250-11.

Step 3250-11

When the problem is resolved, see the removal and replacement procedures topic for the system unit on which you are working and do the "Verifying the repair" procedure.

Step 3250-12

Identify the adapter SAS port that is associated with the problem by examining the hardware error log. The hardware error log can be viewed as follows:

Follow the steps in Examining the hardware error log and return here.
Select the hardware error log to view. In the hardware error log, under the Disk Information heading, the Resource field can be used to identify which controller port the error is associated with.

Note: If you do not see the Disk Information heading in the error log, obtain the Resource field from the Detail Data / PROBLEM DATA section as illustrated in the following example:

Detail Data

PROBLEM DATA

0001 0800 1910 00F0 0408 0100 0101 0000 0150 003E 0000 0030 57B5 4100 0000 0001



0004 FFFF FFFF FFFF 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0004 AA98

          ^

          |

      Resource is 0004FFFF

Go to Step 3250-13.

Step 3250-13

Using the resource found in step 2, see SAS resource locations to understand how to identify the controller's port to which the device, or device enclosure, is attached.

For example, if the resource is equal to 0004FFFF, port 04 on the adapter is used to attach the device, or the device enclosure that is experiencing the problem.

The resource found in the previous step can also be used to identify the device. To identify the device, you can attempt to match the resource with one found on the display, which is displayed by completing the following steps:

Start the IBM SAS Disk Array Manager:
1. Start the diagnostics program and select Task Selection from the Function Selection display.
2. Select RAID Array Manager > IBM SAS Disk Array Manager.
Select Diagnostics and Recovery Options > Show SAS Controller Physical Resources > Show Physical Resource Locations.

Step 3250-14

Because the problem persists, some corrective action is needed to resolve the problem. Using the port or device information found in the previous step, proceed by doing the following steps:

Power off the system or logical partition.
Perform only one of the following corrective actions, which are listed in the order of preference. If one of the corrective actions was previously attempted, proceed to the next action in the list.
Note: Prior to replacing parts, consider using a complete power-down of the entire system, including any external device enclosures, to reset all possible failing components. This might correct the problem without replacing parts.
- Reseat the cables on the adapter and the device enclosure.
- Replace the cable from the adapter to the device enclosure.
- Replace the device.
  Note: If multiple devices have a path that is not marked as Operational, the problem is not likely to be with a device.
- Replace the internal device enclosure, or see the service documentation for an external expansion drawer.
- Replace the adapter.
- Contact your hardware service provider.
Power on the system or logical partition.
Note: In some situations, it might be acceptable to unconfigure and reconfigure the adapter instead of powering off and powering on the system or logical partition.

Step 3250-15

Does the problem still occur after performing the corrective action?

No: Go to Step 3250-16.
Yes: Go to Step 3250-14.

Step 3250-16

When the problem is resolved, see the removal and replacement procedures topic for the system unit on which you are working and do the "Verifying the repair" procedure.

Last updated: Wed, May 24, 2017