Networker

Re: [Networker] STK L700e drive issue

2005-01-19 10:19:02
Subject: Re: [Networker] STK L700e drive issue
From: "Huff, Robert" <robert.huff AT CHRISTUSHEALTH DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 19 Jan 2005 09:05:09 -0600
I have had all kinds of issues with AS.  We are also using Seagate
viper\certance drives.  One of the many cases I opened with legato
suggest that the AS port (default 444444) either disables or locks and
suggested that I reboot the AS server when this happens.  Just be sure
to do an asnw_dbsync -v after the reboot and a robot inventory.  You may
also check for the latest drivers
(http://www.certance.com/support/drivers/?producttype=LTO1).
If you do upgrade drivers be sure you have the latest firmware for your
juke and your drives from storagetek (found out the hard way).

Rob

Robert Huff | Sr. Systems Administrator
Christus Health
Tel 713.613.3882 | Page 1.888.247.4752
robert.huff AT christushealth DOT org
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Conrad Macina
Sent: Wednesday, January 19, 2005 8:47 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] STK L700e drive issue

Hi, Jim,

I haven't seen that particular problem, most likely because it appears
to be
drive-related and we don't use Seagate drives. Does it always happen on
the
same drive? If so, the drive may be bad and need service or replacement.
If
it happens across all your drives, you may need to update the drive
firmware.

Good luck,

Conrad Macina
Pfizer, Inc.


On Tue, 18 Jan 2005 13:21:45 -0500, Neild, Jim <Jim.Neild AT SSHA.ON DOT CA>
wrote:

>I have a couple of L700e libraries with 3.07 firmware and Seagate LT01
>Viper drives.  I periodically get the log entries below in my FSC log
>after NetWorker, via AlphaStor, have requested an unmount.  NetWorker
>thinks the unmount and eject succeeded, AS thinks it just errored out
>and the tape stays stuck in the drive with a status of LOADED BUSY.
>Anyone else ever get this?
>
>
>
>
>LOG ENTRY
>--------------
>
>
>FSC 0x3e1f  Mechanism DRIVE_04_00  Severity Warning
>
>---------  Summary ---------
>DRV Wait for Rewind Failed - Drive rewind did not complete when
>expected.
>
>---------- Description -----------
>DRV Wait for Rewind Failed - Drive rewind did not complete when
>expected.
>
>
>
>Cheers,
>Jim
>
>--
>Note: To sign off this list, send a "signoff networker" command via
email
>to listserv AT listserv.temple DOT edu or visit the list's Web site at
>http://listserv.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>