Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 865
  • Last Modified:

VMware ESXi 5.1 disconnects from vSphere client during storage creation

We have a new Dell T420, RAID5, out of the box, with ESXi 5.1 pre-installed, after installing the vSphere Client on my machine, connect and start to create storage, when it reaches Current Disk Format, it immediately disconnect the client. Sometimes I can reconnect, sometimes I have restart ESXi. I've changed IPs, as someone mentioned, IP conflict.

I have no CD or DVD drive, nor IDE ports to plug one up, just a SATA, which I don't have a SATA C/DVD drive to use. So, I trying to figure out how to fix or re-install ESXi.

Any ideas?
0
Harold
Asked:
Harold
  • 3
  • 2
1 Solution
 
Zephyr ICTCloud ArchitectCommented:
You're probably the same guy from VMware communities ... But anyway:

There's probably some DELL partitions on those disks, I'm guessing it's local storage yes?

 Search the log for errors on something like this: “HostDatastoreSystem.QueryVmfsDatastore- CreateOptions”
0
 
HaroldNetwork EngineerAuthor Commented:
I am and tried to search for that, but got no results. I sent you the log in VM Comm. You need it again, here it is.
viclient-7-0000.log
0
 
Zephyr ICTCloud ArchitectCommented:
No problem ... We'll continue on the communities to keep it easy ;-)
0
 
Zephyr ICTCloud ArchitectCommented:
The solution to this issue is to be found in this KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2037192

It comes down to deleting pre-existing partitions (in this case 2) that come with the DELL disks.
The vSphere client isn't able to delete them and create new storage.

These are the commands:

fdisk -u /vmfs/devices/disks/naa.690b11c049b2a600194a4c871a10b492 (this number you'll have to either search for in the vSphere client logs or on the ESXi host)

Then following:

The number of cylinders for this disk is set to 36404.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): d
Partition number (1-4): 1

Command (m for help): d
Selected partition 2

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table
~ #

Then Type following again for confirmation

fdisk -lu
0
 
HaroldNetwork EngineerAuthor Commented:
Thanks so much for the help!!

Regards
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now