Call “HostStorageSystem.ComputeDiskPartitionInfo” for object “storageSystem” on ESXi failed

On an internal VMware server we have for development machines we increased storage using a spare disk, but shortly after rebooting we received the following error: Call "HostStorageSystem.ComputeDiskPartitionInfo" for object "storageSystem" on ESXi "192.168.xxx.xxx" failed. It appears from searching around that ESXi is not correctly wiping the disk when it says it does.

Step 1 is to enable SSH access through theESXi console so that you can remotely access the server using something like PuTTY.

Step 2: Now try and find the name of the local disk:

~ # esxcfg-scsidevs -l

mpx.vmhba1:C0:T0:L0
   Device Type: CD-ROM
   Size: 0 MB
   Display Name: Local LG CD-ROM (mpx.vmhba1:C0:T0:L0)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/cdrom/mpx.vmhba1:C0:T0:L0
   Devfs Path: /vmfs/devices/cdrom/mpx.vmhba1:C0:T0:L0
   Vendor: LG        Model: CD-ROM CRD-8521B  Revis: 1.03
   SCSI Level: 5  Is Pseudo: false Status: on
   Is RDM Capable: false Is Removable: true
   Is Local: true  Is SSD: false
   Other Names:
      vml.0005000000766d686261313a303a30
   VAAI Status: unsupported
t10.ATA_____ST31000520AS________________________________________9VX0JTG0
   Device Type: Direct-Access
   Size: 953869 MB
   Display Name: Local ATA Disk (t10.ATA_____ST31000520AS________________________________________9VX0JTG0)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/disks/t10.ATA_____ST31000520AS________________________________________9VX0JTG0
   Devfs Path: /vmfs/devices/disks/t10.ATA_____ST31000520AS________________________________________9VX0JTG0
   Vendor: ATA       Model: ST31000520AS      Revis: CC32
   SCSI Level: 5  Is Pseudo: false Status: on
   Is RDM Capable: false Is Removable: false
   Is Local: true  Is SSD: false
   Other Names:
      vml.0100000000202020202020202020202020395658304a544730535433313030
   VAAI Status: unknown
t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875
   Device Type: Direct-Access
   Size: 238418 MB
   Display Name: Local ATA Disk (t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/disks/t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875
   Devfs Path: /vmfs/devices/disks/t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875
   Vendor: ATA       Model: WDC WD2500JS-75N  Revis: 10.0
   SCSI Level: 5  Is Pseudo: false Status: on
   Is RDM Capable: false Is Removable: false
   Is Local: true  Is SSD: false
   Other Names:
      vml.0100000000202020202057442d574d414e4b36303239383735574443205744
   VAAI Status: unknown

Then you can see the partitions (the first line shows disk information rather than being the first partition):

# partedUtil get /dev/disks/t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875

30394 255 63 488281250
1 63 488281247 165 128

("1" is partition number)

Now you should be able to delete the partition using: (important thing… you need to put partition # that you going to delete)

# partedUtil delete /dev/disks/t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875 1

You can double check its been deleted by running the partedUtil command again:

~ # partedUtil get /dev/disks/t10.ATA_____WDC_WD2500JS2D75NCB3__________________________WD2DWMANK6029875
30394 255 63 488281250

Now when you run the VSphere Client the disk should be successfully created.

Source this post : http://daniel-farm.com/call-hoststoragesystem-computediskpartitioninfo-object-storagesystem-esxi-failed/

need installation support on Fatal error: Panel requires Ruby 1.8 (Ruby 1.9 is not supported).

need installation support on Fatal error: Panel requires Ruby 1.8 (Ruby 1.9 is not supported).

When installer stops do next: 2. ruby -v (output will be probably ruby1.9.1...) 1. apt-get install ruby-switch 3. ruby-switch --list (output - all installed ruby versions -> ruby1.8 & ruby1.9.1) 4. ruby-switch --set ruby1.8 5. ruby -v (output -> ruby 1.8.7 (2012-02-08 patchlevel 358) [x86_64-linux]) 6. run installer again #./ai.sh

OpenVZ on Debian

OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated containers (otherwise known as VE or VPS) on a single physical server enabling better server utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files.

Step 1. Installation:
An OpenVZ kernel and the vzctl and vzquota packages are available in the Debian Squeeze repositories, so we can install them as follows:

apt-get install linux-image-openvz-686  vzctl  vzquota

Step 2. Create a symlink from /var/lib/vz to /vz to provide backward compatibility:

ln -s /var/lib/vz /vz

Step 3. Open with your favorite editor (eg: nano, vim) /etc/sysctl.conf and edit as following :

net.ipv4.conf.all.rp_filter=1
net.ipv4.icmp_echo_ignore_broadcasts=1
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.ip_forward=1
kernel.sysrq = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.eth0.proxy_arp=1

After you’ve edited /etc/sysctl.conf file run:

sysctl -p

Step 4. Open /etc/vz/vz.conf and set as following:

NOTE: This is important! If you don’t do this, networking will not work in the virtual machines!

NEIGHBOUR_DEVS=all

Step 5. Reboot the system using:

reboot or shutdown -r now

Step 6. After reboot run:

uname -r

Your output should be like this:

2.6.32-5-openvz-686

Step 6. Using OpenVZ

Before we can create virtual machines we need to have a template for the distribution that we want to use  in the/var/lib/vz/template/cache directory.

You can find a list of precreated templates on http://wiki.openvz.org/Download/template/precreated. For example, we can download a minimal Debian Squeeze template.

Step 7. Basic commands for using OpenVZ:

a) To set up a VPS from the debian-6.0-i386-minimal template run:

vzctl create 101 –ostemplate debian-6.0-1386-minimal –config basic

NOTE: 101 is the ID of your virtual machine. Each virtual machine must have  unique ID
b) Set the virtual machine to be started at boot:

vzctl set 101 –onboot yes –save

c) Set a hostname and IP address for the virtual machine:

vzctl set 101 –hostname debian-tutorials.com –save
vzctl set 101 –ipadd 10.10.0.2 –save

d) Start the virtual machine:

vzctl start 101

e) Set a root password for the virtual machine:

vzctl exec 101 passwd.

f) IPTables NAT that OpenVZ Container can connect to internet

   iptables -t nat -A POSROUTING -o eth0 -j MASQUERADE

For more commands you can use the man vzctl command.

https://openvz.org/Using_NAT_for_container_with_private_IPs
http://openvz.org/Installation_on_Debian

This tutorial is adapted for debian squeeze from http://howtoforge.com