First off:  You have my sympathy for still using 1TB SATA disks.  Other than that here are a few additional thoughts:  >  You mentioned pulling and reseating both of the drives; I don't know what you did there, but I would have suggested only doing one at a time, and waiting a while in between.  But honestly, even if the two were from the same 6+2R6 group, that shouldn't have been a huge problem.  > Some SATA failures involve flooding the bus with errors.  In cases where performance seems to drop off to a trickle I look at the events for both SPs to insure that one of them isn't getting hammered with error messages.  If that is the case, pull the offending drive to quiet the bus back down.  > In your pool, while you may have deleted all the user LUNs, have you looked for private LUNs that may still exist there?  If a LUN was failed, you may find that a private or unowned LUN still exists.  > You could definitely try rebooting one SP at a time, during a quiet off-peak time.  I don't know if it would help...but it *might* shake something loose.  >  As a last resort, I might consider unseating *all* the disks from that pool, then rebooting the SPs (again one at a time).  I do something similar to this when I want to remove a DAE from a running system; at first it thinks everything is broken, but after the reboots it accepts the loss and moves on with its life.  I'm sure this is not a recommended or approved procedure, but desperate times call for desperate measures...  If that cleaned things up I would start putting the disks back in, and see how that goes.  Best of luck.
I have a pool which I have been trying to drop for almost 12 hours. The pool reports that it's been dropping for almost 12 hours, but no progress. Can I somehow force the drop to complete?
Plz help drop faulted pool