From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Iu5Cw-00034h-AU for garchives@archives.gentoo.org; Mon, 19 Nov 2007 11:54:31 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lAJBqiu3009688; Mon, 19 Nov 2007 11:52:44 GMT Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lAJBqi2U009683 for ; Mon, 19 Nov 2007 11:52:44 GMT Received: by mu-out-0910.google.com with SMTP id i2so2632845mue for ; Mon, 19 Nov 2007 03:52:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=ZZCtXepBVcVkks4oqTMS9QZfXJDSTA3VN0oNci0Xel8=; b=KYm64M3G4x+dnyharRRIx6dYN9XaReyTwS3IizRE4kwaEfSdECA2qg/cN0s6urr+9w+gZaKD+NtFWdL1ZBtQEHLe+KzA1L13B6j0UItCgHdtBLDeuaL9sgosihpKgcfLTHofE5oknezem069QdFYWcK6huUn4wEOkP0+tFW3Eaw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=GNYpTTo207bLxJU99WdzFJgmK17XD9Y/5ZcOcN+e2Q6Ohyh9TW47qtDyYJQn2LfpARe10KYx+KLDSxChqhuMLwiOiXZoS64DDuzOYjBgCo/t0dnnqvVh1ewD6bL3ipZC69pUsD7b/2fuVCz8wh74BRUBeY9Nkjznal7ZcBQrO3A= Received: by 10.82.183.19 with SMTP id g19mr13656220buf.1195473162986; Mon, 19 Nov 2007 03:52:42 -0800 (PST) Received: by 10.82.141.15 with HTTP; Mon, 19 Nov 2007 03:52:41 -0800 (PST) Message-ID: Date: Mon, 19 Nov 2007 12:52:42 +0100 From: Beso To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] not amd64 specific - disk failure In-Reply-To: <47415FCD.300@st.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15931_5140706.1195473162974" References: <47415FCD.300@st.com> X-Archives-Salt: 37813b2d-b327-424c-8804-eef0ab153493 X-Archives-Hash: 47011fac853518624d563d49c31ca8a3 ------=_Part_15931_5140706.1195473162974 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline before doing something on the disk first, read all and then take a decision on which options may help you. on my reiserfs filesystem, the included utils were enough to let me recover about 98% of the data after the full index rebuild. if you've journaled your filesystem, then i think that you should be able to recover it. also, it may only be a problem of superblock and in that case the second link might help you more. anyway, get a disk that can contain all the data that there was on the failed one, since you wouldn't want to do stuff on it to avoid loss of data. try reading this (the ext2/3 part): http://edseek.com/archives/2004/02/25/ext3-filesystem-bad-superblock-recovery/ and this: http://forums.gentoo.org/viewtopic-t-569462-highlight-ext3+recover.html or you might try this utility: http://www.cgsecurity.org/wiki/PhotoRec 2007/11/19, Raffaele BELARDI : > > Yesterday evening I had one 250Gb SATA disk Maxtor MaXLine Plus II fail. > The drive is formatted as ext3, single partition (sdc1), no RAID, used > as an archive of divx movies, completely full with data. Motherboard is > ASUS M2NPV-VM (Nvidia Nforce 430 chipset), I can easily mount it on an > ASUS K8V SE (Via K8T800 chipset) if it helps. > > At boot the syslog shows (more or less): > > I/O buffer read error: logical block 0 > I/O buffer read error: logical block 1 > > Any attempt to mount /dev/sdc1 results in tens of the above message > (plus other details I don't remember right now) and finally fails. > > fdisk -l shows the partition table as it should be. > > It was late night so I gave up. Are there any chances to recover my data > by e.g. specifying a different superblock (whatever that is)? Any links > to help me? > > thanks, > > raffaele > > PS I bought the drive in 2005 and I've used it only to archive movies, > so very little. It' the last Maxtor I buy (ok, also because it's Seagate > now..) > -- > gentoo-amd64@gentoo.org mailing list > > -- dott. ing. beso ------=_Part_15931_5140706.1195473162974 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline before doing something on the disk first, read all and then take a decision on which options may help you. on my reiserfs filesystem, the included utils were enough to let me recover about 98% of the data after the full index rebuild. if you've journaled your filesystem, then i think that you should be able to recover it. also, it may only be a problem of superblock and in that case the second link might help you more. anyway, get a disk that can contain all the data that there was on the failed one, since you wouldn't want to do stuff on it to avoid loss of data.
try reading this (the ext2/3 part):
http://edseek.com/archives/2004/02/25/ext3-filesystem-bad-superblock-recovery/
and this:
http://forums.gentoo.org/viewtopic-t-569462-highlight-ext3+recover.html
or you might try this utility:
http://www.cgsecurity.org/wiki/PhotoRec

2007/11/19, Raffaele BELARDI <raffaele.belardi@st.com>:
Yesterday evening I had one 250Gb SATA disk Maxtor MaXLine Plus II fail.
The drive is formatted as ext3, single partition (sdc1), no RAID, used
as an archive of divx movies, completely full with data. Motherboard is
ASUS M2NPV-VM (Nvidia Nforce 430 chipset), I can easily mount it on an
ASUS K8V SE (Via K8T800 chipset) if it helps.

At boot the syslog shows (more or less):

I/O buffer read error: logical block 0
I/O buffer read error: logical block 1

Any attempt to mount /dev/sdc1 results in tens of the above message
(plus other details I don't remember right now) and finally fails.

fdisk -l shows the partition table as it should be.

It was late night so I gave up. Are there any chances to recover my data
by e.g. specifying a different superblock (whatever that is)? Any links
to help me?

thanks,

raffaele

PS I bought the drive in 2005 and I've used it only to archive movies,
so very little. It' the last Maxtor I buy (ok, also because it's Seagate
now..)
--
gentoo-amd64@gentoo.org mailing list




--
dott. ing. beso ------=_Part_15931_5140706.1195473162974-- -- gentoo-amd64@gentoo.org mailing list