|
Ok, some new news. I went and checked the pins to ensure they were not
bend (no issues). When I turned the tape drive back on it is now issuing
an error code "8" which in reading the manual indicates an interface error.
I tried switching cables between the ports 0 and 1 and disconnecting /
reconnecting the cables but the error code appears on every tape drive
power up.
Is this sounding like a hardware issue, or could it still have something
to do with the way it's configured on the iSeries box?
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Wednesday, November 26, 2014 1:50 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Tape Drive not Detected
Sometimes you need to vary off/ vary on Reset . . . . . . . . . . . . .
*YES
And/or IPL the IOP, just make sure no disks attached.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Pete Massiello - ML
Sent: Wednesday, November 26, 2014 1:47 PM
To: Midrange Systems Technical Discussion
Subject: RE: Tape Drive not Detected
One other thing.
Turn the tape drive off, uncable everything and make sure all those little
pins didn't get bent.
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Pete Massiello - ML
Sent: Wednesday, November 26, 2014 1:45 PM
To: Midrange Systems Technical Discussion
Subject: RE: Tape Drive not Detected
No, do you have a terminator on the other port of the tape drive?
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Brian Piotrowski
Sent: Wednesday, November 26, 2014 1:44 PM
To: Midrange Systems Technical Discussion
Subject: RE: Tape Drive not Detected
Actually in looking at this list again I do see the 571A listed as DC05.
However, it doesn't report anything connected to it.
Could it have something to do with the way it is plugged in? As I
mentioned the 571A card has two ports on it - SCSI ID 0 and SCSI ID 1. I
have the cable plugged into SCSI ID 1 and the tape drive is set to SCSI ID
0.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Brian Piotrowski
Sent: Wednesday, November 26, 2014 1:41 PM
To: Midrange Systems Technical Discussion
Subject: RE: Tape Drive not Detected
When I work with hardware resources for storage, I see this:
Resource Type-model Status
CMB01 2844-001 Operational
DC04 5702-001 Not detected
DC03 2749-001 Not detected
DC05 571A-001 Operational
CMB02 286D-001 Operational
DC01 2757-001 Operational
CMB03 268C-001 Operational
DC02 6B02-001 Operational
The 2749 we can already discount as it was in the machine, but is no
longer there.
When I work with the resource DC04 I see this:
Resource Type-model Status
DC04 5702-001 Not detected
TAP03 3580-003 Not detected
Looking at resource detail for DC04 reveals:
Resource name . . . . . . . : DC04
Text . . . . . . . . . . . . : Storage Controller
Type-model . . . . . . . . . : 5702-001
Serial number . . . . . . . : 28-6096024
Part number . . . . . . . . : 0000097P6513
Physical location:
Frame ID 1
Card position C02
Logical address:
PCI bus:
System bus 1
System board 0
System card 21
Storage:
I/O adapter 7
Resource detail for TAP03 shows:
Resource name . . . . . . . : TAP03
Text . . . . . . . . . . . . : Tape Unit
Type-model . . . . . . . . . : 3580-003
Serial number . . . . . . . : 00-0336400
Part number . . . . . . . . :
Physical location:
Logical address:
PCI bus:
System bus 1
System board 0
System card 21
Storage:
I/O adapter 7
I/O bus 0
Controller 2
Device 0
Maybe that might help?
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jim Oberholtzer
Sent: Wednesday, November 26, 2014 1:19 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Tape Drive not Detected
I was having the same thoughts as I was reading the original post, even
going so far as to glance back at a spare 2749 on my credenza.
"IF" you managed to connect the cables up with a 2749, and I'm not sure
there is a cable that would properly connect due to the ends being
different, I'll bet Roberto is correct. Fried green tape drive unit.
Now there is a 5702 card that's not reporting in your config below and I'm
guessing if you cabled it with the cables that came off the tape device on
the P5 box you might be OK. What we don't know is if those cards are not
reporting due to card placement with respect the controlling IOP or not.
The IOP would appear to be reporting in so I'll guess it's card placements
that are the problem or you don't have another IOP to drive the tape
controller and the base IOP is full.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Roberto José Etcheverry Romero
Sent: Wednesday, November 26, 2014 11:52 AM
To: Midrange Systems Technical Discussion
Subject: Re: Tape Drive not Detected
Just to start, you might have fried the LTO4 drive. The 2749 is an HVD
controller not an LVD one. Mixing HVD with LVD never ends well... And wait,
the 2749 does NOT have 2 ports, it's a single port HVD controller...
weird...
You need either a 5702 or 571A controller to drive the LTO4, of course you
have to hang that IOA under an IOP for LTO usage. Read the PCI/PCI-X
placement rules redbook for locations and requirements on building a config
for the 810.
Best Regards,
Roberto
On Wed, Nov 26, 2014 at 2:42 PM, Brian Piotrowski <
bpiotrowski@xxxxxxxxxxxxxxx<mailto:bpiotrowski@xxxxxxxxxxxxxxx>> wrote:
Hi All,
I'm having an issue with connecting a tape drive to our iSeries box.
The box is a 9406-810 (yes, yes I know it's old, but I need to back it
up and restore it to the new server). The tape drive I have is a
3580-L43 single tape drive SCSI ID 0. The card I installed in the 810
is a 2749 which has two ports - SCSI ID 0, SCSI ID 1. I originally
removed this card from an
i520 box and installed it in slot C02 on the 810. I connected the LVD
cable from the LTO drive to SCSI PORT ID 1 on the interface card.
When I IPLed the system I would normally expect to see the tape drive
there when I do a WRKDEVD *TAP. However, there are no tape drives
present which would lead me to believe it might be misconfigured or I
am
missing something.
Anyone have any ideas where I should start? I went into SST and
looked under packaging resources and there are two tape units listed
there, but neither of them are the model that I have (they are listed
as 3580-003 and
3580-001 - checking the serial number on both shows neither of them
are the device I am trying to set up).
Looking into the failed and non-reporting logical hardware resources I
see these items:
Description Type-model Status Resource Name
Storage IOA ? 5702-001 Unknown DC04
Storage IOA ? 2749-001 Unknown DC03
Tape Unit ? 3580-003 Unknown TAP03
Tape Unit ? 3580-001 Unknown TAP04
I'm a bit stuck on how to proceed....what are my next steps to try and
get this resolved so I can get the LTO operational?
Thankee-sai!
/b;
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Manager - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x5995
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com<http://www.simcoeparts.com/<http://www.simc
oeparts.com%3chttp:/www.simcoeparts.com/>>
Please consider the environment. Don't print this e-mail unless you
really need to.
The information contained in this communication is confidential and
intended only for the use of those to whom it is addressed. If you
have received this communication in error, please notify me by
telephone (collect if necessary) and delete or destroy any copies of it.
Thank you!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx<mailto: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<mailto: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<mailto:
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<mailto:
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<mailto:
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<mailto:
MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to
review the archives at http://archive.midrange.com/midrange-l.
-----
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2015.0.5577 / Virus Database: 4223/8629 - Release Date: 11/25/14
--
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.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
