View Only
  • 1.  286C SRC from a power 6 9406-800

    Posted Tue February 27, 2024 10:32 AM

    I have an SRC in Function 11 reading 286C3203. As I understand it, after reading the documentation, this points to a processor i/o error. These servers are not my wheelhouse at all, but I've been trying to troubleshoot this 9406-800 that is not displaying anything to the terminals. 

    The server powers on just fine, however, the yellow attention light is also powered. I've rebooted the server several times, reseated the components. 

    Does this usually point to a system board problem? Any help would be greatly appreciated. 

    Carlos Castilla

  • 2.  RE: 286C SRC from a power 6 9406-800

    Posted Wed February 28, 2024 05:20 AM



    Unfortunately, you have an IOP Card failure. Try to plug off the machine, and reseat the card. If this doesn't work, try to start in B Manual mode. If this doesn't work, try to boot in D Manual mode with the LIC DVD and try to boot up to restricted DST and test if the IOP is detected.


    If everything fails, call your IBM maintenance CAS because your machine is totally dead. And that model (I asume that is an IBM iSeries 9406-800) is  End Of Life at least 10 years ago, so if you have IBM Hardware maintenance contract active with that machine, maybe you may not have Support because the machine is very old to be maintained from IBM.


    In that case, write down the IOP card part number and if you are lucky, maybe someone will sell it in eBay or similar.


    Un saludo,


    Urtzi Larrieta

    Responsable Sistemas de Información | Ecna informática

    Tel: 944 15 96 88, ext. 2050 | 944 55 96 50 | 666 05 14 74

    Bilbao: Rodríguez Arias 15, 7ª planta dcha., 48008

    Vitoria-Gasteiz: Vicente Goikoetxea 6, 1º- ofic. 4F, 01008



  • 3.  RE: 286C SRC from a power 6 9406-800

    Posted Fri May 24, 2024 09:55 AM

    Hola Carlos. Tengo el mismo problema. Me gustaría saber si pudiste dar con la solución. 

    Aaron Campos

  • 4.  RE: 286C SRC from a power 6 9406-800

    IBM Champion
    Posted Mon May 27, 2024 06:17 AM

    The error message indicates a dependency conflict during a package update process. Here's how to address it:

    Understanding the Error:

    • rpm-build-3.0.5-30.ppc (package you're trying to update) requires:
      • /bin/bash2 (specific version of bash shell)
      • libpopt.so (library)
    • The system cannot install these dependencies because of conflicts with existing packages:
      • Multiple versions of bash are installed, and they seem to be incompatible.
      • Conflicting versions of popt library are present.

    Solving the Issue:

    There are three approaches you can take, depending on your risk tolerance and desired outcome:

    1. Forcefully Replace Conflicting Packages (Risky):

      • Use the --allowerasing flag with your package manager command. This forcefully removes conflicting packages to install the desired one (rpm-build). However, this approach can potentially break other functionalities that relied on the removed packages. Use with caution!
    2. Skip Broken Packages (Less Risky):

      • Use the --skip-broken flag. This skips installing rpm-build and any other packages that have unresolvable dependency conflicts. This leaves you with the current (potentially broken) state.
    3. Find Compatible Versions (Recommended):

      • This is the safest and most recommended approach. Investigate what bash and popt versions are compatible with rpm-build-3.0.5-30.ppc. You might need to search online for documentation or community forums specific to your package manager.
      • Once you identify compatible versions, try updating bash and popt to those specific versions before attempting to update rpm-build. This ensures compatibility without risking breakage.

    Additional Tips:

    • Consider using a virtual environment if you're working with development tools like rpm-build. This isolates dependencies and prevents conflicts with system-wide packages.
    • Consult your package manager's documentation for specific flags and options related to dependency resolution.

    Remember, forcing package replacement should be a last resort. Analyze the situation and choose the approach that best suits your needs.

    -- Source Google Gemini 

    Rakesh Ghoshal
    Principal Solution Architect

    Gulf Business Machines
    E-Mail: rghshal@gbmme.com
    Linkedin: www.linkedin.com/in/rkg-kw
    PO Box 4175, Safat, Kuwait
    General Marketing & Services Representative for IBM WTC