From owner-freebsd-hackers  Tue Jan  3 15:25:21 1995
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA01510 for hackers-outgoing; Tue, 3 Jan 1995 15:25:21 -0800
Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA01497 for <hackers@freebsd.org>; Tue, 3 Jan 1995 15:25:16 -0800
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id PAA12493; Tue, 3 Jan 1995 15:24:33 -0800
X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol
To: mtaylor@gateway.cybernet.com (Mark J. Taylor)
cc: hackers@freebsd.org
Subject: Re: Bad sectors on SCSI drive! 
In-reply-to: Your message of "Tue, 03 Jan 95 18:30:27 EST."
             <v01510104ab2f8aa17407@[192.245.33.12]> 
Date: Tue, 03 Jan 1995 15:24:32 -0800
Message-ID: <12492.789175472@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: hackers-owner@freebsd.org
Precedence: bulk

> Allright, so what can be done?  How can I map out bad sectors on a scsi
> drive?  Do I have to newfs the drive?

Return it to the manufacturer.  A good SCSI drive shouldn't develop faults
like this, and when it does, it's time to shoot it.

					Jordan

> 
> 
> pocs1[2]: fsck /dev/rsd0e
> ** /dev/rsd0e
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> sd0(aha0:0:0): medium error, info = 848030 (decimal)
> 
> CANNOT READ: BLK 663616
> CONTINUE? [yn] y
> sd0(aha0:0:0): medium error, info = 848030 (decimal)
> sd0(aha0:0:0): medium error, info = 848031 (decimal)
> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 663710, 663711,
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 20099 files, 334968 used, 83029 free (10405 frags, 9078 blocks, 2.5%
> fragmentation)
> 
> 
> 
> -Mark Taylor
> mtaylor@cybernet.com
> 
>