Determine Where Server Is Booting From

[fitzie22]

I recently started at a new company and I have 2 esx servers both with a Raid-1 146gig array for local storage and is also connected to a SAN. I went to copy an ISO image to the local storage only to not be able to find it. below is a vdf -h output. I just want to know if wheter they never created a local vmfs3 volume and if not how do I go about adding it? Also how to I find out where it is even booting fro. I replaces the lun names with "Servername"

Filesystem Size Used Avail Use% Mounted on

/dev/sdz3 20G 2.1G 17G 12% /

none 131M 0 131M 0% /dev/shm

/vmfs/devices 3.2T 0 3.2T 0% /vmfs/devices

/vmfs/volumes/46432f49-f4063330-653e-0015171989f0

24G 18G 5.9G 76% /vmfs/volumes/Servername

/vmfs/volumes/464da37e-bae1a960-5a68-0015171989f0

51G 25G 26G 49% /vmfs/volumes/Servername

/vmfs/volumes/4664001c-c5179290-106e-0015171989f0

11G 11G 652M 94% /vmfs/volumes/Servername

/vmfs/volumes/46a05baa-f2c1b100-0c69-001517198dba

24G 18G 6.1G 75% /vmfs/volumes/Servername

/vmfs/volumes/46a08e32-36aa9fe0-0a8e-001517198db

26G 21G 4.9G 81% /vmfs/volumes/Servername

/vmfs/volumes/46a73c78-3cbe6dd0-21f7-001517198dba

21G 18G 3.2G 85% /vmfs/volumes/Servername

/vmfs/volumes/46c446df-054d9d80-4510-001517198dba

20G 20G 405M 98% /vmfs/volumes/Servername

/vmfs/volumes/46cbdf5b-23c85360-2caf-0015171989f0

24G 18G 6.2G 75% /vmfs/volumes/Servername

/vmfs/volumes/46cbe939-63ae3080-c0d8-001517198dba

22G 17G 4.9G 78% /vmfs/volumes/Servername

/vmfs/volumes/46ceed13-1925a450-b37a-0015171989f0

13G 9.4G 4.1G 69% /vmfs/volumes/Servername

/vmfs/volumes/46d6b1aa-906f5980-8eb1-0015171989f0

74G 69G 5.1G 93% /vmfs/volumes/Servername

/vmfs/volumes/46dd576c-874dc470-22d2-0015171989f0

21G 20G 1.1G 94% /vmfs/volumes/Servername

/vmfs/volumes/46ded464-308d0b40-d45e-001517198dba

21G 20G 1.1G 94% /vmfs/volumes/Servernam

/vmfs/volumes/46e51291-630d8cc0-10d7-001517198dba

33G 28G 4.9G 85% /vmfs/volumes/Servername

/vmfs/volumes/46e694ed-47b69230-0ce3-001517198db

21G 20G 1.1G 94% /vmfs/volumes/Servernam

/vmfs/volumes/46e7d36c-ecdd2ce0-cedc-001517198db

49G 37G 11G 76% /vmfs/volumes/Servername

/vmfs/volumes/46e909a9-c13bbd00-0c12-001517198dba

103G 102G 1.1G 98% /vmfs/volumes/Servernam

/vmfs/volumes/46efd432-e1b35160-d49b-001517198dba

92G 87G 4.8G 94% /vmfs/volumes/Servername

/vmfs/volumes/46fa3e23-f7de3bc0-3445-001517198dba

47G 44G 2.9G 93% /vmfs/volumes/Servername

/vmfs/volumes/46fa4038-11afb5f0-a2bc-001517198dba

99G 94G 4.4G 95% /vmfs/volumes/Servername

/vmfs/volumes/46fa41dd-4c373fc0-a1af-001517198dba

76G 72G 3.9G 94% /vmfs/volumes/Servername

/vmfs/volumes/470b7a6a-809e94b0-6bf1-0015171989f0

43G 42G 1.1G 97% /vmfs/volumes/Servernam

/vmfs/volumes/4715d657-2382b930-b622-001517198dba

23G 626M 23G 2% /vmfs/volumes/Servername

/vmfs/volumes/476b87dd-b2a70130-c3ac-001517198dba

119G 114G 5.1G 95% /vmfs/volumes/Servername

/vmfs/volumes/47cfb438-9b154e20-c83b-0015171989f0

9.8G 6.1G 3.6G 62% /vmfs/volumes/Servername

/vmfs/volumes/47d611e5-62acbd20-22aa-001517198dba

14G 10G 4.1G 72% /vmfs/volumes/Servername

/vmfs/volumes/47d66721-d7ba4240-e2d2-0015171989f0

14G 11G 3.1G 78% /vmfs/volumes/Servername

/vmfs/volumes/47d78ce1-52a8f4a0-9123-001517198dba

