Skip to main content
NetApp Knowledge Base

SnapCenter RDM creation fails with "Failed to create windows file system"

  1. Last updated
    May 20, 2025
  2. Save as PDF
Views:
1,160
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:
5/20/2025, 5:37:17 PM

Applies to

  • SnapCenter (SC)
  • SnapCenter plug-in for Windows (SCW)
  • SnapCenter plug-in for VMware vSphere (SCV)

Issue

  • When creating a Raw Device Mapping (RDM) for a host, the 'New-SDStorage' PowerShell cmdlet fails with :

Failed to create windows file system

and

Failed to get disk information [<Lun Serial #>]. Please check if there is SAN connectivity between the host/hypervisor and storage controller.

  • This is accompanied by errors in the SCW job logs like:

[Timestamp] Error SDW PID=[XXXX] TID=[XXXX] Error: RDM can be provisioned only on guest Operating systems based on Esx
[Timestamp] Error SDW PID=[XXXX] TID=[XXXX] Map virtual disk failed

[Timestamp] Verbose SDW PID=[XXXX] TID=[XXXX] task: Rescanning host bus status: Failed message: Error: RDM can be provisioned only on guest Operating systems based on Esx

 

 

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.