From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: Re: Kernel 2.6.23.9 / P35 Chipset + WD 750GB Drives (reset port)
Date: Sun, 2 Dec 2007 22:14:18 +0100 [thread overview]
Message-ID: <20071202221418.6f269022@absurd> (raw)
In-Reply-To: <Pine.LNX.4.64.0712020409280.30169@p34.internal.lan>
Justin Piszcz said: (by the date of Sun, 2 Dec 2007 04:11:59 -0500 (EST))
> The badblocks did not do anything; however, when I built a software raid 5
> and the performed a dd:
>
> /usr/bin/time dd if=/dev/zero of=fill_disk bs=1M
>
> I saw this somewhere along the way:
>
> [42332.936706] ata5.00: spurious completions during NCQ issue=0x0
> SAct=0x7000 FIS=004040a1:00000800
> [42333.240054] ata5: soft resetting port
I know nothing about NCQ ;) But I find it interesting that *slower*
access worked fine while *fast* access didn't.
If I understand you correctly:
- badblocks is slower, and you said that it worked flawlessly, right?
- getting from /dev/zero is the fastest thing you can do, and it fails...
I'd check jumpers on HDD and if there is any, set it to 1.5 Gb speed
instead of default 3.0 Gb. Or sth. along that way. I remember seeing
such jumper on one of my HDDs (I don't remember the exact speed
numbers though).
Also on one forum I remember about problems occurring when HDD was
working at maximum speed, which was faster than the IO controller
could handle.
I dunno. It's just what came to my mind...
--
Janek Kozicki |
next prev parent reply other threads:[~2007-12-02 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 11:26 Kernel 2.6.23.9 / P35 Chipset + WD 750GB Drives (reset port) Justin Piszcz
2007-12-01 12:13 ` Jan Engelhardt
2007-12-01 12:23 ` Justin Piszcz
2007-12-01 16:47 ` Janek Kozicki
2007-12-01 16:55 ` Justin Piszcz
2007-12-02 9:11 ` Justin Piszcz
2007-12-02 21:14 ` Janek Kozicki [this message]
2007-12-02 21:21 ` Justin Piszcz
2007-12-02 21:25 ` Michael Tokarev
2007-12-02 21:32 ` Justin Piszcz
2007-12-10 8:23 ` Tejun Heo
2007-12-01 18:44 ` Bill Davidsen
2007-12-10 8:14 ` Tejun Heo
2007-12-13 22:27 ` Bill Davidsen
2007-12-06 22:00 ` Andrew Morton
2007-12-06 22:38 ` Justin Piszcz
2007-12-06 23:05 ` Andrew Morton
[not found] <fa.hhS4g1h0uppt8Xx/ZZfNNQfAv1Q@ifi.uio.no>
2007-12-01 20:08 ` Robert Hancock
[not found] ` <fa.YIWyRfjQw18aIH2fKaze37Gwuzo@ifi.uio.no>
[not found] ` <fa.ib4H8TQ3raADIWdsEBy+eSL/1RU@ifi.uio.no>
[not found] ` <fa.S4u1AwoYnqrSuegcUaP78D3SFXQ@ifi.uio.no>
[not found] ` <fa.H1nTe/xQV/oyEMTHAkOjqgqu7jY@ifi.uio.no>
[not found] ` <fa.YpQ6xCPOijQOCKsLJr1SDINFURI@ifi.uio.no>
2007-12-05 1:26 ` Robert Hancock
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=20071202221418.6f269022@absurd \
--to=janek_listy@wp.pl \
--cc=linux-raid@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).