1. Login to filer and
verify the device address of the failed disk via command line
filer02>
vol status -f
Note: device address
usually has the form ., e.g, 0a.18,
0a.20
2. Physically
identify the failed disk by locating an amber light blinking on and off on the
lower part of the disk.
3. If you cannot see
any amber light, got to advanced mode and turn ON the led by issuing the
commands below:
filer02>
priv set advanced
filer02*>
led_on 0a.19
4. If you still
cannot see any amber light blinking, manually turn on the leds on the
neighboring disks to locate the faulty disk:
filer02*>
led_on 0a.18
filer02*>
led_on 0a.20
5. When the location
of the failed disk has been verified, remove it by pulling the latch and
pulling it partially.
Wait for 2 minutes to
let it spin down then remove it afterwards. During this process, you can see
the messages below
popping out from the
terminal.
filer02*>
Wed Mar 5 20:21:23 EST
[filer02:fci.adapter.link.online:info]: Fibre Channel adapter 1a link online.
Wed
Mar 5 20:21:23 EST
[filer02:fci.adapter.link.online:info]: Fibre Channel adapter 0a link online.
Wed
Mar 5 20:21:30 EST
[filer02:raid.disk.missing:info]: Disk 0a.19 Shelf 1 Bay 3 [NETAPP X291_S15K6420F15 NA01] S/N
[3QQ0MSBX00009922S2N5] is missing from the system
Wed
Mar 5 20:21:54 EST
[filer02:config.BadPoolAssign:warning]: Disk 1a.27 is in Pool1 and other disks
on this loop/domain are in Pool0. Disks/Interfaces need to be in separate pools
for SyncMirror.
6. Insert the new
disk by pushing the latch in upward position until it snaps into place. Wait
another 2 minutes
to let the
synchronization finish. Messages below will appear during this process.
filer02*>
Wed Mar 5 20:23:16 EST
[filer02:fci.adapter.link.online:info]: Fibre Channel adapter 1a link online.
Wed
Mar 5 20:23:16 EST
[filer02:fci.adapter.link.online:info]: Fibre Channel adapter 0a link online.
NOTE: sometimes, that
message don;t appear
7. The amber light
should stop illuminating by now. If not, turn it off manually:
filer02*>
led_off 0a.19
8. Go back to admin
mode (exit advanced mode) and assign the disk to the filer.
filer02*>
priv set
filer02>
disk assign 0a.19 --> use the device
ID on the line with .. is missing from the system
10. Verify the new
disk. You can see below that the new disk replaced the spare disk that was used
during the rebuilt of data when the
original disk has
failed.
filer02>
aggr status -s
Spare
disks
RAID Disk
Device HA SHELF BAY CHAN Pool Type RPM
Used (MB/blks) Phys (MB/blks)
---------
------ ------------- ----
---- ---- ----- --------------
--------------
Spare disks for block checksum
spare 1a.19 1a
1 3 FC:B
- FCAL 15000
418000/856064000 420584/861357448
spare
2d.03.8 2d 3
8 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.9 2d 3
9 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.10 2d 3
10 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.11 2d 3
11 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.13 2d 3
13 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.16 2d 3
16 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.17 2d 3
17 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.18 2d 3
18 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.19 2d 3
19 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.20 2d 3
20 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.21 2d 3
21 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
spare
2d.03.22 2d 3
22 SA:B -
SAS 15000 560000/1146880000 560879/1148681096
filer02>
No comments:
Post a Comment