• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 444
  • Last Modified:

During drive rebuild; drive status goes into que state.

I have a Novell 6.5 server that had a failed drive; I replaced the drive and the rebuild proceeded as normal. At about the 21% of the rebuild the drive goes into a que status and then back to a ready for recovery in the HP Smart Array Online Config Util. It is showing no failed drives and all drives are present. Could this be a firmware related issue?

Queued-Snapshot1..doc
0
smartin36
Asked:
smartin36
  • 3
  • 3
1 Solution
 
ShineOnCommented:
NetWare 6.5.

Novell is a company - it doesn't come in numeric versions.

That said, NetWare 6.5 is incidental to this issue, in my humble opinion.  This is a hardware thing, and might actually not be a problem.  Hard to say for sure without a tad more info.

What is the RAID controller model?  What is the RAID level you're using?  How many drives?  Any hot spares?  Have you checked the array by booting to the RAID controller utilities rather than via the online utility?
0
 
smartin36Author Commented:
I was able to upgrade the firmware and that resolved my issue.
0
 
ShineOnCommented:
Technically speaking, if the fix was a firmware update, presumably on the RAID controller, then the statement in my comment "This is a hardware thing ..." is correct, and the Asker did not answer any pertinent questions about the hardware, or whether they tried the RAID controller utilities at boot time rather than via the online utility - answers to which might well have led directly to a harware provider's support site and an answer of "update the firmware."

It's not beyond imagination that the Expert questions asked prompted the Asker to follow that path, resulting in the firmware update.

Unless the rules have changed on questions/answers and how to close, I don't see that deleting it is a valid request.  It would be better to post back controller model and original/new firmware rev level (assuming it was the controller's firmware) and PAQ it for posterity.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
smartin36Author Commented:
The firmware issue was related to the MB. The firmware on the array was up to date. I went on and updated the firmware that was required. I then rebooted the server and proceeded to check the array utility and the drive was in the process of rebuilding. I assumed the drive would fail to rebuild because it had failed to rebuild previously with the up to date firmware on the array. But to my suprise the drive rebuilt successfully. I used the firmware maintance CD  ...firmware 8.00 zip Feb 11, 2008 for Netware 6.5. I did not follow the experts questions to determine the path to follow I had already presummed it was firmware related and was only looking for a yes or no response to confirm what I had already suspected.
0
 
ShineOnCommented:
Recommend {http:#a21984095} for paq with refund, and thank you to smartin36 for posting back the actual situation.

smartin36 - just to be clear, I understand you asked if it could be firmware-related, but didn't indicate what type of firmware or exact hardware beyond server model.  If you already did all that legwork and just wanted to use E-E as a sounding-board to see if your suspicion of server mainboard firmware/BIOS update was on the right track, saying so up front would've been helpful to reduce confusion.
0
 
smartin36Author Commented:
Thank you!

ShineOn - I believe I did indicate which hardware I was having the issue with and that would have been where I said (I  have a Novell 6.5 server that had a failed drive; I replaced the drive and the rebuild proceeded as normal. At about the 21% of the rebuild the drive goes into a que status and then back to a ready for recovery in the HP Smart Array Online Config Util. Could this be a firmware related issue?) I believe that would indicate HARD DRIVE not MB so the actual situation was indicated in the question. At the time I had asked the question I had not checked the firmware that was on the server. It was only after I decided to run the firmware CD did I determine that the MB firmware needed to be updated and that the firmware on the array was already up to date. I do not beieve I used E-E as a sounding board to see if my suspicion of server mainboard firmware/BIOS was on the right track that was only determined after I ran the firmware CD. So at the end of the day could this be a firmware related issue the answer is yes. Just because I suspected firmware does not mean that I already knew which firmware I suspected. In the end make sure all of your firmware is up to date.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now