From: David Sumbler <david@aeolia.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Hard drive - dead or dying?
Date: Thu, 12 Jul 2007 07:40:44 +0100 [thread overview]
Message-ID: <1184222444.5969.0.camel@ceres> (raw)
My computer (Ubuntu Feisty) would not boot correctly a few days
ago: it seemed to get into a loop with the following printed about
every 7 seconds (all laboriously copied in longhand, since it wasn't
logged!):
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.01: (BMDMA stat 0x65)
ata1.01: cmd c8/00:08:80:b4:a8/00:00:00:00:00/f4 tag0 cdb 0x0 data 4096
in
res 51/01:08:80:b4:a8/00:00:00:00:00/f4 Emark 0x1 (device
error)
ata1.01: ata_hpa_resize 1: sectors = 78165360, hpa_sectors : 78165360
ata1.00: ata_hpa_resize 1: sectors = 160086528, hpa_sectors : 160086528
ata1.00: configured for UDMA/33
ata1.01: ata_hpa_resize 1: sectors = 78165360, hpa_sectors : 78165360
ata1.01: configured for PIO3
ata1.01: EH complete
Periodically there would be other messages.
Most of this means nothing to me, but after several attempts I concluded
that ata1.00 probably refers to /dev/sda, and ata1.01 to /dev/sdb, and
that there was a fault with the second.
I disconnected the drive, and the computer booted OK. I have now
commented out references to the partitions on /dev/sdb in /etc/fstab.
The drive in question was giving minor problems a couple of years ago,
and on advice I bought a new one, but kept the old one for backups
etc. Until now, it seems to have behaved pretty well.
Can someone tell me this: has the drive now as-good-as died, or is there
any hope of resurrection?
David
--
David Sumbler <david@aeolia.co.uk>
next reply other threads:[~2007-07-12 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 6:40 David Sumbler [this message]
2007-07-12 13:35 ` Hard drive - dead or dying? Mark Lord
2007-07-12 20:31 ` David Sumbler
2007-07-13 8:13 ` Tejun Heo
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=1184222444.5969.0.camel@ceres \
--to=david@aeolia.co.uk \
--cc=linux-kernel@vger.kernel.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