Date: Thu, 24 Dec 1998 10:52:46 +0000 From: nclayton@lehman.com To: questions@FreeBSD.ORG, scsi@FreeBSD.ORG Cc: nik@FreeBSD.ORG Subject: Python 02635-XXX 567D tape drive hangs 2.2.7-stable Message-ID: <19981224105246.I10040@lehman.com>
next in thread | raw e-mail | index | archive | help
[ sent to -questions and -scsi, since either could be appropriate ] I'm trying to back up my home system using a SCSI tape drive I've had handy. It's from a Sun system. However, ~30 minutes after starting 'dump', the system hangs, printing /kernel: sd1(ncr0:1:0): error code 1 /kernel: , retries:4 /kernel: sd1(ncr0:1:0): error code 1 /kernel: , retries:2 /kernel: sd1(ncr0:1:0): error code 1 /kernel: , FAILURE /kernel: sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted /kernel: , retries:3 on the console. I can ^C the dump command to get the prompt back, but any further disk access (ls, sync, and so on) locks the machine. This also happens when I use tar. This happens *before* dump has printed any of its messages. The boot messages for the SCSI devices on the system are: */kernel: ncr0 <ncr 53c875 fast20 wide scsi> rev 3 int a irq 10 on pci0:12:0 /kernel: (ncr0:0:0): "QUANTUM XP32275W LXY4" type 0 fixed SCSI 2 /kernel: sd0(ncr0:0:0): Direct-Access /kernel: sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled /kernel: sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 16) /kernel: 2170MB (4445380 512 byte sectors) /kernel: (ncr0:1:0): "SEAGATE ST34520W 1444" type 0 fixed SCSI 2 /kernel: sd1(ncr0:1:0): Direct-Access /kernel: sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled /kernel: sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15) /kernel: 4340MB (8888924 512 byte sectors) */kernel: (ncr0:4:0): "ARCHIVE Python 02635-XXX 567D" type 1 removable SCSI 2 */kernel: st0(ncr0:4:0): Sequential-Access */kernel: st0(ncr0:4:0): 6.7 MB/s (150 ns, offset 15) */kernel: density code 0x8c, 512-byte blocks, write-enabled /kernel: (ncr0:6:0): "TOSHIBA CD-ROM XM-3801TA 0207" type 5 removable SCSI 2 /kernel: cd0(ncr0:6:0): CD-ROM /kernel: cd0(ncr0:6:0): 10.0 MB/s (100 ns, offset 8) * = controller and tape drive. The mailing list archives have messages from people using ARCHIVE Python drives successfully, but none of them seem to have the same revision number as this one. AltaVista and DejaNews searches for those error messages (and revision numbers) haven't turned up anything useful either. I've checked for SCSI problems. The internal SCSI cable (two disks on it) is short enough, and properly terminated. The external SCSI cable only has this tape drive on it, and is ~ 1.5 feet long. The tape drive is self terminating, but the problem happens if add a terminator to the drive as well. I'm running 2.2.7-stable, built around the middle of last November. Upgrading to 2.2.8 is feasible to fix this, but if possible I don't want to have to go to -current to fix it (the reason I want it working is so that I can take a backup, wipe the system, and start running -current on it). Any suggestions gratefully received. N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- 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?19981224105246.I10040>