14G 10G 4.1G 71% /vmfs/volumes/Servername

/vmfs/volumes/47da271c-5548b2a0-8a45-001517198dba

49G 46G 3.1G 93% /vmfs/volumes/Servername

/vmfs/volumes/47da2eaa-8f2cf750-cb39-001517198dba

59G 51G 8.1G 86% /vmfs/volumes/Servername

/vmfs/volumes/47da40f3-2d4e6590-7009-001517198db

45G 41G 4.1G 91% /vmfs/volumes/Servername

/vmfs/volumes/47e79290-61cecdd0-0f1f-001517198dba

26G 23G 3.1G 88% /vmfs/volumes/Servername

/vmfs/volumes/47fdb7d9-e0bf96c0-097c-001517198dba

59G 54G 5.1G 91% /vmfs/volumes/Servername

/vmfs/volumes/4806fb92-48fcff10-55a9-001517198dba

49G 41G 8.1G 83% /vmfs/volumes/Servername

/vmfs/volumes/4808451d-8e9c2780-6034-001517198dba

14G 11G 3.1G 78% /vmfs/volumes/Servername

/vmfs/volumes/48088cae-f3c7dbd0-494e-0015171989

129G 121G 8.1G 93% /vmfs/volumes/Servername

/vmfs/volumes/4856746d-d8559b90-29a0-001517198dba

89G 627M 89G 0% /vmfs/volumes/Servername

/vmfs/volumes/485774f6-6edb5450-4501-001517198dba

39G 31G 8.0G 79% /vmfs/volumes/Servername

See this is how one of my other servers looks like

Filesystem Size Used Avail Use% Mounted on

/dev/sda2 4.0G 2.0G 1.8G 54% /

/dev/sda1 46M 16M 28M 37% /boot

none 131M 0 131M 0% /dev/shm

/vmfs/devices 2.8T 0 2.8T 0% /vmfs/devices

/vmfs/volumes/452be7e6-b44bf312-c65e-001372406f6a

869G 363G 505G 41% /vmfs/volumes/VMDisk2

/vmfs/volumes/ccc69ea4-da117faf-9394-87128767b1af

540G 225G 314G 41% /vmfs/volumes/VMDiskx

[Texiwill]

Hello,

Looks like the system is installed boot from SAN so there is no local drive. Do the following to get more information:

fdisk -l

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[rajkn]

doing cat /proc/scsi/scsi might help. The first LUN entry on the output should correspond to /dev/sda from which the system boot'd.

[fitzie22]

OK if I am not mistaken it is booting locally (see below) if I am correct in saying that would I also be correct in that they did not add the remaining disk space to vmfs3 for local storage?

Device Boot Start End Blocks Id System

/dev/sdq1 1 3133 25165758+ fb Unknown

Disk /dev/sdr: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdr1 1 522 4192901 fb Unknown

Disk /dev/sds: 128.8 GB, 128849018880 bytes

255 heads, 63 sectors/track, 15665 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sds1 1 15665 125829048+ fb Unknown

Disk /dev/sdt: 53.6 GB, 53687091200 bytes

255 heads, 63 sectors/track, 6527 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdt1 1 6527 52428063+ fb Unknown

Disk /dev/sdu: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdu1 1 522 4192901 fb Unknown

Disk /dev/sdv: 5368 MB, 5368709120 bytes

255 heads, 63 sectors/track, 652 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdv1 1 652 5237126 fb Unknown

Disk /dev/sdw: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdw1 1 522 4192901 fb Unknown

Disk /dev/sdx: 55.8 GB, 55834574848 bytes

255 heads, 63 sectors/track, 6788 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdx1 1 6788 54524546 fb Unknown

Disk /dev/sdy: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdy1 1 522 4192901 fb Unknown

Disk /dev/sdz: 146.1 GB, 146163105792 bytes

255 heads, 63 sectors/track, 17769 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdz1 1 9 72261 de Dell Utility

/dev/sdz2 * 10 270 2096482+ 6 FAT16

/dev/sdz3 271 2820 20482875 83 Linux

/dev/sdz4 2821 17769 120077842+ f Win95 Ext'd (LBA)

/dev/sdz5 2821 3852 8289508+ 82 Linux swap

Disk /dev/sdaa: 5368 MB, 5368709120 bytes

255 heads, 63 sectors/track, 652 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdaa1 1 652 5237126 fb Unknown

Disk /dev/sdab: 2147 MB, 2147483648 bytes

255 heads, 63 sectors/track, 261 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdab1 1 261 2096418+ fb Unknown

Disk /dev/sdac: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdac1 1 522 4192901 fb Unknown

Disk /dev/sdad: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdad1 1 522 4192901 fb Unknown

Disk /dev/sdae: 5368 MB, 5368709120 bytes

255 heads, 63 sectors/track, 652 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdae1 1 652 5237126 fb Unknown

