couple of things that I found useful so I thought Id make a note:

Identifying The Disk

A failed disk should have an orange LED lit. Sometimes it doesnt though but you
can manually switch the LED on.
1. SSH onto the NetApp box and logon
2. Switch to advanced mode:
CONTROLLER-A> priv set advanced
3. Switch the LED on for disk 0c.00.7:
CONTROLLER-A> blink_on 0c.007
4. To switch the LED off for disk 0c.00.7:
CONTROLLER-A> blink_off 0c.007
5. Come out of advanced mode:
CONTROLLER-A> priv set
Assigning the replacement disk
When you physically swap the disk it will fire off some Autosupport messages and
will hopefully pick up the new disk. In my case, it didnt do anything with the
disk and nothing showed up in the NetApp System Manager. I had to go to the CLI
and assign it manually.
1. Display unassigned disks:
CONTROLLER-A> disk show -n
DISK OWNER POOL SERIAL NUMBER
---------- ------------- ----- -------------
0c.00.7 Not Owned NONE JMY4YGLC
2. Assign the disk to the correct controller:
CONTROLLER-A> disk assign 0c.00.7
Fri Mar 18 11:57:37 GMT [NSH-A: diskown.changingOwner:info]: changing ownership
for disk 0c.00.7 (S/N JMY4YGLC) from unowned (ID -1) to CONTROLLER-A (ID 1351096
46)
NSH-A*> Fri Mar 18 11:57:37 GMT [NSH-A: diskown.RescanMessageFailed:warning]: Co
uld not send rescan message to CONTROLLER-A. Please type disk show on the consol
e of NSH-A for it to scan the newly inserted disks.
3. If it wont accept the command in step 2, it might have been auto assigned to
the wrong controller/system. You can you can clear the assignment from the disk
using the following command then retry step 2:
CONTROLLER-A> disk assign 0c.00.7 -s unowned -f
CONTROLLER-A> disk assign 0c.00.7
dont forget to exit privileged mode when done:
fas3050clow*> priv set
Note: Disks may be automatically assigned to this node, since option disk.auto_a
ssign is on.
Checking back in System Manager shows that the disk is back in action but its sti
ll showing as a spare. It seems that NetApp systems arent bothered about going b
ack to the original hot spare, which seems like a very sensible idea. Why bothe
r reconstructing the new disk when its already been done once when it originally
failed over to the spare?
Its probably best to temporarily disable AutoSupport while doing this. That way
the FAS is prevented from phoning home and possibly generating unrequired support
cases. I overlooked this and got an additional drive delivered 4 hours after re
placing the failed one. The FAS seems to have triggered a new AutoSupport case
when I pulled the drive to replace it.
=======
Or;
Problem
When I replace a failed disk, my filer doesn't see the disks immediately. The Fi
ler Status page is complaining "Assign unowned disks".
Solution
Your filer is set up with software disk ownership, presumably so that clustered
filer heads can share the same shelves. As a side-effect, you must set the "disk
ownership" of disks after you replace them.
Scenario: two disks failed, 0b.19 and 0b.23. NetApp has supplied replacement dis
ks, which have been inserted and have gone green. The filer is still complaining
about "insufficient spare drives", and says "Assign unowned disks". The FilerVi
ew thing isn't showing the inserted disks in the Disk Management page.
nas02> disk show
Note that the replaced/inserted disks 0b.19 and 0b.23 are not in the above list.
(The list is unsorted, so it is hard to tell immediately.)
Use the disk assign command to assign the inserted disks:
nas02> disk assign all
The parameter all refers to all currently unassigned disks.
Now confirm that the assignment worked:
nas02> disk show
=====================================================
How to replace Disk in netapp
Disk replace:

Disk can be replaced automatically from Spare disk or you can replace manu
ally using disk replace command.
filer>disk replace start -f 0a.28 0a.28
This command uses Rapid RAID Recovery to copy data from the specified file syste
m disk to the specified spare disk. At the end of that process, roles of disks a
re reversed. The spare disk will replace the file system disk in the RAID group
and the file system disk will become a spare. The -f option can be used to skip
the confirmation.