From owner-freebsd-scsi Sun Apr 21 07:12:27 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id HAA19803
for freebsd-scsi-outgoing; Sun, 21 Apr 1996 07:12:27 -0700 (PDT)
Received: (from jmb@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id HAA19797
Sun, 21 Apr 1996 07:12:25 -0700 (PDT)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199604211412.HAA19797@freefall.freebsd.org>
Subject: Re: Archive Anaconda on 1540B -- waiting forever for tape to become ready
To: peter@taronga.com (Peter da Silva)
Date: Sun, 21 Apr 1996 07:12:25 -0700 (PDT)
Cc: scsi@freebsd.org
In-Reply-To: <199604210600.BAA05138@bonkers.taronga.com> from "Peter da Silva" at Apr 21, 96 01:00:00 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
Peter da Silva wrote:
>
> > is this a brand new blank tape? never before used?
> > if so you have to "force" the tape. try "mt -f /dev/rst0 fsf 1"
> > for me that results in
> > "st0(ncr1:4:0): HARDWARE FAILURE info:1 asc:80,8a"
> > but afterward mt operations work!
>
> That got it to do something, and the status worked, so I decided to
> try tarring some stuff to it. Now I get:
>
> Apr 21 00:50:32 bonkers /kernel: st0(aha0:5:0): HARDWARE FAILURE info:1 asc:80,8a
> Apr 21 00:53:34 bonkers /kernel: st0(aha0:5:0): timed out
>
this message appears only once in the aha1542.c code, in the function
aha_timeout(). stefan esser added to the ncr.c code to deal with
time outs by extending the interval for command completion.
the timeout was extended from 4 to 1200 (which is 20 minutes, if
i remember correctly that the units are seconds.)
the timeout is part of the struct scsi_xfer and is set in scsi_base.c
BUT this is kermel code version dependent. so what are you
running?
this should go to the scsi mailing list, i am going to cc: it
there and remove -hackers from the list
--
Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG
FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/
From owner-freebsd-scsi Sun Apr 21 08:06:54 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id IAA21864
for freebsd-scsi-outgoing; Sun, 21 Apr 1996 08:06:54 -0700 (PDT)
Received: from sbac.edu (r2d3.sbac.edu [150.104.65.1])
by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA21858
Sun, 21 Apr 1996 08:06:49 -0700 (PDT)
Received: from melissa (cs1dial1.sbac.edu [150.104.65.11]) by sbac.edu (8.6.11/8.6.11) with SMTP id KAA40565; Sun, 21 Apr 1996 10:52:11 -0400
Date: Sun, 21 Apr 1996 11:07:14 -0400 ()
From: Dan Cromer <cromerdh@sbac.edu>
To: "Jordan K. Hubbard" <jkh@FreeBSD.org>
cc: freebsd-scsi@FreeBSD.org
Subject: Re: Problem with Buslogic(?) kernel panic
In-Reply-To: <317832F4.2781E494@FreeBSD.org>
Message-ID: <Pine.WNT.3.92.960421110258.-1014083B-100000@melissa>
X-Sender: cromerdh@r2d3.sbac.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk
Jordan was right, the bt0 driver is handling SCSI connection fine. I
just had to learn that /cdrom had the noauto option in fstab and needed to
mount it manually. OK, now why is "pig" in apropos and man, but not in
/usr/local/bin? Just kidding :-)
Dan
On Fri, 19 Apr 1996, Jordan K. Hubbard wrote:
> Dan Cromer wrote:
> > fine (from Toshiba 3401 SCSI), but at reboot I get last lines:
> > pci0:20 Buslogic, device=0x1040, class=storage (SCSI) [no driver
> > assigned]
>
> Not the problem - this is just informational (there's no PCI driver for
> the Bt946c - it's handled using the generic Buslogic ISA/EISA/VLB/PCI
> driver).
>
> > changing root device to sd1a
> > panic: cannot mount root
>
> Are you using a boot manager? How are you booting this second drive?
> Is there also an IDE drive in this system, perhaps? What happens if you
> type: sd(1,a)/kernel at the `boot:' prompt?
> --
> - Jordan Hubbard
> President, FreeBSD Project
>
From owner-freebsd-scsi Sun Apr 21 10:45:49 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id KAA27266
for freebsd-scsi-outgoing; Sun, 21 Apr 1996 10:45:49 -0700 (PDT)
Received: from cicerone.uunet.ca (cicerone.uunet.ca [142.77.1.11])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA27250
Sun, 21 Apr 1996 10:45:45 -0700 (PDT)
Received: from why ([205.150.249.1]) by cicerone.uunet.ca with SMTP id <177091-2>; Sun, 21 Apr 1996 13:45:25 -0400
Date: Sun, 21 Apr 1996 13:45:18 -0400
From: Andrew Herdman <andrew@whine.com>
X-Sender: andrew@why
To: questions@freebsd.org
cc: scsi@freebsd.org
Subject: Re: Problems with the st driver in 2.2-960323-SNAP
In-Reply-To: <Pine.BSF.3.91.960417194140.1018A-100000@why>
Message-ID: <Pine.BSF.3.91.960421134255.192A-100000@why>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
After some considerable poking around in the scsi code I found the
following changes in st.c were causing the problem.
in
st_open:
scsi_prevent(sc_link, PR_PREVENT, 0); /* who cares if it fails? */
and
st_close:
scsi_prevent(sc_link, PR_ALLOW, SCSI_SILENT);
Now I do agree that calling this function is appropriate. But it doesn't
seem to work properly. I'm not a scsi expert so I'm not sure why it fails.
Andrew
On Wed, 17 Apr 1996, Andrew Herdman wrote:
> After upgrading to the recent snap, I have been having problems with my
> Archive Python 4mm Dat drive on a buslogics 946c and the nrst device.
>
> Using tar i can do the following:
>
> tar cf /dev/nrst0 /dir1
> tar cf /dev/nrst0 /dir2
> tar cf /dev/nrst0 /dir3
> mt -f /dev/rst0 rewind
>
> tar tvf /dev/nrst0
> <lists files from /dir1>
> tar tvf /dev/nrst0
> <does nothing>
> tar tvf /dev/nrst0
> <lists files from /dir2>
> tar tvf /dev/nrst0
> <does nothing>
> tar tvf /dev/nrst0
> <lists files from /dir3>
>
> Using dump, i get the following:
>
> # dump 9uBf 2000000 /dev/nrst0 /dev/rsd0a
> DUMP: Date of this level 9 dump: Wed Apr 17 19:41:25 1996
> DUMP: Date of last level 0 dump: Sat Apr 13 08:09:32 1996
> DUMP: Dumping /dev/rsd0a (/) to /dev/nrst0
> DUMP: mapping (Pass I) [regular files]
> DUMP: mapping (Pass II) [directories]
> DUMP: estimated 15855 tape blocks on 0.01 tape(s).
> DUMP: dumping (Pass III) [directories]
> DUMP: dumping (Pass IV) [regular files]
> DUMP: DUMP: 15882 tape blocks on 1 volumes(s)
> DUMP: finished in 92 seconds, throughput 172 KBytes/sec
> DUMP: level 9 dump on Wed Apr 17 19:41:25 1996
> DUMP: Closing /dev/nrst0
> st0: not ready
> DUMP: DUMP IS DONE
>
>
> If I do multiple dumps on one tape it rewinds to the beginning and erases
> the previous dump (not a very effective backup system ;). This all
> worked perfectly fine with 2.1.0-RELEASE. I've been poking thru the
> kernel sources (doing diff's between the 2 kernel sources) and haven't
> found anything yet. Is this a known problem? Would the people working
> on this area contact me, I'd like to help as much as I can to help solve
> the problem.
>
> Thanks
> Andrew
>
>
From owner-freebsd-scsi Sun Apr 21 17:18:02 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id RAA23535
for freebsd-scsi-outgoing; Sun, 21 Apr 1996 17:18:02 -0700 (PDT)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA23519
Sun, 21 Apr 1996 17:18:00 -0700 (PDT)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id LAA18183; Sun, 21 Apr 1996 11:14:18 -0700 (PDT)
Message-Id: <199604211814.LAA18183@ref.tfs.com>
Subject: Re: Problems with the st driver in 2.2-960323-SNAP
To: andrew@whine.com (Andrew Herdman)
Date: Sun, 21 Apr 1996 11:14:18 -0700 (PDT)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: questions@freebsd.org, scsi@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960421134255.192A-100000@why> from "Andrew Herdman" at Apr 21, 96 01:45:18 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
>
> After some considerable poking around in the scsi code I found the
> following changes in st.c were causing the problem.
>
> in
>
> st_open:
>
> scsi_prevent(sc_link, PR_PREVENT, 0); /* who cares if it fails? */
>
> and
>
> st_close:
>
> scsi_prevent(sc_link, PR_ALLOW, SCSI_SILENT);
>
> Now I do agree that calling this function is appropriate. But it doesn't
> seem to work properly. I'm not a scsi expert so I'm not sure why it fails.
>
> Andrew
>
hmmm this is a semantic change that was introduced recently...
prior to this, a 'mount session' lasted until you explicitly
ended it by unloading the tape (or using the rst device instead of the nrst
device.) Recently it was decided that if the device was closed, then the]
user should have the option of ending the session by pressing the 'eject'
button. This would have the effect of causing a mount session reset at
the next open. In effect it would be the same as retrospectively
changing the last close to a close and unmount.
>
> On Wed, 17 Apr 1996, Andrew Herdman wrote:
>
> > After upgrading to the recent snap, I have been having problems with my
> > Archive Python 4mm Dat drive on a buslogics 946c and the nrst device.
> >
> > Using tar i can do the following:
> >
> > tar cf /dev/nrst0 /dir1
> > tar cf /dev/nrst0 /dir2
> > tar cf /dev/nrst0 /dir3
> > mt -f /dev/rst0 rewind
> >
> > tar tvf /dev/nrst0
> > <lists files from /dir1>
> > tar tvf /dev/nrst0
> > <does nothing>
this is expected.. what happens is:
tar reads until it sees it's EOF record, and stops reading..
IT HAS NOT YET READ IN THE TAPE EOF MARKER
the next read will IMMEDIATLY HIT THAT EOF MARKER and return eof.
This is documented somewhere.. I think psooibly in the tar man page..
> > tar tvf /dev/nrst0
> > <lists files from /dir2>
> > tar tvf /dev/nrst0
> > <does nothing>
> > tar tvf /dev/nrst0
> > <lists files from /dir3>
> >
> > Using dump, i get the following:
> >
> > # dump 9uBf 2000000 /dev/nrst0 /dev/rsd0a
> > DUMP: Date of this level 9 dump: Wed Apr 17 19:41:25 1996
> > DUMP: Date of last level 0 dump: Sat Apr 13 08:09:32 1996
> > DUMP: Dumping /dev/rsd0a (/) to /dev/nrst0
> > DUMP: mapping (Pass I) [regular files]
> > DUMP: mapping (Pass II) [directories]
> > DUMP: estimated 15855 tape blocks on 0.01 tape(s).
> > DUMP: dumping (Pass III) [directories]
> > DUMP: dumping (Pass IV) [regular files]
> > DUMP: DUMP: 15882 tape blocks on 1 volumes(s)
> > DUMP: finished in 92 seconds, throughput 172 KBytes/sec
> > DUMP: level 9 dump on Wed Apr 17 19:41:25 1996
> > DUMP: Closing /dev/nrst0
> > st0: not ready
> > DUMP: DUMP IS DONE
I think that the call device close() on LAST CLOSE might be broken..
dump uses several processes.. possibly
the first to finish closes the device and the others also try,
but it's already being closed.. ?
> >
> >
> > If I do multiple dumps on one tape it rewinds to the beginning and erases
> > the previous dump (not a very effective backup system ;). This all
> > worked perfectly fine with 2.1.0-RELEASE. I've been poking thru the
> > kernel sources (doing diff's between the 2 kernel sources) and haven't
> > found anything yet. Is this a known problem? Would the people working
> > on this area contact me, I'd like to help as much as I can to help solve
> > the problem.
I think you could safely remove the lines in question...
I'm not sure why it fails though.. they ar valid commands..
> >
> > Thanks
> > Andrew
> >
> >
>
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@tfs.com +------>x USA \ in a very strange
| ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country !
+- X_.---._/ USA+(510) 645-3137(wk) \_/ \\ ><DARWIN>
v LL LL
From owner-freebsd-scsi Sun Apr 21 19:59:58 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id TAA03687
for freebsd-scsi-outgoing; Sun, 21 Apr 1996 19:59:58 -0700 (PDT)
Received: from phantasma.bevc.blacksburg.va.us (root@phantasma.bevc.blacksburg.va.us [198.82.200.65])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA03680
for <scsi@freebsd.org>; Sun, 21 Apr 1996 19:59:55 -0700 (PDT)
Received: (from kmitch@localhost) by phantasma.bevc.blacksburg.va.us (8.7.5/8.7.3) id WAA01811; Sun, 21 Apr 1996 22:59:50 -0400 (EDT)
Date: Sun, 21 Apr 1996 22:59:50 -0400 (EDT)
From: Keith Mitchell <kmitch@phantasma.bevc.blacksburg.va.us>
Message-Id: <199604220259.WAA01811@phantasma.bevc.blacksburg.va.us>
To: julian@ref.tfs.com (JULIAN Elischer)
Cc: scsi@freebsd.org
Subject: Re: Problems with the st driver in 2.2-960323-SNAP
X-Newsreader: TIN [version 1.2 PL2]
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
In article <199604211814.LAA18183@ref.tfs.com> you wrote:
: hmmm this is a semantic change that was introduced recently...
: prior to this, a 'mount session' lasted until you explicitly
: ended it by unloading the tape (or using the rst device instead of the nrst
: device.) Recently it was decided that if the device was closed, then the]
: user should have the option of ending the session by pressing the 'eject'
: button. This would have the effect of causing a mount session reset at
: the next open. In effect it would be the same as retrospectively
: changing the last close to a close and unmount.
I see the same problem (only with Adaptec 2940/Archive Python), but it does
not happen *ALL* of the time. Maybe once or twice a week during the nightly
backup. So whatever the problem is, it seems to be intermittant (at least
for me). I was running -current from 3/31 until yesterday when I recompiled.
I haven't seen the problem yet with the 4/20 -current, but it has only backed
up once.
From owner-freebsd-scsi Mon Apr 22 05:23:10 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id FAA01594
for freebsd-scsi-outgoing; Mon, 22 Apr 1996 05:23:10 -0700 (PDT)
Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA01589
for <scsi@freebsd.org>; Mon, 22 Apr 1996 05:23:08 -0700 (PDT)
Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id GAA18513 for scsi@freebsd.org; Mon, 22 Apr 1996 06:32:01 -0500 (CDT)
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id GAA14220; Mon, 22 Apr 1996 06:24:17 -0500
Date: Mon, 22 Apr 1996 06:24:17 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199604221124.GAA14220@bonkers.taronga.com>
To: scsi@freebsd.org
Subject: Problems with Archive Anaconda...
References: <199604220259.WAA01811@phantasma.bevc.blacksburg.va.us>
Organization: I can usually find things six months later without looking
for them. That's organized enough for me.
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
Julian Elischer wrote:
> hmmm this is a semantic change that was introduced recently...
> prior to this, a 'mount session' lasted until you explicitly
> ended it by unloading the tape (or using the rst device instead of the nrst
> device.) Recently it was decided that if the device was closed, then the]
> user should have the option of ending the session by pressing the 'eject'
> button. This would have the effect of causing a mount session reset at
> the next open. In effect it would be the same as retrospectively
> changing the last close to a close and unmount.
Ah! I was wondering why I couldn't eject a tape that wasn't open on my
new Archive Anaconda. That explains it. Thanks for changing the semantics
there, even if I'll have to upgrade to take advantage of it...
Anyway, I've got some problems withthis drive, and I've been respectfully
informed that FreeBSD-SCSI is the place to bring them up.
First of all, I have to do the following sequence (thanks for the help
figuring it out!) to load a new tape:
Insert the tape.
Eject the tape.
Insert the tape. Drive spins.
Run "mt -f /dev/rst0 fsf 1". Drive spins. Error message.
Eject the tape.
Insert the tape.
FreeBSD 2.0.5, Adaptec 1540B, Archive Anaconda:
(aha0:5:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2
st0(aha0:5:0): Sequential-Access density code 0x0, drive empty
If I skip the various steps I get the following results:
First insert and eject:
st0(aha0:5:0): NOT READY asc:4,1
st0(aha0:5:0): Logical unit is in process of becoming ready
Doesn't matter how long I wait.
Don't mt -f /dev/rst0 fsf 1:
st0(aha0:5:0): MEDIUM ERROR info:2b4 asc:c,0 Write error
st0(aha0:5:0): MEDIUM ERROR asc:c,0 Write error
Doesn't matter how often I try, it does this.
Don't eject after this:
This seems to lock the device. I can't open the device,
it says it's busy, but nothing has it open. It's like
the SCSI or tape driver is wedged somewhere. Sometimes
one of my attempts to open the device after this *will*
hang uninterruptably.
Also, it recognised DC600 tapes (I put the tape in, do an mt status, and
it says it's a QIC-120) but can't read or write them.
Possibly I've just got a flakey drive. I'm going to buy an external SCSI
enclosure so I can try it on my Bt747, but that can't be until the next
paycheck (it's not a total waste of money: I need the enclosure for other
stuff), but if the drive's flakey I'd rather not. Input?
From owner-freebsd-scsi Mon Apr 22 20:09:26 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id UAA23497
for freebsd-scsi-outgoing; Mon, 22 Apr 1996 20:09:26 -0700 (PDT)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA23481
for <scsi@FreeBSD.ORG>; Mon, 22 Apr 1996 20:09:17 -0700 (PDT)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id FAA19124; Tue, 23 Apr 1996 05:09:12 +0200
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
id FAA05236; Tue, 23 Apr 1996 05:09:10 +0200
Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id FAA20816; Tue, 23 Apr 1996 05:05:21 +0200 (MET DST)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199604230305.FAA20816@uriah.heep.sax.de>
Subject: Re: Problems with Archive Anaconda...
To: peter@taronga.com (Peter da Silva)
Date: Tue, 23 Apr 1996 05:05:20 +0200 (MET DST)
Cc: scsi@FreeBSD.ORG
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199604221124.GAA14220@bonkers.taronga.com> from "Peter da Silva" at Apr 22, 96 06:24:17 am
X-Phone: +49-351-2012 669
X-Mailer: ELM [version 2.4 PL24 ME8a]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
As Peter da Silva wrote:
> First insert and eject:
> st0(aha0:5:0): NOT READY asc:4,1
> st0(aha0:5:0): Logical unit is in process of becoming ready
> Doesn't matter how long I wait.
>
> Don't mt -f /dev/rst0 fsf 1:
> st0(aha0:5:0): MEDIUM ERROR info:2b4 asc:c,0 Write error
> st0(aha0:5:0): MEDIUM ERROR asc:c,0 Write error
> Doesn't matter how often I try, it does this.
Time to get a SCSI reference manual for it from Archive?
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
From owner-freebsd-scsi Tue Apr 23 07:02:48 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id HAA04187
for freebsd-scsi-outgoing; Tue, 23 Apr 1996 07:02:48 -0700 (PDT)
Received: (from jmb@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id HAA04178
Tue, 23 Apr 1996 07:02:45 -0700 (PDT)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199604231402.HAA04178@freefall.freebsd.org>
Subject: Re: Problems with Archive Anaconda...
To: joerg_wunsch@uriah.heep.sax.de
Date: Tue, 23 Apr 1996 07:02:45 -0700 (PDT)
Cc: peter@taronga.com, scsi@FreeBSD.org
In-Reply-To: <199604230305.FAA20816@uriah.heep.sax.de> from "J Wunsch" at Apr 23, 96 05:05:20 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-scsi@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk
J Wunsch wrote:
>
> As Peter da Silva wrote:
>
> > First insert and eject:
> > st0(aha0:5:0): NOT READY asc:4,1
> > st0(aha0:5:0): Logical unit is in process of becoming ready
> > Doesn't matter how long I wait.
> >
> > Don't mt -f /dev/rst0 fsf 1:
> > st0(aha0:5:0): MEDIUM ERROR info:2b4 asc:c,0 Write error
> > st0(aha0:5:0): MEDIUM ERROR asc:c,0 Write error
> > Doesn't matter how often I try, it does this.
>
> Time to get a SCSI reference manual for it from Archive?
absolutely, if we can.
conner bought archive
seagate bought conner.
--
Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG
FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/
From owner-freebsd-scsi Wed Apr 24 19:17:41 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id TAA02473
for freebsd-scsi-outgoing; Wed, 24 Apr 1996 19:17:41 -0700 (PDT)
Received: from post.io.org (post.io.org [198.133.36.6])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA02463
for <freebsd-scsi@freebsd.org>; Wed, 24 Apr 1996 19:17:37 -0700 (PDT)
Received: from zot.io.org (taob@zot.io.org [198.133.36.82]) by post.io.org (8.7.5/8.7.3) with SMTP id WAA27261; Wed, 24 Apr 1996 22:18:25 -0400 (EDT)
Date: Wed, 24 Apr 1996 22:13:21 -0400 (EDT)
From: Brian Tao <taob@io.org>
To: FREEBSD-SCSI-L <freebsd-scsi@freebsd.org>, netbsd-help@netbsd.org
Subject: Tape library or DLT support in FreeBSD/NetBSD
Message-ID: <Pine.NEB.3.92.960424214031.19106A-100000@zot.io.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
What options do I have if I'm looking for hardware that will
allow me to backup 20 to 30 gigabytes of data unattended? Right now
I'm pondering the merits of tape libraries and autoloaders vs.
high-end DLT drives. On the one hand, tape changers may require
special software support for fully automated operation (I don't think
tar/pax/dump will change tapes for you... maybe amanda?), but they use
readily available media and provide a migration path from single-unit
DAT drives.. On the other hand, DLT is more expensive (both drive
hardware and media) and isn't as mature as DDS-2 technology, but it is
much faster that DAT and you only have to worry about the software
seeing one giant device.
Of prime importance is OS support for the unit. :) Has anyone
successfully used something like the HP C1553A or the Conner 4586NP
autoloaders? I have a script that uses FreeBSD's scsi(8) command to
change cartridges on the C1553A, but that still requires some sort of
operator intervention. Something like a DLT4000 unit would be great
if I can access it through /dev/nrst0 like any other SCSI tape drive.
Thanks in advance for any recommendations.
--
Brian Tao (BT300, taob@io.org)
Systems and Network Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"
From owner-freebsd-scsi Thu Apr 25 02:07:49 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id CAA26883
for freebsd-scsi-outgoing; Thu, 25 Apr 1996 02:07:49 -0700 (PDT)
Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA26869
for <freebsd-scsi@freebsd.org>; Thu, 25 Apr 1996 02:07:43 -0700 (PDT)
Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.4/8.7.3) with SMTP id EAA10006; Thu, 25 Apr 1996 04:07:46 -0500 (CDT)
Date: Thu, 25 Apr 1996 04:07:46 -0500 (CDT)
From: "Matthew N. Dodd" <winter@jurai.net>
X-Sender: winter@sasami
To: Brian Tao <taob@io.org>
cc: FREEBSD-SCSI-L <freebsd-scsi@freebsd.org>, netbsd-help@netbsd.org
Subject: Re: Tape library or DLT support in FreeBSD/NetBSD
In-Reply-To: <Pine.NEB.3.92.960424214031.19106A-100000@zot.io.org>
Message-ID: <Pine.BSI.3.93.960425040229.2318C-100000@sasami>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
On Wed, 24 Apr 1996, Brian Tao wrote:
> DAT drives.. On the other hand, DLT is more expensive (both drive
> hardware and media) and isn't as mature as DDS-2 technology, but it is
I would venture to say that DLT technology is older than DDS-2
technology. DEC was using TK-50s and TK-70s a LONG time ago...
In any event, someone on the freebsd lists was talking about
scsi tape changers and such and from what I remember of the
conversation, it would be possible to write code that would
issue the appropriate commands needed to cause the tape library
to load another tape. (someone kill that sentence for me)
> Of prime importance is OS support for the unit. :) Has anyone
> successfully used something like the HP C1553A or the Conner 4586NP
> autoloaders? I have a script that uses FreeBSD's scsi(8) command to
> change cartridges on the C1553A, but that still requires some sort of
> operator intervention. Something like a DLT4000 unit would be great
> if I can access it through /dev/nrst0 like any other SCSI tape drive.
> Thanks in advance for any recommendations.
I don't see why it shouldn't work... It would probably
be pretty straight forward to get Amanda to work with either solution.
Good luck, and have a good one.
| Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter |
| Technical Manager | mdodd@intersurf.net | http://www.intersurf.net |
| InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"|
From owner-freebsd-scsi Thu Apr 25 06:19:37 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id GAA08565
for freebsd-scsi-outgoing; Thu, 25 Apr 1996 06:19:37 -0700 (PDT)
Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA08559
for <scsi@freebsd.org>; Thu, 25 Apr 1996 06:19:35 -0700 (PDT)
Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id HAA09603 for scsi@freebsd.org; Thu, 25 Apr 1996 07:32:25 -0500 (CDT)
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA03629; Thu, 25 Apr 1996 07:22:25 -0500
Date: Thu, 25 Apr 1996 07:22:25 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199604251222.HAA03629@bonkers.taronga.com>
To: scsi@freebsd.org
Subject: Re: Tape library or DLT support in FreeBSD/NetBSD
In-Reply-To: <Pine.NEB.3.92.960424214031.19106A-100000@zot.io.org>
Organization: none
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
> What options do I have if I'm looking for hardware that will
>allow me to backup 20 to 30 gigabytes of data unattended?
First of all, with 30G of disk you're on easy street with about 1/4 of that
total tape if you're using Amanda. So a single DLT10/20 (10 real/20 compressed)
will work fine. You can get by with half that, so DAT 4/8 will do, barely,
but you won't have much room for expansion and Amanda will bitch a lot about
delayed saves. Go by the *uncompressed* size, since Amanda compresses/gzips
and generally does better than the compression on the drive.
We went with DLT at work, after looking into other options, and I'm glad
we did. It's now up to 40/80 so there's plenty of room for growth.
>On the other hand, DLT is more expensive (both drive
>hardware and media) and isn't as mature as DDS-2 technology, but it is
>much faster that DAT and you only have to worry about the software
>seeing one giant device.
I wouldn't say that DLT isn't mature. DEC's 1/2 inch cartridges date back
to the '80s. The TZ87 is really a linear (heh) descendent of the old TK70.
From owner-freebsd-scsi Thu Apr 25 10:54:18 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id KAA25180
for freebsd-scsi-outgoing; Thu, 25 Apr 1996 10:54:18 -0700 (PDT)
Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA25173
for <freebsd-scsi@freebsd.org>; Thu, 25 Apr 1996 10:54:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.4/8.6.12) with SMTP id KAA13834; Thu, 25 Apr 1996 10:52:39 -0700 (PDT)
Message-Id: <199604251752.KAA13834@lestat.nas.nasa.gov>
X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol
To: "Matthew N. Dodd" <winter@jurai.net>
Cc: Brian Tao <taob@io.org>, FREEBSD-SCSI-L <freebsd-scsi@freebsd.org>,
netbsd-help@netbsd.org
Subject: Re: Tape library or DLT support in FreeBSD/NetBSD
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Thu, 25 Apr 1996 10:52:38 -0700
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
On Thu, 25 Apr 1996 04:07:46 -0500 (CDT)
"Matthew N. Dodd" <winter@jurai.net> wrote:
> > Of prime importance is OS support for the unit. :) Has anyone
> > successfully used something like the HP C1553A or the Conner 4586NP
> > autoloaders? I have a script that uses FreeBSD's scsi(8) command to
> > change cartridges on the C1553A, but that still requires some sort of
> > operator intervention. Something like a DLT4000 unit would be great
> > if I can access it through /dev/nrst0 like any other SCSI tape drive.
> > Thanks in advance for any recommendations.
For the record, I wrote a new SCSI changer driver for NetBSD (and ported it
to FreeBSD, though I haven't submitted the PR to the FreeBSD guys, yet) and
userland program to control the changer. It's been thoroughly tested
under NetBSD-current and FreeBSD-2.1 with a Conner changer coupled with
an Archive Python DAT. On the particular changer I used, the tape drive
was at lun0 and the changer at lun1 (which caused at least a little
trouble, given the autoconfiguration scheme employed by the FreeBSD SCSI
code, but is work-around-able).
The new ch driver should work with any model of SCSI changer that follows
the SCSI changer spec. For users of NetBSD-current, see the chio(1)
manual page.
> I don't see why it shouldn't work... It would probably
> be pretty straight forward to get Amanda to work with either solution.
The fellow I wrote the driver for is using it for automated backups, and
it's working Great. Using the FreeBSD scsi(8) command is sort of ugly
for manipulating a changer, since there's nothing there to keep state for
you. The new ch driver takes care of all of this.
Anyhow, I'll try and get the FreeBSD version packaged up and sent off today.
--------------------------------------------------------------------------
Jason R. Thorpe thorpej@nas.nasa.gov
NASA Ames Research Center Home: 408.866.1912
NAS: M/S 258-6 Work: 415.604.0935
Moffett Field, CA 94035 Pager: 415.428.6939
From owner-freebsd-scsi Sat Apr 27 16:17:51 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id QAA14862
for freebsd-scsi-outgoing; Sat, 27 Apr 1996 16:17:51 -0700 (PDT)
Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA14856
for <scsi@freebsd.org>; Sat, 27 Apr 1996 16:17:48 -0700 (PDT)
Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id SAA23375 for scsi@freebsd.org; Sat, 27 Apr 1996 18:02:54 -0500 (CDT)
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id RAA01804 for scsi@freebsd.org; Sat, 27 Apr 1996 17:49:59 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199604272249.RAA01804@bonkers.taronga.com>
Subject: Adaptec 1542, Adaptec 1742, Bustek 747, Archive Viper, Help?
To: scsi@freebsd.org
Date: Sat, 27 Apr 1996 17:49:58 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
OK, I've got on hand:
1 (one) Bustek 747.
1 (one) Adaptec 1540B.
1 (one) Adaptec 1742A.
1 (one) Archive Viper.
I don't have a SCSI cable with enough connectors to put the Viper on the
747.
When I have it on the 1540B, I get fatal write errors halfway through the
tape. About halfway. It's not predictable. (already posted about this)
I've tried multiple tapes. Same results, but in different places. The tapes
can't *all* be bad. I got the drive and tapes from CSC.
When I try to install the 1742 as a second controller, it interferes with
the 747. No matter what EISA config I set, if the 1742 is enabled the Bustek
BIOS tried to drive it as a Bustek. I don't understand EISA config that
well, so I could simply be thick.
Help? I'll be happy to supply any and all details.
FreeBSD 2.0.5-RELEASE #0: Sat Apr 27 10:26:49 CDT 1996
peter@bonkers.taronga.com:/usr/src/sys/compile/BONK
CPU: i486 DX2 (486-class CPU)
Origin = "GenuineIntel" Id = 0x435 Stepping=5
Features=0x3<FPU,VME>
real memory = 16384000 (4000 pages)
avail memory = 14917632 (3642 pages)
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16450
sio2 at 0x3e8-0x3ef irq 5 on isa
sio2: type 16550A
sio3 at 0x2e8-0x2ef irq 9 on isa
sio3: type 16550A
sio4 at 0x2a0-0x2a7 flags 0x705 on isa
sio4: type 16550A (multiport)
sio5 at 0x2a8-0x2af flags 0x705 on isa
sio5: type 16550A (multiport)
sio6 at 0x2b0-0x2b7 flags 0x705 on isa
sio6: type 16550A (multiport)
sio7 at 0x2b8-0x2bf irq 10 flags 0x705 on isa
sio7: type 16550A (multiport master)
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
fd1: 1.2MB 5.25in
bt0: Bt747 / 0-PCI/EISA/VLB(32bit) bus
bt0: reading board settings, busmastering, int=12
bt0: version 3.37, fast sync, parity, 32 mbxs, 32 ccbs
bt0: targ 0 sync rate= 5.00MB/s(200ns), offset=15
bt0: targ 1 sync rate= 5.00MB/s(200ns), offset=15
bt0: targ 6 sync rate= 4.54MB/s(220ns), offset=15
bt0: Enabling Round robin scheme
bt0 at 0x330 irq 12 on isa
bt0 waiting for scsi devices to settle
(bt0:0:0): "FUJITSU M2684S-512 2039" type 0 fixed SCSI 2
sd0(bt0:0:0): Direct-Access 507MB (1039329 512 byte sectors)
(bt0:1:0): "QUANTUM PD1800S 3162" type 0 fixed SCSI 2
sd1(bt0:1:0): Direct-Access 1717MB (3517856 512 byte sectors)
(bt0:6:0): "TOSHIBA CD-ROM XM-3401TA 2873" type 5 removable SCSI 2
cd0(bt0:6:0): CD-ROM cd present.[41150 x 2048 byte records]
ahb0 not found
aha0 at 0x334-0x337 irq 15 drq 7 on isa
aha0 waiting for scsi devices to settle
(aha0:5:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2
st0(aha0:5:0): Sequential-Access density code 0x0, drive empty
npx0 on motherboard
npx0: INT 16 interface
sb0 at 0x220 irq 3 drq 1 on isa
sb0: <SoundBlaster 2.2>
opl0 at 0x388 on isa
opl0: <Yamaha 2-OP FM>
From owner-freebsd-scsi Sat Apr 27 18:59:00 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id SAA24691
for freebsd-scsi-outgoing; Sat, 27 Apr 1996 18:59:00 -0700 (PDT)
Received: (from jmb@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id SAA24683
Sat, 27 Apr 1996 18:58:58 -0700 (PDT)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199604280158.SAA24683@freefall.freebsd.org>
Subject: Re: Adaptec 1542, Adaptec 1742, Bustek 747, Archive Viper, Help?
To: peter@taronga.com (Peter da Silva)
Date: Sat, 27 Apr 1996 18:58:58 -0700 (PDT)
Cc: scsi@freebsd.org
In-Reply-To: <199604272249.RAA01804@bonkers.taronga.com> from "Peter da Silva" at Apr 27, 96 05:49:58 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
Peter da Silva wrote:
>
> OK, I've got on hand:
>
> 1 (one) Bustek 747.
> 1 (one) Adaptec 1540B.
> 1 (one) Adaptec 1742A.
> 1 (one) Archive Viper.
Peter, i may be missing something obvious here. your boot messges
for the archive viper are identical to mine for the archive anaconda!
yours:
(aha0:5:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2
st0(aha0:5:0): Sequential-Access density code 0x0, drive empty
mine:
(ncr1:4:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2
st0(ncr1:4:0): Sequential-Access
st0(ncr1:4:0): 200ns (5 Mb/sec) offset 8.
>
> I don't have a SCSI cable with enough connectors to put the Viper on the
> 747.
>
> When I have it on the 1540B, I get fatal write errors halfway through the
> tape. About halfway. It's not predictable. (already posted about this)
>
can you post the syslog messags and the command line that
you are using?
> I've tried multiple tapes. Same results, but in different places. The tapes
> can't *all* be bad. I got the drive and tapes from CSC.
--
Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG
FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/
From owner-freebsd-scsi Sat Apr 27 20:19:45 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id UAA29904
for freebsd-scsi-outgoing; Sat, 27 Apr 1996 20:19:45 -0700 (PDT)
Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3])
by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA29878
Sat, 27 Apr 1996 20:19:42 -0700 (PDT)
Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id VAA08000; Sat, 27 Apr 1996 21:18:06 -0500 (CDT)
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id VAA04791; Sat, 27 Apr 1996 21:11:55 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199604280211.VAA04791@bonkers.taronga.com>
Subject: Re: Adaptec 1542, Adaptec 1742, Bustek 747, Archive Viper, Help?
To: jmb@freefall.freebsd.org (Jonathan M. Bresler)
Date: Sat, 27 Apr 1996 21:11:54 -0500 (CDT)
Cc: peter@taronga.com, scsi@freebsd.org
In-Reply-To: <199604280158.SAA24683@freefall.freebsd.org> from "Jonathan M. Bresler" at Apr 27, 96 06:58:58 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
> Peter, i may be missing something obvious here. your boot messges
> for the archive viper are identical to mine for the archive anaconda!
My head exploded or something. I meant Anaconda.
> can you post the syslog messags and the command line that
> you are using?
I already sent them to the hackers group last week, let me see if they're still
in my news spool.
tar cvfB /dev/nrst0 /
only got 412057600 bytes
st0(aha0:5:0): MEDIUM ERROR info:2b8 asc:c,0 Write error
st0(aha0:5:0): MEDIUM ERROR asc:c,0 Write error
Got the same result with
dd if=/dev/zero of=/dev/nrst0 bs=10k
And like I said, it's with 5 consecutive brand new unused tapes (either they're
new or someone did a hell of a bulk-erase job).