From: Marc MERLIN <marc@merlins.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: PMP SMART error recovery and failure code decoding help
Date: Wed, 29 Jun 2011 10:14:02 -0700 [thread overview]
Message-ID: <20110629171402.GA10803@merlins.org> (raw)
In-Reply-To: <20110117172924.GE27342@merlins.org>
On Mon, Jan 17, 2011 at 09:29:24AM -0800, Marc MERLIN wrote:
> On Mon, Jan 17, 2011 at 06:12:09PM +0100, Tejun Heo wrote:
> > Hello,
> >
> > On Mon, Jan 17, 2011 at 08:43:40AM -0800, Marc MERLIN wrote:
> > > > It could be that the drives need to spin up to answer the smart
> > > > command and the timeout on the smart commands is a bit too short for
> > > > that to happen. Forcing a disk access before issuing the smart
> > > > command could work around the problem.
> > >
> > > Right, although the idea is of course to keep the drives spun down :)
> > > I haven't been able to find which SMART call is causing those errors yet.
> > > Does cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 translate to anything useful?
> >
> > That's SMART ENABLE OPERATIONS. It turns on SMART.
>
> Haha, ok, not as useful as I thought :)
As an update for the list archives, more recent smartmontools (5.40 and
maybe older) allow this:
DEVICESCAN -n standby
This tells smartmontools not to talk to drives that are sleeping so that
it does not spin them back up.
In turn it fixed the related PMP timeout and PMP bus reset issues I was getting
from those commands.
Hope this helps someone.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
prev parent reply other threads:[~2011-06-29 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 16:39 PMP SMART error recovery and failure code decoding help Marc MERLIN
2011-01-17 13:26 ` Tejun Heo
2011-01-17 16:43 ` Marc MERLIN
2011-01-17 17:12 ` Tejun Heo
2011-01-17 17:29 ` Marc MERLIN
2011-06-29 17:14 ` Marc MERLIN [this message]
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=20110629171402.GA10803@merlins.org \
--to=marc@merlins.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).