Forum Discussion

Joe_Fortini's avatar
Joe_Fortini
Copper Contributor
Sep 07, 2021

Enable storage bus cache with Storage Spaces on standalone servers generic failure message to create

With the release of server 2022 i have looked forward to implementing storage bus cache.  The KB to do so is rather straight forward https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-storage-bus-cache .  i have prepped a new bare metal server with SSD's and HDD's on SAS and have followed the steps as in the KB.  however it appears that the function Enable-StorageBusCache has a bug or error in it, it appears that the cache drives get configured and space reserved but the part that preps the HDD's to pair with a cache drive fails with a not so useful error message.

 

it appears enable-storagebuscache calls new-storagebusbinding and then the section of preparehddforcache fails.  little to no documentation appears to exist for this so i am not sure where what to do next.  i have tried to take a look at maybe some issues in the MS script however its rather long and complicated, and i did not see any typo's jump out at me.  im assuming i have found some type of bug

 

AndrewHansen Storage Innovations in Windows Server 2022 - Microsoft Tech Community


New-StorageBusBinding : Exception calling "PrepareHddForCache" : "Generic failure "
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\StorageBusCache\StorageBusCache.psm1:2941 char:17
+ ... New-StorageBusBinding -CacheGuid $bindOrder[$nextCache] - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-StorageBusBinding], MethodInvocationException
+ FullyQualifiedErrorId : WMIMethodException,New-StorageBusBinding

4 Replies

  • Spale777's avatar
    Spale777
    Copper Contributor
    So basically you just need to clean all drives that are poolable on your system, do not initialize them just leave them partitionless and it will work.

    Hope this helps
  • Joe_Fortini's avatar
    Joe_Fortini
    Copper Contributor
    I think i figured it out, reset-physicaldisk does not correctly clean the drive. i did a diskpart select disk X and then clean and the enable can now enable. i think the MS script needs to be updated to handle cleaning of disks
    • Joe_Fortini's avatar
      Joe_Fortini
      Copper Contributor
      so i tried to add another drive and it just blew up so tried to remove the bindings disable and start again and now this

      PS C:\Users\Administrator> Enable-StorageBusCache
      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




      this seems way to touchy to be in the prod release of 2022, or im just doing something totally wrong.

      all my drives are cleaned and raw and online, they can be seen in server manager UI all correctly. and get-physicaldisk shows all the correct media types
      • Anonymous's avatar
        Anonymous
        run "Get-StorageBusCache" to check the storage bus cache is enabled,
        and then run "Update-StorageBusCache" to completed storage bus cache deployment,
        finally, you can run "Get-StoragePool Stor*| Get-PhysicalDisk | sort size" to check that all disks are joined to storage bus cache pool.

Resources