From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1P5Gw1-0004Ph-VJ for garchives@archives.gentoo.org; Mon, 11 Oct 2010 11:52:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8B16CE06B4; Mon, 11 Oct 2010 11:51:59 +0000 (UTC) Received: from mail-iw0-f181.google.com (mail-iw0-f181.google.com [209.85.214.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 6A4C8E06B4 for ; Mon, 11 Oct 2010 11:51:59 +0000 (UTC) Received: by iwn39 with SMTP id 39so2567971iwn.40 for ; Mon, 11 Oct 2010 04:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=fQEdJGUCYL+nGvKrKS862xwuv4B/0B4MCAJQ33rmL4M=; b=nCmbIevoHV/5jq2/WHjZp/M8V1PiijvjWZBWTEuLeilxipYIgXIuYoo9obSgbNzMbq 3rtaPywl1aPYJMGUHvfFe5InqSzRLPK9vqx0N3HkrLKGOGl6+KpMIp0fWxxvBcAzNxS9 BnhpW109mFsklCzQaawCFZKUwW3e418rkYq04= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=gYbs7OocpcLfSJ20c+Xc9CsxkCkx6yRI9wPw1ep4sW22k4RRXY2tsXyhAxqFfJbZu+ 5kFKntLXqbDrR8UFq0wyfEh2cgLABwiVtVoPXkDfStq+D4WmeFEtjHYUftL8CEC0ne8E zfjafL1yruBQf6hs/XaAtBTQ4C2XxMZgTJ/Ps= Received: by 10.231.154.73 with SMTP id n9mr4604325ibw.10.1286797919090; Mon, 11 Oct 2010 04:51:59 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Sender: fthtmn@gmail.com Received: by 10.231.19.71 with HTTP; Mon, 11 Oct 2010 04:51:28 -0700 (PDT) In-Reply-To: References: From: =?ISO-8859-1?Q?Fatih_T=FCmen?= Date: Mon, 11 Oct 2010 14:51:28 +0300 X-Google-Sender-Auth: E_M569OtqV3r_ddOVohzKBsxEnk Message-ID: Subject: Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2 To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 8869e537-a69a-49ac-a67d-ef7c5b25ecd5 X-Archives-Hash: 152dca6e4c941fc0c5476cd995a18805 On Mon, Oct 11, 2010 at 1:02 AM, Stroller wrote: > > On 10 Oct 2010, at 17:21, Fatih T=FCmen wrote: >> There problem is I have two more partition with about 80GB of data. >> >>> .... >>> If you need to get data off this disk then we can advise (but search th= e archives for GNU dd_rescue, or just read its manual) but apart from that = there's nothing we can do for this drive. >> >> I will that a look at dd_rescue, thanks. > > > My previous spelling was wrong - the GNU version is without the underscor= e. You want ddrescue NOT dd_rescue. > > $ eix -I rescue > [I] sys-fs/ddrescue > =A0 =A0 Available versions: =A01.9 1.11 ~1.12 > =A0 =A0 Installed versions: =A01.11(12:52:56 05/03/10) > =A0 =A0 Homepage: =A0 =A0 =A0 =A0 =A0 =A0http://www.gnu.org/software/ddre= scue/ddrescue.html > =A0 =A0 Description: =A0 =A0 =A0 =A0 Copies data from one file or block d= evice to another with read-error recovery > > $ > > I have found it very useful. From my previous casual glance at your logs = you have some hopes - you may not be able to read block 1289, =A0but you ma= y well be able to get blocks 1288 & 1290. My (limited) experience has been = that even with a *really* badly failing hard-drive, over 99% of the blocks = are recoverable. > > Confer with the manual and then do something like: > > =A0ddrescue -f -n /dev/sda2 /mnt/volumes/my_disk/recovered.img recovery.l= og > =A0 > =A0ddrescue -d -f -r3 /dev/sda2 /mnt/volumes/my_disk/recovered.img recove= ry.log > > (where /dev/sda2 is the partition containing the data you want to recover= ). > > Keep running `ddrescue -r X` (where X is a number) for as many passes as = you can. If you get data off on one pass, then another one may get more, if= you have the time for it. If you're really lucky then you'll find that onl= y a block or two are unrecoverable, if you're unlucky then the unrecoverabl= e blocks will be measured in megabytes. > > If you have multiple partitions then post back here (with their sizes and= the total size of the disk). You'll need to have at least enough empty spa= ce (on a single usable partition) for the whole partition that you want to = recover. Ideally you'll have twice that much space, or even three times - t= his is not the time to skimp on hard-drive capacity. Ideally what you want = to do when the above commands have finished is make a copy of recovered.img= , so that if one method of recovery doesn't work, you can try another. > > I'm not sure what will happen if you simply tried to loopback mount recov= ered.img - hopefully fsck would run on it automagically, but I suspect that= would be too easy. You might have to use losetup to treat the .img as a bl= ock device, and then run fsck on /dev/loop0, or something like that. > > If the disk / partition image fscks without toooooo many errors (and a pa= ge or two of them would probably be quite acceptable - expect one error per= unrecoverable block) then you still need enough free disk space for all th= e files you intend to copy off. > > Keep posting your progress back here, so we can advise further. > > Stroller. > > > Thank you very much for sharing your experience. ddrescue sounds quiet promising. The disk was of 160GB I think. Right now I wont have enough space for recovery until I will order a new disk. I will post the result here as soon as I am done. P.S. Would you recommend against 7200rpm usb 2.5" disks? -- Fatih