From owner-freebsd-stable  Tue Jun 16 15:33:51 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA08845
          for freebsd-stable-outgoing; Tue, 16 Jun 1998 15:33:51 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08793;
          Tue, 16 Jun 1998 15:33:03 -0700 (PDT)
          (envelope-from se@dialup124.zpr.uni-koeln.de)
Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124])
	by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id AAA18362;
	Wed, 17 Jun 1998 00:33:01 +0200 (MET DST)
Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id XAA01130; Tue, 16 Jun 1998 23:41:18 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-ID: <19980616234117.00597@mi.uni-koeln.de>
Date: Tue, 16 Jun 1998 23:41:17 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: Sean Eric Fagan <sef@kithrup.com>, stable@FreeBSD.ORG
Cc: Stefan Esser <se@FreeBSD.ORG>
Subject: Re: Worrisome scsi messages
References: <199806161552.IAA02165@kithrup.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89i
In-Reply-To: <199806161552.IAA02165@kithrup.com>; from Sean Eric Fagan on Tue, Jun 16, 1998 at 08:52:25AM -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 1998-06-16 08:52 -0700, Sean Eric Fagan <sef@kithrup.com> wrote:
> After a powerfailure, I started getting these messages.  I re-power cycled,
> and fsck'd all of the filesystems on sd0 (and dd'd the swap area, just to be
> safe) while in single user mode, and didn't get any errors, but they're still
> happening intermittently.

Well, I guess that if you had dd'd the whole disk
(e.g. the 'c' partition), then the same error (and
possibly more might have been reported ...

> Any ideas just how badly I should be worried?

There definitely is a unrecoverable read error. But
this may still be a soft error (e.g. a write has been
interrupted in the middle of a sector and there just
is no way the missing data may be reconstructed from
the ECC syndrome). It is extremely unlikely, that the
surface of your drive was damaged and that the sector
in question needs to be remapped.

> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , retries:4
> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , retries:3
> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , retries:2
> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , retries:1
> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , FAILURE

> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , FAILURE
> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , FAILURE
> sd0(ncr0:0:0): MEDIUM ERROR info:0x13b2c9 asc:11,0 Unrecovered read error sks:80,33
> , FAILURE

It's always the same sector that can't be read. You
should backup this disk, and if it was mine, then I'd
just dd /dev/zero all over it, recreate the filesystems
and try to restore the old contents from the backup.

You will loose a single file (the one that contained 
the read error), but that should be it ...

Regards, STefan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message