From owner-freebsd-questions Sat Dec 7 09:18:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA01284 for questions-outgoing; Sat, 7 Dec 1996 09:18:16 -0800 (PST) Received: from buffnet4.buffnet.net (root@buffnet4.buffnet.net [205.246.19.13]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA01279 for ; Sat, 7 Dec 1996 09:18:13 -0800 (PST) Received: from buffnet1.buffnet.net (mmdf@buffnet1.buffnet.net [205.246.19.10]) by buffnet4.buffnet.net (8.6.12/8.6.9) with SMTP id RAA27185 for ; Sat, 7 Dec 1996 17:20:02 GMT Received: from buffnet11.buffnet.net by buffnet1.buffnet.net id aa06897; 7 Dec 96 12:27 EST Date: Sat, 7 Dec 1996 12:27:01 -0500 (EST) From: Steve To: Network Coordinator cc: questions@freebsd.org Subject: Re: Marking Bad Blocks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Looks like you are using adaptec - so you can use the controller's verify function - just do control-A when it comes up as the computer is coming up, and pick disk utilities, and verify - verify looks for and remaps bad spots. On Fri, 6 Dec 1996, Network Coordinator wrote: > > > We are seeing errors like this on one of our lab systems: > > sd0(ahc0:0:0): MEDIUM ERROR info:396e24 asc:11,0 Unrecovered read error > field re > placeable unit: ea sks:80,d > , retries:4 > sd0(ahc0:0:0): MEDIUM ERROR info:396e24 asc:11,0 Unrecovered read error > field re > placeable unit: ea sks:80,d > , retries:3 > sd0(ahc0:0:0): MEDIUM ERROR info:396e24 asc:11,0 Unrecovered read error > field re > placeable unit: ea sks:80,d > , retries:2 > sd0(ahc0:0:0): MEDIUM ERROR info:396e24 asc:11,0 Unrecovered read error > field re > placeable unit: ea sks:80,d > , retries:1 > > Any friendly utilities to examine the drive(s) and mark the blocks as > unusable? > > Thanks, > > John Hubbel > American Information Network > > > > >