Skip to main content
NetApp Knowledge Base

Drive Location Reported in unreadable-sectors.txt does not match Drive Location in GUI or MEL

Views:
122
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

Prior to SANtricity OS 11.70.2

Issue

Drive Location Reported in unreadable-sectors.txt does not match Drive Location in GUI or Major Event Log (MEL).
  • MEL

B:5/6/21, 6:21:06 AM (06:21:06) 167631 226c Drive failure - Shelf 0, Bay 7 - Cause: 3 = Write failure; Drive WWN: 5000c50086bdexxx; SN: Z4014M9L0000C730xxx <--CRITICAL
B:5/6/21, 6:21:06 AM (06:21:06) 167627 226c Drive failure - Shelf 0, Bay 11 - Cause: 3 = Write failure; Drive WWN: 5000c50086bdaxxx; SN: Z40134F50000C730xxx<--CRITICAL

  • Unreadable Sector Table (unreadable-sectors.txt)

Volume LUN Accessible By Date/Time Volume LBA Drive Location Drive LBA Failure Type
vmwarexxx 1 Host Cluster xxxx 5/6/21, 6:32:08 AM 0x66151xxx Shelf 0, Bay 8 0x6c2axxx DA Error
vmwarexxx 1 Host Cluster xxxx 5/6/21, 6:32:07 AM 0x66151xxx Shelf 0, Bay 12 0x6c2axxx DA Error

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.