A customer is using a DL380 Gen10. They attempt to boot an installation media ISO with iLO Virtual Media, and the system fails to access the ISO. What are the most likely causes of this issue?…

Question

Options

• AHPSSA drives are configured for RAID 1 and not RAID 5
• BLegacy Boot is not enabled and the media is not UEFI compatible
• CSecure Boot has derived access to the ISO
• DThe ISO operating system is not supported by HPE
• EUEFI is not configured for iSCSI initiator support

• A
  3% (1)
• B
  15% (5)
• C
  76% (25)
• E
  6% (2)

Explanation

Secure Boot (C) and OS compatibility (D) are the two most likely culprits when iLO Virtual Media fails to access an ISO.

Why C is correct: Secure Boot enforces cryptographic signature validation on boot media. If the ISO lacks a valid UEFI Secure Boot signature, the firmware will deny access to it entirely - a common gotcha when mounting non-HPE-signed or unsigned installation media via iLO.

Why D is correct: If the operating system in the ISO is not on HPE's Hardware Support Matrix for the DL380 Gen10, iLO Virtual Media may fail to mount or present it properly to the system, resulting in a failed boot attempt.

Why the distractors are wrong:

• A (RAID 1 vs RAID 5): RAID configuration affects local disk redundancy, not the ability to access a remote ISO via iLO Virtual Media - completely unrelated.
• B (Legacy Boot not enabled): While UEFI/Legacy compatibility is a real concern in general, iLO Virtual Media operates at the firmware level and this is not the primary cause here.
• E (iSCSI initiator): iSCSI is for network-attached storage (SAN boot), not Virtual Media ISO mounting - a different boot method entirely.

Memory tip: Think of the two "S" filters - Secure Boot (blocks unsigned media) and Support matrix (blocks unsupported OSes). If either "S" fails, the ISO never boots. Eliminate anything about local storage (RAID) or network storage (iSCSI) since Virtual Media is neither.

No community discussion yet for this question.