How to identify the corresponding vmdks to that of disks in windows guest OS

[workstation123]

Hi,

Is there a way to identify the vmdks at esx level to that of disks in guest level(windows os)? If so please help me with this?

Say I have two vmdks 1.vmdk and 2.vmdk whose corresponding SCSI controllers are (0,1) and (0,1)

and internally in the windows guest OS, these are seen as Disk 1 and Disk 2.

So now I want to generate a map between the two. Is this possible? If so please tell me how to do this?

PS: Im a newbie, so if this post does not belong here, please tell me where to post this.

[geddam]

Firstly, it shouldn't be "SCSI controllers are (0,1) and (0,1)" it should be (0,0) and (0,1).

Open command prompt from your windows guest...Type diskpart (a utility comes with Windows)...

1. Enter command: List volume (ex: ouput will be volume 1 and volume 2)

2. Enter command: Select volume 1 (this will select the volume for which you want to see details)

3. Enter command: detail disk (In the ouput you will se, Target and Lun ID, match the same with SCSI controller and disk IDs).

The same information will be present under Device Manager->Disk Drives-> right click appropriate drive-> select properties-> general tab (look for Target and LUN ID).

Thanks,,

Ramesh. Geddam,

VCP 3&4, MCTS(Hyper-V).

Please award points, if helpful

[workstation123]

Hi,

Thanks for the correction. That was 0,0 and 0,1.

I checked on this already but Target ID corresponds to SCSI controller info but LUN id is always 0.

I mean say if hard disk at esx level is (2,5) ; Then at guest level , Target ID - 5 but LUN is 0. So this is not helping yet.

[geddam]

Target ID is the actual disk ID...So I believe this info will be sufficient to identify a disk inside windows...This is an expected behavior..

Thanks,,

Ramesh. Geddam,

VCP 3&4, MCTS(Hyper-V).

Please award points, if helpful

[workstation123]

The issue comes when the controller info is (2,1) and (3,1)

In this case, we cannot distinguish based on target id itself (which is 1 for both in this case). This is where I am stuck at.

You said this is expected behavior on LUN id part. Can you brief me why this is so or point me to a location which will explain this.

Thanks for replying.