From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Kt1tI-0003w1-8w for garchives@archives.gentoo.org; Thu, 23 Oct 2008 15:14:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13815E02AB; Thu, 23 Oct 2008 15:14:23 +0000 (UTC) Received: from web51307.mail.re2.yahoo.com (web51307.mail.re2.yahoo.com [206.190.38.173]) by pigeon.gentoo.org (Postfix) with SMTP id AFB37E02AB for ; Thu, 23 Oct 2008 15:14:22 +0000 (UTC) Received: (qmail 50676 invoked by uid 60001); 23 Oct 2008 15:14:21 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=eQmgJnz2pZR7dgkVNy/cN4IdyYhv1gD5obmjAAUBjP1Gq4wN9bZ/p9GhgdCI7g/ikw/QuDo1Oz1Yh5gNVQ/ftZt7VaeKLOk6yARdO+cNPwCmqYWfdlRKn0PGKkhRk6KaoqyJrmiT0Y9RwwUKvcpd1jyvy2LC+hmGEYZg+hzjF+M=; X-YMail-OSG: EOAvvDQVM1kmeSzRQpA947foRJBjYedY3xjLp00rKv4JZ6xtb1ge8jG2RRhqW8aWji4gQlpw1IL0EwzwGt_zbc09xHw1hVgUa8FgRS8AmUz.fVVoJ7wwuWJCnpgSJXxM7qz0JrQ_UT0.HUeXmZYwnen7iKRGatqOvi2bxDQmdobp2EBKb64sTs_Ldw-- Received: from [193.114.208.194] by web51307.mail.re2.yahoo.com via HTTP; Thu, 23 Oct 2008 08:14:20 PDT X-Mailer: YahooMailWebService/0.7.247.3 Date: Thu, 23 Oct 2008 08:14:20 -0700 (PDT) From: Jon Hardcastle Subject: [gentoo-user] Smartd To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <76740.50007.qm@web51307.mail.re2.yahoo.com> X-Archives-Salt: 1234c6ff-b744-4252-aa25-84277d249ba3 X-Archives-Hash: 294be7f87b2efb150d9c6cb3ceb3563d Probably not strictly a Gentoo issue, but as i am running Gentoo I'll see i= f the collective knowledge here can help me! I have a strange problem with my server. All the hard drives go to sleep af= ter ~3hrs of inactivity. BUT if they happen to still be asleep when the sch= eduled smart check takes place you can hear it 'spin up' and just before yo= u know the drive is 'up' smartd decides the drive isn't smart capable and g= ives up. I get log entries in 'messages' and dmesg and also smartd emails m= e to tell me the drive isn't smart capable. You get the same result if you do -a on a sleeping drive... it says the dri= ve isn't capable.. run it again.. and Bob's your uncle. Any clues? Can you = vary the time before it tries after a spin up? ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com '..Be fearful when others are greedy, and be greedy when others are fearful= .' -----------------------