Page Comparison

...

1. Unzip the topology file and open file de.sva.bvq.powervm.model.VirtualIOServer.json.
   This file shows the VIOS information collected from the HMC.
   Convert the JSON file using Notepad++ and a JSON plugin.
   

   

   
   

2. Fold all
   

   

3. There is only 1 foldable Textblock left
   Search for the uniqueDeviceID, which was already displayed in the log above:
   ”Cannot persist physical volume 01MkMwMzMDUyYzDEwMUzMDADAwMDAMTwMyNTM4jAyMAxNjAzNDMzMzQW52bWU=”
   

   

4. You have found the correct volume, as you can see the volume infos are now unfolded, as is the info of the corresponding VIO
   You can see:
   "uniqueDeviceID" - of the volume
   "volumeName" - of the volume
   "locationCode" - internal disk location → null is problematical
   ”partitionName" - affected VIOS system
   

   

5. Log on to the affected VIOS system and run cfgmgr to re-check the configuration of the VIOS
   Execute the script

   View file
   name cleanup_cmdb_with_logging.sh

   on the VIOS.
   Important: These are very profound changes! Only execute this script on HA tested Systems!

6. Check with “lscfg -vl hdiskX” if the volume is now showing a location code.
   Repeat the procedure for all affected VIOS.
   As soon as all hdisks are fixed, the topo persist should succeed.

...