Date: Sun, 31 Dec 2000 00:13:10 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: David Kelly <dkelly@HiWAAY.net> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI tape diagnostics? Message-ID: <Pine.BSF.4.21.0012310010450.5032-100000@beppo.feral.com> In-Reply-To: <200012310550.eBV5o2Q73875@grumpy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
C'mon, David, you know the drill... CAMDEBUG kernel, camcontrol debug -Ic ... The 'mt' error stuff is limited to what errno can return. However, you can also try mt errstat on the control device to see what was latched up. (err, um, it *is* in the man page....) On Sat, 30 Dec 2000, David Kelly wrote: > Most of my toys were nuked by a lightning strike about 2 weeks ago. Let > a local shop rebuild my computer. Not sure what diagnostics they did on > my DDS-2 tape drive other than observe the Symbios SCSI card recognized > it. Wouldn't be writting now if I thought it worked. > > Thought I'd stashed away in my email archive the instructions > recommened to others having problems. Can't find it. And haven't hit on > the right search words to find it at http://www.freebsd.org/search/ > > The fact inserting a tape causes the motor to run a minute or two, then > the orange activity light flashes fast, suggests there is nothing > FreeBSD can do. Acts a lot like the drive thinks its heads are dirty. > Cleaning tape doesn't help, but behaves normally. > > Tape drive, HD, scsi card, cables, were lifted from the dead machine > where they had been working for years. HD is terminated on the drive MB > and connected via a wide cable. Tape drive is also terminated on the > drive and connected to the SCSI card with a narrow cable. Nothing is on > the external connector. > > /var/log/messages doesn't say anything about the tape failure. > > This is what dmesg has to say about my SCSI stuff: > > sym0: <875> port 0xa000-0xa0ff mem 0xe0800000-0xe0800fff,0xe1000000-0xe10000ff i > rq 3 at device 10.0 on pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > [...] > sa0 at sym0 bus 0 target 5 lun 0 > sa0: <ARCHIVE Python 28388-XXX 4.CM> Removable Sequential Access SCSI-2 device > sa0: 5.000MB/s transfers (5.000MHz, offset 15) > Mounting root from ufs:/dev/da0s2a > da0 at sym0 bus 0 target 0 lun 0 > da0: <IBM OEM DCHS09W 2222> Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > > It would be nice to have a specific error code or something from the > drive other than the simple: > > grumpy: {456} mt stat > mt: /dev/nsa0: Input/output error > grumpy: {457} mt errstat > mt: /dev/nsa0: Input/output error > grumpy: {458} > > -- > David Kelly N4HHE, dkelly@hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0012310010450.5032-100000>