Disk /dev/sdaf: 2147 MB, 2147483648 bytes

255 heads, 63 sectors/track, 261 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdaf1 1 261 2096418+ fb Unknown

Disk /dev/sda: 26.8 GB, 26843545600 bytes

255 heads, 63 sectors/track, 3263 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 1 3263 26209983+ fb Unknown

Disk /dev/sdb: 26.8 GB, 26843545600 bytes

255 heads, 63 sectors/track, 3263 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 1 3263 26209983+ fb Unknown

Disk /dev/sdc: 76.2 GB, 76235669504 bytes

255 heads, 63 sectors/track, 9268 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdc1 1 9268 74445146 fb Unknown

Disk /dev/sdd: 23.6 GB, 23622320128 bytes

255 heads, 63 sectors/track, 2871 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdd1 1 2871 23061243+ fb Unknown

Disk /dev/sde: 23.6 GB, 23622320128 bytes

255 heads, 63 sectors/track, 2871 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sde1 1 2871 23061243+ fb Unknown

Disk /dev/sdf: 23.6 GB, 23622320128 bytes

255 heads, 63 sectors/track, 2871 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdf1 1 2871 23061243+ fb Unknown

Disk /dev/sdg: 32.2 GB, 32212254720 bytes

255 heads, 63 sectors/track, 3916 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdg1 1 3916 31455206 fb Unknown

Disk /dev/sdh: 41.8 GB, 41875931136 bytes

255 heads, 63 sectors/track, 5091 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdh1 1 5091 40893393+ fb Unknown

Disk /dev/sdi: 111.6 GB, 111669149696 bytes

255 heads, 63 sectors/track, 13576 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdi1 1 13576 109049156 fb Unknown

Disk /dev/sdj: 95.5 GB, 95563022336 bytes

255 heads, 63 sectors/track, 11618 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdj1 1 11618 93321521 fb Unknown

Disk /dev/sdk: 47.2 GB, 47244640256 bytes

255 heads, 63 sectors/track, 5743 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdk1 1 5743 46130583+ fb Unknown

Disk /dev/sdl: 47.2 GB, 47244640256 bytes

255 heads, 63 sectors/track, 5743 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdl1 1 5743 46130583+ fb Unknown

Disk /dev/sdm: 21.4 GB, 21474836480 bytes

255 heads, 63 sectors/track, 2610 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdm1 1 2610 20964761 fb Unknown

Disk /dev/sdn: 79.4 GB, 79456894976 bytes

255 heads, 63 sectors/track, 9660 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdn1 1 9660 77593886 fb Unknown

Disk /dev/sdo: 1073 MB, 1073741824 bytes

128 heads, 32 sectors/track, 512 cylinders

Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System

/dev/sdo1 1 512 1048512 fb Unknown

Disk /dev/sdp: 47.2 GB, 47244640256 bytes

255 heads, 63 sectors/track, 5743 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdp1 1 5743 46130583+ fb Unknown

[Texiwill]

Hello,

You have quite a few LUNs there. When the system was installed did you disconnect the FC cables? That is generally a requirement. Note:

Disk /dev/sda: 26.8 GB, 26843545600 bytes

255 heads, 63 sectors/track, 3263 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 1 3263 26209983+ fb Unknown

Is a VMFS.... /dev/sdz is the boot volume, whereever that is located.

I would disconnect the FC cables or dezone the ESX server and then reboot. See what happens. I think you are not booting from local storage. Also you can run:

esxcfg-vmhbadev -q

That will list out which dev goes with what. Until you somehow remove the FC you may never know as each disk is a /dev/sd and not anything specific to the local host.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[fitzie22]

As to your first question I can't answer that as to they were built by a guy that is no longer here. Now the below entry from the output I beleive is the the local disk because it is the only lun the is the exact size that is configured locally (146 gig ) and the * under boot. Am I reading this wrong? As far as the amount of luns I hear you. It is a management nightmare...

Disk /dev/sdz: 146.1 GB, 146163105792 bytes

255 heads, 63 sectors/track, 17769 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sdz1 1 9 72261 de Dell Utility

/dev/sdz2 * 10 270 2096482+ 6 FAT16

/dev/sdz3 271 2820 20482875 83 Linux

/dev/sdz4 2821 17769 120077842+ f Win95 Ext'd (LBA)

/dev/sdz5 2821 3852 8289508+ 82 Linux swap

[Texiwill]

Hello,

Another way to check is write a large file to /tmp and see if the disk activity lights on the local device speeds up. However, I would say you are correct. Now you went to write an ISO to the local storage and now you want to attach that to a VM I assume? You will need to write that to the /vmimages directory or any other VMFS to be seen by the Edit Settings section to attach to your VM. It is not possible to see it from any other locations on your ESX boot disks.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization