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 1P53zD-0004xE-G2 for garchives@archives.gentoo.org; Sun, 10 Oct 2010 22:03:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A420BE0807; Sun, 10 Oct 2010 22:02:18 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 506FAE0807 for ; Sun, 10 Oct 2010 22:02:17 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.57,310,1283727600"; d="scan'208";a="222437668" Received: from 213-152-39-90.dsl.eclipse.net.uk (HELO compaq.stroller.uk.eu.org) ([213.152.39.90]) by smtpout.karoo.kcom.com with ESMTP; 10 Oct 2010 23:02:16 +0100 Received: from [192.168.1.101] (unknown [192.168.1.101]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id 6E4C58AFE0 for ; Sun, 10 Oct 2010 23:02:13 +0100 (BST) Content-Type: text/plain; charset=iso-8859-1 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 (Apple Message framework v1078) 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 From: Stroller In-Reply-To: Date: Sun, 10 Oct 2010 23:02:15 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: gentoo-user@lists.gentoo.org X-Mailer: Apple Mail (2.1078) X-Archives-Salt: 13b01e88-2e5a-43d0-94b5-46b3a647b976 X-Archives-Hash: 4ecec7f248ee7cc95725d738cd2d48f3 On 10 Oct 2010, at 17:21, Fatih T=FCmen wrote: > There problem is I have two more partition with about 80GB of data. >=20 >> .... >> If you need to get data off this disk then we can advise (but search = the archives for GNU dd_rescue, or just read its manual) but apart from = that there's nothing we can do for this drive. >=20 > I will that a look at dd_rescue, thanks. My previous spelling was wrong - the GNU version is without the = underscore. You want ddrescue NOT dd_rescue. $ eix -I rescue [I] sys-fs/ddrescue Available versions: 1.9 1.11 ~1.12 Installed versions: 1.11(12:52:56 05/03/10) Homepage: = http://www.gnu.org/software/ddrescue/ddrescue.html Description: Copies data from one file or block device to = another with read-error recovery $ I have found it very useful. =46rom my previous casual glance at your = logs you have some hopes - you may not be able to read block 1289, but = you may 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.=20 Confer with the manual = and then do something like: ddrescue -f -n /dev/sda2 /mnt/volumes/my_disk/recovered.img = recovery.log ddrescue -d -f -r3 /dev/sda2 /mnt/volumes/my_disk/recovered.img = recovery.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 only a block or two are unrecoverable, if you're unlucky then the = unrecoverable 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 space (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 - this 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 = recovered.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 block device, and then run fsck on /dev/loop0, or = something like that. If the disk / partition image fscks without toooooo many errors (and a = page 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 the files you intend to copy off.=20 Keep posting your progress back here, so we can advise further. Stroller.