SCSI Port 2 Drive ID 0 is not stamped for monitoring

[Dave Onex]

Yes, those drives now show as having 5 hours on them :-)

Perhaps I can sell them as 'near new' units :-)

I'm glad we've got it cased and they are performance stamped etc.

Thanks you guys for all your help - I like knowing the system is up to date again and things are working well.

Best!
Marvin

[James ~ Happy Dude]

o N/A: The answer was simply a point of clarification to my original question

o 1-3: The answer didn't really help answer my question, but thanks for your assistance!

o 4- 7: The answer helped with a portion of my question, but I still need some additional help!

o 8-10: The answer has solved my problem completely! Now I'm a happy camper!


Although assigning points is not mandatory, it is a key component of a strong, interactive community, and it is STRONGLY ENCOURAGED. Others have taken time to help you, so please take a moment to give them credit for their assistance!

[Mark Myerscough]

Exact same problem on my server.

ML 350, Generation 3 with 6 72.8 Ultra 320 SCSI drives.
SmartArray 532 card.

The Array Diagnostics Utility reports that all six drives are not stamped for monitoring. There are a total of three logical drives on the physical drives.

So far I have (both with and without reboots between for testing purposes when applicable):
1. Used the Array Configuration Utility (ACU) to change settings on the array.
2. Deleted ALL logical drives on the Array, Used the latest version of SmartStart (7.80) to re-install everything (including Windows 2003 Enterprise Edition).
3. Used Firmware 7.90 to update all of the firmware. The SmartArray 532 card is already using version 2.66, I reinstalled it. The Hard Drives were already using the latest version as well. The only thing that FirmWare 7.90 reported as needing updated was the BroadCom network interface. I updated it.
4. Used ACU to change settings again, trying to get it to regenerate and re-stamp the drives.

I'm running out of ideas here, but can not get the drives stamped for monitoring.

The problem I am having is that the server will randomly lock up, freezing all operations on it. I am running VMWare with three virtual servers inside it, but the lock up problem has also occurred when running Microsoft's Virtual server with the same three servers running within it. If I boot the system off a Smart Start CD and run diagnostics on it overnight, nothing is reported as having problems.

I've attached a report from the ADU output to this message.

[Mark Myerscough]

I just did more investigation.

One of my six drives has an out-of-date ROM Firmware (HPB4 instead of the HPB8 the other five have.)

I tried using the Firmware Update disc (v. 7.90) to update it by enabling Re-install for the drive firmware. When it ran, it re-installed on the five good drives (I could tell by watching the orange light come on in sequence) but skipped the one out-of-date drive.

I then removed the five good drives, re-ran the firmware with only the out-of-date drive installed in the machine, and the Firmware software did not even recognize that a drive was installed.

I rebooted the machine with only the five good drives installed (fortunately my boot drive is configured on just two of the drives and they were both in my "good" set). Went through the ACU / ADU process - and I now have five drives, all NOT stamped for monitoring and performance.

I am now officially exhausted on ideas, but doing a search for "not stamped for monitoring" on the forums leads me to believe that this is a significant problem. Will a tech person from HP please chime in here with an solution to this problem??

[Mark Myerscough]

For explicit discussion on this topic, see:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00839354

Apparently, SmartStart versions ABOVE 7.0 will NOT correct the problem, so pushing users to the latest/greatest/newest release is not solving the problem.

I am now downloading SmartStart 7.0 and will run it as soon as it is finished downloading. Will report on the results as soon as possible, but based on the article listed above, the problem is a known bug (er, design consideration) in later versions of SmartStart. And to think, I always thought later releases were intended to clean up known bugs, not purposefully introduce new ones - silly me!

[Mark Myerscough]

After downloading and burning two copies of the SmartStart 7.00.0 software, I am pleased to report the problem was solved.

The solution, to re-iterate for everyone who follows is to use the Array Configuration Utility included on the SmartStart 7.00.0 CD. All later versions of the software have a design flaw, and will not solve the problem.

[James ~ Happy Dude]

Thanks For the updates Mark;

"However", All these situations & many more have been corrected in SmartStart 7.9

Regards,
James.

[Mark Myerscough]

"All these problems have been fixed in SmartStart 7.9.0".

WRONG! I used 7.9.0 as the original base for creating my machine earlier this week. I also booted using that CD, and ran the ACU utility from it. It did not solve the problem. The only thing that worked was using ACU 7.0.1 from SmartStart 7.00.0.

[Mike Dawkins]

Thank you for this post and solution! The SmartStart 7.0 CD works!