From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 30802] exception & eSATA hard link resets
Date: Thu, 10 Mar 2011 10:40:24 GMT [thread overview]
Message-ID: <201103101040.p2AAeOvm028037@demeter2.kernel.org> (raw)
In-Reply-To: <bug-30802-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=30802
Tejun Heo <tj@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tj@kernel.org
--- Comment #6 from Tejun Heo <tj@kernel.org> 2011-03-10 10:40:22 ---
First of all, please don't paste kernel log in-line and don't attach them as
tar.gz either unless the file is really big. Attach them as separate
text/plain files.
It definitely looks like hardware problem to me. You're trying to use wd
raptor 15k rpm drive, right? I don't know your setup but it could be that the
enclosure you're using isn't upto the task power-wise. The FLUSH_CACHE failure
combined with PHY going down is also indicative of power problems. Can you
please do the followings?
1. Boot and run "smartctl -a" on the hard drive.
2. Trigger the problem.
3. Reset the computer but don't power cycle the enclosure.
4. Run "smartctl -a" on the drive again.
Post the two outputs from the smartctl.
Thanks.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-03-10 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:53 [Bug 30802] New: exception & eSATA hard link resets bugzilla-daemon
2011-03-09 13:55 ` [Bug 30802] " bugzilla-daemon
2011-03-09 13:58 ` bugzilla-daemon
2011-03-10 2:23 ` bugzilla-daemon
2011-03-10 8:51 ` bugzilla-daemon
2011-03-10 10:21 ` bugzilla-daemon
2011-03-10 10:40 ` bugzilla-daemon [this message]
2011-03-10 19:40 ` bugzilla-daemon
2012-07-02 13:40 ` bugzilla-daemon
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=201103101040.p2AAeOvm028037@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).