Sudden power outages at home today, after which the ESXi server has been crazy, connected to the monitor, and found that it has not been activated. Staying in the ESXi Loading module ipmi_si_drv is not loaded by the ipmi_si_drv module.
So various reasons to find, google, saw a post as follows, you need to close this module, but even the server can not connect!
Today, when I restart a failed server, stuck in Loading module ipmi_si_drv ... , about 30 minutes boot is completed. avoid-vmware-esxi-loading-module-ipmi_si_drv First try setting IPMI to Shared in BIOS, if the option is available. When booting your installation media, press Shift O to display the boot arguments and add noipmiEnabled to the boot arguments. Remember to do the same once the installation/upgrade is complete. Manually turn off or remove the module by turning the option VMkernel.Boot.ipmiEnabled off in vSphere or using the commands below: # Do a dry run first: esxcli software vib remove –dry-run –vibname ipmi-ipmi-si-drv # Remove the module: esxcli software vib remove –vibname ipmi-ipmi-si-drv or try the following command in an unsupported shell connection: esxcfg-module -d ipmi_si_drv This disables the module although it still gets loaded. Use a -l argument to see what modules are enabled/loaded and check that your desired one is disabled. This appears to be persistent across a reboot.
Later I found the HP iLO is not responding article:
When during boot of an HP ProLiant server you see the “iLO2 not responding. System health monitoring has been disabled.” error message you need to restart the HP Integrated Lights-Out (iLO) component in the server. iLo is a small, always on computer with a web interface to monitor and manage the hardware of the HP ProLiant servers. You can monitor the temperature sensors, fan speeds, power usage, and you can turn on and off the server remotely. So if you accidentally shut down the server or the server loses power and does not start automatically you can push the virtual power button on the web interface and turn on the server as if you would stand in front of it. To restart iLO in the HP ProLiant server you have to completely discharge all electricity from the server. shut down the server, disconnect all power cords from the electrical outlets, remove all power supplies from the server (you need to disconnect the power cord from the power supply too to remove the power supply), press and hold the power button on the front of the server for 15-30 seconds, re-install the power supplies, connect the power cables to the power supplies, connect the power cables to the electrical outlets, momentarily press the power button on the front of the server to turn on the server. This power reset does not erase any information of the iLO configuration, just restarts it. On the power on screen you should see the usual messages from iLO.
Originally because iLO information was lost after power failure, iLO4 could not be started. The message of iLO4 is: Warning iLO4 not responding solution To restart iLO in HP ProLiant server, all power must be completely released from the server:
1. Shut down the server;
2. Unplug the power cord from the power outlet;
3. Remove all power from the server (you also need to disconnect the power cord from the power supply to cancel the power supply);
4. Press and hold the power button on the front of the server for 15-30 seconds.
5. Reinstall the power supply;
6. Connect the power cord to the power supply;
7. Connect the power cord to a power outlet;
8. Temporarily press the power button on the front of the server to open the server.
9. This power reset does not clear any information about the iLO configuration, just restart it.
After that, everything was restored, and it took 2 hours before and after, hoping to help people who encountered the same problem.
评论专区