Date: Fri, 28 Jul 1995 12:07:14 -0400 (EDT) From: Kristyn Fayette <kristyn@gnu.ai.mit.edu> To: questions@freebsd.org (FreeBSD Questions) Subject: Floppy Tape timeout errors Message-ID: <199507281607.MAA07112@spiff.gnu.ai.mit.edu>
next in thread | raw e-mail | index | archive | help
Hiya,
I've been backing up my system with my Colorado Jumbo 250 QIC-80 drive since
1.0.2. And, I think the 1.0.2 version (it was an add-on package then) worked
the best. But 2.0.5's version seems to be better than 1.1.5.1's. In 1.1.5.1,
I wasn't able to use ft & dump together to back up /usr (wd1e?). Dumping the
root mount point, however, worked fine. Incidently, tar & ft always worked
ok with either slice.
Well, with 2.0.5, I seem to be able to backup /usr again with dump. I
haven't actually let the dump run all the way thru yet, but it didn't bomb
right away, which is a great sign!
The problem I'm having now, tho, is whenever I do any operations with ft, I
get:
Jul 27 20:57:25 scylla /kernel: fdc0 input ready timeout or
Jul 27 20:57:25 scylla /kernel: fdc0 output ready timeout
These messages keep being repeated on the console, naturally, which is
really annoying.
I can't even guess at what might be causing this. My kernel config file
has the default entries (I don't have fd1):
controller fdc0 at isa? port "IO_FD1" bio irq6 drq 2 vector fdintr
disk fd0 at fdc0 drive 0
tape ft0 at fdc0 drive 2
And the probs come back with:
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
ft0: Colorado tape
Any ideas?
--
-=(*)=- Kristyn Fayette -=(*)=-
kristyn@gnu.ai.mit.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507281607.MAA07112>