- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Servers - General
- >
- Storage Spaces Direct (s2d) wrong BusType with rai...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2024 07:02 AM - last edited on тАО12-29-2024 11:28 PM by Sunitha_Mod
тАО12-27-2024 07:02 AM - last edited on тАО12-29-2024 11:28 PM by Sunitha_Mod
I am facing issues while enabling Storage Spaces Direct (S2D) on my Windows Server setup.
Here are the details of my setup and the problem encountered:
Server Setup:
Server 1:
- Domain Controller Server and Failover Cluster Manager.
- Windows Server 2022 Standard
Server 2 (Cluster Node 1):
- Windows Server 2022 Datacenter
- Disks
PS C:\Users\Administrator> Get-PhysicalDisk
Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size
------ ------------ ------------ --------- ------- ----------------- ------------ ----- ----
2 ATA SAMSUNG MZ7L3960 **confidential info erased** SSD True OK Healthy Auto-Select 894.25 GB
0 ATA SAMSUNG MZ7L3960 **confidential info erased** SSD False OK Healthy Auto-Select 894.25 GB
1 ATA SAMSUNG MZ7L3960 **confidential info erased** SSD True OK Healthy Auto-Select 894.25 GB
PS C:\Users\Administrator> Get-Disk
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
------ ------------- ------------- ------------ ----------------- ---------- ----------
0 ATA SAMSUN... **confidential info erased** Healthy Online 894.25 GB GPT
1 ATA SAMSUN... **confidential info erased** Healthy Offline 894.25 GB RAW
2 ATA SAMSUN... **confidential info erased** Healthy Offline 894.25 GB RAW
PS C:\Users\Administrator> Get-PhysicalDisk | Select-Object DeviceID, FriendlyName, MediaType, BusType, Size | Format-Table
DeviceID FriendlyName MediaType BusType Size
-------- ------------ --------- ------- ----
2 ATA SAMSUNG MZ7L3960 SSD RAID 960197124096
0 ATA SAMSUNG MZ7L3960 SSD RAID 960197124096
1 ATA SAMSUNG MZ7L3960 SSD RAID 960197124096
Server 3 (Cluster Node 2):
- Windows Server 2022 Datacenter
- Disks :
PS C:\Users\Administrator> Get-PhysicalDisk
Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size
------ ------------ ------------ --------- ------- ----------------- ------------ ----- ----
1 ATA SAMSUNG MZ7L3960 **confidential info erased** SSD True OK Healthy Auto-Select 894.25 GB
0 ATA SAMSUNG MZ7L3960 **confidential info erased** SSD False OK Healthy Auto-Select 894.25 GB
2 ATA SAMSUNG MZ7L3960 **confidential info erased** SSD True OK Healthy Auto-Select 894.25 GB
PS C:\Users\Administrator> Get-Disk Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition Style ------ ------------- ------------- ------------ ----------------- ---------- ---------- 0 ATA SAMSUN... S6EKNC0X400942 Healthy Online 894.25 GB GPT 1 ATA SAMSUN... S6EKNC0X400944 Healthy Offline 894.25 GB RAW 2 ATA SAMSUN... **confidential info erased** Healthy Offline 894.25 GB RAW PS C:\Users\Administrator> Get-PhysicalDisk | Select-Object DeviceID, FriendlyName, MediaType, BusType, Size | Format-Table DeviceID FriendlyName MediaType BusType Size -------- ------------ --------- ------- ---- 1 ATA SAMSUNG MZ7L3960 SSD RAID 960197124096
0 ATA SAMSUNG MZ7L3960 SSD RAID 960197124096
2 ATA SAMSUNG MZ7L3960 SSD RAID 960197124096
MegaRAID Controller:
- RAID controller has been set up in JBOD mode.
PS C:\Users\Administrator> .\storcli64.exe /cAll show
Generating detailed summary of the adapter, it may take a while to complete.
CLI Version = 007.2309.0000.0000 Sep 16, 2022
Operating system = Windows Server 2022
Controller = 0
Status = Success
Description = None
Product Name = SAS 3916
Serial Number = **confidential info erased**
SAS Address = 5003048023cb9203
PCI Address = 00:6f:00:00
System Time = 12/26/2024 17:22:21
Mfg. Date = 09/11/24
Controller Time = 12/26/2024 17:22:20
FW Package Build = 52.28.0-5455
BIOS Version = 7.28.00.0_0x071C0000
FW Version = 5.280.02-4008
Driver Name = megasas35.sys
Driver Version = 7.716.02.00
Current Personality = JBOD-Mode
Host Interface = PCI-E
Device Interface = SAS-12G
Bus Number = 111
Device Number = 0
Function Number = 0
Domain ID = 0
Security Protocol = None
JBOD Drives = 3
JBOD LIST :
=========
------------------------------------------------------------------------------------------
ID EID:Slt DID State Intf Med Size SeSz Model Vendor Port
------------------------------------------------------------------------------------------
0 252:0 0 Onln SATA SSD 894.252 GB 512B SAMSUNG MZ7L3960HBLT-00A07 ATA C0.0 x1
1 252:1 1 Onln SATA SSD 894.252 GB 512B SAMSUNG MZ7L3960HBLT-00A07 ATA C0.0 x1
2 252:2 2 Onln SATA SSD 894.252 GB 512B SAMSUNG MZ7L3960HBLT-00A07 ATA C0.0 x1
------------------------------------------------------------------------------------------
ID=JBOD Target ID|EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|Onln=Online
Offln=Offline|Intf=Interface|Med=Media Type|SeSz=Sector Size
SED=Self Encryptive Drive|PI=Protection Info|Sp=Spun|U=Up|D=Down
Physical Drives = 3
PD LIST :
=======
----------------------------------------------------------------------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type
----------------------------------------------------------------------------------------
252:0 0 Onln - 894.252 GB SATA SSD Y N 512B SAMSUNG MZ7L3960HBLT-00A07 U JBOD
252:1 1 Onln - 894.252 GB SATA SSD Y N 512B SAMSUNG MZ7L3960HBLT-00A07 U JBOD
252:2 2 Onln - 894.252 GB SATA SSD Y N 512B SAMSUNG MZ7L3960HBLT-00A07 U JBOD
----------------------------------------------------------------------------------------
EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|DG=DriveGroup
DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare
UBad=Unconfigured Bad|Sntze=Sanitize|Onln=Online|Offln=Offline|Intf=Interface
Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info
SeSz=Sector Size|Sp=Spun|U=Up|D=Down|T=Transition|F=Foreign
UGUnsp=UGood Unsupported|UGShld=UGood shielded|HSPShld=Hotspare shielded
CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded
UBUnsp=UBad Unsupported|Rbld=Rebuild
Steps Taken:
- Installed the required features on nodes from the cluster manager server.
Invoke-Command -ComputerName win-6pn5tsncl07.test_ad.local,win-slefc1bh2f8.test_ad.local {
Install-WindowsFeature FS-FileServer,Failover-Clustering,Hyper-V -IncludeAllSubFeature -IncludeManagementTools
}
- Manually restarted both cluster nodes.
- Create the cluster:
New-Cluster -Name Test-Cluster -Node win-6pn5tsncl07.test_ad.local,win-slefc1bh2f8.test_ad.local -StaticAddress 192.168.10.10 -NoStorage
Ran cluster validation
Cluster Validation Report:
Failed to list all disks for Storage Spaces Direct:
Error Summary:
No eligible disks were found on which to perform cluster validation tests.
Eligible disks must comply with the following:
- Default supported bus types are "SAS", "SATA" and "NVMe"
- Disks with a SAS or NVMe bus types must support page 83
- Disks with a SATA bus types must support page 80
- A disk with no partition table (RAW) or a partition table with a GPT or an MBR format is supported
- Disks with a GPT partition table must not contain any system or basic data partitions
- Disks with an MBR partition table may only contain unused, logical disk manager (LDM), or Microsoft Storage Spaces partitions
Disk won't be eligible either if any of the following is true:
- Disk is a boot volume
- Disk is a system volume
- Disk is used for paging files
- Disk is a hibernate disk
- Disk is used for memory dump files
- Disk is removable
- The port driver used by the disk does not support clustering
- Disk type is dynamic
- Disk is in use by another application
- Disk is a redundant multipath I/O (MPIO) disk
- Disk is a snapshot disk
- Disk belongs to a non primordial storage pool
- Disk is failing IO. Control code failures
- Disk is unreadable
Disk0: Disk is a boot volume. Disk is a system volume. Disk is used for paging files. Disk bus type does not support clustering. Disk partition style is GPT. Disk has a System Partition. Cannot cluster a disk with a System Partition. Disk has a Microsoft Reserved Partition. Disk has a Basic Data Partition. Cannot cluster a disk with a Basic Data Partition.. Disk has a Microsoft Recovery Partition. Disk type DYNAMIC. Disk does not have non-volatile
Disk1: Disk bus type does not support clustering. No disk partition style defined. Disk is RAW. Disk type is BASIC. Disk does not have non-volatile cache.
Disk2: Disk bus type does not support clustering. No disk partition style defined. Disk is RAW. Disk type is BASIC. Disk does not have non-volatile cache.
[Moderator edit: Erased the confidential info.]
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2024 06:17 AM
тАО12-28-2024 06:17 AM
Re: Storage Spaces Direct (s2d) wrong BusType with raid controller in HBA mode
Hi @samadhan ,
Will this video and this document help you if you missing the steps somewhere.
Regards,
Shiva_jr
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2025 09:08 PM
тАО01-02-2025 09:08 PM
Query: Storage Spaces Direct (s2d) wrong BusType with raid controller in HBA mode
Hello,
Let us know if you were able to resolve the issue.
If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2025 12:29 AM - edited тАО01-09-2025 12:30 AM
тАО01-09-2025 12:29 AM - edited тАО01-09-2025 12:30 AM
SolutionHi @shiva_jr
Cc : @support_s
Thank you for your response.
I also reached out to the Microsoft community regarding this matter. I learned that there is a workaround to enable Storage Spaces Direct (S2D) on top of RAID BusType. However, please note that this approach is not supported for production environments.
Available Options
Approach 1: Forcing S2D to Accept RAID BusType
If you want to keep the OS as is, you can use the S2D hack to force it to accept the RAID BusType, but that is unsupported for production.
To force S2D accepting RAID BusType, you need to run the following command on each cluster node:
(Get-Cluster).S2DBusTypes=256
To force S2D accepting any BusType, run the following command on each cluster node:
(Get-Cluster).S2DBusTypes=4294967295
Approach 2: Adding a Registry Key
Add a registry key that enables support for shared storage using Direct Attached clustered RAID controllers.
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
To add the key to the registry, follow these steps:
- Open Registry editor (regedit.exe).
- Locate and then select the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Parameters
- Right-click Parameters and then select New.
- Select DWORD and give it a name of AllowBusTypeRAID.
- Once the key is created, give it a value of 0x01.
- Click OK.
- Exit the Registry editor.
- Restart the computer.
Approach 3: Firmware or Controller Update
Update Controller Firmware:
Flash or update the RAID controller firmware. This often resolves compatibility issues.Reference: Resolving Enable-ClusterS2D Bus Type Support Issue.
Use S2D-Compatible Storage Controllers:
Consider replacing the RAID controller with an S2D-compatible Host Bus Adapter (HBA).Reference: Storage Spaces Frequently Asked Questions (FAQ).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2025 09:41 PM - edited тАО01-09-2025 09:41 PM
тАО01-09-2025 09:41 PM - edited тАО01-09-2025 09:41 PM
Re: Storage Spaces Direct (s2d) wrong BusType with raid controller in HBA mode
Hi @samadhan,
That's perfect!
We are glad to hear you found the workaround and we appreciate you for keeping us updated.
Thanks,
Sunitha G
I'm an HPE employee.
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
