HP Proliant problem, proxmox 3.0

[andrea68]

Hi,

I have 2 HP DL380 G7.
I proceed to install proxmox on both machines with latest version.
On the first one it's seems all working fine, on second one I had a problem: whenever I restart the server an error booting (illegal OpCode) happened...
Now I try to reinstall proxmox.

Meantime digging about this problem I see maybe could be a Grub-related problem.
Someone out there have same kind of problem?

Thanks...

 

[andrea68]

UPDATE: A fresh installation goes well, the problem rise after a full upgrade to latest patches and kernel.

Can someone confirm that?

 

[sumsum]

Can you post a picture of the boot error?
On some HP server a boot error shows up. But according various discussions in different forums this error can be ignored.

 

[andrea68]

This is the error at boot that I see when I start the server (after a full upgrade of proxmox3).
At this point I can just restart manually the machine and I see error again...



Now, after a clean install of Proxmox 3.0 (a very very slow one), the server start with many others errors like this ones:



But after a long time (approx. 10/15 minutes!!!) started correctly and seems working...

 

[sumsum]

I'm sorry, I never saw such an error on a HP proliant before. It may can be a hardware related error.

 

[andrea68]

Just for clarification: first error occured just when I upgrade to latest patches and kernel proxmox 3.
Digging on internet I found some HP link that said it's a Grub problem.

The second image instead show what happened after a clean installation of Proxmox 3.
The server has an hardware raid that proxmox recognise without problem during the installation.
If I restart the server I see many and many of these errors, but eventually server started and worked.

Anyone has seen something similar?

Thanks.

 

[oakleeman]

I know that this is several months old but I was running into the same problem recently with some BL360 G6 blades. After much trial and error I figured out that my BIOS had one of the onboard NICs had network boot enabled and even though I had the HDDs set to boot first it still wouldn't work. As soon as I disabled network boot on that NIC I didn't get any more errors and the servers boot properly.

 

[andrea68]

I know that this is several months old but I was running into the same problem recently with some BL360 G6 blades. After much trial and error I figured out that my BIOS had one of the onboard NICs had network boot enabled and even though I had the HDDs set to boot first it still wouldn't work. As soon as I disabled network boot on that NIC I didn't get any more errors and the servers boot properly.

Well, thank you anyway!!! Maybe it will be useful for someone else!