Actually, if you had already booted from floppy, simply running "download" at the filer prompt would have been sufficient. I have seen this exact same problem a couple of times and that was the fix.
Another alternative that usually works is to shut the system off, and swap the first two disk positions, i.e. 0 & 1 which are on the opposite side from the power supply This presumes the system is booting from disk 0. This lets the system read the same kernel from a different disk. Of course, you do not want to swap if it is a spare, in that case just pick any other non-spare disk & swap with 0 (again, if this is the boot disk)
--tmac
So I rebooted from floppies (after swapping the disks back around correctly), and that seemed cool -- it figured out which disk was what, and did all the necessary RAID reconstruction. Everything looked OK.
Booting from floppies is a good idea at that point.
What I *think* I could've done was: reboot from floppies; splat the ontap stuff into /vol/vol0/etc from afar; typed 'download' at the filer, and it might've worked. (But would I have had reason to trust any of the ordinary RAID data at this point?)