Search results

Thanks dasaint, came across something similar to that, but those links you posted give me a bit more info. Came across this a short while after I posted this, tried it and I can vMotion a machine back and forth without issue...

I've checked the BIOS, all virtualization options (that are available) are on.

I have 2 servers, one is a Lenovo TS430 (044116U) E3-1240 w/ 20GB Ram, and the other is an X8SIL-F w/ X3440 and 12GB Ram. Yesterday I upgraded vCenter, and the Lenovo host to 5.1, while the X8SIL host is still at 4.1. What I wanted to do was enable it so I could vMotion machines across to...

Thats the same kind of log entries I was getting before making that bios change. I'd email asrock support and see what they have to say about that option.

You may need to contact ASrock support and ask them about that specific options for that motherboard and see what they have to say. I'm not 100% certain, but, this option (or lack of) maybe whats causing esxi to choke on that driver. Have you looked at the logs while its loading to see what...

Does it completely hang, or just take a long time (5mins+) to go past loading that driver? It never really hung for me, just took a long time to load until I found the information I posted in the last post on that thread. PCI Rom Priority <- is the key setting, try to find that in the bios...

Just an update to this, did some searching again for new info, and came across a link at the vmware community forums (http://communities.vmware.com/message/2023326). I searched for this specific option with regards to a TS430 and got a link at lenovo support...

Thanks for the help lopoetve, gonna try to see what IBM/Lenovo have to say if anything.

Is it possible its doing that because there are no drives attached to it yet?

Disabled IRQ remapping and rebooted host, unfortunately, still the length delay and resets. Thought i'd post a bigger snippet of the log containing all the megaraid_sas info, from loading to success: 2012-03-04T18:41:53.426Z cpu4:2626)Loading module megaraid_sas ...

You can download the vsphere client (that runs on your local desktop) for free, its needed to connect to the ESXi machine to do anything. At least I was able to, going through the normal downloads.

The firmware when I got the machine initially was 20.10.1-0029, but I updated it to the latest firmware of 20.10.1-0077 from LSI's website while I was doing the u1 update to the machine. But there is still the delay on the latest firmware.

So I just recently got my hands on a Lenovo ThinkServer TS430 which happens to have an LSI 9240-8i controller card. I don't have any drives for it yet, trying to source the hot swap tray for cheaper then $70 bucks :( I have the drives (1TB WD Blacks), and going to setup a RAID10 array with 6...

Just download it on your desktop, and using vSphere Client, upload it to the data store. If its network storage, can copy it that way to, whichever way works for how your system is configured. As an example, I have a NFS share on a windows server that contains ISOs, so I just copied it via...

Download your patches, and copy em to a data store. In the vSphere Client, enable SSH access, and power down all currently active VMs, and enter maintenance mode. Logon to your ESXi server using putty (or your choice of SSH client), using root username with the password you set. The...

From post #35, it should be fixed from that patch bundle onwards; at least I've had zero issues since. Been running for 3 months, 1 power failure somewhere in there as well; and logs aren't ballooning out of control like they use to with IPMI enabled.

I used the command line esxupdate via the tech support shell since I don't have vCenter loaded. I put ESXi in maintenance mode first, then uploaded the bundle zip to a data store and from did an esxupdate esxupdate --bundle=ESXi410-201104001.zip stage esxupdate...

An update to this... Went looking for patches today and noticed the patch bundle ESXi410-201104001. After reading about the 2 updates in it, the ESXi410-201104401-SG update, has an interesting entry in its KB (http://kb.vmware.com/kb/1035108) which i pasted below. I went about applying...

By complete power loss I don't mean just turning it off, I mean a physical loss of power, so either unplugging it from the outlet, or a power outage. Even if you just power the machine down, its still drawing power (the IPMI and ethernet lights will still be active, as well you'll see the IPMI...

Forgot to mention a side-effect of solution (b), every time power is completely lost, the IPMI will be reset, so you need to do the fan thing again.

Sure, go for it...

I have a solution to this issue, that doesn't involve disabling IPMI in ESXi or CIM. It seems as tho, from a complete power loss (so new board, or unplugging the power) the sensor statuses are reset. So all fans are listed in a normal state. Now, if you do not use all the fan headers, the...

If you have spare fans, just plug a fan in, wait for it to register, unplug it, repeat for each header. and try to get them in alert states. Thats the only other thing I can think of to try.

I know one other thing I had tried when I was troubleshooting this, I grabbed some extra fans and just plugged them in so it registered them as being there (don't think i rebooted when i did this tho), but the log files still grew... they shows as normal with the rpm afterwards so they were...

sel will probably have "System Boot:" on every single line, and sel.raw will be "efef ef ef ef ef ef..." repeated many many times over, mine did when I had this problem.

in the IPMI web page, under server health, sensor readings; do the remaining 4 fans show as red with a Lower Non-recoverable as the status? or green with status as normal?

I'm not sure then, when I was going through everything, that's the only thing I did that seemed to correct it. Are you using all the fan headers?

When I was dealing with that issue, it worked for me, i'm guessing you rebooted after setting the asset tag?

ifru -N 192.168.1.X -U ADMIN -P ADMIN -a X8SIL-F X8SIL-F becomes the asset tag, limited to 16 characters. or use whatever you'd like for the asset tag

yep, make sure to put a string for the asset tag, and only need to set it once. did you check to see if it was the IPMI logs filling up? after you set it, i'd reboot the machine so esx starts off from a fresh boot, and monitor the /var/log/ipmi/0 folder for those 2 files, if you have some fans...

Grab the win32 zip (ipmiutil-2.7.4-win32.zip) extract it to a folder, open a command prompt, goto that folder, and ifru -N <ip> -U <user> -P <pass> -a <tag you want> That should do it.

Using the program from http://ipmiutil.sourceforge.net/ And used the ifru app, with the -a switch and just set the asset tag to X8SIL-F, be sure to specify the node (-N), user and password (-U and -P). As I had mentioned, it almost seems like this kick started something into working cause...

I ran into this exact same problem, use vdf -h to see the partitions for the file system, logs are stored in a 32MB ramdisk (specifically MAINSYS). Posted about it to but got no replies. If you check /var/log/ipmi/0/ and the sel and sel.raw files are filling up fast, then its the IPMI. I did...

So I managed to get this working, I don't know if it was a fluke or what. But I had decided to set the FRU Asset Tag (I don't know why, but I did), then all of a sudden it started behaving. It's almost as if that alone caused the IPMI to initialize and start working properly. Because after...

After lots of reading, I've finally have an ESXi 4.1u1 setup running on an X8SIL-F (w/ X3450, 8GB Ram) but I seem to be running into a slight problem. The problem persists on 4.1, and 4.1u1, haven't tried 4.0. The /var/log/ipmi/0 folder grows to the point where there is no space left, so any...