1837533 Members
3574 Online
110117 Solutions
New Discussion

Re: EMS and NO_HW

 
Jim Mallett
Honored Contributor

EMS and NO_HW

I have an HP SureStore 818 DLT. It works perfectly, but every month or two it stops responding and shows up as NO_HW. Nobody has touched the drive and if I reboot I'm fine for another month or two. I don't have the luxury of rebooting as much now though.
The initial ioscan shows NO_HW from the ext_bus right down to the tape drive. I recycle the power on the SureStore, rerun the ioscan and everything is claimed except for the autochanger (still NO_HW).
Short term: Any ideas on getting the autochr claimed without rebooting?
Long term: HP has told me they think that EMS is interfering with the tape drive and I should shut that piece of it off. I do see a message in my syslog from the EMS. Any ideas on how to shut off this aspect of EMS?

TIA... Jim Mallett

Attached is the ioscan and an excerpt from the syslog.
Hindsight is 20/20
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: EMS and NO_HW

I would tend to lean toward scsi device conflict, loose cabling or bad power to the DLT device. Our's doesn't do that.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Bryan D. Quinn
Respected Contributor

Re: EMS and NO_HW

Hey Jim,

We had a scenario similar to this about a year ago, and it seems that EMS was brought up for our problem also. To make a long story short, the HP CE swap a couple of boards out and it finally came down to a flaky SCSI cable. There was a third party cable being used, that had been working just fine for quite some time. We put a new HP cable on it and it has been great ever since.

-Bryan
Michael Steele_2
Honored Contributor

Re: EMS and NO_HW

That's your picker or robotic arm that's a problem.

Please go to 'LOGTOOL' and respond with the first & last dates and the number of errors besides each HW address posted in your attachement, this will give an indication of your history of errors and weather or not you've got a device ready for replacement.

ext_bus 0/3/0/0
autoch 0/3/0/0.0.0
tape 0/3/0/0.1.0
ctl 0/3/0/0.7.0

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY.

Note the first and last dates of transactions and calculate the difference. If the difference is short, like 4 hours, then this is important to note. Now read down the report of hardware addresses and observe the integer numbers in parenthesis. Anything over 150 in this 4 hour period should be called into HP for replacement.

Support Fatherhood - Stop Family Law
Jim Mallett
Honored Contributor

Re: EMS and NO_HW

I did some searching on some different keywords in the forum and came up with a response from Michael Tully regarding stopping the dm_stape monitoring on EMS. I followed those steps and now (without a reboot) I am able to utilize the SureStore again. Everything is CLAIMED.

(I'm not ruling out bad cables etc, something is causing the issue....but disabling the EMS has at least temporarily resolved it.)


http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x662536e69499d611abdb0090277a778c,00.html
Hindsight is 20/20