I tried install ESX 3.5 update2 (esx-3.5.0_Update_2-110268.iso) for HP BL465c G5 in c3000.
I received message by reboot after it had installed it.
---
Mounting root failed.
Dropping into basic maintenance shell.
To collect logs for VMware,connect a USB storage device and
run 'bin/vm-support '
Machine will be rebooted when you exit from this shell.
--
see ref Attach File.
How should I just investigate a cause?
detail:
BL465c G5 have HP Smart Array E200i.
BL465c G5 is on http://www.vmware.com/pdf/vi35_systems_guide.pdf.
HP Smart Array E200i is on http://www.vmware.com/pdf/vi35_io_guide.pdf
and
The kind of problem which is similar was found in the case of nv_sata.
but E200i is SAS and cciss.
I can use Service console .
lspci -v
...
50:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200
Subsystem: Hewlett-Packard Company Smart Array E200i
Flags: bus master, fast devsel, latency 64, IRQ 20
Memory at fdf80000 (64-bit, non-prefetchable)
Memory at fdf70000 (32-bit, non-prefetchable)
Capabilities: Power Management version 2
Capabilities: Message Signalled Interrupts: 64bit+ Queue=0/1 Enable-
Capabilities: PCI-X non-bridge device.
lspci -vn
...
50:08.0 Class 0104: 103c:3238
Subsystem: 103c:3211
Flags: bus master, fast devsel, latency 64, IRQ 20
Memory at fdf80000 (64-bit, non-prefetchable)
Memory at fdf70000 (32-bit, non-prefetchable)
Capabilities: Power Management version 2
Capabilities: Message Signalled Interrupts: 64bit+ Queue=0/1 Enable-
Capabilities: PCI-X non-bridge device.
less /etc/vmware/pciid/cciss.xml
...
There was no strange point though it saw similarly.
I'm seeing this same problem on one of my BL465c boxes in a c7000 chassis using 3.5 u2. I'm re-running the install now and doing a media check to be certain, but it's quite unusual because we're running SAS drives on the e200i controller. Anyone else have any thoughts?
Hi, bit of a long shot but is your firmware recent on your system, array controller and disks? Might also be worth checking with irq's might be shared.
It's all the latest firmware, confirmed about 30 minutes ago. Similar to some other threads, I can boot into the Service console mode ok, but not into the full ESX. Looking into it more, it looks like the DIMMs are populated incorrectly, so I'll see about making a trip out to our datacenter (other side of town) to fix the DIMMs and see if that helps. For people's future reference, if you've got 2 physical CPUs in a BL465c, make sure that you populate banks A and C first, then B and D.
ESX worked when the memory was arranged in A and C slot.
Thank you!.
Two CPU did not move ESX here because of the arrangement of the
memory either.
ESX worked in one CPU, too.
Because usual Linux operated with two CPU, too it was thought whether
why of it be going.
I can also use ESX with two CPU in this. :smileyblush: