Date: Tue, 21 Apr 1998 11:06:49 -0400 From: Howard Goldstein <hgoldste@bbs.mpcs.com> To: freebsd-questions@FreeBSD.ORG Subject: SCSI tape prob 2.2.6R Message-ID: <199804211506.LAA11316@bbs.mpcs.com>
next in thread | raw e-mail | index | archive | help
I'm seeing these failures during attempts to read tarred stuff from an HP 1533A (surestore) with 'tar t'. Writes go through OK... Apr 21 10:52:42 cally /kernel: st0(ahc0:4:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 21 10:52:43 cally /kernel: SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 =0x5 SSTAT1 = 0xa Apr 21 10:52:43 cally /kernel: st0(ahc0:4:0): Queueing an Abort SCB Apr 21 10:52:43 cally /kernel: st0(ahc0:4:0): Abort Message Sent Apr 21 10:52:43 cally /kernel: st0(ahc0:4:0): SCB 8 - Abort Completed. Apr 21 10:52:43 cally /kernel: st0(ahc0:4:0): no longer in timeout Apr 21 10:54:23 cally /kernel: st0(ahc0:4:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 21 10:54:23 cally /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Apr 21 10:54:23 cally /kernel: st0(ahc0:4:0): Queueing an Abort SCB Apr 21 10:54:23 cally /kernel: st0(ahc0:4:0): Abort Message Sent Apr 21 10:54:23 cally /kernel: st0(ahc0:4:0): SCB 6 - Abort Completed. Apr 21 10:54:23 cally /kernel: st0(ahc0:4:0): no longer in timeout Apr 21 10:58:32 cally /kernel: st0(ahc0:4:0): MEDIUM ERROR info:0x2800 asc:11,0 Unrecovered read error During the glitches the drive seems to be winding, and then it commences to read again. I don't recall seeing this kind of problem under 2.2.5R. Problem occurs on different physical tapes, but in different places. The drive is accessed as rst0. Writes are fine. My drive's orange light flashes after it's done this for a number of minutes (hardware error? OEM drive, no manual, all mention of the 1533 disappeared from HP's site) ---also -- concerning density: cally:/u2# mt status Present Mode: Density = 0x24 Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = X3.136-1986 Blocksize = 512 bytes Mode 2: Density = X3.39-1986 Blocksize variable Mode 3: Density = X3.54-1986 Blocksize variable is this density code a problem? it doesn't appear to be documented in mt(1). attempts to change the density appear to work for the moment but always reverts back to 0x24 after certain tape ops (read, write, attempt to retension (the latter never does anything)) but not all (rewind when already at BOT) Thank you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804211506.LAA11316>