Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!news-feed-1.peachnet.edu!umn.edu!BUS18.mndly.umn.edu!worthen From: worthen@main.mndly.umn.edu Subject: Caching Controller Question - FreeBSD 1.1R Message-ID: <worthen.94.2E0EF8B3@main.mndly.umn.edu> Sender: news@news.cis.umn.edu (Usenet News Administration) Nntp-Posting-Host: bus18.mndly.umn.edu Organization: the Minnesota Daily (U of MN Student Newspaper) Date: Mon, 27 Jun 1994 16:05:07 GMT Lines: 42 I'm running a FreeBSD 1.1R system with a DC-680T caching controller from Green Cache (I believe...). What it does is run for a while - from one hour to three days - and then choke. Before I send this sad caching card back to the manufacturer, I was wondering if anyone could help me get this to work. The system it is running on is an ATI 486/66 EISA with a Maxtor 7546 540M hard drive. The caching controller has it's own BIOS, so the kernel (at boot up, for example) is unable to recognize the hard drive. Once /etc/disktab is created with the correct parameters, though, it works enough to permit installation. Eventually it will begin having errors, though. Disk access will become very slow, but I can still log in and out, and read small files. I generally reboot at this point, and then the problem goes away for another seemingly random length of time. I'm including a sample of the error messages it leaves in /var/log/messages. Jun 27 12:06:41 bus66 /386bsd: wd0: interrupt timeout: Jun 27 12:07:04 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:07:43 bus66 /386bsd: wd0: interrupt timeout: Jun 27 12:07:43 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:07:43 bus66 /386bsd: wd0e: hard error reading fsbn 301008 of 301008-301023 (wd0 bn 483456; cn 479 tn 9 sn 57) Jun 27 12:07:43 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:07:43 bus66 /386bsd: wd0e: hard error reading fsbn 301040 of 301040-301055 (wd0 bn 483488; cn 479 tn 10 sn 26) Jun 27 12:07:43 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:29:06 bus66 /386bsd: wd0: interrupt timeout: Jun 27 12:29:06 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:29:06 bus66 /386bsd: wd0: interrupt timeout: Jun 27 12:29:06 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:29:06 bus66 /386bsd: wd0e: hard error reading fsbn 301248 of 301248-301263 (wd0 bn 483696; cn 479 tn 13 sn 45) Jun 27 12:29:06 bus66 /386bsd: wd0: status 51<seekdone,err> error 0 Jun 27 12:29:06 bus66 /386bsd: wd0: interrupt timeout: Jun 27 12:29:06 bus66 /386bsd: wd0: status 58<seekdone,drq> error 0 Thanks in advance for any help... ...brad worthen@main.mndly.umn.edu Computer Technician, Minnesota Daily.