mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: JG <jg@cms.ac>
To: John Bradford <john@grabjohn.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: could someone plz explain those ext3/hard disk errors
Date: Wed, 18 Feb 2004 16:54:23 +0100	[thread overview]
Message-ID: <20040218155433.D6BE41A9DC6@23.cms.ac> (raw)
In-Reply-To: <200402181442.i1IEgwF2000170@81-2-122-30.bradfords.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

hi,

> I.E. Even though there is every chance that the drive is faulty, the
> posted error message doesn't indicate a drive failiure in itself, and
> you should look elsewhere.

i recently got the new disks and could backup nearly everything (after reboot the disks were accessible again, though i've lost some data).

i tried to zero out the disk with 'dd if=/dev/zero of=/dev/hdX' which led to a complete system lockup after some time.

after a reboot i wanted to run the long S.M.A.R.T. tests (smartctl -t long /dev/hdX, smartctl v5.26). it said that it is backgrounding for about 80 minutes. but again after some time => complete lockup.
i couldn't do anything anymore on the server, only sysrq-keys were working. killing the processes gave me some error messages (can't remember the exact wording but they were like: "DMA lost" on nearly every disk and some weird interrupt errors (related to the NIC).

$ cat /proc/interrupts
           CPU0
  0:  435370782          XT-PIC  timer
  1:        315          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:    6144225          XT-PIC  ide2, ide3, ide4, ide5
  8:          2          XT-PIC  rtc
 10:          0          XT-PIC  ohci_hcd
 11:   68722839          XT-PIC  eth1
 12:  227629214          XT-PIC  ohci_hcd, eth0
 14:    4515100          XT-PIC  ide0
 15:     643567          XT-PIC  ide1
NMI:          0
LOC:  435357136
ERR:     680356
MIS:          0

don't know if the ERR-rate is too high, this is with an uptime of 5 days. i usually have much higher ERR numbers. 

JG

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-18 15:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08 17:53 JG
2004-02-08 18:55 ` Micha Feigin
2004-02-08 19:05   ` JG
2004-02-09  1:47 ` Heriberto A Tejeda
2004-02-09  9:52   ` JG
2004-02-09 10:26     ` John Bradford
2004-02-09 11:06       ` JG
2004-02-18 13:31       ` Bill Davidsen
2004-02-18 14:42         ` John Bradford
2004-02-18 15:54           ` JG [this message]
2004-02-18 18:26           ` Bill Davidsen
2004-02-09 11:52     ` Gene Heskett
2004-02-18 13:41       ` Bill Davidsen

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=20040218155433.D6BE41A9DC6@23.cms.ac \
    --to=jg@cms.ac \
    --cc=davidsen@tmr.com \
    --cc=john@grabjohn.com \
    --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

all inboxes | Powered by JetHome®