RE: LTO backup drive failing?

An IPL is a bit of overkill. What really needs to happen is the IOP/IOA
need to be restarted. If you know how to do that (and there are not any
disk units being run by that IOP) it's easy and fast. If there are disk on
that IOP then an IPL is the only choice.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger
Harman
Sent: Friday, January 30, 2015 4:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: LTO backup drive failing?

Devd damaged?


Perhaps delete the device and recreate? I don't recall if it was V5.3 or
V5.4, I had to delete the device and IPL for it to
auto-discover/auto-config. There was some issue that wouldn't let me
recreate it manually.



Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power OCEAN
User Group

<http://www.ocean400.org>






----------------------------------------

From: bcagle@xxxxxxxxxxx
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: LTO backup drive failing?
Date: Fri, 30 Jan 2015 17:04:27 +0000

I have an external IBM Ultrium LTO drive - 3580-003, attached to an i5 520

that I *think* might be failing. The last three mornings the backup job has
been stuck in an EVTW status with the drive's activity light blinking. The
job log shows that only the first library has been saved. My guess is that
it's attempting to write the library to tape, but the tape is just spinning.
The only thing I can think that I did different is that I actually cleaned
it with a cleaning cartridge the day before this began. Yes, I've cleaned it
before, with the same cartridge, about 6 months ago...

The backup job is just a CL that begins with SAVLIB *ALLUSR, then does
a SAVDLO, SAVSECDTA, SAVCFG, and SAV. The backup normally takes around
3 hours to finish completely, but it is getting stuck on this first
library for over 5 hours. (We're a really, really small shop)

There are no obvious errors that I can find. After some digging, I found

the Service Action Log in the Hardware Service Manager of SST, and two NEW
entries are shown here for both resource DC03 and TAP02 (which is the
problem drive). So I guess that is proof that *something* is wrong.

My next step is to place a service request with IBM, but thought I would

post here to see if anyone had any ideas what might be wrong. The tape drive
was purchased used almost two years ago.

Thanks for any input.

Bob Cagle
IT Manager
Lynk, Inc.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.