HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

HP ML350 T5 Network booting loop

 
Mr.McRAID
Occasional Advisor

HP ML350 T5 Network booting loop

I Install With Smartstart Windows Server 2003 R2 64Bits, no problem, disc 1 and disk 2.

Then reboot to Windows and run updates from Microsoft.
After that a reboot, but even if the boot sequence is correct, and network is as last, it wants to boot from network...again and again.

Intel boot agent and BIOS shows boot sequence:

Diskette
USB
DVD Drive
Embedded Network
PCI network

Still it trying to boot from network.

I started all over again, but after MS Updates is is trying to boot from network?

I can remove the second PCI-E network card (but I'm not on location right now)

But will that help? because there is still a embedded network card to boot from (with a looping result)

Try try to disable network in BIOS, but didn't find a entry to disable it?

Anyone a hint to fix this problem.

Because there are now 2 network cards, HP installed teaming sofware, not sure if that could be the problem. I just want to boot from internal SAS controller.
4 REPLIES
Mr.McRAID
Occasional Advisor

Re: HP ML350 T5 Network booting loop

Add printscreen
marcus1234
Honored Contributor

Re: HP ML350 T5 Network booting loop

ok so does that mean before ms updates it is okay,

if so note drivers for controller before and after updates do they change ,,
Mr.McRAID
Occasional Advisor

Re: HP ML350 T5 Network booting loop

Hi Marc,

The point is, after update it's looping in a try to boot from netwerk. So I can't look what is changed inti Windows and/or drivers.
Mr.McRAID
Occasional Advisor

Re: HP ML350 T5 Network booting loop

After install OS (not after updates only) same problem.

But problem solved by removing the USB stick !!!

Pfffffffttt