ACU shows disk added as "not-supported" when it is!?!?

I have windows 2000 server with 2x 72gb SAS drives though a smart array p400 on a HP DL380 G4 carved as RAID1+0 mirror set.  I ejected and re-inserted the drive yesterday afternoon.  The Array Configuration utility showed the drive going off-line, and then started a rebuild when the drive came back on-line.  Even when the array was rebuilding, the activity LED on the physical drive was still off, when wed expect to see a lot of activity.  The thing I noted is that the second LED, a blue one, was active when the ACU was in use.  This is similar to the older 3½ drives, which light up an orange LED to show which controller or array is being configured, so at least we know that the drive is responding to a control from the ACU.  The ACU is still showing the first drive with a transfer speed of 3Gbps, while the transfer speed for the second drive is still showing as "not supported"!!!!  Im really not convinced that this is standard behaviour for a two-drive array, and I think the green LED may be off for a reason, i.e. the non-supported transfer rate.  When the drive was initially added back into the drive bay the system event log showed the logical disk as rebuilding and laterly then went to a status of ok for arry and drive as "ok".  Im still a bit concerned that although the ACU shows the array as active, we have no way of confirming this.  Ive hunted through the HP web site, and I cant find any related articles.  Please see screen shots of the array & disk attached.
The Array Diagnostics also report both drives being present and operational &..

 

Drive 1

 
Last Failure Reason: 0x00 (Drive has not failed)
Phys Drive Flags:    0x01 0x25 0xa0 0x00
                     Drive present and operational
                     S.M.A.R.T. Supported
                     S.M.A.R.T. Enabled
                     Configured as part of Logical Drive
                     Drive write cache setting is changeable and safe
 

Drive 2

 
Last Failure Reason: 0x14 (Drive removed from hot plug)
Phys Drive Flags:    0x01 0x25 0xa0 0x00
                     Drive present and operational
                     S.M.A.R.T. Supported
                     S.M.A.R.T. Enabled
                     Configured as part of Logical Drive
                     Drive write cache setting is changeable and safe

My thoughts are that the drive may be corrupted and that if we source a new replacement one it may rebuild successfully as indicated by ACU and by the appropraite LED's on the SAS disk.  But I would really appreciate if anyone had any suggestions to fix this issue without replacing the "dodgy" disk.
meepmakerAsked:
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.

65tdRetiredCommented:
Are the Insight agents installed?
How's the firmware up to date?
0
andyalderCommented:
>This is similar to the older 3½" drives, which light up an orange LED...

Neither the 3.5" or 2.5" drives have LEDs on them, it just looks like they do. In reality they have light-pipes that guide the light from LEDs mounted on the backplane to the front of the caddy. The state of the LEDs is therefore much more dependent on software than hardware - the server is trying to tell you something :)

>I ejected and re-inserted the drive yesterday afternoon.

If the drive was running correctly at the time that was very naughty. As far as the server knows one of the drives failed and has been reseated which brought it back online.

>Last Failure Reason: 0x14 (Drive removed from hot plug)

That message means the disk disconnected from the bus unexpectedly. This is logged both on the disk and the motherboard. A few more unexpected bus disconnects and it will start shouting pre-failure warranty warnings at you.

You need to mark the hardware fault as having been resolved by going to the System Management Homepage log or Insight Manager or whatever you're using to clear the event off the motherboard but I don't know whether you can acknowledge it as a "my bad" on the physical disk or remember it indefinitely.
0

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
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
Server Hardware

From novice to tech pro — start learning today.