From owner-freebsd-current Tue Mar 21 2:53: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id A426037B80C for ; Tue, 21 Mar 2000 02:52:57 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id LAA27866; Tue, 21 Mar 2000 11:51:08 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003211051.LAA27866@info.iet.unipi.it> Subject: Reading from bad disk ? To: current@freebsd.org Date: Tue, 21 Mar 2000 11:51:08 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, sometimes i get IDE disks with hard errors on some sectors (status 59 error 40) and of course this makes it problematic to use a filesystem on it. I wonder, is there a way to fetch the data from these sectors (even if partly erroneous) ? I am asking because a strategy which often 'fixes' the problem for me is to overwrite the erroneous sector with some data. Of course i can use a zero-filled block but this is kind of risky, and maybe it is preferable to use a portion of the original data and hope that fsck is able to fix this. And related: is there a way to tell fsck that in such cases it should try and adopt the same method ? Otherwise it is really boring to run my locally modified version of dd (which is able to use 'skip' over character devices) to try read the bad sector and write it back. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message