Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Apr 1996 19:39:26 -0500 (CDT)
From:      peter@taronga.com (Peter da Silva)
To:        hackers@freebsd.org
Subject:   Archive Anaconda on 1540B -- waiting forever for tape to become ready
Message-ID:  <199604210039.TAA00757@bonkers.taronga.com>

index | next in thread | raw e-mail

Well, I followed the advice of various FreeBSD hackers and got an Archive
Anaconda from CSC.  Unfortunately, the cable I bought at the same time was
flakey (when I'm using it /dev/sd1 isn't even recognised by my controller,
just switch back to my old cable everything's fine... but I've only got 4
connectors on it) so I've got it on my old Adaptec 1540B. It seems to come
up and be recognised fine:

Apr 20 19:09:14 bonkers /kernel: FreeBSD 2.0.5-RELEASE #0: Sat Apr 20 19:06:11 CDT 1996
Apr 20 19:09:14 bonkers /kernel:     root@bonkers.taronga.com:/usr/src/sys/compile/BONK
Apr 20 19:09:14 bonkers /kernel: CPU: i486 DX2 (486-class CPU)
Apr 20 19:09:14 bonkers /kernel:   Origin = "GenuineIntel"  Id = 0x435  Stepping=5
Apr 20 19:09:14 bonkers /kernel:   Features=0x3<FPU,VME>
Apr 20 19:09:14 bonkers /kernel: real memory  = 16384000 (4000 pages)
Apr 20 19:09:14 bonkers /kernel: avail memory = 14897152 (3637 pages)
...
Apr 20 19:09:15 bonkers /kernel: aha0 at 0x334-0x337 irq 15 drq 7 on isa
Apr 20 19:09:15 bonkers /kernel: aha0 waiting for scsi devices to settle
Apr 20 19:09:15 bonkers /kernel: (aha0:5:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2
Apr 20 19:09:15 bonkers /kernel: st0(aha0:5:0): Sequential-Access density code 0x0,  drive empty
...

Later on I tried to write a tape (brand new Maxell 9135) and got this:

Apr 20 19:14:29 bonkers /kernel: st0(aha0:5:0): NOT READY asc:4,1
Apr 20 19:14:29 bonkers /kernel: st0(aha0:5:0):  Logical unit is in process of becoming ready

At this point no matter how long I try it doesn't see the tape. I stuck
an old DC6150 in there and it came back with "Error 0" but no kernel
messages. Someone mentioned a patch to the NCR driver to get it to work
right with this drive. Possibly the AHA driver needs a similar patch?

Or could I just have bought a bad drive?


help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604210039.TAA00757>