Hi guys,
We're running DataOnTap 5.2.1 on a bunch of F330s. One of them had a disk failure this weekend, and since I was in for a power shutdown, I figured I'd just swap in a spare disk from a returned filer (upgrade to an F740).
The problem is the before the old F330 was returned, we never did any of the disk commands to make all the disks into spares. We just copied the data off and shutdown the system.
So I took one of these disks from the old Filer and did the usual disk swap, disk swap procedure to put it into the Filer with the failed disk. And now comes the problem. The Filer sees the new disk and scans it in, but hey! It's got volume info on it, and it won't initialize the disk and just use it on the new filer.
Sigh... I've tried using the command 'disk fail 8a.4' but it won't let me because it's part of a volume.
So I look at the volume status and I get this:
swtoast> vol status Volume State Status Options vol0 online normal root vol0 offline foreign partial
Yup, *two* volumes, both named 'vol0' and I can't get rid of the foreign one. If I just do 'vol status vol0' I get the online volume listed. What I want to do is just a volume destroy, or a disk initialize without any questions asked. But I can't figure out how to do this.
Any hints? I do have a call into NetApp, but I've been on hold for about 15 minutes already...
Thanks, John John Stoffel - Senior Unix Systems Administrator - Lucent Technologies stoffel@lucent.com - http://www.lucent.com - 978-952-7548 john.stoffel@ascend.com - http://www.ascend.com