EF & E-Series, SANtricity, and Related Plug-ins

two questions with isp cfgMarkNonOptimalDriveGroupOnline,<SSID> command and other issue.


Dear all,


I have two questions may need your opinion,


1st is with the command of isp cfgMarkNonOptimalDriveGroupOnline,<SSID> in E-series hardware product with the drive offline issue in controller firmware of 6 .

In our internal reference, it is mentioned this command can only be applicable when only one disk is with Failed status, such as below,

I want to know if that is ture or not with the limitation of failed disk.


Ch  Devnum   Phydev    State/Status      Flags  #Pcs  Dg#  T/S
 0  000001  0837bc98  OPTIMAL/OFFLINE  00200000 0001   3   0/1
 0  000007  0836e6e0  OPTIMAL/OFFLINE  00208000 0001   3   0/7
 0  000006  0836ebc8  FAILED/WRT_FAIL  00200000 0001   3   0/6
 0  000004  0836f0b0  OPTIMAL/OFFLINE  00200000 0001   3   0/4
 0  000002  08377eb8  OPTIMAL/OFFLINE  00200000 0001   3   0/2
 0  000005  083783a0  OPTIMAL/OFFLINE  00200000 0001   3   0/5
 0  000003  08375f0c  OPTIMAL/OFFLINE  04200000 0001   3   0/3


2nd question is with one function of SANTRICITY,

when drive wth Incompatitable status, we can using below function to clear the invalid dacstore info, so the disk

can be returned to optimal status.

dstStartStop (devnum,1,0) isp dsmWipe,devnum,1   Unseat the drive wait 30 seconds insert the drive


There is one function called Initialize in the SANTRICITY, I wonder if that option share the same function with upper command,

Just erase the dacstore info on the incomptitable disks and after that,

I can use recover script to recover the data on that disk.


Thank you for your help on the upper two questions.










There are situations (config issues, multi-drive failures, controller reboots, and so on.) that might cause the drives to go to an offline state.
If the volume group is offline due to any of these you can use cfgMarkNonOptimalDriveGroupOnline to get the volume online.


When you initialize a physical disk, all old volume group and volume information is erased and the physical disk is returned to an unassigned state. Returning a physical disk to an unassigned state adds unconfigured capacity to a storage array. You can use this capacity to create additional volume groups and volumes. CAUTION Potential data loss. When you initialize a physical disk all data on the physical disk is lost.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.