I found the following directions for you on our NOW site:
Command for updating disk firmware
Use the disk_fw_update command from the storage system console to update firmware on all disks or a specified disk on a storage system.
The disk_fw_update command updates disks for which firmware files are present in the /etc/disk_fw directory and which need to be updated. It does not update other disks.
The disk_fw_update command is applicable to SCSI, Fibre Channel, SATA, and SAS disks.
For more information, see the disk_fw_update(1) man page.
Attention: This command makes disks inaccessible for up to two minutes, so network sessions using the storage system should be terminated before running the command. This is particularly true for CIFS sessions, which otherwise are terminated while this command executes.
When to update disk firmware manually
If you receive error messages about firmware compatibility, you must manually update your disk firmware.
Manually update disk firmware with the disk_fw_update command.
Download the new disk firmware from the NOW site, then enter the following command at the storage system prompt:disk_fw_update
Note: When you upgrade the storage system software, disk firmware is updated automatically as part of the storage system software upgrade process. A manual update is not necessary unless the new firmware is not compatible with the storage system disks.
Well I hope that I not going to be a bother. The disk is not part of the system. It is being ignored. I tried to update the firmware from a cmd prompt telnet to the filer but it says No disk in primary FC loop eligible for download. Firmware up to date on all disk drives.
Yet when I look at the disks in filerview the one identified as broken is not a part of the all disks but part of the broken disks.
Thanks for your reply. Actually, it is a very long story. My filer already had its spare disk accidentally allocated to the volume and so we now have no spare. I have to actively monitor the filer for disk failures because of this fact. So when I have a disk fail I have to quickly replace it. I had purchased extra 72 GB disks for that very purpose but unfortunately the two drives I received must have had some data left on them and so I am getting a bad label error on both drives. I would like to clear that data off of those drives so that they will be accepted by the filer as a empty disk that can be used. I am not a Net App expert and really was given the job of IT because I had the most experience in the PC world. Our filer is too old and is considered at EOL and so not supported by Net App. So here I am with drives I can't use and the lack of knowledge to clear the data from the disks. This filer works well when the disks don't fail and even then if I have replacements then I can just replace the drives until such time as I can destroy the aggregate and then rebuild it with a spare drive. As it should be.
It turned out that the firmware version on my drive was earlier than the replacement drive. I was fortunate enough that the company that I purchased the drive from exchanged it for one that they put the same version as what I needed.