ADSM-L

Re: Win2K, Fiber and I/O problem

2002-10-17 00:12:57
Subject: Re: Win2K, Fiber and I/O problem
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 17 Oct 2002 00:10:34 -0400
Been there, seen this, solved this.  For some reason the TSM Boot ADSMSCSI
driver does not pickup the drives first.  What you have to do is disable the
drives in device manager and reboot.  Make sure the ADSMSCSI driver service
(BOOT) is setup in the configuration.  Otherwise, the drives will not get
picked up by TSM.

We have seen if you get the (BOOT) driver installed from TSM correctly and
delete the drives from device manager the TSM boot driver will pick them up
correctly.

Our case was Magstar tape drives but the symptoms were exactly the same.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Cowperthwaite, Eric [mailto:eric.cowperthwaite AT EDS DOT COM]
Sent: Tuesday, October 15, 2002 7:45 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Win2K, Fiber and I/O problem


I have an interesting problem. One of my TSM servers is running on Win2K
Server. The server is connected to a Brocade FC switch and the FC switch is
connected to an FC-SCSI bridge. The library is an HP SureStore 6/60 with
DLT8000 drives. Every once in a while I get I/O error on a tape drive and
the server resets the drive. When it does the drive renames from the TSM
Driver name to the NT Driver name (i.e. from mtx.x.x.x to \\..\tape0
<\\..\tape0> ). Has anyone else had this sort of problem and what did you do
to resolve it?

Thanks,



Eric W. Cowperthwaite
EDS Operations Solutions
Desk - 916-636-1929
Cell - 916-919-6271
eric.cowperthwaite AT eds DOT com <mailto:eric.cowperthwaite AT eds DOT com>

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