<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: disk.senseError during initialize NetApp in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157848#M35870</link>
    <description>&lt;P&gt;We see the event on just disk 0a.00.1. If the errors are still continuing , then I would suggest to simply reseat that disk by keeping out for a min.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Aman Subba&lt;/P&gt;</description>
    <pubDate>Sat, 18 Jul 2020 10:44:44 GMT</pubDate>
    <dc:creator>amans</dc:creator>
    <dc:date>2020-07-18T10:44:44Z</dc:date>
    <item>
      <title>disk.senseError during initialize NetApp</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157828#M35858</link>
      <description>&lt;P&gt;Hi ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a NetApp storage FAS2554 with DS4243 shelf .&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I want to initialize it . Boot into boot menu 4 . During the initialization . This error is print :&amp;nbsp;&lt;/P&gt;
&lt;P&gt;==============================&lt;/P&gt;
&lt;P&gt;Zero disks, reset config and install a new file system?: Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(0). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: &lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;Disk device 0a.00.1&lt;/FONT&gt;&lt;/STRONG&gt;: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(0). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(1). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(60). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(61). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(61). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(63). &lt;BR /&gt;Jul 17 07:28:26 [localhost:scsi.cmd.noMorePaths:debug]: Disk device 0a.00.1: No more paths to device: cdb 0x28:0000a3e8:0018. All retries have failed. &lt;BR /&gt;Jul 17 07:28:26&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt; [localhost:disk.senseError:error]: Disk 0a.00.1: op 0x28:0000a3e8:0018 sector 18446744073709551615 SCSI:aborted command - (b 44 0 3c)&lt;/STRONG&gt; &lt;/FONT&gt;&lt;BR /&gt;Jul 17 07:28:26 [localhost:disk.ioFailed:error]: I/O operation failed despite several retries. &lt;BR /&gt;Jul 17 07:28:26 [localhost:diskown.errorReadingOwnership:warning]: error 129 (aborted error disk event) while reading ownership on disk 0a.00.1 (S/N ) &lt;BR /&gt;Jul 17 07:28:28 [localhost:wafl.memory.status:info]: 11128MB of memory is currently available for the WAFL file system. &lt;BR /&gt;Jul 17 07:28:28 [localhost:dcs.framework.enabled:info]: The DCS framework is enabled on this node. &lt;BR /&gt;Jul 17 07:28:30 [localhost:snmp.link.down:info]: Interface 7 is down. &lt;BR /&gt;Jul 17 07:28:30 [localhost:netif.linkDown:info]: Ethernet e0M: Link down, check cable. &lt;BR /&gt;Jul 17 07:28:31 [localhost:sas.cable.error:debug]: Failed to retrieve info of cable attached to SAS port "0a". &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(1). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(1). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(1). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(2). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(2). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(2). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.checkCondition:debug]: Disk device 0a.00.1: Check Condition: CDB 0x28:0000a3e8:0018: Sense Data SCSI:aborted command - (0xb - 0x44 0x0 0x3c)(2). &lt;BR /&gt;Jul 17 07:28:31 [localhost:scsi.cmd.noMorePaths:debug]: Disk device 0a.00.1: No more paths to device: cdb 0x28:0000a3e8:0018. All retries have failed. &lt;BR /&gt;Jul 17 07:28:31 [localhost:disk.senseError:error]: Disk 0a.00.1: op 0x28:0000a3e8:0018 sector 18446744073709551615 SCSI:aborted command - (b 44 0 3c) &lt;BR /&gt;Jul 17 07:28:31 &lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;[localhost:disk.ioFailed:error]: I/O operation failed despite several retries.&lt;/FONT&gt; &lt;/STRONG&gt;&lt;BR /&gt;Jul 17 07:28:31 &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;[localhost:diskown.errorReadingOwnership:warning]: error 129 (aborted error disk event) while reading ownership on disk 0a.00.1 (S/N )&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;==============================================&lt;/P&gt;
&lt;P&gt;The alter (!) light becomes yellow . I am not sure what is wrong .&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you have any idea ?&amp;nbsp; Thanks in advance .&amp;nbsp;&lt;/P&gt;
&lt;DIV id="gtx-trans" style="position: absolute; left: 100px; top: 1304px;"&gt;
&lt;DIV class="gtx-trans-icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 04 Jun 2025 11:00:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157828#M35858</guid>
      <dc:creator>JackWang</dc:creator>
      <dc:date>2025-06-04T11:00:57Z</dc:date>
    </item>
    <item>
      <title>Re: disk.senseError during initialize NetApp</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157845#M35867</link>
      <description>&lt;P&gt;I see this in the error log:&lt;BR /&gt;Jul 17 07:28:31 [localhost:&lt;STRONG&gt;sas.cable.error&lt;/STRONG&gt;:debug]: &lt;STRONG&gt;Failed to retrieve&lt;/STRONG&gt; info of &lt;STRONG&gt;cable attached&lt;/STRONG&gt; to SAS port &lt;STRONG&gt;"0a".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Possible cause:&lt;BR /&gt;Faulty SAS port in the controller - most likely SAS port '0a', check the cable/port.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Steps to check:&lt;BR /&gt;1) Re-seat/replace the SAS cable for that path (0a).&lt;BR /&gt;2) If the issue remains, re-seat/replace the IOM for that path.&lt;BR /&gt;3) If the issue remains, replace the controller with the SAS port for that path (For NetApp Support to decide)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Please refer this KB: (If need be, raise a ticket with NetApp)&lt;BR /&gt;&lt;A href="https://kb.netapp.com/Advice_and_Troubleshooting/Flash_Storage/AFF_Series/scsi.cmd.checkCondition_errors_reported_for_all_the_disks_in_the_same_path" target="_blank"&gt;https://kb.netapp.com/Advice_and_Troubleshooting/Flash_Storage/AFF_Series/scsi.cmd.checkCondition_errors_reported_for_all_the_disks_in_the_same_path&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 18 Jul 2020 01:32:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157845#M35867</guid>
      <dc:creator>Ontapforrum</dc:creator>
      <dc:date>2020-07-18T01:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: disk.senseError during initialize NetApp</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157848#M35870</link>
      <description>&lt;P&gt;We see the event on just disk 0a.00.1. If the errors are still continuing , then I would suggest to simply reseat that disk by keeping out for a min.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Aman Subba&lt;/P&gt;</description>
      <pubDate>Sat, 18 Jul 2020 10:44:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157848#M35870</guid>
      <dc:creator>amans</dc:creator>
      <dc:date>2020-07-18T10:44:44Z</dc:date>
    </item>
    <item>
      <title>Re: disk.senseError during initialize NetApp</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157928#M35909</link>
      <description>&lt;P&gt;I switch disk on this port with another normal one . The disk is broken .&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2020 03:48:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/disk-senseError-during-initialize-NetApp/m-p/157928#M35909</guid>
      <dc:creator>JackWang</dc:creator>
      <dc:date>2020-07-23T03:48:14Z</dc:date>
    </item>
  </channel>
</rss>

