PowerFlex: SDC can’t access it is assigned volumes

PowerFlex SDC driver running on a Windows 2012 R2 VM that was hosted on PowerFlex  storage was loading slowly, finally hanging and not accessing the volumes mapped to it.

Symptoms 
Running the ping command would not successfully complete from the Windows SDC to one of the SDS nodes. 
The system event log in to the Windows server was displaying disk issues such as the following.

03/15/2017 09:33:53 AM Error PDC04OPFTPGL01.h 154 disk The IO operation at logical block address 0x5a1278 for Disk 1 (PDO name: \Device\0000003c) 
failed due to a hardware error. 03/15/2017 09:33:13 AM Error PDC04OPFTPGL01.h 154 disk The IO operation at logical block address 0x5a1270 for Disk 1 (PDO name: \Device\0000003c) 
failed due to a hardware error. 03/15/2017 09:32:33 AM Error PDC04OPFTPGL01.h 154 disk The IO operation at logical block address 0x5a1268 for Disk 1 (PDO name: \Device\0000003c) 
failed due to a hardware error.

03/15/2017 12:47:28 AM Warning PDC04OPFTPGL01.h 140 Microsoft-Windows-Ntfs The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: . (The request failed due to a fatal device hardware error.) 03/15/2017 12:48:50 AM Error PDC04OPFTPGL01.h 55 Ntfs A corruption was discovered in the file system structure on volume D:. The exact nature of the corruption is unknown. The file system structures need to be scanned online.

Impact
The host became slow and unresponsive. Access to the SDC's assigned volumes was lost.

Changes were made in the firewall rules in the environment. One SDS node was not in the firewall ruleset causing the SDC to lose access to assigned volumes.

The fastest way to regain volume access is by putting the firewalled SDSs into maintenance mode. This only applies if only one fault set was affected (normal maintenance mode rules apply)

Make corrections to the firewall rules, adding the PowerFlex SDS node back into the rules. Ensure that port 7072 is open and not in use by any other application.

Test with ping/telnet to confirm the firewall rule has applied, and it s safe to take the SDS out of maintenance mode.

Impacted versions

All SIO versions

Fixed in version

N/A Not a ScaleIO issue