Skip to main content
Pure1 Support Portal

Windows Reporting Drives Offline After Reboots

Applies to Platforms 

  • FA-3xx
  • FA-4xx
  • FlashArray//M
  • FlashArray//X

Applies to Operating Systems

  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Storage Server 2012 
  • Windows Storage Server 2016
  • Windows Server, version 1709

Resolved in Purity


After reboot, LUNs previously connected to Windows Servers remain in an OFFLINE (VDS_SP_OFFLINE) state due to the following reason:

"The disk is offline because of policy set by an administrator".

You are able to bring the drive back into service manually by opening Disk Manager and right-clicking the drive and selecting "online". Once the disk is online it is able to service IO as expected and no further issues are noted.


This issue can be seen after a Purity//FA upgrade has been performed on the FlashArray sometime since the last reboot was completed on the Windows Host. 

The reason the disks are in an offline state is that our LUNs are assigned new 'revision numbers' when an upgrade of Purity//FA is performed. The Windows 2008 and Windows 2012 servers then interpret these as "new" disks because of this new revision number and then sets the drives to offline after a host reboot.

The primary reason this happens is a design change within Windows 2008 and forward where the default SAN policy for shared drives is set to the following:


This means if a new shared drive is presented to a Windows Host it will keep the drive offline to ensure that drive should be presented to this host. If that drive is supposed to be presented to the specific host then it can be brought online as needed by the Administrator.


The fastest resolution is to bring the drive back into service manually by opening Disk Management and right-clicking the drive and selecting "online". Once the disk is online it is able to service IO as expected and no further issues are noted. As the Product Revision will no longer change in future versions of Purity//FA.

The first step to resolving this issue long term is changing the SAN Policy to "Online All"  as per our Step 04 -- Disk Policy Configuration (SAN Policy) KB. By setting this policy you ensure that any newly created disks attached to the Windows Server will be in an online state after a Windows Server reboot. Windows Server defaults to OfflineShared which is the correct setting when using Windows Server Failover Clustering. 

This task can be completed by following the Microsoft TechNet Article:

If the SAN Policy was set to 'Offline Shared', and disks were already presented to the Windows host from the FlashArray, then you must edit the existing disks 'Attributes' to ensure they will remain online following a Purity//FA upgrade and Windows host reboot. However, if this volume is used in Windows Server Failover Clustering you must ensure the disks are returned to the correct state following a reboot since setting the SAN Policy will not set the disk to read and write as these disks are on a "shared bus (such as SCSI and iSCSI)" and will be set to read-only as per the TechNet article above.  For assistance with this, please contact Pure Storage Support.