is this server supported in the 'smart start' toolkit ? that should have all the drivers you need, atleast for 2003 and winpe 2.0.
We downloaded the smart start cd and yanked the drivers for win2k3 and 2k8 from there. Image creation completes with no errors and incorporates the drivers but when we boot the system it goes through the winpe load and then stops with the "No buffer overflow no active nic found" error before starting the OS load. We tried with 2008 several times yesterday and are switching to 2k3 this morning but it fails with the same error.
I have some notes from Kunal on manipulating the silent install script through the advanced view to tweak injecting the drivers but I wanted to verify we had the right ones first. We had a devil of a time finding the correct storage drivers with that particular customer. This is with a 7.4.5 install. I saw a previous post you had addressed dealing this one where it looked like a driver issue but if we have the correct ones I am not sure what is up. I will happily take any guidance you can offer.
Your issue sounds driver related, but not storage driver. It sounds like it is the wrong NIC drivers. Are you sure the server is PXE booting from the onboard NICS and not a PCI NIC card? Those would potentially require different drivers than what is loaded by default.
and what is generating that message, that looks like it's BMI, and i know there have been bmi issues in the past... are you using the right arch of BMI w/ the right arch of winpe and your drivers (x86 vs x64) ?
Yes, it is a nic issue. I just mentioned Kunal's notes because it helped with that situation at the time. We have confirmed that the system is pxe booting from onboard eth0.
Okay, did a full review of our documentation with building out the Win drivers and we do appear to have everything correct. Not sure what is up here unless the drivers we have are bad.
can you step through the init.bat to see where it fails ?
I found the following HP doc noting an issue with loading winpe nic drivers. The nic we are using is on the list of affected units. We are working through manually adding the drivers to see if that helps. I will walk through the file as soon as we finish trying this fix and post results. I already have a ticket in for tracking purposes. Will include that in my next post for reference.
Document ID: c01425505
The HP NC-Series Multifunction Driver for Windows Server (BXVBDA.SYS - 64-bit and BXVBDX.SYS - 32-bit) is not included in the Windows Preinstallation Environment (WinPE) on the base Windows Server 2008 media. When attempting a scripted installation of Windows Server 2008 using WinPE, the HP NC-Series Multifunction Driver for Windows Server will not load.
Note: The HP NC-Series Multifunction Driver for Windows Server is used with following HP NC-Series network adapters:
HP NC370F Multifunction Gigabit Server Adapter
HP Dual NC370i Multifunction Network Adapter
HP NC370T Multifunction Gigabit Server Adapter
HP NC371i Integrated PCI-X Multifunction Gigabit Server Adapter
HP NC373F PCI-E MFN 1000SX Gigabit Server Adapter
HP NC373i Integrated Multifunction Gigabit Server Adapter
HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter
HP NC373T PCI Express Multifunction Gigabit Server Adapter
HP NC374m PCI Express Dual Port Multifunction Gigabit Server Adapter
HP NC380T PCI-E DP MFN 1000T Gigabit Server Adapter
To ensure the Windows Preinstallation Environment (WinPE) Windows Server 2008 scripted installation includes the HP NC-Series Multifunction Driver for Windows Server, perform the following:
Install the Windows Automated Installation Kit (WAIK).
Start a command prompt in the WAIK as follows:
Start->All Programs->Microsoft Windows AIK->Windows PE Tools Command Prompt
Create folders for this operation similar to the following:
Both of the following files should be displayed:
If the files are not displayed, repeat the peimg command (step 7) and the imagex command (step 8) until the files are displayed.
Import the Boot.wim into Windows Deployment Services (WDS).
PXE the blade and choose the new WIM. Windows Server 2008 (or Windows Server 2003) will then perform the installation from WDS in the usual manner.
Issue resolved! Also found out that one of the drivers we were using was corrupt by running through the steps above. Ticket 30924 is the reference ticket.