From owner-freebsd-hardware  Mon Sep  4 22:36:45 1995
Return-Path: hardware-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.11/8.6.6) id WAA03325
          for hardware-outgoing; Mon, 4 Sep 1995 22:36:45 -0700
Received: from who.cdrom.com (who.cdrom.com [192.216.222.3])
          by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id WAA03275
          for <freebsd-hardware@FreeBSD.org>; Mon, 4 Sep 1995 22:36:36 -0700
Received: from monster.telekom.lv (monster.telekom.lv [194.8.16.106])
          by who.cdrom.com (8.6.11/8.6.11) with ESMTP id JAA13504
          for <freebsd-hardware@freebsd.org>; Mon, 4 Sep 1995 09:11:14 -0700
Received: (from webby@localhost) by monster.telekom.lv (8.6.10/8.6.9) id TAA00418; Mon, 4 Sep 1995 19:09:29 +0300
Date: Mon, 4 Sep 1995 19:09:28 +0300 (EET DST)
From: Haralds Jakovels <webby@monster.telekom.lv>
To: freebsd-hardware@FreeBSD.org
Message-ID: <Pine.BSF.3.91.950904190247.377A-100000@monster.telekom.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hardware-owner@FreeBSD.org
Precedence: bulk

Hello,

I am having huge problems with FreeBSD 2.0.5. The machine I am talking 
about is 486dx2 66 unknown brand - well, it has not any labels on it.
The problems started just today. It has 

(dmesg output, some devices omitted)

CPU: i486DX (486-class CPU)
real memory  = 33161216 (8096 pages)
avail memory = 30883840 (7540 pages) 
[...]
bt0: Bt445S/ 0-PCI/EISA/VLB(32bit) bus
bt0: reading board settings, busmastering, int=11
bt0: version 3.37, fast sync, parity, 32 mbxs, 32 ccbs
bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15
bt0: targ 1 sync rate=10.00MB/s(100ns), offset=08
bt0: Enabling Round robin scheme
bt0 at 0x330 irq 11 on isa
bt0 waiting for scsi devices to settle
(bt0:0:0): "HP C3323-300 4269" type 0 fixed SCSI 2
sd0(bt0:0:0): Direct-Access 1003MB (2056008 512 byte sectors)
(bt0:1:0): "HP C2247-300 0BA4" type 0 fixed SCSI 2
sd1(bt0:1:0): Direct-Access 1003MB (2054864 512 byte sectors)
[...]

extract from /var/log/messages (this happened just today)

Sep  4 17:40:49 monster /kernel: sd0(bt0:0:0): MEDIUM ERROR info:1c548 
asc:11,0
Unrecovered read error
Sep  4 17:41:00 monster /kernel: , retries:4
Sep  4 17:41:00 monster /kernel: sd0(bt0:0:0): MEDIUM ERROR info:1c548 
asc:11,0
Unrecovered read error
Sep  4 17:41:00 monster /kernel: , retries:3
Sep  4 17:41:00 monster /kernel: sd0(bt0:0:0): MEDIUM ERROR info:1c548 
asc:11,0
Unrecovered read error
Sep  4 17:41:00 monster /kernel: , retries:2
Sep  4 17:41:00 monster /kernel: sd0(bt0:0:0): MEDIUM ERROR info:1c548 
asc:11,0
Unrecovered read error
Sep  4 17:41:00 monster /kernel: , retries:1
Sep  4 17:41:00 monster /kernel: sd0(bt0:0:0): MEDIUM ERROR info:1c548 
asc:11,0
Unrecovered read error
Sep  4 17:41:00 monster /kernel: , FAILURE
Sep  4 17:41:00 monster /kernel: sd0(bt0:0:0): MEDIUM ERROR info:1c548 
asc:11,0
Unrecovered read error
[...]

is there anything I can do about it? the error can be almost 100% 
reproduced with 'iozone 90' on that partition, that is, doing large 
reads/writes to the disk.

also, there's some 'unremovable' damaged file. fsck says

UNREF FILE I=118  OWNER=root MODE=100444
SIZE=5758 MTIME=Sep  4 17:25 1995
CLEAR?

I answer with 'y',  and the file is still here after reboot... needless 
to say, that file is on /dev/sd0a (root partition) :( 

cc me any reply, please.

thanks in advance
HJ