Skip to main content
NetApp Knowledge Base

A drive is in the DriveMissing state

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
h-series
Specialty:
hci
Last Updated:

Applies to

  • H610S
  • NetApp Element Software

Issue

  • The system reports a block drive as DriveMissing
sf-master-info log:
2025-08-27T09:33:47.186785Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 50491 master-1 drive/DriveDevice.cpp:837:TryReadLink|stat failed on result=/dev/slot1
2025-08-27T09:33:47.186817Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 50491 master-1 drive/DriveDevice.cpp:124:DriveDevice|Bad path lookupPath=/dev/slot1
2025-08-27T09:35:10.256451Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 50491 master-1 drive/Fstab.cpp:557:GetConnectedDevices|Missing dev.driveType=Block ent->GetPath()=/dev/slot1 dev={"canonicalName":"","connected":false,"dev":0,"devPath":"/dev/slot1","driveEncryptionCapability":"sed","driveType":"Block","name":"slot1","path":"/dev/slot1","pathLink":"/dev/slot1","product":"Unknown","scsiCompatId":"","scsiState":"Unknown","securityAtMaximum":false,"securityEnabled":false,"securityFrozen":false,"securityLocked":false,"securitySupported":false,"serial":"","size":0,"slot":1,"uuid":"xxxxxxxx-xxxx-xxxx-xxxxxxxxxx","vendor":"Unknown","version":"Unknown"}
 
events log:
2025-08-27T09:35:52.354Z Warning drive 1 node_name 0 No driveFailed 1 drive(s) with state: "DriveMissing" driveID: xx.
  • After reseating, replacing the missed drive, the missing status remain unresolved
sf-master-info log:
2025-09-02T06:01:52.157772Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52876 RPCServ-3 drive/DriveDevice.cpp:837:TryReadLink|stat failed on result=/dev/slot1
2025-09-02T06:01:52.157881Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52876 RPCServ-3 drive/DriveDevice.cpp:124:DriveDevice|Bad path lookupPath=/dev/slot1
…
2025-09-02T06:20:37.317494Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52870 RPCServ-3 drive/DriveDevice.cpp:837:TryReadLink|stat failed on result=/dev/slot1
2025-09-02T06:20:37.317602Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52870 RPCServ-3 drive/DriveDevice.cpp:124:DriveDevice|Bad path lookupPath=/dev/slot1
…
2025-09-02T06:27:56.487559Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52870 RPCServ-3 drive/DriveDevice.cpp:837:TryReadLink|stat failed on result=/dev/slot1
2025-09-02T06:27:56.487613Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52870 RPCServ-3 drive/DriveDevice.cpp:124:DriveDevice|Bad path lookupPath=/dev/slot1
…
2025-09-03T08:36:01.727663Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52866 RPCServ-3 drive/DriveDevice.cpp:837:TryReadLink|stat failed on result=/dev/slot1
2025-09-03T08:36:01.727768Z node_name master-1[50491]: [UNEXPERR-2] [Drive] 52866 RPCServ-3 drive/DriveDevice.cpp:124:DriveDevice|Bad path lookupPath=/dev/slot1

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.