We received a replacement drive last week for a bad drive in our SAN. The slot the drive was in wasn't configured yet. Turns out the drive (refurbished obviously) had data still on it. No big deal right?
This logical drive that existed on the drive also happened to use the same LUN as one of our existing drives. I kept getting errors when I tried to delete the bad drive. When I tried to remove the mapping it took with it the mapping for our existing drive. Fortunately that server wasn't online. To meet a deadline, I recreated the previous array ...with a different LUN this time. The drive is no longer there, but...
Now (then too) I have no option to delete this array. The option is grayed out. I'm not sure what to do at this point. A third party support representative said we would have to rebuild our entire SAN. (Oh joy!!) It contains several severs so this would be quite a "recovery" job for a single faulty drive from a supplier.
I know it should be tested when possible, but I had never imagining it would corrupt a SAN configuration. Has anyone else been through this? Our support company has offered to compensate us. It created quite a problem obviously, or else I wouldn't be here. Not to mention the time it took to recreate a new array.
Oh, we're using IBM Storage Manager.