i ran into the same problem with [i believe] the cheetah 18G drives. i later found the insignificant little piece of paper stating that there might be a problem if you didn't download the latest disk defs.
i can understand the filer not recognizing/using the disk. but slamming to a halt? brrrrrr.
the netapp engineer agreed that the notice should be large red and very visable. sad to see that this did not happen.
if anyone in netapp-land is listening, could this packaging bug be fixed? thank you. i'd be happy to provide case details to netapp upon request. ---
This has a fix. This is part of the 6.1 release which is currently in FCS.
You can check details on this on the NOW site.
The root of this is..we are very particular over what drives we allow in our systems. Different vendors have different way of "working" and we thoroughly test all drives, models, and specific firmware versions before we release it to the wild. Data protection is whats on our mind here. Clearly there is always a better way, and feedback into Engineering asking why we did it that way resulted in reocnstructing how we deal with non-qualified drives and it no longer causes downtime in the current FCS release of ONTAP 6.1. Please review the FCS documentation on NOW to better understand what our OS release procedures and definitions are.
If anyone ever has features for different ways of doing things they want to be heard here at Netapp..open a case and ask. Your technical support rep. will find the answers..and if they dont exist will open an RFE. Your sales contacts are also open to suggestions from the field.
Free leather jackets are not considered RFE material..just so were all in sync on that. :^)