Search the VMware Knowledge Base (KB)
View by Article ID

Troubleshooting ESXi 4.1 Scripted Install errors (1022308)

  • 4 Ratings

Purpose

This article provides troubleshooting assistance for ESXi 4.1 Scripted Install issues. 
 
Note: This is not a comprehensive guide on setting up Scripted Install. For more information on setting up Scripted Install, see the ESXi Installable and vCenter Server Setup Guide.

Resolution

Logs

The installer parses a log file before running any of the commands. If there are syntax errors or incorrect command entries, these are displayed by the installer during the parsing phase.
 
If the Scripted Install breaks at any point during the deployment, the /var/log/weasel.log file (located on the host) may indicate the reason.  To check the contents the weasel.log file, press ALT+F1 from the install screen and log in as root with no password.
 
Caution: Do not reboot the ESXi host after the install fails, or the weasel.log file is lost. Weasel is VMware’s boot loader for ESX/ESXi.

Common errors

This list of errors may help you troubleshoot common Scripted Install issues:
  • Error 1:

    Error (see log for more info):
    An error has occurred while parsing the installation script
    error:nfs://xxx.xxx.xxx.xxx/mnt/array1/SERVER/scripted/ks.cfg:line 8: The disk (mpx.vmhba1:C0:T0:L0) specified in autopart is too small

    To resolve this error, ensure that the boot disk is at least 5 GB (the minimum size required for Scripted Install).
     
  • Error 2:

    Error (see log for more info)
    Error copying / downloading file
    NFS mount failure for URL nfs://xxx.xxx.xxx.xxx:/install

    To get more information about this error:
    1. Press ALT+F1.
    2. Login as root with no password.
    3. Change to the /var/log folder.
    4. Read the contents of the weasel.log. You may see an entry similar to:

      2010-01-14 09:37:30.285 INFO NFS source was not already mounted.  Mounting....
      2010-01-14 09:37:30.285 INFO NFS mount failure (Unable to resolve hostname xxx.xxx.xxx.xxx:) for host xxx.xxx.xxx.xxx.xxx:. root /
      2010-01-14 09:37:30.285 ERROR Could not open file over NFS nfs://10.21.74.192:/install
      2010-01-14 09:37:30.285 ERROR Exception: Error (see log for more info):
      Error copying / downloading file
      NFS mount failure for URL nfs://xxx.xxx.xxx.xxx:/install

      This log entry indicates that the file install does not exist. You must manually recreate the file. For more information, see the ESXi Installable and vCenter Server Setup Guide.
       
  • Error 3:

    Error (see log for more info):
    Error connecting to the network
    Did not get an IP Address from DHCP server

    This error may occur if the ks= command does not contain static IP information and if no DHCP server is reachable or configured. If there is no DHCP server, then you must assign a static address. Scripted Install defaults to DHCP when static addresses are not defined. If there is no DHCP server on the network, then the installer has no way of retrieving files over the network. 

You may also encounter this problem if your network is using VLANs and the vlan=xx (where xx is the VLAN being used) parameter is not specified.  Ensure that you read the ESXi Installable and vCenter Server Setup Guide for all valid parameters for the ks= command. 

  • Error 4:

    The following warnings were encountered while parsing the installation script
    warning:nfs://xxx.xxx.xxx.xxx:/SI_NFS/ks.cfg:line 5: bootproto was set to static but "--hostname=" was not set.  Hostname will be set automatically.

    To avoid this warning and ensure a hands-off installation, specify a hostname when setting a static IP. If you do not specify a hostname, this warning continually displays and you have to press Enter each time to complete the installation.

Tags

scripted-install ks-errors

Update History

03/21/2012 - Added information about VLANs.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 4 Ratings
Actions
KB: