Appliance Patch Release Notes v2.1.1 (

Last modified


Last modified - 09/20/2016

Release notes in pdf format - Pdf attachment

This document provides release notes that identify open issues with software version v2.1.1 ( installed on your appliance. This release includes a new release for SSDPC. Please download and use the SSDPC v2.1.1.548 to work with this release. To upgrade your software, follow the instructions detailed in Software Patch Upgrade Guide v2.1.1.548.

The document is broken down into following sections:


What's New in v2.1.1 (

The following enhancements were introduced in this StorSimple release:

  • Automated space reclamation optimization – When data is deleted on thinly provisioned volumes, the unused storage blocks need to be reclaimed. This release has improved the space reclamation process from the cloud resulting in the unused space becoming available faster as compared to the previous versions. 
  • Improvements and bug fixes have been made to the driver software.                                                  


Issues Resolved in v2.1.1 (

The following issues have been addressed in this software version (


ID Summary
3421179 In the previous releases, snapshots would fail on a heavily loaded appliance (when CPU utilization exceeded 90%). This issue is fixed in this release.  
6740664 In an earlier release, during the software upgrade, the active controller  would crash. This issue has been root-caused and resolved in this release.

In the last release, due to a bug, the automated space reclamation cycle states were incorrectly set for newly created cloud configurations. This would raise a "Backup registry incomplete" critical alert in the web UI. Since the state was incorrectly set, the space reclamation cycle would never run for the new cloud configuration. This issue is fixed in this release.


A bug in the earlier release would cause backups and restores to fail when trying to read from a Logical Disk Manager (LDM) database. The user would receive errors such as "Unexpected VBLK type" or "at EOB. (ArgumentException)". This issue is fixed in this release.

4936854, MSCSA-418 Due to a bug in the earlier release, the EBOD array resync would fail at 99.9%. with the error "Access beyond end of device." This issue is resolved via a RAID-10 driver fix in this release. 
MSCSA-376 Improvements have been made to the disk driver software in this release.
8465293 In the previous versions of software, owing to a bug, the user would encounter repeated crashes when attempting a failover during disaster recovery. This bug has been resolved in this release.


Known Limitations for v2.1.1 (

There are no new limitations noted for StorSimple software version 2.1.1 ( 




Comments and/or Workarounds


Using quick format to re-format a large volume on Windows Server 2012 may take a long time.

On Windows Server 2012, the thin-provisioning feature is enabled when you use a StorSimple iSCSI volume. It is recommended that you delete a thin-provisioned volume and create a new volume instead of reformatting. If you still prefer to reformat a volume, run the following command prior to the reformat to avoid space reclamation delays:
fsutil behavior set disabledeletenotify 1

When the formatting is complete, run the following command to re-enable space reclamation:
fsutil behavior set disabledeletenotify 0


If the internal platform firmware engine is rebooted, the system software may sporadically lose access to vital information about the health of each hardware component.

In such a scenario, the hardware page would not be able to correctly display the status of all the hardware elements. To avoid this issue, please force a reboot of the active controller which will automatically trigger a failover in the system.

CSC-4255, CSC-4231

UI errors with Internet Explorer versions older than 8.

Internet Explorer version 8, 9, or 10 are supported with the StorSimple web UI. Please make sure to install the latest update available for the version of choice.


A Google cloud account restore during configuration import may lead to "Forbidden Access" to the cloud.

This is a known Google limitation on the number of different devices that can use the same Google credentials and authentication tokens. If possible, avoid performing multiple imports of the same Google account. You can also contact StorSimple support for alternative solutions to address this known limitation.


SCSI ABORT may occur with Round Robin multipath policy set on Centos host. iSCSI sessions might get disconnected/connected resulting in high host I/O latencies.

There is no known workaround for this issue at this time.


When the fingerprint type is altered for a custom type volume, the write and read performance can be impacted.

The performance can be reduced because the data may need to be de-duplicated again based on the different type; such operation requires additional CPU cycles as well as extra reads and writes from storage. After the entire volume content is fully rewritten, the write and read throughput will stabilize to the optimal value again.


Printing reports in portrait orientation may overflow and not print correctly.

Printing of reports is supported in only Landscape orientation.


When the appliance is powered off and quickly powered on, some drives show up as missing. 

This issue has been observed very sporadically when forcing a quick power off/on through a managed APC that would cut the power to the appliance for less than 1 second.
As a work-around, please ensure that the power is supplied again a few seconds after the power off (what is usually called a "delayed power on" in a managed APC).


In rare instances, on resetting the active controller, the Host I/Os may be aborted.

In some high load scenarios, host I/Os are aborted because the appliance takes more than 20 seconds before completing the operation. The issue subsides after the load is reduced.
As a workaround, we recommend a reduction in host load and/or a failover of the controller.

CSC- 3217, CSC-2335

Printer-friendly version of reports does not work in IE9 and Firefox.

Use the browser print option for printing out reports.


A canceled Cloud Clone or Cloud Snapshot restore/clone job may resume after a controller failover.

If the user cancels the restore/clone job, and then triggers a controller failover or the system fails over automatically for some other reason, then a canceled job will resume unless the cancel action has been completely processed by the system.
To work around this issue, the user needs to cancel the job again and ensure that no more failovers are triggered until the cancel action has been fully processed by the system.


A different state may be displayed on the serial console when the system is in recovery mode.

Only one controller may display the management console screen, with the state shown as "OFFLINE".


If one of the Web UI charts is kept open in Auto-refresh mode, the refresh may stop after some time.

Typically, this issue can be overcome by opening a new browser session and selecting the same chart display page again with Auto-refresh mode.
If the Web application fails to open (that is, the login page does not come up), then the issue can be worked around by forcing an active controller reboot.


Rate limiting enforces the lowest limit value configured across cloud configurations.

When multiple cloud configurations are set up and rate limiting is enabled in more than one, the overall throughput to the cloud will converge over time to the smallest rate limiting value configured (as opposed to the sum of the configured rates).


An existing iSCSI session remains active even after disabling the iSCSI check box in the UI.

The "iSCSI Enabled" setting is effective only after a controller reboot/failover. The existing sessions are not altered; therefore:

  • Existing iSCSI sessions from hosts remain active after the check box is disabled.
  • New iSCSI sessions to a target are successful using the IP address of the interface that is unmarked as "iSCSI Enabled."

To overcome this issue, please reboot the active controller. The automatic failover will ensure that the desired configuration is applied correctly from that point onwards.


Active Directory domain user is able to log on with old password after the password is changed in the domain.

This is due to the old password being cached by the domain controller server that has been configured. This password remains available when authentication occurs. Since the StorSimple application cannot force a flush of the old passwords, please connect to the domain controller server and perform the necessary flush operation.


In the Hardware page, the standby controller appears in a different state when it has been shut down or pulled out.

There are no negative side effects on the system behavior.


Known Issues for v2.1.1 (

The known issues for StorSimple software version 2.1.1 ( are tabulated below. The issues reported in this version of software are marked with an asterisk (*).  The remaining issues have carried over from previous releases. 




Comments and/or Workarounds




An unexpected controller failover occurs due to a bug related to leap second insertion.  
8914498* If  a DR is performed on an appliance using the "Import backups from an existing  appliance" option and the source appliance is then upgraded, the upgrade fails.  
4758049* Following a power loss, the NVRAM state is displayed on the Hardware page as "degraded".   
8354605, CSC-4725*

In rare instances, a controller failover occurs due to a known kernel bug in the current OS version. 

MSCSA-368 After controller replacement, if your standby controller is running a software version lower than, and you attempt an upgrade, the upgrade will fail. Please contact Microsoft Support for assistance in performing the upgrade.
MSCSA-242 In rare instances, CPU temperature sensors may incorrectly show up as 'failed' on StorSimple controllers.  If you encounter this issue, please contact Microsoft Support.
CSC-4672 SSDPC should be installed only in the C: drive of your Windows host. Backups will fail if the installation is in any other drive.  
CSC-4657 There are known issues with pop-ups and the UI not rendering properly.

To work around this problem, perform the following steps:

  1. Clear the entire cache.​
  2. Press Ctrl+F5 to refresh the browser and the UI.
CSC-4650 In some instances, the Web UI hangs due to mono issues.

To work around this problem, perform the following steps:

  1. Use the management serial console to access the appliance.
  2. In the command window, at the prompt type:

web restart

CSC-4649 There is an issue in which the Y-Axis of the Deduplication Report can show Trillions of Bytes instead of Gigabytes.  
CSC-4636 A temporary warning alert is seen immediately after upgrading to this patch release: "Backup Registry Incomplete - Rebuilding catalog. If you recently upgraded, this should automatically resolve. If this alert persists for more than 24 hours or you did not recently upgrade, please contact Microsoft Support."

This is a transient alert that requires no user intervention. The alert automatically clears in less than 24 hours after the catalog is completely rebuilt. 

If you have not upgraded the software and see this alert, or if the alert persists for longer than 24 hours, please contact Microsoft Support. 

CSC-4631 The maximum volume size in this release has been limited to 64 TB. After you have upgraded to this version of software, volumes larger than 64 TB will fail the volume size check.  Create new volumes to migrate data from volumes larger than 64 TB.
CSC-4609 If the original appliance is alive and clones need to be accessed on the secondary appliance, please do NOT delete cloud snapshots on the original appliance.  
CSC-4607 If the SSDPC installation package is copied in a folder with a Chinese name, SSDPC cannot be extracted from this folder.  Ensure that the SSDPC installation package is always copied into a folder with an English name and then extracted.
CSC-4529 In some instances, you may see an error on Cloud credential verification that states: "Could not synchronize the device time. Please verify that your NTP servers are properly configured, the servers are online and reachable, and that the network between your device and your NTP servers is operating correctly."​ In most cases, retrying the operation or simply refreshing the browser solves this issue.
CSC-4248 After a DR from appliance A to appliance B, backups that are deleted on appliance A will continue to be visible on appliance B. Attempts to clone or restore the deleted backups will fail.  This is a known issue and the workaround is to manually delete the corresponding backup(s) on appliance B.
CSC-4413 With recent Chrome version 31.0.1650.57, the Web UI page for QoS template may have issues displaying the pop-up for creating the template. The issue is related to cached data and can be resolved by using Ctrl+F5 to perform a complete page refresh.


"Use SSL" checkbox in the cloud credentials dialog is unchecked by default for all cloud service providers, resulting in cloud communications over HTTP if the user doesn't check it before saving the configuration. This is a change in behavior compared to prior versions. 

We recommend that you enable SSL ito ensure validation of cloud service authenticity. A valid SSL server certificate is required to be installed on the cloud service side to establish SSL communication.


A valid backup policy schedule cannot be saved in 'Create Scheduled Policy' dialog, following a failed save attempt of an invalid schedule.

Close the 'Create Scheduled Policy' dialog and reopen to create a valid schedule.


The web UI displays an Oops! error when a 31 or 32-character long encryption key is entered in the corresponding field in Cloud Configuration.

When a 31 or 32-character key is to be configured, either type or copy and paste the key string without pressing the Enter key at the end.


When configuring a monthly backup policy with an invalid day for the selected month, an Oops error is presented.

Select a valid day for the month.


When performing a backup registry restore on other appliance, while original appliance is still active, any backup deleted on the original appliance will continue to appear on the second appliance until it is either manually deleted or expired per configured schedule. An attempt to restore from a backup run that appears in the catalog but has been deleted on the original appliance will result in an error notice and the operation will not proceed.

Manually delete the invalid backup on the second appliance or let it expire if expiration date is configured.

CSC-4159, CSC-4154

The Web UI may briefly display an Object Reference Error or a Server Error.

In rare circumstances, the Web UI becomes inaccessible and displays the error mentioned. The Web UI only remains in this state for a brief period of time and it will become accessible again after a refresh of the page.


Migration Upgrade: Stage 3 of 8: 'Converting data to new format' shows percentage complete above 100%.

This can happen if new volumes are created during stage 3 of the upgrade. This is not a severe issue and no user action is required. The upgrade will progress once the new volumes have been properly handled.


Logon to the UI home page may get stuck indefinitely following a failover.

This can happen if a failover occurs in an appliance with no gateway configured for cloud access.
A possible workaround, if acceptable in the customer network topology, is to configure the gateway for the MGMT interface using the console connection. When the UI is accessible again, please reconfigure the network interface settings with the appropriate gateway details.


The Web UI is not reachable after 2.0.1 to 2.1.1 upgrade.

Please contact Customer Support. The workaround is to restart the management service from serial console access.


The Web UI should not allow preferred LUN settings greater than 255 for a volume.

Avoid setting preferred LUN of a volume to a value greater than 255. Preferred LUN of a volume should be within 0-255 range.


The Web UI may not be accessible for few minutes during the upgrade from 2.0.3 to 2.1.1.

During the upgrade from version 2.0.3 to version 2.1.1, the Web UI may display the error message "Operation completed with status = CSA_STATUS_SERVER_API_DISABLED" for a few minutes during a specific phase of the upgrade. Please try to access the UI after a couple of minutes and the monitoring of the upgrade progress should be available again.


When a volume is deleted without removing it from a volume group, further backups on the VG for remaining volumes will fail with "One or more of the source volumes unavailable (Backupexception)".

Edit the volume group and save it again without making any changes. Any further backups will now succeed.


Deletion of a volume during an upgrade can cause the upgrade to fail.

This failure does not affect the Host/Application I/Os. The upgrade operation can be retried but the volume deletion operation should be avoided until the upgrade process is complete.


After a successful pre-validation on the Software Upgrade screen, the Start Upgrade button may not be accessible.

As a workaround, please retry the operation after waiting for an hour. If the issue persists, restart the active controller and then start the upgrade process again.


The 5000-7000 series appliance controller may reboot under heavy load.

Under very rare circumstances, the controller may become very slow or unresponsive. When the system detects such a situation, a reboot of the active controller is automatically triggered and a failover to the standby controller occurs. The system then continues to operate normally without any host disruption. If this doesn't occur, please contact StorSimple support to restore the system to a fully functional state.


Upload of the upgrade package for version 2.0.3 may stop abruptly.

This is generally seen when the upload reaches 35-40  persent, in particular when the system is operating under heavy load. This issue is addressed in build, therefore it is recommended to perform a patch upgrade to build first and then again upgrade to version 2.0.3. 


The cloud properties popup may not close properly when clicking on the X button on the top right hand corner.

As a workaround, please refresh the whole page and reopen the popup again.


Invalid cloud configuration/credential settings may lead to the entire system becoming very slow connecting to the cloud for valid accounts.

Please contact StorSimple support to help resolve the problem and bring the system back to its full functionality. 


Using invalid credentials for Web Proxy settings may result in a controller failover.

If invalid credentials have been entered in the Web Proxy Settings in the Web UI, the active node will reboot and there will be a cluster failover. Ensure that valid credentials are used for the Web Proxy settings.

CSC- 3224

In Firefox 3, while configuring QoS templates, the Save/View Timeline buttons may get disabled.

This issue can be observed only in some specific sequences of operations involving deleting and creating multiple QoS templates. The issue can be overcome by refreshing the browser page and then attempting the configuration of the QoS template again.

CSC- 3222

In RDP sessions Web UI popups cannot be closed by clicking on the x in the top right corner for the first time.

Click the red icon again to close the popup.

CSC- 3211

The Web UI displays the error "Server Error:'~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadScriptManager requires a HttpHandler registration in web.config."

There is a rare known issue in which the Web UI becomes inaccessible and displays the error mentioned. The Web UI only remains in this state for a brief period of time and will become accessible again within one minute. No user intervention is required.


Web UI may render incorrectly on a restarted appliance.

Accessing the Web UI on a new browser window will resolve the issue.


Under rare circumstances a disk failure may cause the system to go offline.

There are some corner case scenarios that may occur with a high stress read workload. When the StorSimple software detects a failure in a drive from which it cannot quickly and easily recover, it intentionally brings down the system to protect the data integrity. If such an event occurs, please contact StorSimple support to address the issue and restore full functionality.

CSC-3042, CSC-3067

The appliance controller reboots when an I/O to the internal disks takes an abnormally long time to complete.

Under extremely rare circumstances, an I/O to a drive (SSD or HDD) may take an abnormally long time. The StorSimple software detects this as an incomplete operation and forces a controller failover to ensure that the system can continue serving I/Os without causing application timeouts.


Rebooting the controller from the shell results in a "500 Internal Server Error" in the Web UI.

This issue is caused by a rare race condition when web requests coincide with the web service starting up. The problem can be worked around by forcing an additional controller reboot.


When a configuration restore/import fails, the same cloud account may be configured multiple times.

Upon configuration restore or import failures, in rare circumstances some portions of the configuration are restored/imported. In case the restore or import operation is repeated again, the same cloud account might be configured multiple times. To work around this issue, please check the configuration after the failure and delete any partially imported information, especially the cloud account portion.


Multiple failovers performed under heavy load may result in loss of iSCSI connection between the host and the appliance.

Under heavy I/O, if there are failovers performed there is possibility of active controller reboot. This may result in loss of iSCSI connection between the initiator and the target. To restore the proper connectivity, reboot the appliance.


Under stress testing of the system failover, the host may lose access to the appliance volumes.

During stress testing of the system failover, inducing continuous failures (artificially), a Windows host may lose access to the volumes. To restore the volume access, please force an iSCSI rediscovery of the target or power cycle the host.


Microsoft iSCSI initiator doesn't support LUN ID 255.

Use a LUN ID of 0 to 254.


Contacting Technical Support

Should you encounter any issues with your appliance, please do not hesitate to contact StorSimple Technical Support at:

  • Telephone: 1-800-642-7676
  • Web:
    • In the page presented, click on plus icon to expand the 'Get Technical Support' node. In the expanded pane, click on 'Get Microsoft Technical Support'.




Page statistics
978 view(s) and 29 edit(s)
Social share
Share this page?


This page has no custom tags.
This page has no classifications.