cannot see first disk - vhost 1

[mdraja]

Hi

I have created two lvs: lvroot and lvdata and assigned them to vhost0 as VTDs data and root
padmin@localhost# lsmap -vadapter vhost0
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9119.590.518191E-V9-C15 0x00000000

VTD data
LUN 0x8200000000000000
Backing device lvdata
Physloc

VTD root
LUN 0x8100000000000000
Backing device lvroot
Physloc

I am trying to run and NIM install for this client. However, when the client boots via SMS, I can only see lvdata (8200000000000) when I look at all hard disks. Does anyone know why 810000000 is not coming up (root)? Incidentally, when searching for hard disks, it does scan 8100000 but doesn't allocate it?

Any help greatly appreciated

 

[p5wizard]

Double check the mapping between the vhost adapter on the VIOS and the vscsi adapter on the client LPAR.

I'd also try and recreate the VTD with a different name, just to make sure that the name "root" is not causing your trouble.


HTH,

p5wizard

 

[mdraja]

Mapping is fine, it can definitely see one of the vtds which are on the same vhost
Changed the vtd name to servername_root, but still not picking it up unfortunately

 

[p5wizard]

Not convinced (yet):

SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9119.590.518191E-V9-C15 0x00000000

That 0x00000000 in the Client Partition ID column tells me that the VHOST vhost0 is not (yet) connected to a VSCSI adapter on a client LPAR.

Rerun the lsmap command while the client LPAR is in SMS menu, so you can verify that the vhost is serving to the correct VSCSI adapter on the correct LPAR.

Also, on the VIOS, run the command lsvg -lv rootvg (or other VG name if the "serving" LVs are in another VG)



HTH,

p5wizard

 

[mdraja]

Thanks p5wizard - found a hardware error on the HMC for this LPAR. Created another LPAR and it worked fine. It was strange that one LV (data) managed to come up successfully. You're quite right that the client partition ID is incorrect. Will investigate the h/w failure further. Many thanks for the help