Date: Sun, 29 Oct 2000 14:55:24 +1030 From: Greg Lehey <grog@lemis.com> To: Kenneth Ingham <ingham@i-pi.com> Cc: questions@FreeBSD.ORG Subject: Re: Missing tape drive? Message-ID: <20001029145524.H68266@wantadilla.lemis.com> In-Reply-To: <20001027121918.B20788@Socrates.i-pi.com>; from ingham@i-pi.com on Fri, Oct 27, 2000 at 12:19:18PM -0600 References: <20001026155132.H17432@Socrates.i-pi.com> <20001026172839.A15066@dan.emsphone.com> <20001026214722.A18729@Socrates.i-pi.com> <20001027131955.C51550@wantadilla.lemis.com> <20001026221013.A18818@Socrates.i-pi.com> <20001027135238.D51550@wantadilla.lemis.com> <20001027121918.B20788@Socrates.i-pi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 27 October 2000 at 12:19:18 -0600, Kenneth Ingham wrote: >> OK, let's recapitulate: do you know that the drive has worked >> elsewhere? What happens if, instead of 'mt status', you do an 'mt >> rewind'? It's just barely possible that the drive is not returning a >> good status because the tape has never been written, though I can't >> reproduce this behaviour on my machine. Also, let's see the relevant >> dmesg output again. > > The drive worked fine on two other FreeBSD 4.1 machines. Identical > hardware. Similar, but not quite identical OS versions. We just shut > down the machine it was on, shut down the destination machine, > moved the cable from one machine to the other, then powered everybody > back up. Obviously, we should have considered doing a remote dump > instead of moving the tape drive... Hmm. That sounds strange. > mt rewind does the same thing as mt status; a kernel message (on > the console and in dmesg) stating: ``(sa0:ahc0:0:5:0): unable to > rewind after test read'' as well as a message on the terminal where > the command was run saying ``mt: /dev/nrsa0: Device not configured''. > > I removed and recreated the *sa* devices in /dev with no effect. No, that wouldn't have any effect. You've already established that you're talking to the correct drive, it's just not understanding. > Relevant dmesg output is: > ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xdc00-0xdcff mem 0xedfff000-0xedffffff irq 11 at device 13.0 on pci0 > aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs > sa0 at ahc0 bus 0 target 5 lun 0 > sa0: <HP HP35470A 1009> Removable Sequential Access SCSI-2 device > sa0: 5.000MB/s transfers (5.000MHz, offset 8) Hmm. Is this the old HP DDS-1 drive? I have found them to be by far the most unreliable hardware I have had to deal with in the last 10 years. I had three of them in the space of 18 months, and the average life span was 8 months. If that's the case, it has probably just died. You could try connecting it to the old machine again, of course. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers 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?20001029145524.H68266>