Fxed: Unmountable Boot Volume error with Windows Server 2016 and Storagecraft’s SPX

BSOD imageWe’ve been tracking down issues with Windows Server 2016 on a multitude of servers this week where the servers will reboot and come back with Unmountable Boot Volume which is a pretty nasty experience for oncall. So far we’ve mainly seen it on Domain Controllers but also on a Hyper-V server. The solution is typically to do a last known good boot on the machine and then try to work out what has changed on the server and needs redoing. So far we’ve had issues with duplicate servers in Webroot and Automate along with a couple of server functions not working correctly.

Initially we thought it was a problem with Windows Updates, but it seems that the culprit is Storagecraft’s SPX version 6.7.4
The solution is either to downgrade to version 6.5 or get a patch for 6.7.4 that fixes this issue.

Download location for SPX 6.5.2:

For 6.7.4, You will need to get the patched stcvsm.sys  from Storagecraft and then apply these instructions.

Patch is a very manual process. New version of the stcvsm.sys driver is 2.2.73.0.36
1. Install SPX 6.7.2:
2. Do NOT reboot
3. Rename %windir%\system32\drivers\stcvsm.sys to %windir%\system32\drivers\stcvsm-rtm.sys
4. Copy the 2.2.73 driver to %windir%\system32\drivers. Be sure to select the correct ‘bitness’.
5. Reboot

 

It’s been very frustrating to have gone through this issue without any notification of this pretty serious bug from #Storagecraft

7 thoughts on “Fxed: Unmountable Boot Volume error with Windows Server 2016 and Storagecraft’s SPX

  1. Andy – thanks for sharing this information. The StorageCraft technical support team is delighted to assist with this issue. A support request may be submitted via support.storagecraft.com.
    Regards,
    Connie Whiteside
    Sr Director Customer Success
    [email protected]

  2. Thanks for the follow up Connie. My team is in the process of rolling out the patch or downgrading to the previous version which is working for us.

  3. Disregard previous comment. How did you determine that it was StorageCraft SPX causing the issue?

  4. Hi Jorge,
    Thanks for commenting – we fixed it by rolling back to the previous version – it was quicker than applying the patch and I’ve been swamped with other things this week which means I haven’t had a chance to try the manual patch. As you also need to contact Storagecraft for the patch itself, it’s quicker just to roll back (as long as you don’t have an auto upgrade function on your servers.

    As to how we found it – a lot of very painful rollbacks and a process of elimination. Iniitially we thought it was a windows update as it occurred after machines rebooted due to the patches, but after building a new server, applying the various windows patches we were not able to reproduce the issue. As one of the machines we had to rebuild was also going to be in production we installed spx on it and it failed to complete the boot cycle afterwards. We rolled back the image and were able to reproduce the issue, contacted Storagecraft and were told it was a known issue and were provided the patch file to test or to revert back to the previous version.

    I am not providing the actual patch file here as it’s not my property to distribute and Storagecraft need to be aware of how many customers this affected which can only be done by customers contacting support.

  5. Experiencing this now, random issue with a relatively new 2016 server deployment. Storagecraft customer.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.