EMS log reports "scsi cmd checkCondition" error on disk
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/EMS_log_reports_scsi_cmd_checkCondition_er…
Updated: Sun, 26 Jan 2025 03:19:44 GMT
Applies to
• ONTAP 9
• Drives
Issue
• EMS log reports scsi cmd checkCondition errors on one disk and the errors recover automatically
[node: Error] scsi_cmdblk_strthr_admin scsi cmd checkCondition:
deviceType="Disk" deviceName="0b.00.10"
cdb="0x88:000000016f1e7200:00000200" sSenseKey="SCSI:aborted command"
sSenseCode="" iSenseKey="0xb" iASC="0x4b" iASCQ="0x3" iFRU="0x0" DTime="1"
'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 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
disk_information=""
[node: Debug] pmcsas_admin_0 scsi cmd retrySuccess: deviceType="Disk"
deviceName="0b.00.10" retryCount="1" freeRetryCount="0"
cdb="0x88:000000016f1e7200:00000200" dTime="118"
[node: Error] scsi_cmdblk_strthr_admin scsi cmd checkCondition:
deviceType="Disk" deviceName="0b.00.10"
cdb="0x88:000000016f840e00:00000200" sSenseKey="SCSI:aborted command"
sSenseCode="" iSenseKey="0xb" iASC="0x4b" iASCQ="0x3" iFRU="0x0" DTime="1"
disk_information=""
[node: Debug] pmcsas_admin_0 scsi cmd retrySuccess: deviceType="Disk"
deviceName="0b.00.10" retryCount="1" freeRetryCount="0"
cdb="0x88:000000016f840e00:00000200" dTime="118"
[node: Error] scsi_cmdblk_strthr_admin scsi cmd checkCondition:
deviceType="Disk" deviceName="0b.00.10"
cdb="0x88:0000000170f82a00:00000200" sSenseKey="SCSI:aborted command"
sSenseCode="" iSenseKey="0xb" iASC="0x4b" iASCQ="0x3" iFRU="0x0" DTime="2"
disk_information=""
[node: Debug] pmcsas_admin_0 scsi cmd retrySuccess: deviceType="Disk"
deviceName="0b.00.10" retryCount="1" freeRetryCount="0"
cdb="0x88:0000000170f82a00:00000200" dTime="96"
◦ Other log output examples
[node: scsi_cmdblk_strthr_admin: scsi.cmd.checkCondition:error]: Disk
device 0a.01.7: Check Condition: CDB 0x2f:bb0a0800:0400: Sense Data
SCSI:no sense - (0x0 - 0x0 0x0 0x0)(32). ......
[node: scsi_cmdblk_strthr_admin: scsi.cmd.retrySuccess:debug]: Disk
device 0d.01.7: request successful after retry #0/#12: cdb
0x88:00000002f243ddc0:00000008 (20148).
• Syslog event details
Ems Identifier scsi.cmd.checkCondition
Syslog %s device %s: Check Condition: CDB %s: Sense Data %s - %s (0x%x - 0x%x 0x%x
Message 0x%x)(%d). %s
Severity ERROR
Description This message occurs when a check condition is received from a device. A check
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
condition is the mechanism whereby a target device reports an informational condition or
error status to the requesting host. Either the condition that generated this event is an
error that occurred during execution of the command and was not cleared by retrying the
request or an informational condition reporting status of the present operation or media
state.
• Drive reports missing:
12:33:45 +0100 [node4: config_thread:
raid.config.filesystem.disk.missing:info]: File system Disk
/aggr1_SAS_euhstorp13/plex0/rg0/bsasswpj5-2:9.126L91 Shelf 0 Bay
10 [NETAPP X343_HCBFE1T8A10 NA06] S/N [08H5L03A] UID
[5000CCA0:2C4283C4:00000000:00000000:00000000:00000000:00000000:00000000:000000
is missing.
Cause
Intermittent device hardware or firmware problems that are automatically handled by the ONTAP drivers through
command retries
Solution
• No action is required
• ONTAP has the ability to determine if a disk has exceeded its error thresholds, ONTAP then performs a
Rapid RAID Recovery by removing the disk from its RAID group for testing and, if necessary, failing the disk.
• If the frequency of this error is very high and EMS also reports other errors like medium error on the affected
disk
The solution might require a part replacement. Please contact NetApp Technical Support or log into the
NetApp Support Site to create a case. Reference this article for further assistance.
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3
Additional Information
Understanding Media and Recovered Disk Errors
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 4
