public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Murphy <poisonbl@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: hard disk access and recovery impossible under  linux ?
Date: Sat, 31 Jul 2010 13:11:45 -0400	[thread overview]
Message-ID: <AANLkTik2tsHgUKWRKQgnPCK-rPjMg1vD+15XDSpbLgCM@mail.gmail.com> (raw)
In-Reply-To: <201007311714.55223.michaelkintzios@gmail.com>

On Sat, Jul 31, 2010 at 12:14 PM, Mick <michaelkintzios@gmail.com> wrote:
> On Saturday 31 July 2010 16:33:18 Dale wrote:
>> Kacper Kopczyński wrote:
>> > Dnia 2010-07-31, o godz. 16:15:51
>> >
>> > Volker Armin Hemmann<volkerarmin@googlemail.com>  napisał(a):
>> >> On Samstag 31 Juli 2010, Kacper Kopczyński 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?
>
> --
> Regards,
> Mick
>

Not likely, though just looking at *how* it fails, if the data'd not
already been backed up, I'd hold at least a little hope that it's not
really a problem with the on-disk data, aside from what's been
corrupted since the problems started, but rather just the controller
and firmware. If I had a spare drive from the same batch, I'd swap in
the not-dying controller card and see if that got me anywhere. Since
the drive's already backed up, though... that one's a new paperweight
for the desk, and if the data's anything sensitive, physical
destruction of the drive's the way I'd go to 'secure' it before it
goes out with the trash.

-- 
Poison [BLX]
Joshua M. Murphy



  reply	other threads:[~2010-07-31 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31 13:27 [gentoo-user] OT: hard disk access and recovery impossible under linux ? Kacper Kopczyński
2010-07-31 14:15 ` Volker Armin Hemmann
2010-07-31 14:57   ` Kacper Kopczyński
2010-07-31 15:33     ` Dale
2010-07-31 16:14       ` Mick
2010-07-31 17:11         ` Joshua Murphy [this message]
2010-07-31 18:04         ` Volker Armin Hemmann
2010-07-31 18:32           ` Mick
2010-07-31 19:14             ` Volker Armin Hemmann
2010-08-08 16:19               ` Mark Shields
2010-08-08 17:53                 ` Kacper Kopczyński
2010-07-31 16:14     ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTik2tsHgUKWRKQgnPCK-rPjMg1vD+15XDSpbLgCM@mail.gmail.com \
    --to=poisonbl@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox