Date: Sat, 7 Dec 1996 12:27:01 -0500 (EST) From: Steve <shovey@buffnet.net> To: Network Coordinator <nc@ai.net> Cc: questions@freebsd.org Subject: Re: Marking Bad Blocks Message-ID: <Pine.BSI.3.95.961207122617.10513E-100000@buffnet11.buffnet.net> In-Reply-To: <Pine.BSF.3.91.961206200415.15041A-100000@alyssa.ai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.961207122617.10513E-100000>