Archive

Archive for May, 2009

VMFS creation error: Unable to read partition information from this disk.

May 6th, 2009 Eric No comments

When trying to add a VMFS volume in the VIC I received the message “Unable to read partition information from this disk.” I did not have an option to overwrite any data and could not continue. The SAN administrator said that the disk was presented the exact same way that another working LUN was.

At the console I figured out which device it was (esxcfg-vmhbadevs) and tested to see if I could read the partition table.  Here is what I got.

[me@vmhost me]$ sudo fdisk -l /dev/sdf

There is a valid AIX label on this disk.
Unfortunately Linux cannot handle these
disks at the moment.  Nevertheless some
advice:
1. fdisk will destroy its contents on write.
2. Be sure that this disk is NOT a still vital
part of a volume group. (Otherwise you may
erase the other disks as well, if unmirrored.)
3. Before deleting this physical volume be sure
to remove the disk logically from your AIX
machine.  (Otherwise you become an AIXpert).

Disk /dev/sdf: 543.0 GB, 543050956800 bytes
255 heads, 63 sectors/track, 66022 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot    Start       End    Blocks   Id  System

It appears that the LUN was had remnants of a file system that the service console refused to deal with. All I really needed to do was destroy the information on the disk. There are many options for doing this, but the one I chose was to launch fdisk and write an empty DOS partition table by using the o command. A quick w(rite) and I could create a VMFS volume on the LUN.

Categories: VMware Tags:

Alternative solution to deployment issues when change Service Console IP

May 5th, 2009 Eric No comments

Host IP in vpxa.cfg retains old value after changing service console IP.

The VMware solution is:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006768

The problem is that I did not want to lose my host’s historical information.  An alternative to removing and re-adding the host is to stop the Virtual Center service and update the VPX_HOST table in the Virtual Center database to contain the correct IP for the server(s).  When you start the service back up it will update the hosts configuration (vpxa.cfg) and everything should work again.

The query I used:

UPDATE VPX_HOST SET IP_ADDRESS = '10.11.12.13'
WHERE DNS_NAME = 'myvhost.localdomain.local'
Categories: VMware Tags:

Switch to our mobile site