asked on

Raw mappings ESXi

Hi,

I'm trying to do raw mappings according to this : https://www.experts-exchange.com/Software/VMWare/A_9174-HOW-TO-Add-Local-Storage-e-g-a-SATA-disk-as-a-Raw-Disk-Mapping-RDM-or-Mapped-RAW-LUN-to-a-virtual-machine-hosted-on-ESXi.html

However, I got 2 questions:

1.how can I determine which disk is what? I have 2 laptop disks, 3 sata disks of 2TB, 1 SSD of 120 GB (on which a vm to which I will map the disks) and 3 disks of 60 GB? Can be harmfull to map wrong things

2.when I try to map , it says:
/dev/disks # vmkfstools -r vmfs/devices/disks/t10.ATA_____ST2000DM02512D9YN164__________________________________W1d21MNQ /vmfs/volumes/VMFS5_HPM01
_SSD_LOCAL/ATA250_01/ATA250_01.vmdk
Failed to create virtual disk: The destination file system does not support large files (12).

3.howto unmap when wrong: just delete the vmdk?

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

1. As per Step 2 in the article

esxcfg-mpath -l or ls -al /vmfs/devices/disks

2. what size is the datastore? 250GB ? looks like it's too small, also try -z instead or -r

3. delete the vmdk

janhoedt

ASKER

Thanks.
1. Didn t go through full article. Will check that.
2.? Datastore to small? Yes, it s 250 gb. Don t understand. What I thought was happening = mapping of vmdk to physical disk. Iow: I map the physical disk of 250 gb to a virtual disk. That happens on my storage volume of 120 gb (ssd). I have to map also 3 disks of 2tb, I cannot make vmdk s of 2 tb(?!)

janhoedt

ASKER

Out of the article ". The mapping file contains metadata used to manage and redirect disk accesses to the physical device."
It is metadata, not the full content, right? So an ssd of 120 gb should suffice?

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

did you try -z ?

janhoedt

ASKER

Not yet. But please advise on mapping.
I have 2 laptop disks of 250GB, 3 SSD of 60 GB, 1 of 120 GB (on which the nexenta zfs so I should not touch that). Then I have 3 SATA disks of 2TB. No idea which disk is which one with the

When I do this ls -al /vmfs/devices/disks, I get the following (filtered out what seems necessary to me). 14 disks, whereas I only have 9 ... and it shows 6 ocz wheras there are only 3 ocz (3x 60 GB).

Please advise.
J.

lrwxrwxrwx 1 root root 73 Jan 26 19:23 vml.010000000020202020202020202020202057314532314d4e51535432303030 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21MNQ
lrwxrwxrwx 1 root root 75 Jan 26 19:23 vml.010000000020202020202020202020202057314532314d4e51535432303030:1 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21MNQ:1
lrwxrwxrwx 1 root root 73 Jan 26 19:23 vml.0100000000202020202020202020202020573145323152574a535432303030 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21RWJ
lrwxrwxrwx 1 root root 75 Jan 26 19:23 vml.0100000000202020202020202020202020573145323152574a535432303030:1 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21RWJ:1
lrwxrwxrwx 1 root root 75 Jan 26 19:23 vml.0100000000202020202020202020202020573145323152574a535432303030:2 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21RWJ:2
lrwxrwxrwx 1 root root 73 Jan 26 19:23 vml.010000000020202020202020202020202057314532315a4a4a535432303030 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21ZJJ
lrwxrwxrwx 1 root root 75 Jan 26 19:23 vml.010000000020202020202020202020202057314532315a4a4a535432303030:1 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21ZJJ:1
lrwxrwxrwx 1 root root 75 Jan 26 19:23 vml.010000000020202020202020202020202057314532315a4a4a535432303030:2 -> t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21ZJJ:2
lrwxrwxrwx 1 root root 74 Jan 26 19:23 vml.01000000004f435a2d324c3645524e553434425531583349464f435a2d4147 -> t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF
lrwxrwxrwx 1 root root 76 Jan 26 19:23 vml.01000000004f435a2d324c3645524e553434425531583349464f435a2d4147:1 -> t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF:1
lrwxrwxrwx 1 root root 74 Jan 26 19:23 vml.01000000004f435a2d535247335a52343750414c4c515755364f435a2d4147 -> t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6
lrwxrwxrwx 1 root root 76 Jan 26 19:23 vml.01000000004f435a2d535247335a52343750414c4c515755364f435a2d4147:1 -> t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6:1
lrwxrwxrwx 1 root root 76 Jan 26 19:23 vml.01000000004f435a2d535247335a52343750414c4c515755364f435a2d4147:2 -> t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6:2
lrwxrwxrwx 1 root root 76 Jan 26 19:23 vml.01000000004f435a2d535247335a52343750414c4c515755364f435a2d4147:3 -> t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6:3

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

