IBM Support

IBM i Client Partition with VIOS (Virtual I/O Server) Host Partition Fails to Boot with SRCB2004158 When PVID is Set in VIOS

Troubleshooting


Problem

This document describes how to correct the problem where the PVID was set on an hdisk in VIOS, causing the i partition to fail to boot with SRCB2004158.

Resolving The Problem

If the command chdev hdiskx pv=yes is used in VIOS on a drive that is a load source drive for an i partition, this will cause the i partition not to boot and to receive SRCB2004158. The load source tagging gets over written with IBMA instead of IMD1. To correct the problem, you need to DM IPL from media to get to DST, and modify the page data on the load source drive. Once you get to DST, select option Work with disk units-->Work with disk unit recovery-->Disk unit problem recovery procedures-->Display Change Page Data. If you do not know which drive is the Load source, you can find it by going to page 00000010 on each disk and looking at offset 0040. The loadsource will have this offset 0040 set to 00010000.  






     
  • - Disk Header after chdev pv=yes, at offset0080 you can see the PVID calculated by VIOS



    This is a screen shot of the first page of Load Source Drive after PVID is set.

    This is a screen shot of offset 80 on the first page of the load source drive after PVID is set.

  • - Disk Header after changes



    Offset 0000 needs to contain C9D4C4F1 00000000 FF87C800 00040000 = 'IMD1. . . . .gH. . . . .'
    Offset 0080 needs to be changed back to all zero's.

    This is a screen shot of the modifications that are needed to return the drive to a load source drive.



F9 to save the changes, once the page data has been updated.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHzAAM","label":"VIOS"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

539113458

Document Information

Modified date:
04 May 2023

UID

nas8N1012691