I boot from the CD rom, it starts loading the files, gets to the end (or near the end) and gives this message:
failed to resolve circular relocation
The computer then freezes until rebooted.
Does anyone have any idea why its saying this or what it means?
Thanks,
Derek of Colorado
yeah. Sorry about that.
mf
Thx. Will intel PCI-e and -x slot cards work?
I have already tried running the firmware update with LSI's FW but upon booting and config menu, it is still Intel. I got my hands on another one and got it working.
Thanks again.
Did you verify the MD5 checksum of the downloaded ISO image and - if the checksum is correct - did you try to burn another CD?
What kind of hardware do you use?
André
It is a IBM Server (MT 4251) with a Core I3 processor and 1GB of ram.
The CD was given to me by someone who has successfully used it to install ESXi on another server of ours, so I did not check the MD5 because its already worked on another server.
Do you think it could be a damaged CD issue?
EDIT: Also, it is installing off a USB CD-Rom that I have plugged into the server. That wouldn't affect this would it? I can try to load it off a USB thumb drive if necessary, but the server has no built-in CDRom and I have no PXE environment.
Thanks,
Derek of Colorado
From the system's specs, I rather think it's an issue with the host. I'm not sure whether the server you are using is supported, but ESXi requires at least 2GB RAM (more if you want to run VMs on the host) to be installed.
André
... to see whether the host and/or its components are supported, see http://www.vmware.com/go/hcl
André
Hey Jack,
Here are a few initial thoughts. If you can afford downtime, you can simply power down the VMs, download them to removable media (like an external hard drive), get them to the hosted facility (hand-carry, courier, covered wagon, etc.), then have them upload the VMs to the other host(s) datastores. Someone will then need to re-add the VMs to inventory via vCenter or directly on the host.
I've never done business with a hosting facility, but could there be competent engineers or administrators that work there that could accept your removable media and copy/upload them to your host(s) and/or datastores?
Without some sort of trusted WAN between facilities and some type of replicated or shared storage between the two, you may be very limited on options. I'll check back to see what others have to say.
Cheers,
Mike
https://twitter.com/#!/VirtuallyMikeB
http://LinkedIn.com/in/michaelbbrown
Message was edited by: VirtuallyMikeB
I'm sure you are correct.
That is my fault.
I was under the impression that ESXi ran on very very minimal specs, and that the hosts are what needed the hardware. I gotta watch those assumptions....
I'll try other options for this server.
Thank you for your help.
Derek of Colorado.
I checked the log on hostd.log
The error displays: Failed to send a response to client: broken pipe
The command "more" doesn't work (not found return), but "less" works. How do I end it while its reading the file? Control + C or Control + Q??
I had a similar incident, I did two things and not sure which action solved the probelm (1. disconnect and remove host from cluster 2. Reconfigured HA on the 1st node that was already in the cluster)
It was done in the order mentioned below
1. Disconnected the new node that I was trying to add to the cluster, then removed it from cluster
2. Reconfigured HA on the 1st node that was in cluster already, it had 4 guest os/virtual machine running on it (you don't need to take the host into maintenance mode to perform this step and this step does not affect the running virtual machine)
3. Add the host again (this time with FQDN e.g server2.blueeye.com) and exit from maintainence mode, HA agent got enabled without any error and host succesfully participated in the cluster.
What are the "better" alternatives to protect the vCentre server from failures
We need to build a new ESX i 5 vCentre and have had issues with the older one dying, so I want to get this one built with as much redundantcy as we can.
Either physical or virtual
Vmware FT only supports a tiny VM
Vmware HA doesn't really help, if you have corruption issues.
Vmware Heartbeat , comments?
MSCS ?
other's?
My extends dont seem to be connected. They are available to add, but I dont want to lose my data, and it states they will be formatted if i add them.
Please help
VMware. Net App. Versatile. – The Virtualization Dream Team
Hey Mike,
Yea, that is my train of thought also, I will have kvm access to the new site so configuration won't be a problem and both Colo's are in the same city, just that the new site doesn't allow customers to physically touch the hosted servers. I could probably send them an ESXi iso have them put it in the drive so I could install and configure ESXi, I was wondering if there was anyway to launch Vsphere client remotely, wonder what ports would need to be open to do a nat translation
Make sure the paths you specify in the build profile are reachable by the authenticating user. See page 51, in https://www.vmware.com/support/developer/studio/studio26/studio_developer.pdf
Thanks Duncan,
I forgot to mention that I have created a VM on the specified LUN and attempted to protect it. I just get the error "Not Replicated" next to the HDD in the wizard.
By checking the logs, do you mean on the main screen the System Log Files, or is there a specific log file for SRM?
I know that in recover point the LUN is added to the consisntency group and is listed as replicated.
In the attachment, i have highlighted the datastore group that all the rest of the LUNs appear in. Any new LUNs that are created will not appear. I have pressed "rescan array" and it doesn't change. This leads me to believe that there is a specific group either in SRM or SRA that these new LUNs need to be added to.
Can anyone confirm where this group is?
Hi Jack,
As far as the default ports for VMware products, here's a list of them:
Depending on the policies and capabilities of your hosting facility, you could set up a management client at the remote end and install the vSphere Client. Then a VPN to that client would suffice for management.
Cheers,
Mike
we fixed the reply counts and if you still see reply counts wrong, let us know. Also give us an example with detail on what is wrong with timestamp and reply counts, so that we can drill down the bug. Vendor does have bugs in this version and sometimes, the patch is not recommended and upgrade is more a solution. For reply counts bug, we patched it ourselves and hopefully it works now.
For some reason, one of my virutal drives was in it own folder. I just copied the drive folder over and that was the problem. Once I copied the other folder over with the .vmx and modified the .vmx to path all drives to the same folder it works!
Thanks for your help 
