public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fatih Tümen" <fthtmn+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
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
Date: Sun, 10 Oct 2010 19:28:06 +0300	[thread overview]
Message-ID: <AANLkTikbGawUpbTkpVTAPFHzcArztaJkp4e18xbip9+1@mail.gmail.com> (raw)
In-Reply-To: <201010101101.23597.michaelkintzios@gmail.com>

On Sun, Oct 10, 2010 at 1:01 PM, Mick <michaelkintzios@gmail.com> wrote:
> On Sunday 10 October 2010 04:58:04 Fatih Tümen wrote:
>> On Sun, Oct 10, 2010 at 12:15 AM, walt <w41ter@gmail.com> wrote:
>
>> > Will fdisk read and recognize the partition table on the USB disk? If
>> > fdisk results in disk read errors then I'd begin to think more about
>> > 'hardware' :(
>>
>> No "Unable to read /dev/sda" is what fdisk says. I never had a disk
>> (hardware) failure before. Is there no way to extract data from it?
>
> The noise you're describing is indicative of mechanical failure.
>

That I was fearing but I cant understand how it can fail all of a
sudden. I did not drop it or something. Just ran eix and boom. Would
you call it a coincidence of running eix with the best before date of
the disk?

> Unless your PC can access the drive (dmesg will show what the kernel sees)
> then there is no easy way of getting the data out of it.
>
> I have heard of people opening the USB enclosure of external drives and
> removing the drive, which they then installed in a laptop.  However, these
> were cases where the USB controller was faulty, rather than the moving
> elements of the drive itself.
>

I tried that to a friend laptop's dead drive. It Didt work. I am
afraid im in a similar situation here.

> If you had access to a forensics lab you could even take the platters out of
> the drive itself and read them on platter reader.  On the other hand, if you
> only had ccache, distfiles and packages a resync with a new external drive
> will get you a working system again.
>

I actually thought about that too. There is a forensic lab quite close
to me but I doubt that they would bother with this or whether it would
worth the effort.

> Before you head for the shops you would at least want to try another USB cable
> as Walter suggested, just in case.

I found the cable and tried. Same!
Anyway thanks for the suggestion.



  reply	other threads:[~2010-10-10 16:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09 19:24 [gentoo-user] USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2 Fatih Tümen
2010-10-09 19:36 ` [gentoo-user] " Fatih Tümen
2010-10-09 21:15   ` walt
2010-10-10  3:58     ` Fatih Tümen
2010-10-10  9:23       ` Stroller
2010-10-10 16:21         ` Fatih Tümen
2010-10-10 22:02           ` Stroller
2010-10-11 11:51             ` Fatih Tümen
2010-10-11 12:33               ` Stroller
2010-10-12  5:42                 ` Fatih Tümen
2010-10-10 10:01       ` Mick
2010-10-10 16:28         ` Fatih Tümen [this message]
2010-10-10 18:49           ` walt
2010-10-11  9:51             ` James Wall
2010-10-10 22:11           ` Stroller
2010-10-12 16:41 ` [gentoo-user] " Paul Hartman
2010-10-15  1:13   ` Daniel da Veiga
2010-10-15  7:41     ` Alan McKinnon

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=AANLkTikbGawUpbTkpVTAPFHzcArztaJkp4e18xbip9+1@mail.gmail.com \
    --to=fthtmn+gentoo@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