Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESX host boot stops at the error: VSD mount/Bin/SH:cant access TTY job control turned off (1012874)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 45454Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

An ESX 4.x host becomes unresponsive when it is put into maintenance mode.

Rebooting the host fails.

On the ESX console, you see the error:

VSD mount/bin/sh:can't access TTY; job control turned off.

The ESX host does not boot and drops into Troubleshooting (busy box) mode.

The last lines in the /var/log/messages log file are similar to:

sysboot: Getting '/boot/cosvdmk' parameter from esx.conf
sysboot: COS VMDK Specified in esx.conf: /vmfs/volumes/4b27ec62-93ec3816-0475-00215aaf882a/esxconsole-4b27e9e3-20ee-69d7-ae11-00215aaf882a/esxconsole.vmdk
sysboot: 66.vsd-mount returned critical failure
sysboot: Executing 'chvt 1'

Cause

This issue occurs if an ESX host cannot identify the esxconsole.vmdk file in which the service console resides.

Resolution

This issue is resolved in ESX 4.0 Update 3 and ESX 4.1 Update 2.

Important: If your ESX is booting from SAN, the service console must be installed on a VMFS datastore that is resident on a host's local disk or on a SAN disk that is masked and zoned to that particular host only. This datastore cannot be shared between hosts. For more information, see the ESX and vCenter Server Installation Guide. Verify these requirements are met before continuing with the troubleshooting.

To attempt to work around the issue without updating the ESX host:

Go to the console of the ESX host. After the error message, ESX drops into Troubleshooting (busy box) mode.

Find the .vmdk for the service console by running the command:

# grep "/boot/cosvmdk" /etc/vmware/esx.conf

The output is similar to:

/boot/cosvmdk = "/vmfs/volumes/<uuid>/<dir>/esxconsole.vmdk"

For example:

/boot/cosvmdk = "/vmfs/volumes/4a14d968-88bf7161-700f-00145ef48f76/esxconsole-4a14d906-2f96-7956-7284-00145ef48f74/esxconsole.vmdk"
</dir>

Make note of the <uuid> and the <dir> values in the output.</dir>

Verify that the files exist by running the command:

# ls -al /vmfs/volumes/<uuid>/<dir>/*.vmdk

Where <uuid> and <path> is from the output of step 2.

The output is similar to:

total 7906560
drwxr-xr-x 1 root root 840 May 21 00:45 .
drwxr-xr-t 1 root root 2660 Oct 21 09:10 ..
-rw------- 1 root root 8095006720 Oct 26 15:37 esxconsole-flat.vmdk
-rw------- 1 root root 475 May 21 00:32 esxconsole.vmdk
drwxr-xr-x 1 root root 980 May 21 00:45 logs

Note: You may receive the error: ls: /vmfs/volumes/4a14d968-88bf7161-700f-00145ef48f76/esxconsole-4a14d906-2f96-7956-7284-045ef48f74/: No such file or directory. If the directory does not exist, see ESX fails to boot when the disk containing the datastore with esxconsole.vmdk is detected as a snapshot (1012142).
</dir>

Ensure that the esxconsole-flat.vmdk

If the esxconsole.vmdk file does not exist, see Recreating a missing virtual disk (VMDK) header/descriptor file (1002511) and ensure that the following settings are in place:

ddb.adapterType = "buslogic"

ddb.consoleOsDisk = "True"

Ensure that the esxconsole-flat.vmdk exists.

Note: If the esxconsole-flat file does not exist, you must reinstall ESX to recreate the service console.

Note: If reinstalling ESX is required and virtual machines or other important data reside on the local storage, ensure to select the Preserve VMFS option during the installation. This ensures that any local VMFS partition is left untouched.

Related Information

ESX fails to boot when the disk containing the datastore with esxconsole.vmdk is detected as a snapshot
ESX ホスト起動が次のエラーで停止する： VSD mount/Bin/SH:cant access TTY job control turned off
在出现以下错误时，ESX 主机停止引导：VSD mount/Bin/SH:无法访问 TTY，作业控制已关闭

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
可导致虚拟机无响应的常见 ESX/ESXi 主机配置问题 (1007813)

KB
•
了解消息“一个或多个第三方 NMI 处理程序请求崩溃” (2005413)

KB
•
ESX, ESXiとハードウェアイニシエータをつかったiSCSI アレイ接続に関するトラブルシューティング (1003951)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant