Storage Spaces
13 TopicsServer 2022 Storage Bus Cache with Storage Spaces can't identify cache devices
I have a brand new, fresh out of box server with a clean install of Server 2002 Standard. The server has 25 SATA spinning disks presented to the OS in JBOD fashion, and 4 6TB NVME drvies, again presented in JBOD. Following the guide (https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-storage-bus-cache) I've also ensured that cluster services is enabled. Running Get-PhysicalDisk shows the drives as they should, and correctly displays the media type of SSD and HDD, as well as showing that they can pool. Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthSta tus ------ ------------ ------------ --------- ------- ----------------- --------- 9 ATA ST24000NM002H-3K ZYD04JDL HDD True OK Healthy 26 Micron_7450_MTFDKCC6T4TFS 0000_0000_0000_0001_00A0_7523_4454_326C. SSD True OK Healthy 1 ATA ST24000NM002H-3K ZYD04DHG HDD True OK Healthy 0 ATA ST24000NM002H-3K ZYD05GQ3 HDD True OK Healthy 24 ATA ST24000NM002H-3K ZYD052MB HDD True OK Healthy 27 Micron_7450_MTFDKCC6T4TFS 0000_0000_0000_0001_00A0_7523_4454_46BD. SSD True OK Healthy 8 ATA ST24000NM002H-3K ZYD051JQ HDD True OK Healthy 12 ATA ST24000NM002H-3K ZYD01HX2 HDD True OK Healthy 22 ATA ST24000NM002H-3K ZYD050BB HDD True OK Healthy 7 ATA ST24000NM002H-3K ZYD050MB HDD True OK Healthy 29 Intel Raid 1 Volume Volume0 SSD False OK Healthy 15 ATA ST24000NM002H-3K ZYD04KEK HDD True OK Healthy 10 ATA ST24000NM002H-3K ZYD05GLS HDD True OK Healthy 13 ATA ST24000NM002H-3K ZYD041DX HDD True OK Healthy 11 ATA ST24000NM002H-3K ZYD04D3Y HDD True OK Healthy 16 ATA ST24000NM002H-3K ZYD04D3E HDD True OK Healthy 18 ATA ST24000NM002H-3K ZYD05MF2 HDD True OK Healthy 2 ATA ST24000NM002H-3K ZYD06L7S HDD True OK Healthy 4 ATA ST24000NM002H-3K ZYD05J2H HDD True OK Healthy 28 Micron_7450_MTFDKCC6T4TFS 0000_0000_0000_0001_00A0_7523_4454_46AF. SSD True OK Healthy 21 ATA ST24000NM002H-3K ZYD051M5 HDD True OK Healthy 3 ATA ST24000NM002H-3K ZYD05GWH HDD True OK Healthy 17 ATA ST24000NM002H-3K ZYD052L9 HDD True OK Healthy 6 ATA ST24000NM002H-3K ZYD04JTH HDD True OK Healthy 19 ATA ST24000NM002H-3K ZYD059Y7 HDD True OK Healthy 20 ATA ST24000NM002H-3K ZYD051RA HDD True OK Healthy 23 ATA ST24000NM002H-3K ZYD050ZP HDD True OK Healthy 14 ATA ST24000NM002H-3K ZYD05JF9 HDD True OK Healthy 25 Micron_7450_MTFDKCC6T4TFS 0000_0000_0000_0001_00A0_7523_4454_45C1. SSD True OK Healthy 5 ATA ST24000NM002H-3K ZYD05JA7 HDD True OK Healthy However running Enable-StorageBusCache just yields the "Storage Bus does not have identifiable cache devices" Update-StorageBusCache : Storage Bus does not have identifiable cache devices At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:1074 char:13 + Update-StorageBusCache + ~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [Update-StorageBusCache], RuntimeException + FullyQualifiedErrorId : NotFound,Update-StorageBusCache There aren't many resources on the web about this, and there's nothing in event viewer that indicates any kind of error or anything else beyond generic drive messages. The only post I could find was one where another person seemed to run into this and ran DISKPART, and CLEAN on each disk. I've done this, but no success or change whatsoever. I've also confirmed that despite the error message, it isn't a false positive and no pool is created. The only pool that exists is the primordial one. There doesn't seem to be any way to force selection either, and it's unclear why Windows is ignoring what's reported in DiskPart. Does anyone have any advice here?399Views0likes0CommentsCan't enable StorageBusCache on Server 2022 | New-StorageBusCacheStore produces "Generic Failure"
Trying to create a tiered storage space on Server 2022 Datacenter - 4x HDDs, 2x SDDs. The following command shows all the correct drives as CanPool, True: PS C:\Users\Administrator> Get-PhysicalDisk Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size ------ ------------ ------------ --------- ------- ----------------- ------------ ----- ---- 6 Samsung SSD 980 PRO 1TB 0025_38BA_1150_2DE1. SSD False OK Healthy Auto-Select ...B 1 WDC WD40EFZX-68AWUN0 WD-WXB2DA1PYZJA HDD True OK Healthy Auto-Select ...B 4 WDC WDS250G2B0A-00SM50 1820A5802535 SSD True OK Healthy Auto-Select ...B 0 WDC WD40EFZX-68AWUN0 WD-WX52D71DH899 HDD True OK Healthy Auto-Select ...B 3 WDC WD40EFZX-68AWUN0 WD-WXB2DA1PYU0Z HDD True OK Healthy Auto-Select ...B 5 WDC WDS250G2B0A-00SM50 1820A5805134 SSD True OK Healthy Auto-Select ...B 7 Samsung SSD 960 EVO 500GB 0025_3858_71B1_204B. SSD False OK Healthy Auto-Select ...B 2 WDC WD40EFZX-68AWUN0 WD-WX52D710HSJK HDD True OK Healthy Auto-Select ...B But when I take the next step of Enable-StorageBusCache, the script invokes the New-StorageBusCacheStore cmdlet producing an exception when calling "CreateSsdCacheStore" leading to generic failure. I assume that this failure leads to the proceeding failures on down the line. ' New-StorageBusCacheStore : Exception calling "CreateSsdCacheStore" : "Generic failure " At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2409 char:13 + New-StorageBusCacheStore -Guid $cacheDevice.DeviceGuid + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-StorageBusCacheStore], MethodInvocationException + FullyQualifiedErrorId : WMIMethodException,New-StorageBusCacheStore New-StorageBusBinding : No cache store found on cache device At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17 + ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [New-StorageBusBinding], RuntimeException + FullyQualifiedErrorId : NotFound,New-StorageBusBinding New-StorageBusCacheStore : Exception calling "CreateSsdCacheStore" : "Generic failure " At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2409 char:13 + New-StorageBusCacheStore -Guid $cacheDevice.DeviceGuid + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-StorageBusCacheStore], MethodInvocationException + FullyQualifiedErrorId : WMIMethodException,New-StorageBusCacheStore New-StorageBusBinding : No cache store found on cache device At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17 + ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [New-StorageBusBinding], RuntimeException + FullyQualifiedErrorId : NotFound,New-StorageBusBinding New-StorageBusCacheStore : Exception calling "CreateSsdCacheStore" : "Generic failure " At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2409 char:13 + New-StorageBusCacheStore -Guid $cacheDevice.DeviceGuid + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-StorageBusCacheStore], MethodInvocationException + FullyQualifiedErrorId : WMIMethodException,New-StorageBusCacheStore New-StorageBusBinding : No cache store found on cache device At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17 + ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [New-StorageBusBinding], RuntimeException + FullyQualifiedErrorId : NotFound,New-StorageBusBinding New-StorageBusCacheStore : Exception calling "CreateSsdCacheStore" : "Generic failure " At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2409 char:13 + New-StorageBusCacheStore -Guid $cacheDevice.DeviceGuid + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-StorageBusCacheStore], MethodInvocationException + FullyQualifiedErrorId : WMIMethodException,New-StorageBusCacheStore New-StorageBusBinding : No cache store found on cache device At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17 + ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [New-StorageBusBinding], RuntimeException + FullyQualifiedErrorId : NotFound,New-StorageBusBinding New-StorageBusCacheStore : Exception calling "CreateSsdCacheStore" : "Generic failure " At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2409 char:13 + New-StorageBusCacheStore -Guid $cacheDevice.DeviceGuid + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-StorageBusCacheStore], MethodInvocationException + FullyQualifiedErrorId : WMIMethodException,New-StorageBusCacheStore New-StorageBusBinding : No cache store found on cache device At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17 + ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [New-StorageBusBinding], RuntimeException + FullyQualifiedErrorId : NotFound,New-StorageBusBinding New-StorageBusCacheStore : Exception calling "CreateSsdCacheStore" : "Generic failure " At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2409 char:13 + New-StorageBusCacheStore -Guid $cacheDevice.DeviceGuid + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-StorageBusCacheStore], MethodInvocationException + FullyQualifiedErrorId : WMIMethodException,New-StorageBusCacheStore New-StorageBusBinding : No cache store found on cache device At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17 + ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [New-StorageBusBinding], RuntimeException + FullyQualifiedErrorId : NotFound,New-StorageBusBinding Update-StorageBusCache : Storage Bus has unbound capacity devices, autoconfiguration of pool not possible At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:1074 char:13 + Update-StorageBusCache + ~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Update-StorageBusCache], RuntimeException + FullyQualifiedErrorId : InvalidOperation,Update-StorageBusCache ' This sucks and I have no idea what to do about it. I checked out the MSscript quote in the error codes, but it's well above my pay grade. Anyone know what this is all about? EDIT: Sorry the formatting above is a mess. I don't know why it's not interpreting line breaks properly. 😕2.3KViews0likes0CommentsSemaphore timeout when running a backup where source and destination is on the same Storage Space
Dear Server / Storage Team, I am running a lab with Windows Server 2022 LTSC preview to get familiar with the new or changed features but also to help you hunting issues. For a very long time now I faced issues with "semaphore timeouts" reported by the Macrium backup solution and Ned Pyle and Vlad helped me to narrow down that the issue is not a SMB issue but infact a problem with the storage subsystem. Here Storage Spaces consisting of two WD Red Plus 6 TB. mirrored, ReFS 3.6. In previous releases of Windows Server the issue also affected the scenario when clients tried to backup to a SMB share causing the same issue. This improved over releases Now only one issue remains. Here is the Feedback hub item. https://aka.ms/AAbm84d Scenario: Hyper-V Host Hosting various VMs one VM data disk (VHDX) is located on a Storage Spaces Pooling using Dedup (dedup will run outside backup times) When the backup application runs it will write the data from this vhdx via Block Level (tested with or without CBT) to a file share (driveletter A) The timeout will occour reproducibly and so preventing a backup. If I try the same and do not use the SMB Share located on a volume on the Storage Spaces Pool the backup is fine. Source: VM > Data disk (driveletter N) located on Storage Pool 1 volume (driveletter H) Target: SMB Share (driveletter A) located on Storage Pool 1 Error: semaphore timeout more details in the feedback hub from our investigation unaffected builds Windows Server 2019 LTSC 1809 17763.x Windows Server vNext LTSC b20215 affected builds: all other Windows Server vNext / 2022 LTSC the issue happen when the backup data amount is large (20-40 GB will work fine)Solved3KViews0likes5CommentsUpdating Firmware for Disk Drives in Windows Server 2016 (TP4)
First published on TECHNET on Jan 25, 2016 Updating the firmware for disks has historically been a cumbersome task with a potential for downtime, which is why we're making improvements to Storage Spaces and Windows Server 2016 to enable you to more easily update disk firmware prior to placing a server in production.3.2KViews0likes0CommentsDesigning Software-Defined Storage with Windows Server – we’ve got a calculator and a doc for that
First published on TECHNET on Jul 13, 2015 Feast your eyeballs on our new Software-Defined Storage Design Calculator and Design Considerations Guide! Be amazed at how designing a storage solution with Windows Server, Storage Spaces, and SOFS (Scale-Out File Server) can be simultaneously simplified with a colorful spreadsheet and concurrently complexified with a detailed guide to everything you wanted to know about Storage Spaces design, but weren’t afraid to ask (we’ve been getting a lot of questions…).1.9KViews0likes0Comments