DCA V2/V3:  How to handle Dial Home code 12.10005 vdisk in Write Through;  Check health of BBUs

           

   Article Number:     501429                                   Article Version: 2     Article Type:    How To 
   

 


Product:

 

Data Computing Appliance V2,Data Computing Appliance V3

 

Instructions:

 

 

Dial Home Example:   

SymptomCode: 12.10005 Category: Status Severity: Warning Status: Unknown Component: sdw74 : sdw74 ComponentID: DCA2-SSM FirstTime: 06/23/2017 00:32:05 Description: Virtual Disk 3 Write Policy: WriteThrough Count: 1    
   
   
    Virtual Disk in WriteThrough can be indicative of a failed drive or a bad BBU.   
   
    Verify Physical Disks status:   
   
    CmdTool264 -Pdlist -aall | egrep -i 'Slot Number|Raw Size|Media Error Count|Other Error Count|Predictive Failure Count|Firmware State' | paste -d'|' - - - - - -   
        
[root@Segment4 ~]# CmdTool2 -Pdlist -a0 | egrep -i 'Slot Number|Raw Size|Media Error Count|Other Error Count|Predictive Failure Count|Firmware State' | paste -d'|' - - - - - -Slot Number: 0|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 1|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 2|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 3|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 4|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 5|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 6|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 7|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 8|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 9|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 10|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 11|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Hotspare, Spun UpSlot Number: 12|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 13|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 14|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 15|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 16|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 17|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 18|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 19|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 20|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 21|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 22|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Online, Spun UpSlot Number: 23|Media Error Count: 0|Other Error Count: 0|Predictive Failure Count: 0|Raw Size: 1.636 TB [0x1a32dd36 Sectors]|Firmware state: Hotspare, Spun Up    
   
    Even if there is a bad drive verify that the BBUs are healthy as well.   
   
    Verify BBU Health   
   
    Attached to this Knowledge Article is a Script that can be run to check the health of the BBUs or Supercaps.  download the script and upload via SCP or WinSCP to the DCA.   
         
  1.         Verify that the file is executableby root if not chmod 700 the file     
  2.    
   
[root@mdw tmp]# chmod 700 Supercap.sh-rwx------ 1 root root     10107 Mar 29 14:21 Supercap.sh    
   
         
  1.         scp the Supercap.sh from the mdw to the server in question.     
  2.    
   
[root@mdw tmp]# scp Supercap.sh root@sdw4:/tmp/Supercap.shSupercap.sh                                                                         100%   10KB   9.9KB/s   00:00    
   
         
  1.         Run the script        
  2.    
   
[root@Segment4 tmp]# ./Supercap.sh    
Example of Failed BBU:   
[root@sdw2 ~]# /tmp/Supercap.shsdw2.gphd.local - 06-23-2017 16:58:22 - Supercap script executedsdw2.gphd.local - 06-23-2017 16:58:32 - Learn Command not successful on Controller 0sdw2.gphd.local - 06-23-2017 17:14:51 - Supercap learn cycle timeout    
NOTE: If the script times out after a failed Controller 0 cancel the script via 'Ctrl + C' and dispatch for replacement   
   
    Example of Passed BBU:   
[root@Segment4 tmp]# ./Supercap.shSegment4.test - 06-23-2017 15:37:31 - Supercap script executedSegment4.test - 06-23-2017 15:40:44 - PASSED