- Setting hp dl360 g6 to ahci mode install#
- Setting hp dl360 g6 to ahci mode update#
- Setting hp dl360 g6 to ahci mode driver#
After I did this and replaced the files with the ones from the backup my host came back up with the old configuration and everything worked again. Good morning,I have a HP Proliant D元60 G7 server that inexplicably went off. It’s enough, at least it was for me, to extract the local.tgz file from the state.tgz in the backup file to the root of your ESXI host. Where in the BIOS can i check if its in AHCI mode, or wher do i change it. In the end I found out (related blogpost: ), actually its not so hard to do a manual restore without any ESXi cli-tool, Power CLI or vSphere functionality.
I tried a couple of times and finally gave up. A common error seems to be a different UUID which wasn’t the case as this was the same machine. This also failed and finally made me worry.
Setting hp dl360 g6 to ahci mode install#
At first I didn’t really worry about it, I had a configuration backup (created using the “vim-cmd hostsvc/firmware/backup_config” command), so I did a clean install and tried to restore using the “vim-cmd hostsvc/firmware/restore_config” command. This time the installation went up to 78% but then stopped with a generic failure I don’t even remember. I made sure settings for Swap and Scratch were set properly to the local datastore (ESXI itself runs from a SD-Card) and tried again. The install aborted at first telling me there was a caching issue. At first i tried to update, so I mounted the ISO as a virtual DVD-Drive using ILO and was able to boot from it. It worked in the end but I ran into some problems.
Setting hp dl360 g6 to ahci mode update#
I’ve tried to update from 6.5 to 6.7U1 on a HP DL 380 G7 yesterday. This particular micro server is an excellent starting. Because this is a beginners guide, Ill be using the HP ProLiant MicroServer Gen8 G1610T as my server of choice. Open up PowerCLI and do the following:Add the 6.5 bundle There are many different ways to go about setting one up: build your own buy a ready-made barebones server or get a NAS (if media storage is your game).To make it easier, rename them to something like HPE_ESX6.5.zip and HPE_ESX6.0.zip. Download both the ESX 6.5 and 6.0 offline bundles and save them to a convenient place (ex: C:\HP) - download from this link.At the time of this writing, the latest version was 6.5.0R1. That being said, here is the procedure to customize the ISO: Customize your own HPE ESX ISO Unfortunately if you decide to create a custom ISO with the previous version of “hpe-smx-provider”, you will no longer be able to upgrade to any future ESX version and will need to do a full installation every time (thank you HP!).
Setting hp dl360 g6 to ahci mode driver#
(Simply) Replace the driver with it’s older counterpart (version 6.0.0) and reinstall (see below for the procedure or check the “download link” section at the very end for an already fixed ISO). It seems the “hpe-smx-provider” driver version 6.5.0 from the ESX 6.5 ISO is causing the PSOD. If like me you found yourself perplexed by the PSOD (pink screen of death) after upgrading from ESX 6.0 to 6.5, keep on reading for the fix (skip to the bottom for the download link to an already fixed ISO).
They’ve managed to break their custom ESX ISO on the G6 and G7 servers.