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 1OiA5K-0006bu-E1 for garchives@archives.gentoo.org; Sun, 08 Aug 2010 17:54:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8074FE0797; Sun, 8 Aug 2010 17:53:44 +0000 (UTC) Received: from matrix.inten.pl (matrix.inten.pl [91.200.187.34]) by pigeon.gentoo.org (Postfix) with ESMTP id F1274E0797 for ; Sun, 8 Aug 2010 17:53:43 +0000 (UTC) Received: from localhost (unknown [91.200.187.211]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by matrix.inten.pl (Postfix) with ESMTPSA id 99EACA1D88D for ; Sun, 8 Aug 2010 19:53:42 +0200 (CEST) Date: Sun, 8 Aug 2010 19:53:37 +0200 From: Kacper =?UTF-8?B?S29wY3p5xYRza2k=?= To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] OT: hard disk access and recovery impossible under linux ? Message-ID: <20100808195337.6b1b91f7@matrix.inten.pl> In-Reply-To: References: <20100731152732.4da6f3d1@matrix.inten.pl> <201007312004.47268.volkerarmin@googlemail.com> <201007311932.37788.michaelkintzios@gmail.com> <201007312114.38454.volkerarmin@googlemail.com> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.20.1; i686-pc-linux-gnu) 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 46a0f002-5493-455a-bbfa-a1d2f750f2d6 X-Archives-Hash: 5d2b2da3efb30f6f631888dbe668d4ea Dnia 2010-08-08, o godz. 12:19:07 Mark Shields napisa=C5=82(a): > On Sat, Jul 31, 2010 at 3:14 PM, Volker Armin Hemmann < > volkerarmin@googlemail.com> wrote: >=20 > > On Samstag 31 Juli 2010, Mick wrote: > > > On Saturday 31 July 2010 19:04:47 Volker Armin Hemmann wrote: > > > > On Samstag 31 Juli 2010, Mick wrote: > > > > > On Saturday 31 July 2010 16:33:18 Dale wrote: > > > > > > Kacper Kopczy=C5=84ski wrote: > > > > > > > Dnia 2010-07-31, o godz. 16:15:51 > > > > > > > > > > > > > > Volker Armin Hemmann > > > > > > > napisa=C5=82(a): > > > > > > >> On Samstag 31 Juli 2010, Kacper Kopczy=C5=84ski wrote: > > > > > > >>> Hi, > > > > > > >>> > > > > > > >>> My problem is really strange - I can't access my hard > > > > > > >>> drive > > from > > > > > > >>> linux, but it works from windows without problems. It > > > > > > >>> has some bad blocks. > > > > > > >> > > > > > > >> it has a lot of bad blocks and a fucked up firmware it > > > > > > >> seems. No way it is working 'without problems'. > > > > > > > > > > > > > > Well total space taken by bad blocks according to chkdsk > > > > > > > is less than 1MB, windows is still able to access all > > > > > > > data. Linux is only able to see partition table "for a > > > > > > > while" - as you can see in dmesg. > > > > > > > > > > > > > > If firmware is broken then how it is possible that > > > > > > > windows is > > able > > > > > > > to use this disk? > > > > > > > > > > > > Maybe windoze is ignoring the problem? It's not like > > > > > > windoze has never done that before right? > > > > > > > > > > > > Just a thought. > > > > > > > > > > Couldn't it be that the MSWindows partition has no bad > > > > > blocks, while Linux does? > > > > > > > > it is not about partitions. > > > > > > Please explain, I thought that bad blocks would coincide with some > > > partitions. > > > > because defectice partitions don't give you no sense errors nor do > > they give > > you zero capacity errors. Read his dmesg. > > > > If the firmware/logic board is bad, you might be able to replace > > it with > one from the same model. I've heard of some success from a coworker > who took the logic board from a known good drive and put it on a HDD > with good internals but a bad logic board, and it worked. That's if > you need the data, that is. >=20 > - Mark Shields After spending many hours on google it seems to me this is a bug in firmware or seagate's firmware on barracuda discs likes to break itself frequently. Thank you for your help. --=20 Kacper Kopczy=C5=84ski