public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
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 23:11:08 +0100	[thread overview]
Message-ID: <3CC74178-B8FC-4157-A216-B5416335F9BE@stellar.eclipse.co.uk> (raw)
In-Reply-To: <AANLkTikbGawUpbTkpVTAPFHzcArztaJkp4e18xbip9+1@mail.gmail.com>


On 10 Oct 2010, at 17:28, Fatih Tümen wrote:
>> ...
>> 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?

Total coincidence. It has nothing to do with eix - you'll likely be running something on the drive when it fails, that's not what causes the problem.

Most hard-drive failures have nothing to do with being dropped. It's simply that hard-drives spin at 5,000 - 10,000 rpm, about the same speed as a car engine, but unlike a car engine they don't have an oil pump and a radiator and all that stuff to lubricate them.

Hard-drives are simply prone to mechanical failure - wearing out, in other words,

> 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.

They would probably bother if you paid them enough. I would probably consider $500 cheap, and might well expect to pay twice or several times that. In the cases of clicking drives I've had quite some success with ddrescue for no cost.

Stroller.




  parent reply	other threads:[~2010-10-10 22:11 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
2010-10-10 18:49           ` walt
2010-10-11  9:51             ` James Wall
2010-10-10 22:11           ` Stroller [this message]
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=3CC74178-B8FC-4157-A216-B5416335F9BE@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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