what does the vSphere client show in storage ?

janhoedt

ASKER

This should give a good overview:
disks.jpg

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

usually, if you scroll to the right and look at the number, that is usually the serial number of the disk.

janhoedt

ASKER

You mean the identifier (column in screenshot)?

janhoedt

ASKER

I can't map the identifiers from what I see in putty ssh:

-rw------- 1 root root 60022480896 Jan 27 09:50 t10.ATA_____OCZ2DAGILITY3____________________________OCZ2
-rw------- 1 root root 60019441664 Jan 27 09:50 t10.ATA_____OCZ2DAGILITY3____________________________OCZ2
-rw------- 1 root root 60022480896 Jan 27 09:50 t10.ATA_____OCZ2DAGILITY3____________________________OCZ2
-rw------- 1 root root 104857600 Jan 27 09:50 t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DS
-rw------- 1 root root 20902313984 Jan 27 09:50 t10.ATA_____OCZ2DAGILITY3____________________________OCZ2
-rw------- 1 root root 39013318656 Jan 27 09:50 t10.ATA_____OCZ2DAGILITY3____________________________OCZ2
-rw------- 1 root root 2000398934016 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164________________________
-rw------- 1 root root 2000398934016 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164________________________
-rw------- 1 root root 134217728 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164____________________________
-rw------- 1 root root 2000263577600 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164________________________
-rw------- 1 root root 2000398934016 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164________________________
-rw------- 1 root root 134217728 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164____________________________
-rw------- 1 root root 2000263577600 Jan 27 09:50 t10.ATA_____ST2000DM0012D9YN164________________________

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

is the above the full output and width, expand the putty screen?

also what is the output of esxcfg-mpath -l

janhoedt

ASKER

This is the full output of esxcfg-mpath -l

sas.500062b000298a5c-sas.3745423aa9877d88-naa.50000391e6b86c68
Runtime Name: vmhba2:C0:T3:L0
Device: naa.50000391e6b86c68
Device Display Name: ATA Serial Attached SCSI Disk (naa.50000391e6b86c68)
Adapter: vmhba2 Channel: 0 Target: 3 LUN: 0
Adapter Identifier: sas.500062b000298a5c
Target Identifier: sas.3745423aa9877d88
Plugin: NMP
State: active
Transport: sas
Adapter Transport Details: 500062b000298a5c
Target Transport Details: 3745423aa9877d88

usb.vmhba32-usb.0:0-mpx.vmhba32:C0:T0:L0
Runtime Name: vmhba32:C0:T0:L0
Device: mpx.vmhba32:C0:T0:L0
Device Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
Adapter: vmhba32 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: usb.vmhba32
Target Identifier: usb.0:0
Plugin: NMP
State: active
Transport: usb

sas.500062b000298a5c-sas.74572d6d65958c7e-naa.50026b7227013069
Runtime Name: vmhba2:C0:T2:L0
Device: naa.50026b7227013069
Device Display Name: Local ATA Disk (naa.50026b7227013069)
Adapter: vmhba2 Channel: 0 Target: 2 LUN: 0
Adapter Identifier: sas.500062b000298a5c
Target Identifier: sas.74572d6d65958c7e
Plugin: NMP
State: active
Transport: sas
Adapter Transport Details: 500062b000298a5c
Target Transport Details: 74572d6d65958c7e

sata.vmhba0-sata.0:0-t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21ZJJ
Runtime Name: vmhba0:C0:T0:L0
Device: t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21ZJJ
Device Display Name: Local ATA Disk (t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21ZJJ)
Adapter: vmhba0 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: sata.vmhba0
Target Identifier: sata.0:0
Plugin: NMP
State: active
Transport: sata

