All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: linux-kernel@vger.kernel.org
Subject: harddisk or kernel problem?
Date: Fri, 13 Feb 2004 08:54:03 +0100	[thread overview]
Message-ID: <20040213075403.GC1881@schottelius.org> (raw)

Hello!

Since yesterday I have the problem that at bootup my cryptoloop (/home) does not
get mounted anymore. These messages are produced by the kernel:

---------------- snip ------------------

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
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
("xfs_trans_read_buf") error 5 buf count 8192
8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 at 0xd8850e00, 00:0a:e6:ba:f6:c2, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458,
sector=8305454
end_request: I/O error, dev hda, sector 8305454
I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090
("xfs_trans_read_buf") error 5 buf count 8192


---------------- snap ------------------


if I log in as root and issue `mount /home`, it works:

---------------- snip ------------------

XFS mounting filesystem loop0
Ending clean XFS mount for filesystem: loop0

---------------- snap ------------------

Yesterday the errors
 `hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }`
repeated (don't have the dmesg, forgot to dump kernel messages).

Now I am trying the following:
enabling Anticipatory I/O scheduler (additionaly to the Deadline I/O
scheduler) and disabling Vector-based interrupt indexing.

This is just a guess, can someone tell me if that is senseless or if my
harddisk is most likely broken?

Attached dmesg from 'running' system and the new .config (changes see
above) I made.

Help is very much appreciated,

Nico, who just had a hard disk crash some weeks ago

             reply	other threads:[~2004-02-13  7:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  7:54 Nico Schottelius [this message]
2004-02-13  8:11 ` harddisk or kernel problem? 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

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=20040213075403.GC1881@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.