All these are caused by smartd. Updating should fix the problem.
Okay, but there is no newer smartd than what I'm using. (5.37)
Bruce? Original thread can be read from...
http://thread.gmane.org/gmane.linux.kernel/588972
The fixes were added in smartmontools CVS, but there hasn't been a
BTW, while doing the TEST UNIT READY emulation patch for ATA (recently
withdrawn from libata-dev.git#upstream), I found a problem with the
interface that was difficult to get around: TEST UNIT READY simulation
code really wants to look at the result TF of CHECK POWER MODE, even if
ATA_ERR is
Hmm, it sounds as if smartmontools should send a SRST to spin up the
drive, but I do not know enough to be sure.
Eh... Now that I think about it. I don't think there's a way to work
around this from userland. smartmontools doesn't know the current power
mode (sleeping drive doesn't even
Tejun,
Hmm, it sounds as if smartmontools should send a SRST to spin up the
drive, but I do not know enough to be sure.
Could I add you to the developers list and give you CVS write access?
This might make it easier for you to fix the various little smartmontools
problems like this that
Andrew,
I forgot to say 'thank you' for tracking this down.
Thank you!
Cheers,
Bruce
On Fri, 5 Oct 2007, Andrew Paprocki wrote:
Tejun/Bruce,
I tracked down the source of timeouts I have been frequently getting.
It appears smartd is not properly handling drives that are spun down
SNIP
smartd should probably issue CHECK POWER MODE (0xe5) before issuing
other commands. Bruce?
Hi Tejun,
Yes, this seems very reasonable.
I hope you say 'yes' to my offer from five minutes ago.
Cheers,
Bruce
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
Message-
From: Bruce Allen [mailto:[EMAIL PROTECTED]
Sent: Friday, September 28, 2007 9:48 PM
To: Tejun Heo
Cc: Jon Chelton; Bruce Allen; Smartmontools Mailing List;
linux-ide@vger.kernel.org
Subject: Re: sata_sil24 with port multiplier
All errors are interface CRC errors reported by device
All errors are interface CRC errors reported by device on FPDMA_WRITE.
It doesn't seem to have anything to do with SMART. In all cases, SError
DIAG is reporting handshake error too (R_ERR received). I'm fairly sure
these were actual hardware problems. You don't have to pay too much
Hi Tejun,
Thanks! Yes I meant HDIO_DRIVE_TASK. Please let me know what your tests
reveal.
Cheers,
Bruce
On Thu, 27 Sep 2007, Tejun Heo wrote:
Bruce Allen wrote:
Andrew: thanks for isolating this problem.
Tejun: any thoughts? The STRANGE_BUFFER_LENGTH problem is fixed
:
It appears to be the '-o on' causing the problem. If I remove that,
the errors go away. The strange part is that according to the smartctl
documentation, my drives support it:
# smartctl -c /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-7 Bruce Allen
Home page is http
ata5: EH complete
# smartctl -i /dev/sda
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Deskstar T7K250 series
Device Model: HDT722525DLA380
Serial Number
This is what it is in smartd.conf:
/dev/sda -d ata -a -o on -S on
/dev/sdb -d ata -a -o on -S on
/dev/sdc -d ata -a -o on -S on
Thanks, -Andrew
On 9/17/07, Bruce Allen [EMAIL PROTECTED] wrote:
Hi Andrew,
Please build the CVS version (unreleased) of smartmontools. The versions
below are dated 2006/12/20
Tejun: thanks for the CC. I'm clueless about what is at fault here.
Eamonn: could you please build the latest version of smartmontools from
CVS HEAD source and see if the problem exists in that version? Then write
back. I don't think this will help but want to eliminate obvious things.
13 matches
Mail list logo