SUMMARY : DLT gone bad?

From: Sue Thielen <Sue.Thielen_at_epeople.com>
Date: Tue Sep 18 2001 - 13:10:33 EDT
Well.. I did power cycle the DLT in the L280. And the messages went away
for about an hour. I wound up getting the drive replaced, and replacing a 
couple tapes that had been frozen. After a bit of mucking around trying to
get support from Veritas, I did manage to get things working. Seems that
the latest patch stomps on the st.conf file as well.. 


Thanks for the tips

sue


Original Post


I've been having trauma with my DLT running netbackup...

Here's the nasty messages... 

p  7 17:02:26 wolf tsdd[675]: TSD(0) [216] test_ready failed
Sep  7 17:02:26 wolf tsdd[675]: TSD(0) [216] Sense Key:  Hardware Error
(0x4)
Sep  7 17:02:26 wolf tsdd[675]: TSD(0) [216] ASC 0x40, ASCQ 0x80
Sep  7 17:02:26 wolf tsdd[216]: TSD(0) unavailable: initialization failed:
Robot busy, cannot perform operation

I guess I need to reboot the Robotic drive.. only it's at a datacenter..
Anyway I can diagnose
this remotely?? Or should I get Sun hardware support to check it out?

Other details.. Just put in the latest netbackup patch . The machine is a
Sparc 20 running Solaris 7.

sue
Received on Tue Sep 18 18:10:33 2001

This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:32:31 EDT