Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Jun 1996 07:56:38 -0400 (EDT)
From:      "Amir Y. Rosenblatt" <amir@neuron.net>
To:        freebsd-questions@freebsd.org
Subject:   SCSI Bus weirdness
Message-ID:  <199606141156.HAA00577@prozac.neuron.net>

next in thread | raw e-mail | index | archive | help
At 5 am, when my machine tried to do its nightly dump of all the 
filesystems it apparently choked in  alarge way on the tape drive.  The 
machine is a Pentium 120 with 64 meg of RAM, and Adaptec 2940UW, a pair 
of 2.1 gig F/W Seagate Baraccudas, and an HP C1533A 4mm DAT drive.  The 
machine was fine last night but it seemed to have hung over night -- 
this morning it wouldn;t show anything on screen -- no response to 
keyboard or mouse movements at all.  The following has been culled from 
my messages file (target 3 in the messages is the tape drive):

Jun 14 05:12:49 prozac /kernel: ahc0: target 3, lun 0 (st0) timed out
Jun 14 05:12:50 prozac /kernel: st0(ahc0:3:0): BUS DEVICE RESET message 
queued.
Jun 14 05:13:04 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:13:17 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:15:07 prozac /kernel: ahc0: target 3, lun 0 (st0) timed out
Jun 14 05:15:08 prozac /kernel: st0(ahc0:3:0): BUS DEVICE RESET message 
queued.
Jun 14 05:15:54 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:16:06 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:17:57 prozac /kernel: ahc0: target 3, lun 0 (st0) timed out
Jun 14 05:17:58 prozac /kernel: st0(ahc0:3:0): BUS DEVICE RESET message 
queued.
Jun 14 05:23:44 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:23:54 prozac /kernel: st0(ahc0:3:0): NOT READY asc:4,1
Jun 14 05:23:54 prozac /kernel: st0(ahc0:3:0):  Logical unit is in 
process of becoming ready
Jun 14 05:25:46 prozac /kernel: ahc0: target 3, lun 0 (st0) timed out
Jun 14 05:25:47 prozac /kernel: st0(ahc0:3:0): BUS DEVICE RESET message 
queued.
Jun 14 05:35:08 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:35:18 prozac /kernel: st0(ahc0:3:0): NOT READY asc:4,1
Jun 14 05:35:18 prozac /kernel: st0(ahc0:3:0):  Logical unit is in 
process of becoming ready
Jun 14 05:38:46 prozac /kernel: ahc0: target 3, lun 0 (st0) timed out
Jun 14 05:38:47 prozac /kernel: ahc0: Issued Channel A Bus Reset #3. 0 
SCBs aborted
Jun 14 05:38:47 prozac /kernel: st0(ahc0:3:0): UNIT ATTENTION asc:29,0
Jun 14 05:38:47 prozac /kernel: st0(ahc0:3:0):  Power on, reset, or bus 
device reset occurred
Jun 14 05:38:47 prozac /kernel: st0: oops not queued
Jun 14 05:38:47 prozac /kernel: st0(ahc0:3:0): NOT READY asc:4,1
Jun 14 05:38:47 prozac /kernel: st0(ahc0:3:0):  Logical unit is in 
process of becoming ready
Jun 14 05:38:47 prozac /kernel: st0(ahc0:3:0): NOT READY asc:4,1
Jun 14 05:38:47 prozac /kernel: st0(ahc0:3:0):  Logical unit is in 
process of becoming ready
Jun 14 05:38:47 prozac /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0
Jun 14 05:38:47 prozac /kernel: sd0(ahc0:0:0):  Power on, reset, or bus 
device reset occurred field replaceable unit: 1
Jun 14 05:38:47 prozac /kernel: , retries:4
Jun 14 05:38:55 prozac /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0
Jun 14 05:38:56 prozac /kernel: sd1(ahc0:1:0):  Power on, reset, or bus 
device reset occurred field replaceable unit: 1
Jun 14 05:38:56 prozac /kernel: , retries:4
Jun 14 05:45:30 prozac /kernel: st0(ahc0:3:0): NOT READY asc:3e,0 Logical 
unit has not self-configured yet
Jun 14 05:47:36 prozac /kernel: st0(ahc0:3:0): NOT READY asc:4,1
Jun 14 05:47:36 prozac /kernel: st0(ahc0:3:0):  Logical unit is in 
process of becoming ready
Jun 14 05:47:46 prozac /kernel: st0(ahc0:3:0): NOT READY asc:4,1
Jun 14 05:47:46 prozac /kernel: st0(ahc0:3:0):  Logical unit is in 
process of becoming ready

I'm running 2.1-RELEASE on the machine.  Earlier this week I had some 
problems with the backup apparently due to problems with /dev/tty 
(according to the dump errors).  Yesterday morning I restored /dev/tty 
with a copy froma week-old backup.  Any suggestions?

	-Amir



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