How to Identify a JBOD disk on a StorEdge 3310 Array

I have looked all over the Sun documentation, but I cannot find an answer.  I have a StorEdge 3310 Array that is configured as a JBOD expansion unit (no hardware RAID), Solaris Volume Manager is doing the RAID on Solaris 9.  I have identified a bad disk in one of the mirrors, using metastat(c2t11d0).  I cannot however figure out how to identify which physical bad disk c2t11d0 is. (which slot in the array is it in)  Any help would be appreciated, as I have not seen any documentation on how to do this.  I have found lots of docs, but they focus on how to do this if it is a hardware RAID.  Thanks.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JBOD         is an acronym for Just A Bunch of Drives
barthalamuAuthor Commented:
Okay.  My question is how to identify the failed disk, which is physically located in the StorEdge 3310 Array from the Solaris failed disk c2t11d0.
you might check this Sun manual out.... you need to know what RAID you are running 0,,1,,2,,3,,4,,5,,10???
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

I had the same issue on a D2 array a few months back. We have volume manager running the raid also and it is very difficult to tell which drive it is. However what we did was when you list out the disks on the second line it had what looked like a serial number.

If you took that number the last  4 or 6 digits would match the end of the serial number on the end of the drive it self. We crossed our fingers and yanked and it was right.

Good luck i hope you find it or that someone else can give you a better answer.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
barthalamuAuthor Commented:

I think you are referring to the "Device ID" information produced at the end of a 'metastat' output.  To me this looks like there is a serial number in there also.  I will check this out on the array at our data center as soon as I can.  Thank you very much for the tip!!
How many physical disks are in the system?  If there's less than 5, it's a simple process of elimination.  Take out the first one, look for bad disk, if no, replace, go to next disk...etc...
barthalamuAuthor Commented:
12 disks in the array.
Have you patched the firmware yet?
That's for Solaris 8 & 9.

That's the only thing I could find on the Solaris site.
barthalamuAuthor Commented:
I forgot about this one...sorry about that.

tonkajeep34, I was able to verify that part of that number did match the label on the disk. (although it was on the top and could not be seen until after pulled)  The disk number however did match with the array's numbering.  Thanks!!

Thanks all.
Cool, glad it worked... ours fortuantly were on the ends of the disk also...

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.