- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL380 Gen10 invalid opcode booting esxi
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2023 07:17 AM - last edited on 12-27-2023 08:52 PM by support_s
12-21-2023 07:17 AM - last edited on 12-27-2023 08:52 PM by support_s
DL380 Gen10 invalid opcode booting esxi
I have a DL380 Gen10 that boots esxi 7.x from an sd card. A few days ago I did a routine firmware upgrade via Oneview. Profile firmware install method is set to 'Firmware and OS Drivers using Smart Update Tools'. Same process, same spp, etc that I've used successfully on several other identical servers. But after the first reboot, just as esxi was starting to load, I got an invalid opcode RSOD. I tried several suggested fixes that I found online - power server off for 5 minutes, reset ILO, reapplied the spp, etc. Nothing worked. I rebooted the server with the esxi install ISO and discovered that the sd card was not found. This server is in a remote location so reseating the sd card, or anything else in the server was not an option that day. As a last ditch effort, I reset the bios back to factory defaults and the server then booted. I reapplied the Oneview profile to restore the proper bios settings and the RSOD returned. So repeated the reset to factory defaults process again and got the same results. The server is back up now with factory default bios settings but I need to figure out what's going on as I have 20 or so left to do. My plan is to schedule some time to take the server and change the bios settings back one at a time to figure out which one is breaking it. I have a few hundred esxi hosts all with the same bios config and have no issues.
- Tags:
- SD Card_Slot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2023 08:18 AM
12-21-2023 08:18 AM
Query: DL380 Gen10 invalid opcode booting esxi - Prolaint server - DL380 Gen10
System recommended content:
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2023 12:18 AM
12-26-2023 12:18 AM
Re: DL380 Gen10 invalid opcode booting esxi
Hello|
Uncertain about how a BIOS reset is aiding in resolving the RSOD issue. Could you attempt removing the ADD-ON cards and check if reconfiguring the BIOS helps in recovering from RSOD?
Cheers....
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
