From: "Bjørn Mork" <bjorn@mork.no>
To: Artem Bokhan <aptem@ngs.ru>
Cc: linux-ide@vger.kernel.org
Subject: Re: kernel problems with smart on LSI-92xx
Date: Mon, 29 Nov 2010 08:09:14 +0100 [thread overview]
Message-ID: <878w0cmwrp.fsf@nemi.mork.no> (raw)
In-Reply-To: <4CEFD55D.8060200@ngs.ru> (Artem Bokhan's message of "Fri, 26 Nov 2010 21:42:21 +0600")
Artem Bokhan <aptem@ngs.ru> writes:
> It appears that passing self-test command to SATA disk does not work
> too. Although nobody reports any error, self-test actually just does
> not start.
>
> smartctl -d megaraid,10 -t long /dev/sg0
>
> smartctl 5.40 2010-10-16 r3189 [x86_64-unknown-linux-gnu] (local build)
> Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
>
> /dev/sg0 [megaraid_disk_10] [SAT]: Device open changed type from 'megaraid' to 'sat'
> === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
> Sending command: "Execute SMART Extended self-test routine immediately
> in off-line mode".
> Drive command "Execute SMART Extended self-test routine immediately in
> off-line mode" successful.
> Testing has begun.
> Please wait 255 minutes for test to complete.
> Test will complete after Sat Nov 27 01:54:44 2010
>
> Use smartctl -X to abort test.
I'm not sure I understand you correctly. The above output looks
normal. You mean that "smartctl -l selftest" doesn't show any test in
progress or finished?
Bjørn
next prev parent reply other threads:[~2010-11-29 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 19:27 kernel problems with smart on LSI-92xx Bokhan Artem
2010-11-11 14:06 ` Bjørn Mork
2010-11-10 17:21 ` Bokhan Artem
2010-11-11 18:02 ` [PATCH] [SCSI] megaraid_sas: Sanity check user supplied length before passing it to dma_alloc_coherent() Bjørn Mork
2010-11-26 15:42 ` kernel problems with smart on LSI-92xx Artem Bokhan
2010-11-29 7:09 ` Bjørn Mork [this message]
2010-11-29 9:49 ` Artem Bokhan
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=878w0cmwrp.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=aptem@ngs.ru \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).