Hi,
we've been using ESX Enterprise w. Service Console for over 2 years - never had any trouble. Our ESX "engines" were based on Dell's PE 6850 with 4 dualcores and 48 GB of RAM. In September '08, we ordered 2 of Dell's new flagship servers (R900) with 4 quadcores and 64 GB of RAM, using ESXi embedded installed on a Kingston USB Key.
This year, March to be precise, one of the new hosts got disconnected from vCenter. We could connect directly via VI client, but the logs showed that vCenter failed in reinstalling the vpx-Agent. The reason was a unresponsive USB Key. The messages-log was full of those messages: "...StorageMonitor: 196: vmhba32:0:0:0 status = 0/7 0x0 0x0 0x0...", (vmhba32 is the R900's USB-Controller).
After issuing a call by Dell I redirected some of the directories which seemed to be required for installing the vpx-Agent to a san storage and copied the non corrupted contents from another ESXi-Host .(e.g. /etc/opt, /opt, /tmp, ...)
This workaround enabled us to VMotion all VMs of the host and reinstall ESXi embedded onto a new USB Key.
I thought this was a unique event, as even Dell's staff told us that this was the first case they heard about a corrupted USB-Key.
Ok, it may have been a little naive - Anyway yesterday the other host crashed with the same error.
Has anyone had similar problems? (except of the HP Keys which were defective out of the box)
We're running 55 VMs on the two R900 machines, which shouldn't be too much (btw it's far away from VMware's limits...)
Thanks in advance!
Nico
we've been using ESX Enterprise w. Service Console for over 2 years - never had any trouble. Our ESX "engines" were based on Dell's PE 6850 with 4 dualcores and 48 GB of RAM. In September '08, we ordered 2 of Dell's new flagship servers (R900) with 4 quadcores and 64 GB of RAM, using ESXi embedded installed on a Kingston USB Key.
This year, March to be precise, one of the new hosts got disconnected from vCenter. We could connect directly via VI client, but the logs showed that vCenter failed in reinstalling the vpx-Agent. The reason was a unresponsive USB Key. The messages-log was full of those messages: "...StorageMonitor: 196: vmhba32:0:0:0 status = 0/7 0x0 0x0 0x0...", (vmhba32 is the R900's USB-Controller).
After issuing a call by Dell I redirected some of the directories which seemed to be required for installing the vpx-Agent to a san storage and copied the non corrupted contents from another ESXi-Host .(e.g. /etc/opt, /opt, /tmp, ...)
This workaround enabled us to VMotion all VMs of the host and reinstall ESXi embedded onto a new USB Key.
I thought this was a unique event, as even Dell's staff told us that this was the first case they heard about a corrupted USB-Key.
Ok, it may have been a little naive - Anyway yesterday the other host crashed with the same error.
Has anyone had similar problems? (except of the HP Keys which were defective out of the box)
We're running 55 VMs on the two R900 machines, which shouldn't be too much (btw it's far away from VMware's limits...)
Thanks in advance!
Nico