HPE ProLiant DL380 Gen10 Server Build
Greetings for the day. Hope you all are doing well and staying safe.
I have a very peculiar issue right now.
First about the infrastructure.
I am on MECM 2002 with latest hotfix.
Standalone Primary. SQL on Remote box. 4 MP 50 DP 2 SUP.
Now about the actual issue :-
I have total 5 physical servers to build.
HPE ProLiant DL380 Gen10 – 2
HPE ProLiant DL380 Gen9 – 3
I am installing Windows Server 2016 STD. Content is replicated all over the place. All Gen9 servers build successfully but the Gen10 servers are failing. After apply OS step when it goes for the first reboot then once back we are getting BSOD. Screenshot of the BSOD given above.
Next it tries booting and gets out of BSOD with error below:
I have tried all these steps so far.
- Broke the RAID and configured only 1 array for the build.
- RAID 1 with ACHI.
- Legacy boot mode.
- Reset servers BIOS to default once and then didn’t work so reset to manufacture settings.
- Changing BOOT Image for the build. created new. But we have successful attempts for Gen9 so not sure.
- Left logical drive raw and let TS do DISKPART for me. DISKPART succeeded and GPT as well MBR with MSR drive shown.
- Cold boot.
- Remove unpartition drives.
- Changed NIC to inbuilt and port at switch side.
- Force MSR and GPT for EFI and UEFI.
- Changed ACHI to SSRRAID mode for HDD.
12 Assigned logical drive letter to C.
Since the error comes after first reboot the logs are not much of help. Before the reboot logs are all normal green. No error lines and message about reboot comes with success.
Any help would be appreciated.
Answers ( 7 )
The same task sequence, Boot Image, TS Media, Driver Package and OS Image was being used for both the models GEN 9 & GEN 10.
I was shooting blanks. Because everything was working according to the plans on “HPE ProLiant DL380 Gen9” but not on Gen 10 so we thought of taking it one step at a time.
1. Created Fresh Boot Image (Vanilla. Hope we can still call it). New TS. NEW OS IMAGE, All application packages being used in TS, NEW Drivers, New Drivers Packages.
2. Tried Imaging Gen 9 and successful at the first attempt. While trying Gen 10 we calculated what’s change from Hardware Prospective and we came to know that now it has Smart Storage. 🙂 Downloaded the drivers for the same. Imported. Added to Drivers Package. WHen you Change anything it asks for Package to use and it also says that update ADK and re-distribute content.
3. Did all that. Now created the Task Sequence Media fresh referring the new Boot Image. Booted. Disk PART. OS Installed. Rebooted. No More BSOD.
Apologies for delayed response.
I figured it out actually. Kindly close the thread.
That’s good to know – What was the resolution for this.
Pls share the solution so that others can try the same solution
I haven’t built a server yet but faced same kind of issue when building some special devices delivering for a project from a different vendor.
1. Have to tried to flash update the BIOS if newer version is available?
2. Check the Service Tag of Server, is it having a space in service tag?
3. Not sure if server have TPM settings, if yes try to disable it and then rebuild.
Yes Sir. Vishal’s blog helped me understand “Reboot to Come Out of WinPE”. Once the server comes out and initiates the first reboot that’s when it’s entering to BSOD.
Before that logs are all good. It should come back after the reboot but it enters into error with BSOD.
I’m sure you must already have a look into Vishal’s blog post to understand it better after the restart and getting out of WinPE
I’m sure you might more details in the log files