SIP3250

Use this procedure to complete SAS fabric problem isolation for a PCIe2 or PCIe3 controller.

Considerations:
  • Power off the system, partition, or card slot before you connect and disconnect cables or devices, as appropriate, to prevent hardware damage.
  • Some systems have a disk enclosure or removable media enclosure that is 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:
  • When SAS fabric problems exist, do not replace RAID adapters without assistance from your service provider. Because the adapter might contain nonvolatile write cache data and configuration data for the attached disk arrays, additional problems can be created by replacing an adapter.
  • Do not remove functioning disk units in a disk array without assistance from your service provider. If functioning disk units are removed, a disk array might become unprotected or might fail. The removal of functioning disk units might also result in additional problems in the disk array.
  1. Was the SRC xxxx3020?
    No:
    Go to step 3.
    Yes:
    Go to step 2.
  2. The possible causes are:
    • 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 was 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.
    • A SATA device was incorrectly replaced a SAS device. A SAS device must be used to replace a SAS device.
    This ends the procedure.
  3. Determine the status of the disk units in the array by doing the following steps:
    1. Access the product activity log and display the SRC that sent you here.
    2. Press the F9 key for address information. The displayed information contains the adapter address.
    3. Return to the SST or DST main menu.
    4. Select Work with disk units > Display disk configuration > Display disk configuration status.
    5. On the Display disk configuration status screen, look for the devices that are attached to the adapter that was identified.
    Is there a device that has a status of RAID 5/Unknown, RAID 6/Unknown, RAID 5/Failed, or RAID 6/Failed?
    No:
    Go to step 5.
    Yes:
    Go to step 4.
  4. Other errors might have occurred that are related to the disk array having degraded protection. For these errors, replace the failed disk unit and restore the disk array to a fully protected state. This ends the procedure.
  5. Was the SRC xxxxFFFD?
    No:
    Go to step 8.
    Yes:
    Go to step 6.
  6. Identify the location of the device that is associated with the problem. Perform the following steps:
    1. Access SST or DST.
    2. Access the product activity log and display the SRC that sent you here. Find the location of the device by completing one of the following actions:
      • Record the resource name of the device. Then, use the Hardware Service Manager to determine the location of the device by using the resource name.
      • Go to Hexadecimal product activity log data to obtain the direct select address (DSA) and the unit address information. Then, go to Addresses to determine the location of the device.
  7. Replace the device at the location identified in step 6. For information about locations, see Part locations and location codes. If replacing the device does not resolve the problem, contact your hardware service provider. This ends the procedure.
  8. Have other errors occurred at the same time as this error?
    No:
    Go to step 10.
    Yes:
    Go to step 9.
  9. Fix the other errors that occurred at the same time as this error. This ends the procedure.
  10. Was the SRC xxxxFFFE?
    No:
    Go to step 13.
    Yes:
    Go to step 11.
  11. Check for the latest PTFs for the device, device enclosure, and adapter and apply them. If you need assistance finding PTFs, contact your next level of support. Did you find and apply a PTF?
    No:
    Go to step 13.
    Yes:
    Go to step 12.
  12. This ends the procedure.
  13. Identify the adapter SAS port that is associated with the problem by examining the product activity log. Perform the following steps:
    1. Access SST or DST.
    2. Access the product activity log and display the SRC that sent you here. Record the adapter address and the adapter port by completing one of the following actions:
      • If the SRC is xxxxFFFE, press the F9 key for address information. The adapter address is the bus information. The port is shown in the I/O bus field. Convert the port value from decimal to hexadecimal.
      • Press the F9 key for address information. The adapter address is the bus information. Then, press F12 to cancel and return to the previous screen. Then, press the F4 key to view the additional information, if available. This information is the unit address. Go to SAS address and physical location information and use the unit address to determine the controller port.
      • Go to Hexadecimal product activity log data to obtain the address information. The adapter address is the bus information. The controller port is contained in the unit address. Go to SAS address and physical location information and use the unit address to determine the controller port.
  14. Perform the following steps:
    1. Select Start a Service Tool > Hardware Service Manager > Logical Hardware Resources > System Bus Resources.
    2. Enter the adapter bus address and use the Associated packaging resource(s) option to display the type, model, and unit ID.
    3. Record the type, model, and unit ID of the enclosure in which the adapter is located.
    4. Use the type, model, unit ID, and adapter address to find the location of the adapter (see Addresses to find the location and then go to Part locations and location codes).
    5. The logical port number was identified in step 13. Logical port numbers are indicated on the physical connector labels that are located on the tailstock of the adapter. To locate the device or device enclosure that is experiencing the problem, use the logical port number to determine the physical connector to which the device or device enclosure is attached.
  15. Because the problem persists, some corrective action is required to resolve the problem.

    Perform only one of the following corrective actions (listed in the order of preference). If one of the corrective actions was previously attempted, proceed to the next one in the list.

    • Reseat cables, if present, on adapter and device enclosure. Perform the following steps:
      1. Use adapter concurrent maintenance to power off the adapter slot, or power off the system or partition.
      2. Reseat the cables.
      3. Use adapter concurrent maintenance to power on the adapter slot, or power on the system or partition.
    • Replace the cable, if present, from the adapter to the device enclosure. Perform the following steps:
      1. Use adapter concurrent maintenance to power off the adapter slot, or power off the system or partition.
      2. Replace the cables.
      3. Use adapter concurrent maintenance to power on the adapter slot, or power on the system or partition.
    • Replace the device.
      Note: If there are multiple devices with a path that is not 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 unit. Perform the following steps:
      1. Power off the system or partition. If the enclosure is external, use adapter concurrent maintenance instead to power off the adapter slot.
      2. Replace the device enclosure.
      3. Power on the system or partition. If the enclosure is external, use adapter concurrent maintenance instead to power on the adapter slot.
    • Replace the adapter. The procedure to replace the adapter can be found in PCI adapter.
    • Contact your service provider.
  16. Does the problem still occur after you completed the corrective action?
    • No: This ends the procedure.
    • Yes: Go to step 15.
Parent topic: Serial-attached SCSI isolation procedures


Last updated: Wed, June 19, 2019