mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carsten Otto" <carsten.otto@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Daily crashes, incorrect RAID behaviour
Date: Tue, 15 Aug 2006 14:42:25 +0200	[thread overview]
Message-ID: <13e988610608150542od63a2ecqcbf8684033d9690f@mail.gmail.com> (raw)
In-Reply-To: <1155646621.24077.270.camel@localhost.localdomain>

> Rule of thumb (and a good one). If the soft reboot and BIOS cannot
> recover the disk then the disk is the problem. There isn't really
> anything we can tell the drive to do which should make it take a hike
> and ignore a reset sequence.  (Should.. however..)

Makes sense. I will focus my attention on the disks now (which makes
sense not only because of your information).

> > DriveReadySeekComplete (I do not recall the exact words, sorry) for one disk
> Pity the exact text is essential.

Here is the exact message I saw a few weeks ago (posted in here):

ata4: handling error/timeout
ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
ata4: status=0x50 { DriveReady SeekComplete }
sdd: Current: sense key=0x0
        ASC=0x0 ASCQ=0x0
Info fid=0x0

To my knowledge this time it did not look different at all.

> I assume you've run memtest86 and also checked temperatures look good
> around all the disks.

Of course. I even replaced the mainboard (screwdriver accident..) and
power supply (too weak). And I now know that the sata cables I used at
first did not cause the problems :)

Thanks,
-- 
Carsten Otto
carsten.otto@gmail.com
www.c-otto.de

  reply	other threads:[~2006-08-15 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 11:36 Carsten Otto
2006-08-15 12:33 ` Michael Tokarev
2006-08-15 12:57 ` Alan Cox
2006-08-15 12:42   ` Carsten Otto [this message]
2006-08-15 13:08     ` Jan Engelhardt
2006-08-15 13:45 ` Ralf Müller
2006-08-19 11:37   ` Andrew Baker
2006-08-19 11:47     ` Justin Piszcz
2006-08-19 18:53       ` Andrew Baker
2006-08-15 15:31 ` Carsten Otto
2006-08-15 18:28   ` Mike Dresser
2006-08-15 19:27     ` Alistair John Strachan

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=13e988610608150542od63a2ecqcbf8684033d9690f@mail.gmail.com \
    --to=carsten.otto@gmail.com \
    --cc=alan@lxorguk.ukuu.org.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

all inboxes | Powered by JetHome®