Sun Storage A1000 Array
 
Sun Storage A3500 SCSI Array
 
Sun Netra st A1000 Array
 
Sun Storage A3500 FC Array
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
 

When trying to remove a hot spare drive of Sun StorEdge[TM] A3x00 or A1000 using /usr/lib/osa/bin/raidutil command with -H option and the hot spare drive is used by an LUN, the command will fail as "Delete hot spare operation failed."

For example:

# drivutil -d c2t5d0

Drives in Group for sonoma_001

 Group          Drive List  [Channel,Id]

Hot Spare      [5,10];
Group  1:      [1,0]; [2,0]; [3,0]; [4,0]; [5,0]; 

   :

1. drivutil -i c2t5d0

Drive Information for sonoma_001

Location  Capacity   Status         Vendor  Product          Firmware     Serial
(MB)                              ID             Version      Number
[1,0]     0          Failed         FUJITSU MAA3182S SUN18G  2107         00G08649
[2,0]     17274      Optimal        FUJITSU MAA3182S SUN18G  2107         00G08364
[3,0]     17274      Optimal        FUJITSU MAA3182S SUN18G  2107         00G08386
[4,0]     17274      Optimal        FUJITSU MAA3182S SUN18G  2107         00G04816
[5,0]     17274      Optimal        FUJITSU MAA3182S SUN18G  2107         00G08258    

  :

[5,10]    17274      Spare[1,0]     FUJITSU MAG3182L SUN18G  0707         00524112      

drivutil succeeded!
# drivutil -l c2t5d0
Logical Unit Information for sonoma_001

 LUN      Group      Device           RAID      Capacity      Status
Name             Level     (MB)

  0       1          c2t5d0            5          34469       Optimal

  :

# raidutil -c c2t5d0 -H 510
LUNs found on c2t5d0.
LUN 0    RAID 5    34469 MB
LUN 2    RAID 5    1024 MB
LUN 4    RAID 1    1024 MB
LUN 6    RAID 5    1024 MB
Delete hot spare operation failed.  Status = 6

raidutil failed!
# 

In the this case, one of LUN#0 drives, [1,0], in Sun StorEdge A3500 array failed. As the result, the hot spare drive [5,10] has taken over for this failed drive [1,0]. So [5,10] drive is used as a component of RAID-5 LUN#0 now. In such case, we cannot remove the hot spare drive using raidutil command. If we run raidutil -c c2t5d0 -H 510 command forcely, the command will fails and ASC/ASCQ=9103 event will be logged to /usr/lib/osa/rmlog.logif Sun StorEdge[TM] RAID Manager version is 6.22.1. (ASC/ASCQ=9103 means "Illegal Operation For Current Drive State". For more detail about Sun StorEdge[TM] A3x00/A1000, please refer to Infodoc# 49525.)

However, in such case, the hot spare drive should not be removed because the hot spare drive is used in place of a failed drive in the LUN. Even if the LUN status is not "Optimal" but "Reconstructing", if drivutil command with -i option shows as below, this hot spare drive [5,10] cannot be removed by raidutil command with -H option.

[5,10]    17274      Spare[1,0]     FUJITSU MAG3182L SUN18G  0707         00524112      

If field engineer would like to remove the hot spare drive which is now used by an LUN, first, he should replace the failed drive with new one, then it leads LUN's reconstruction called "copy-back". Once the copy-back process for the LUN finished, then he can run raidutil command with -H option to remove the hot spare drive. Once the copy-back process finishes, then drivutil command with -i option will show as follows. (It should show the status of the hot spare drive is "Spare-Stdby" and not "Spare[x,y]".)

[5,10]    17274      Spare-Stdby    FUJITSU MAG3182L SUN18G  0707         00524112      

If the status of the hot spare drive is "Failed", the hot spare cannot be removed using raidutil command with -H option, either. In such case, the hot spare drive needs to be replaced with new one. Once the status of the hot spare drive changed to "Spare-Stdby", then we can remove it using raidutil command with -H option.

Note: Even if hot spare drive is in "Failed" status, drivutil with -d option will show the drive is registered as a hot spare drive.

This solution has no attachment