Unsolved
This post is more than 5 years old
3 Posts
0
1044
January 31st, 2014 01:00
Strange Hotspare Invoke
Hello all,
Got a strange issue and don't know how to explain; if anybody have an idea?
I had a spare invoked on one of my old DMX3 :
$ symevent list -sid xxx -v -start 01/01/2014
Symmetrix ID: xxxxxxxxxx
Time Zone : Eur
Event at Sat Jan 04 09:07:41 2014:
Reporting Director : DF-1B
Source : Symmetrix
Category : Disk
Severity : Informational
Numeric Code : 0x0052
Event Code Symbol : SPARE_INVOKED
Description : A Hot Spare was invoked against a Symmetrix Disk
When i try to list failed disks
The command returns nothing :
$ symdisk –sid xxx list -failed
No devices were found
Symmetrix ID : xxxxxxxxxxx
When listing hotspare i can see Hotspare 01B:DE contains 42 HVE.
$ symdisk –sid xxx list -hotspare
Symmetrix ID : xxxxxxxxxxx
Disks Selected : 14
Capacity(MB)
Ident Symb Int TID Vendor Type Hypers Total Free Actual
------ ---- --- --- ---------- ---------- ------ -------- -------- --------
DF-1A 01A C E SEAGATE C300LPF 0 0 0 286102
DF-5A 05A C E SEAGATE C300LPF 0 0 0 286102
DF-6A 06A D E SEAGATE BL500LP 0 0 0 476837
DF-11A 11A C E SEAGATE C300LPF 0 0 0 286102
DF-12A 12A D E SEAGATE BL500LP 0 0 0 476837
DF-16A 16A D E SEAGATE C300LPF 0 0 0 286102
DF-1B 01B D E SEAGATE C300LPF 42 0 0 286102
DF-5B 05B D E SEAGATE C300LPF 0 0 0 286102
DF-6B 06B C E SEAGATE T300R10 0 0 0 286102
DF-12B 12B C E SEAGATE T300R10 0 0 0 286102
DF-16B 16B C E SEAGATE C300LPF 0 0 0 286102
DF-1C 01C C E SEAGATE C300LPF 0 0 0 286102
DF-16C 16C D E SEAGATE C300LPF 0 0 0 286102
DF-16D 16D C E SEAGATE C300LPF 0 0 0 286102
Hotspare 01B:DE infos :
$ symdisk -sid xxx -v -spare_info list -da 1B
Symmetrix ID : xxxxxxxxxx
Disks Selected : 1
Director : DF-1B
Interface : D
Target ID : E
Disk Group Number : 0
Vendor ID : SEAGATE
Product ID : SX3300007FC
Product Revision : C300LPF
Serial ID : 3KR1JQNY
Disk Blocks : 0
Block Size : 512
Actual Disk Blocks : 585937499
Total Disk Capacity (MB) : 0
Free Disk Capacity (MB) : 0
Actual Disk Capacity (MB) : 286102
Hypers : 42
Hot Spare : True
Failed Director : DF-12A
Failed Interface : D
Failed Target ID : A
Failed Disk : False
Hypers (42):
{
# Vol Emulation Dev Type Mirror Status Cap(MB)
--- ---- ---------------- ---- ------------- ------ -------------- --------
1 0 FBA 0AAA Spare 3 N/A N/A
2 0 FBA 0AB8 Spare 3 N/A N/A
3 0 FBA 0ABD Spare 3 N/A N/A
4 0 FBA 0AC1 Spare 3 N/A N/A
5 0 FBA 0AC4 Spare 3 N/A N/A
6 0 FBA 0AC9 Spare 3 N/A N/A
7 0 FBA 0ACE Spare 3 N/A N/A
8 0 FBA 0AD3 Spare 3 N/A N/A
9 0 FBA 0ADC Spare 3 N/A N/A
10 0 FBA 0AE0 Spare 3 N/A N/A
11 0 FBA 0AE5 Spare 3 N/A N/A
12 0 FBA 0AE9 Spare 3 N/A N/A
13 0 FBA 0AEC Spare 3 N/A N/A
14 0 FBA 0AF1 Spare 3 N/A N/A
15 0 FBA 0AF6 Spare 3 N/A N/A
16 0 FBA 0AFB Spare 3 N/A N/A
17 0 FBA 0B04 Spare 3 N/A N/A
18 0 FBA 0B08 Spare 3 N/A N/A
19 0 FBA 0B0D Spare 3 N/A N/A
20 0 FBA 0B11 Spare 3 N/A N/A
21 0 FBA 0B14 Spare 3 N/A N/A
22 0 FBA 0B19 Spare 3 N/A N/A
23 0 FBA 0B1E Spare 3 N/A N/A
24 0 FBA 0B23 Spare 3 N/A N/A
25 0 FBA 0B2C Spare 3 N/A N/A
26 0 FBA 0B30 Spare 3 N/A N/A
27 0 FBA 0B35 Spare 3 N/A N/A
28 0 FBA 0B39 Spare 3 N/A N/A
29 0 FBA 0B3C Spare 3 N/A N/A
30 0 FBA 0B41 Spare 3 N/A N/A
31 0 FBA 0B46 Spare 3 N/A N/A
32 0 FBA 0B4B Spare 3 N/A N/A
33 0 FBA 0B54 Spare 3 N/A N/A
34 0 FBA 0B58 Spare 3 N/A N/A
35 0 FBA 0B5D Spare 3 N/A N/A
36 0 FBA 0B61 Spare 3 N/A N/A
37 0 FBA 0B64 Spare 3 N/A N/A
38 0 FBA 0B69 Spare 3 N/A N/A
39 0 FBA 0B6E Spare 3 N/A N/A
40 0 FBA 0B7C Spare 3 N/A N/A
41 0 FBA 0B8E Spare 3 N/A N/A
42 0 FBA 0BA2 Spare 3 N/A N/A
}
Infos about 12A:DF Disk (this disk is not failed!)
symdisk –sid 353 show 12A:DA
Symmetrix ID : xxxxxxxxxxx
Director : DF-12A
Interface : D
Target ID : A
Disk Group Number : 10
Vendor ID : SEAGATE
Product ID : SX3300955FCV
Product Revision : T300R10
Serial ID : 3RH0ZLNZ
Disk Blocks : 585937499
Block Size : 512
Actual Disk Blocks : 585937499
Total Disk Capacity (MB) : 286102
Free Disk Capacity (MB) : 2728
Actual Disk Capacity (MB) : 286102
Hot Spare : False
Failed Disk : False
Hypers (42):
{
# Vol Emulation Dev Type Mirror Status Cap(MB)
--- ---- ---------------- ---- ------------- ------ -------------- --------
1 523 FBA 0AAA Data 1 Ready 3094
2 524 FBA 0AB8 RAID-5 1 Ready 7375
3 525 FBA 0ABD RAID-5 1 Ready 7375
4 526 FBA 0AC1 RAID-5 1 Ready 7375
5 527 FBA 0AC4 RAID-5 1 Ready 7375
6 528 FBA 0AC9 RAID-5 1 Ready 7375
7 529 FBA 0ACE RAID-5 1 Ready 7375
8 530 FBA 0AD3 RAID-5 1 Ready 7375
9 531 FBA 0ADC RAID-5 1 Ready 7375
10 532 FBA 0AE0 RAID-5 1 Ready 7375
11 533 FBA 0AE5 RAID-5 1 Ready 7375
12 534 FBA 0AE9 RAID-5 1 Ready 7375
13 535 FBA 0AEC RAID-5 1 Ready 7375
14 536 FBA 0AF1 RAID-5 1 Ready 7375
15 537 FBA 0AF6 RAID-5 1 Ready 7375
16 538 FBA 0AFB RAID-5 1 Ready 7375
17 539 FBA 0B04 RAID-5 1 Ready 7375
18 540 FBA 0B08 RAID-5 1 Ready 7375
19 541 FBA 0B0D RAID-5 1 Ready 7375
20 542 FBA 0B11 RAID-5 1 Ready 7375
21 543 FBA 0B14 RAID-5 1 Ready 7375
22 544 FBA 0B19 RAID-5 1 Ready 7375
23 545 FBA 0B1E RAID-5 1 Ready 7375
24 546 FBA 0B23 RAID-5 1 Ready 7375
25 547 FBA 0B2C RAID-5 1 Ready 7375
26 548 FBA 0B30 RAID-5 1 Ready 7375
27 549 FBA 0B35 RAID-5 1 Ready 7375
28 550 FBA 0B39 RAID-5 1 Ready 7375
29 551 FBA 0B3C RAID-5 1 Ready 7375
30 552 FBA 0B41 RAID-5 1 Ready 7375
31 553 FBA 0B46 RAID-5 1 Ready 7375
32 554 FBA 0B4B RAID-5 1 Ready 7375
33 555 FBA 0B54 RAID-5 1 Ready 7375
34 556 FBA 0B58 RAID-5 1 Ready 7375
35 557 FBA 0B5D RAID-5 1 Ready 7375
36 558 FBA 0B61 RAID-5 1 Ready 7375
37 559 FBA 0B64 RAID-5 1 Ready 7375
38 560 FBA 0B69 RAID-5 1 Ready 7375
39 561 FBA 0B6E RAID-5 1 Ready 7375
40 562 FBA 0B7C Data 2 Ready 3
41 563 FBA 0B8E Data 1 Ready 3
42 564 FBA 0BA2 Data 2 Ready
If someone could explain to me it will be great.
Thanks for your help.
Regards.
FDEN1
3 Posts
0
January 31st, 2014 04:00
The main problem is that DMX runs out of support and need to be turned off as soon as migration data ends
LBM99
1 Rookie
•
119 Posts
0
January 31st, 2014 04:00
You should open a service request for this. Someone will need to connect to the array and investigate errors that logged at the time of the spare being invoked. A drive doesn't need to completely fail for a spare to be invoked, just a set of errors that are defined in Enginuity to invoke a spare. These errors could be due to drive issues, errors elsewhere on the drive loop, microcode or drive firmware. The support person will look at those errors and determine if the drive needs to be replaced, or other action is required, or the spare can simply be split off.
The array should dial home for those events when they occur. Be sure to have them check if it did, and if it did not, they need to investigate why.
LBM99
1 Rookie
•
119 Posts
0
January 31st, 2014 05:00
OK, but the errors in the array need to be investigated to determine cause. SymCLI commands will not provide enough info.
Mike
FDEN1
3 Posts
0
January 31st, 2014 05:00
That's what i tought.
Thanks for your time
Regards.