DL380 G4 Reboot when attempting to start RIS

[Dean_54]

Hi all,

When trying to start a RIS image the server will successfully PXE Boot and recieve an IP address. On pressing f12 to start network service boot the server will reboot itself.

Image is a Windows 2003.

RIS is working successfully as other pcs are able to commence the Client Installation Wizard.

Over to you all.

[Patrick_146]

Anyone a sollution yet ?

I have exactly the same problem, the image to use is not relevant because it doesn't get that far to choose an image to RIS.

any suggestions ?

[Nathan_63]

I am also having the same problem.

[Nathan_63]

Hi,

I've just tried it against a Windows 2003 RIS server (before I was building from a Windows 2000 RIS Server) and its working.

Hope you all have the same luck.

Regards,
Nathan

[Nathan_63]

Opps, please disregard my last post.

[Patrik Hellgren · Accepted solution]

I had the same problem and called HP support and got this workaround:

Change to IRQ 7 for the NIC that has PXE enabled.

Tried it and it did work after the change. After the change I had the PXE NIC set to IRQ 7 and all other devices set to IRQ 5.
We have seen this on DL360 G4 also but it was more intermittent. The workaround seemed to work on that one also.

I hope this info helps

[Dean_54]

Great.

I'll give it a go then award the points.

I called HP Support and was told that HP don't support RIS builds, only Smart Start and RDP.

[Michael Ellis_4]

We have the same problem on the new DL360 G4. When I change the IRQ of the PXE enabled NIC the IRQ of the other devices change also.

I've contacted HP about this and I'm awaiting a response. If anyone knows more please let me know.

[Patrik Hellgren]

We've had the same problem with DL360 G4. You seem to have to first change the IRQ for the NIC (all other devices also changes) and then change the other devices back to their old IRQ (the NIC keeps the newly defined IRQ). I seem to remember that on the DL360 G4 they seem to change in groups of three (or something like that) but we got it working as long as we had 2 different IRQ settings for the devices.

[Jerry Debner]

We were able to work around this problem by changing the onboard RAID controller - not the NIC. If yo do search on these forums you will find that this work around seeems to be successful for everyone that has tried it.

[Dean_54]

Thanks Patrik for your solution.

Worked fine. Server now boots into the Client Installation Wizard no probs.

[Dean_54]

Didn't try Jerry's suggestion. Thanks to everyone who contributed.