linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jon@eHardcastle.com
Cc: Bruce Allen <ballen@gravity.phys.uwm.edu>,
	Smartmontools Mailing List
	<smartmontools-support@lists.sourceforge.net>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [smartmontools-support] Bug/Issue
Date: Fri, 02 Nov 2007 21:09:44 +0900	[thread overview]
Message-ID: <472B1388.2060208@gmail.com> (raw)
In-Reply-To: <474362.56402.qm@web51305.mail.re2.yahoo.com>

Hello, Jon.

Please don't top-post.

Jon Hardcastle wrote:
> Looking at the logs there is seconds(as in 2~5)
> literally between when the smartd kicks in on the sata
> and when it decides the drive isn't capable. I can
> tell you now it takes at least 10~15 seconds for the
> drive to spin up.. probably longer. I also know that
> when i run the test manually using smartctl it seems
> to work, and that when the scheduled test is run when
> the drives HAVENT spun down it also works.

Okay, please do the following.

1. Post /var/log/boot.msg or dmesg result right after boot.
2. Post the result of "lspci -nnv"
3. Post the results of "hdparm -I /dev/sdX" where sdX is one of th
problematic drives.
4. Run "hdparm -y /dev/sdX" to spin it down then issue SMART short test
manually.  If it fails the same way, post what smartd/smartctl says and
the result of dmesg after the failure.

Thanks.

-- 
tejun

       reply	other threads:[~2007-11-02 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <474362.56402.qm@web51305.mail.re2.yahoo.com>
2007-11-02 12:09 ` Tejun Heo [this message]
2007-11-02 12:11 ` [smartmontools-support] Bug/Issue 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=472B1388.2060208@gmail.com \
    --to=htejun@gmail.com \
    --cc=Jon@eHardcastle.com \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=linux-ide@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).