From: Alex Goller <alex@vivien.franken.de>
To: Nico Schottelius <nico-kernel@schottelius.org>
Subject: Re: harddisk or kernel problem?
Date: Fri, 13 Feb 2004 17:56:59 +0100 [thread overview]
Message-ID: <20040213165659.GA57556@vivien.franken.de> (raw)
In-Reply-To: <20040213075403.GC1881@schottelius.org>
On Fri, Feb 13, 2004 at 08:54:03AM +0100, Nico Schottelius wrote:
> Freeing unused kernel memory: 140k freed
> XFS mounting filesystem hda1
> Ending clean XFS mount for filesystem: hda1
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
> sector=8305454
These result from the ide/dma code. Those errors are normally thrown
(someone correct me if i'm wrong) if ecc on that particular sector
fails. A EIO error is thrown, and is handed over to the layer above
(xfs in your case). These errors happen as well if you do raw reads
on those sectors.
> end_request: I/O error, dev hda, sector 8305454
> I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
This is EIO handed over to xfs.
> Now I am trying the following:
> enabling Anticipatory I/O scheduler (additionaly to the Deadline I/O
> scheduler) and disabling Vector-based interrupt indexing.
I don't think this will help. The proplem is probably all about a
broken sector on your disk. And if i understand the ide code correctly
you can't do anything about that.
> This is just a guess, can someone tell me if that is senseless or if my
> harddisk is most likely broken?
Yes, that's the most likely case. Smartmontools (smartctl) should show
errors on the sectors mentioned in your dumps as well (they do here).
Error 1689 occurred at disk power-on lifetime: 703 hours
When the command that caused the error occurred, the device was active or idle
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 2c 46 58 e0 Error: UNC
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
25 00 30 23 46 58 e0 00 3864.401 READ DMA EXT
25 00 32 21 46 58 e0 00 3860.425 READ DMA EXT
25 00 34 1f 46 58 e0 00 3843.845 READ DMA EXT
25 00 36 1d 46 58 e0 00 3839.939 READ DMA EXT
25 00 38 1b 46 58 e0 00 3839.914 READ DMA EXT
And so on.
bye, alex
--
alexander goller alex@vivien.franken.de
prev parent reply other threads:[~2004-02-13 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 7:54 Nico Schottelius
2004-02-13 8:11 ` Nico Schottelius
2004-02-13 9:52 ` Nico Schottelius
2004-02-13 16:17 ` Bartlomiej Zolnierkiewicz
2004-02-15 23:34 ` Nico Schottelius
2004-02-16 0:09 ` Bartlomiej Zolnierkiewicz
2004-02-18 16:55 ` Bruce Allen
2004-02-19 8:01 ` Nico Schottelius
2004-02-20 16:25 ` Bruce Allen
2004-03-02 20:07 ` Bruce Allen
2004-03-02 23:12 ` Nico Schottelius
2004-02-18 13:30 ` Steve Bromwich
2004-02-18 14:12 ` Nico Schottelius
2004-02-18 16:41 ` Bruce Allen
2004-02-19 0:06 ` Steve Bromwich
2004-02-19 8:16 ` Nico Schottelius
2004-02-20 17:10 ` Frédéric L. W. Meunier
2004-02-20 22:37 ` Eric D. Mudama
2004-02-13 16:56 ` Alex Goller [this message]
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=20040213165659.GA57556@vivien.franken.de \
--to=alex@vivien.franken.de \
--cc=nico-kernel@schottelius.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
all inboxes | Powered by JetHome®