From owner-freebsd-questions@FreeBSD.ORG Wed Aug 13 21:29:04 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF3BB37B401 for ; Wed, 13 Aug 2003 21:29:04 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14F6443F3F for ; Wed, 13 Aug 2003 21:29:03 -0700 (PDT) (envelope-from raj@cisco.com) Received: from cisco.com (171.68.223.137) by sj-iport-3.cisco.com with ESMTP; 13 Aug 2003 21:29:04 -0700 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h7E4T0uG018314; Wed, 13 Aug 2003 21:29:02 -0700 (PDT) Received: from cisco.com (stealth-10-34-245-242.cisco.com [10.34.245.242]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with SMTP id AKI80561; Wed, 13 Aug 2003 21:21:52 -0700 (PDT) Date: Wed, 13 Aug 2003 21:28:47 -0700 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: =?ISO-8859-1?Q?Rapha=EBl_Marmier?= From: Richard Johnson In-Reply-To: <833CD204-C97A-11D7-A0DA-000393D67E4A@computer-rental.ch> Message-Id: Content-Transfer-Encoding: quoted-printable X-Mailer: Apple Mail (2.552) cc: freebsd-questions@freebsd.org Subject: Re: Question re. hard read errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 04:29:05 -0000 Actually, I found the web page on "gzrecover": http://www.urbanophile.com/arenn/hacking/gzrt/gzrt.html This doesn't seem to work for me, probably because the mmap it uses=20 doesn't work very well when the file contains bad blocks. I also found: http://www.gzip.org/recover.txt and will probably pursue this, but it'll take quite a while. Also, there's a reference in the gzip documentation to: If a .tar.gz file is damaged, files beyond the failure point cannot be recovered. (Future versions of gzip will have error recovery features.) so maybe this will be available at some point. I'd love to know if=20 someone is actually working now on this. /raj On Friday, August 8, 2003, at 01:30 AM, Rapha=EBl Marmier wrote: > Try using dd to grab all possible bits of that file: > /bin/sh > dd if=3D/path/tothe/file of=3D/path/to/newfile conv=3Dsync,noerror=20 > >ddlog.txt 2>&1 > > you get the log of all errors and faulty blocks in ddlog.txt > > This will make a copy of the file with unreadable blocks converted to=20= > blank. Then you should fix the compresssed archive with the proper=20 > utility (although I don't know exactly how), then you should be able=20= > to untar it. Maybe the information on which files where lost will even=20= > be available. > > If it turns out you didn't loose that much, it will spare you the=20 > effort to read the disk harder. In case you really lost damn imporant=20= > stuff, you can send the disk to a data recovery company, but it costs=20= > $$$$$$... > > Hope this helps > > Raphael > > Le Vendredi, 8 ao=FB 2003, =E0 01:33 Europe/Zurich, Richard Johnson a=20= > =E9crit : > >> I have a 1.5Gb file stored on a FreeBSD 4.8 disk drive and the system=20= >> is giving me hard read errors when I try reading it. It appears as=20= >> though this disk has a few bad blocks. :( Unfortunately, it's a=20 >> compressed tar file and I (stupidly!) erased the file from the=20 >> original computer before untar'ing it here and finding the errors! =20= >> I'd like to recover as much as possible of this file before writing=20= >> off the entire thing. >> >> I looked at /usr/src/sys/dev/ata/ata-disk.c and found the retry count=20= >> was set to 3. I changed it to 10. After the first error (which is,=20= >> indeed, reported 10 times) the system reports that it's going into=20 >> PIO mode and I still hear the same amount of hammering on the drive=20= >> after that and only one error message produced. >> >> Is there some way I can force the system to retry 10 or more times=20 >> for each and every block? Maybe there's some other utility I can use=20= >> which tries harder to read the blocks? >> >> ANY pointers to information would be greatly appreciated. >> >> /raj >> >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to=20 >> "freebsd-questions-unsubscribe@freebsd.org" >