2011-09-07 09:41 AM
I have replaced some 500G drives with Western Digital 1TB drives. The firmware is up to date. Specs are as follows:
sysconfig -v shows the following for the drives:
ID Vendor Model FW Size
00.1 WDC WD1002FAEX-00ZSS 1D05 847.5GB (Found in scan)
It found them in the scan, but I can't unfail them, I can't do anything to them. Is there something simple I'm missing? It says the firmware is up to date on the drives. It also gives me an Error 19, the disk is not ready. Are Western Digital drives not compatible?
Solved! SEE THE SOLUTION
2011-09-08 04:35 AM
The Seagate's I used work just fine. It's just the Western Digital. You don't have to have disks from NetApp for it to work. I have replaced two FAS2020's with seagate disks.
2011-09-13 12:41 AM
the Seagate disks happen to work because NetApp also sells them, and so they are recognized. WD disks on the other hand have never been used (AFAIK) in filers and thus there's no config information for them in Data ONTAP.
Needless to say that you're running without any support if you do what you're doing there but I think you know that already ;-)
2011-09-13 01:02 AM
If the disk or shelf was NOT provided by NetApp or an authorized distributor, then:
2011-09-13 07:46 AM
So I tried your answer Michael, and that did not work. I think it's as simple as the firmware. The Filer thinks the FW is up to date, but like you said earlier since NetApp does not use WD's, they don't have the firmware for them. I looked in the etc$/disk_fw folder and there is a .LOD and a .LOD.FVF for every type of firmware listed in the qual_devices except for the 1D05 that the WD's are using. So that's probably what it is. There isn't any firmware released to allow WD's to "talk" to the filer. I'm just going to purchase more Seagates. And I realize this is unsupported, but it's a matter of pricing. I don't believe in paying $17,000 for 12 1TB drives when I can get them for $1000. And their support pricing is outrageous. Please don't hold it against me, I was hired after the decision to use NetApp
2011-09-13 08:01 AM
Well, every enterprise storage vendor sells their disks at seemingly expensive prices, NetApp is no exception there. You get what you pay for.
However I don't think that the firmware is to blame, because the newer SATA disks also use the "stock" firmware and no special NetApp firmware anymore. You could also try editing the qual_devices_v3 file (however they are checksummed so it's probably not as easy) because there you can define "disk aliases" etc.
I'd strongly suggest NOT doing these kinds of experiments on a production system because you risk losing your data on unsupported disks (and NetApp certainly won't accept any liability if you do)
2011-09-13 08:16 AM
I'd strongly suggest NOT doing these kinds of experiments on a production system because you risk losing your data on unsupported disks (and NetApp certainly won't accept any liability if you do).
2012-04-23 11:20 PM
only for the sake of interest did you manage to get another (non Netapp drive) to be recognized as qualified by changing qual_devices ?!
if yes, could you give me some more details.