Skip to main content
NetApp Knowledge Base

CSNAPC-989: SnapCenter fails to connect an existing LUN to a host when the LUN has no file system.

  1. Last updated
    Apr 24, 2025
  2. Save as PDF
Views:
39
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:
4/24/2025, 12:54:56 PM

Issue

Connect Disk wizard shows Failed - Failed to connect disk No disk is found on all nodes when SnapCenter tries to connect an existing LUN that has no file system to a host.

  • * When creating a new LUN outside of SC, SC fails to connect it due to the following error:
    Failed - Failed to connect disk No disk is found on all nodes.

  • The same error can come from the command line with Connect-SdStorage (with or without --SharedDisk) on the actual Windows
    Host: Connect-SdStorage : Failed to connect disk No disk is found on all nodes

  • SCW Job Logs (C:\Program Files\NetApp\SnapCenter\SnapCenter Plug-in for Microsoft Windows\job_logs show lines like the following.
    Example:

2020-02-12T11:40:10.6716065+00:00 Error SDW PID=[XXXX] TID=[XXXX] Error: Failed to get partition information from disk on node <PLUGIN HOST>
2020-02-12T11:40:10.6716065+00:00 Verbose SDW PID=[XXXX] TID=[XXXX] Error: Failed to get partition information from disk on node <PLUGIN HOST>   at SnapDrive.Nsf.Core.Host.PartitionManager.<>c__DisplayClass13.<ConnectDisk>b__d(String node)
  • When use SC GUI Hosts => Disks => Choose Host => Connect the job fails at the Creating Windows file system stage with error:
    Failed to connect disk. No disk found on all nodes

 

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.