ESXi and Proliant Weekend Woes
-
What ESXi version are you running?
-
Assuming you're running ESXi 5.0, 5.1 or 5.5 here is a link to an HP Driver update Follow the guides
And here is a person who had the same exact issue, but on the G7 (same hardware from what I can tell as far as the RAID Controller goes)
-
Pinging @John-Nicholson
-
I had a similar issue with my 5.x host two years ago. I updated the driver without a hitch and was good to go.
-
@DustinB3403 said:
Assuming you're running ESXi 5.0, 5.1 or 5.5 here is a link to an HP Driver update Follow the guides
And here is a person who had the same exact issue, but on the G7 (same hardware from what I can tell as far as the RAID Controller goes)
I am running 5.5. I have version 5.0.0-40OEM and it looks the problem driver was 5.5.0.58-1OEM. So my version looks ok. Also, I didn't have a PSOD, it just hung. I'm not averse to updating the driver apart from the fact that I really don't want to have to reboot the host at the moment until I can be sure it will boot successfully.
-
What about the firmware? Any known issues there?
-
Re: VeeamBackup_VEEAM1 (inactive) (unmounted).
What is this all about? The other hosts don't have this datastore and our Veeam server is powered on and has successfully backed up the host, so I'm not seeing any operational issues. I don't think this problem is related to my boot problems, but I'd like to get it cleaned up anyway.This just means that the NFS mount from Veeam, which is used as a connection for the backup is unmounted. When you backup a VM, Veeam will create on of these and it will show up as a datastore. This has happened to me when I moved my backup software to a new server. I just remove the unmounted store. It will get recreated if necessary and the files don't really sit on the host.
I'm pretty sure you are correct and that this is unrelated to your present problem.
-
Yeah, I've unmounted the Veeam datastore but I'm certain that was a red herring.
I really don't know where to go with this, other than to buy a new server! I don't even know if it's an HP issue or a VMware issue, a hardware issue or a software issue.
I need a plan of action!
-
I think I need to create a persistent storage location for logs. At the moment, I can't view any errors in vmkernal.log because the file is overwritten on every boot (it is stored on non-persistent storage).
I'm not sure.
If I specify logs are stored on the datastore (which is local storage), will it work? What happens if the boot hangs before the datastore is mounted? If it is hanging at "loading module hpsa", does this suggest it isn't mounting the datastore? And if that is the case, the logs files won't be written and so won't help me.
Or am I barking up the wrong tree?
-
It certainly wouldn't hurt to grab an older system and set it up to be your remote logging server for your ESXi infrastructure. It would at least give you something to look through while researching this issue.
Have you asked on the ESXi forums if anyone has any input on this?
