Skip to main content
NetApp Knowledge Base

UEFI SAN Boot fails with ONTAP ASA

Views:
134
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • Host servers using UEFI BIOS for SAN boot
  • ONTAP ASA running 9.13.1 or earlier
  • Protocols
    • FCP
    • iSCSI

Issue

  • SAN Boot OS installation using UEFI BIOS fails against ONTAP ASA target.
  • ONTAP EMS logs illegal transfer length errors and invalid_len & INVALID_FIELD_CDB counters increment in the respective ONTAP ASA boot LUN stats during this SAN boot OS installation failure.

::> set -rows 0; event log show -node local -message-name scsiblade.illegal.xfer.len
Time Node Severity Event
------------------- ---------------- ------------- ---------------------------
2/24/2023 05:37:06 a400-01a ERROR scsiblade.illegal.xfer.len: Returned Illegal Request response to host type WINDOWS for command opcode 0x28 with a transfer length of 1441792 bytes on LUN 81K94$UD5IpS.

 

::*> set -privilege diagnostic

::*> statistics show -sample-id windows_sanboot

Object: lun
Instance: /vol/vol_winboot_uefi/winboot
Start-time: 2/24/2023 05:39:35
End-time: 2/24/2023 06:02:09

...
invalid_len 97 <<<<

...
task_errors_hist -
TASK_ERR_NONE 88
TASK_ERR_INVALID_CDB_FIELD 97 <<<<
SCSI_UA_POR 2

 

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.