VMware VS4-ENT-PL-A - vSphere Enterprise Plus, Setup Manual, Page: 261 / 276

Host Stops Unexpectedly at Bootup When Sharing a Boot Disk with Another Host
When more than one host, either physical or virtual, boots from the same shared physical disk or LUN, they
cannot use the same scratch partition.
Problem
The host stops at bootup when sharing a boot disk with another host.
Cause
More than one ESXi host can share the same physical disk or LUN. When two such hosts also have the same
scratch partition configured, either of the hosts can fail at bootup.
Solution
1 Set the hosts to boot sequentially, and boot the hosts.
This setting lets you start the hosts so that you can change the scratch partition for one of them.
2 From the vSphere Web Client, connect to the vCenter Server.
3 Select the host in the inventory.
4 Click the Manage tab.
5 Click Settings.
6 Under System, select Advanced System Settings.
7 Select ScratchConfig.
The field ScratchConfig.CurrentScratchLocation shows the current location of the scratch partition.
8 In the field ScratchConfig.ConfiguredScratchLocation, enter a directory path that is unique for this
host.
9 Reboot the host for the changes to take effect.
View System Logs
System logs provide detailed information about system operational events.
Procedure
1 From the direct console, select View System Logs.
2 Press a corresponding number key to view a log.
vCenter Server Agent (vpxa) logs appear if you add the host to vCenter Server.
3 Press Enter or the spacebar to scroll through the messages.
4 Perform a regular expression search.
a
Press the slash key (/).
b Type the text to find.
c Press Enter.
The found text is highlighted on the screen.
5 Press q to return to the direct console.
What to do next
See also “Configure Syslog on ESXi Hosts,” on page 262.
Chapter 8 Setting Up ESXi
VMware, Inc. 261