* Re: [smartmontools-support] Bug/Issue
[not found] <474362.56402.qm@web51305.mail.re2.yahoo.com>
@ 2007-11-02 12:09 ` Tejun Heo
2007-11-02 12:11 ` Tejun Heo
1 sibling, 0 replies; 2+ messages in thread
From: Tejun Heo @ 2007-11-02 12:09 UTC (permalink / raw)
To: Jon; +Cc: Bruce Allen, Smartmontools Mailing List, IDE/ATA development list
Hello, Jon.
Please don't top-post.
Jon Hardcastle wrote:
> Looking at the logs there is seconds(as in 2~5)
> literally between when the smartd kicks in on the sata
> and when it decides the drive isn't capable. I can
> tell you now it takes at least 10~15 seconds for the
> drive to spin up.. probably longer. I also know that
> when i run the test manually using smartctl it seems
> to work, and that when the scheduled test is run when
> the drives HAVENT spun down it also works.
Okay, please do the following.
1. Post /var/log/boot.msg or dmesg result right after boot.
2. Post the result of "lspci -nnv"
3. Post the results of "hdparm -I /dev/sdX" where sdX is one of th
problematic drives.
4. Run "hdparm -y /dev/sdX" to spin it down then issue SMART short test
manually. If it fails the same way, post what smartd/smartctl says and
the result of dmesg after the failure.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [smartmontools-support] Bug/Issue
[not found] <474362.56402.qm@web51305.mail.re2.yahoo.com>
2007-11-02 12:09 ` [smartmontools-support] Bug/Issue Tejun Heo
@ 2007-11-02 12:11 ` Tejun Heo
1 sibling, 0 replies; 2+ messages in thread
From: Tejun Heo @ 2007-11-02 12:11 UTC (permalink / raw)
To: Jon; +Cc: Bruce Allen, Smartmontools Mailing List, IDE/ATA development list
Hello, Jon.
Please don't top-post.
Jon Hardcastle wrote:
> Looking at the logs there is seconds(as in 2~5)
> literally between when the smartd kicks in on the sata
> and when it decides the drive isn't capable. I can
> tell you now it takes at least 10~15 seconds for the
> drive to spin up.. probably longer. I also know that
> when i run the test manually using smartctl it seems
> to work, and that when the scheduled test is run when
> the drives HAVENT spun down it also works.
Okay, please do the following.
1. Post /var/log/boot.msg or dmesg result right after boot.
2. Post the result of "lspci -nnv"
3. Post the results of "hdparm -I /dev/sdX" where sdX is one of th
problematic drives.
4. Run "hdparm -y /dev/sdX" to spin it down then issue SMART short test
manually. If it fails the same way, post what smartd/smartctl says and
the result of dmesg after the failure.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-02 12:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <474362.56402.qm@web51305.mail.re2.yahoo.com>
2007-11-02 12:09 ` [smartmontools-support] Bug/Issue Tejun Heo
2007-11-02 12:11 ` Tejun Heo
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).