sas.500062b000298a5c-sas.23667455b8c1036a-naa.5e83a97e0d95d643
Runtime Name: vmhba2:C0:T1:L0
Device: naa.5e83a97e0d95d643
Device Display Name: Local ATA Disk (naa.5e83a97e0d95d643)
Adapter: vmhba2 Channel: 0 Target: 1 LUN: 0
Adapter Identifier: sas.500062b000298a5c
Target Identifier: sas.23667455b8c1036a
Plugin: NMP
State: active
Transport: sas
Adapter Transport Details: 500062b000298a5c
Target Transport Details: 23667455b8c1036a

sata.vmhba34-sata.0:0-t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21MNQ
Runtime Name: vmhba34:C0:T0:L0
Device: t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21MNQ
Device Display Name: Local ATA Disk (t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21MNQ)
Adapter: vmhba34 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: sata.vmhba34
Target Identifier: sata.0:0
Plugin: NMP
State: active
Transport: sata

iqn.1998-01.com.vmware:localhost-6b36e40e-00023d000003,iqn.2000-01.com.synology:ds210j.name,t,0-naa.6001405db299711d0c98d3f72d81eede
Runtime Name: vmhba37:C0:T0:L0
Device: naa.6001405db299711d0c98d3f72d81eede
Device Display Name: SYNOLOGY iSCSI Disk (naa.6001405db299711d0c98d3f72d81eede)
Adapter: vmhba37 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:localhost-6b36e40e
Target Identifier: 00023d000003,iqn.2000-01.com.synology:ds210j.name,t,0
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:localhost-6b36e40e
Target Transport Details: IQN=iqn.2000-01.com.synology:ds210j.name Alias= Session=00023d000003 PortalTag=0

sas.500062b000298a5c-sas.28032c056e666246-naa.5000c5005b2c98fe
Runtime Name: vmhba2:C0:T0:L0
Device: naa.5000c5005b2c98fe
Device Display Name: ATA Serial Attached SCSI Disk (naa.5000c5005b2c98fe)
Adapter: vmhba2 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: sas.500062b000298a5c
Target Identifier: sas.28032c056e666246
Plugin: NMP
State: active
Transport: sas
Adapter Transport Details: 500062b000298a5c
Target Transport Details: 28032c056e666246

ide.vmhba1-ide.0:1-t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF
Runtime Name: vmhba1:C0:T1:L0
Device: t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF
Device Display Name: Local ATA Disk (t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF)
Adapter: vmhba1 Channel: 0 Target: 1 LUN: 0
Adapter Identifier: ide.vmhba1
Target Identifier: ide.0:1
Plugin: NMP
State: active
Transport: ide

sata.vmhba33-sata.0:0-t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21RWJ
Runtime Name: vmhba33:C0:T0:L0
Device: t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21RWJ
Device Display Name: Local ATA Disk (t10.ATA_____ST2000DM0012D9YN164__________________________________W1E21RWJ)
Adapter: vmhba33 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: sata.vmhba33
Target Identifier: sata.0:0
Plugin: NMP
State: active
Transport: sata

ide.vmhba1-ide.0:0-t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6
Runtime Name: vmhba1:C0:T0:L0
Device: t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6
Device Display Name: Local ATA Disk (t10.ATA_____OCZ2DAGILITY3____________________________OCZ2DSRG3ZR47PALLQWU6)
Adapter: vmhba1 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: ide.vmhba1
Target Identifier: ide.0:0
Plugin: NMP
State: active
Transport: ide

ASKER CERTIFIED SOLUTION

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

janhoedt

ASKER

How should I do that? Redraw the disk from the server and check? Hoped to avoid that ....

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

I'm afraid that's the only way, if you have not documented which disk, is connected to which SATA port.

janhoedt

ASKER

Ok, then it 'll be trial and error.

This works fine:

vmkfstools -r /vmfs/devices/disks/t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF /vmfs/volumes/VMFS5_HPM01_SSD_LOCAL/RawMappings/SSD60GB_01/SSD60GB_01.vmdk

Can you tell me one thing though: this disk is an SSD but is on my ide apparently, does that harm?

ide.vmhba1-ide.0:1-t10.ATA_____OCZ2DAGILITY3____________________________OCZ2D2L6ERNU44BU1X3IF

janhoedt

ASKER

... and can the devicename be naa.5e83a97e0d95d643 ?