Networker

Re: [Networker] New hardware & Networker config issues

2004-07-12 18:48:34
Subject: Re: [Networker] New hardware & Networker config issues
From: Tim Mooney <mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Mon, 12 Jul 2004 17:48:21 -0500
In regard to: [Networker] New hardware & Networker config issues, Clark,...:

I put the following lines into the st.conf file per HP's information
tape-config-list =
"HP Ultrium", "HP Ultrium", "ULTRIUM";
ULTRIUM = 1, 0x36, 0, 0xd639, 4, 0x00, 0x00, 0x00, 0x42, 3;
name = "st" class = "scsi" target = 1 lun = 0;
name = "st" class = "scsi" target = 2 lun = 0;

I'm surprised you need that, I would think that st for Solaris 9 would
have it.  You can run strings on the st driver and see if there's anything
there that matches:

$strings /kernel/drv/st | egrep -i hp
st_media_watch_cb: unknown drive type %d, default to ST_TYPE_HP
st_media_watch_cb: ST_TYPE_HP
HP      88780
HP      HP35470A
HP      HP35480A
HP      C1533A
HP      C1537A
HP      C1557A
HP      C5683A
HP      C7438A
HP      Ultrium 2*
HP      Ultrium 1*
HP      C5713A
HP-88780 1/2" Reel
HP 35470A 4mm DAT
HP 35480A 4mm DAT
HP JetStore 6000 C1533
HP DDS-3 4MM DAT
HP DDS-3 4MM DAT loader
HP DDS-4 DAT (Sun)
HP DAT-72
HP Ultrium LTO 2
HP Ultrium LTO
HP DDS-4 DAT (Sun)



That's on a Solaris 8 box with recent patches, I would think 9 would
be the same or better.

Jul 12 15:30:23 devtest root: [ID 702911 daemon.notice] NetWorker media:
(warning) /dev/rmt/1cbn reading: read open error: drive status is Drive repo
rts no error - but state is unknown
Jul 12 15:30:26 devtest scsi: [ID 107833 kern.warning] WARNING:
/pci@1d,700000/pci@2/scsi@5 (qus1):
Jul 12 15:30:26 devtest        Target synch. rate reduced. tgt 1 lun 0
Jul 12 15:30:26 devtest scsi: [ID 107833 kern.warning] WARNING:

The question is...Where do I begin?  My old v6.0.3 w/DLT7000 on Solaris v7
hums along and provides no clues.

Begin by using the tapes directly from the OS.  For example, try using
ufsdump for a large partition, and see if the dump succeeds.  If it
does, try browsing it with ufsrestore.

It looks to me like you have SCSI issues, either related to the st/driver
settings or at a lower level (hardware, cables, termination, etc).

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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

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