From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Nl3z0-0005sB-Ea for garchives@archives.gentoo.org; Fri, 26 Feb 2010 17:28:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E5804E0A40; Fri, 26 Feb 2010 17:27:32 +0000 (UTC) Received: from mail.askja.de (mail.askja.de [83.137.103.136]) by pigeon.gentoo.org (Postfix) with ESMTP id A7104E0A40 for ; Fri, 26 Feb 2010 17:27:32 +0000 (UTC) Received: from static-87-79-89-40.netcologne.de ([87.79.89.40] helo=zone.wonkology.org) by mail.askja.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Nl3yO-00042H-1e for gentoo-user@lists.gentoo.org; Fri, 26 Feb 2010 18:27:32 +0100 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by zone.wonkology.org with local; Fri, 26 Feb 2010 18:27:30 +0100 id 00011BB9.4B880482.000035D0 From: Alex Schuster To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] recovery from /var corruption? Date: Fri, 26 Feb 2010 18:27:25 +0100 User-Agent: KMail/1.13.0 (Linux/2.6.31-tuxonice_k8; KDE/4.4.0; i686; ; ) References: <5bdc1c8b1002251933s6a250b99v607c97e09f41d4fe@mail.gmail.com> <201002261701.55621.wonko@wonkology.org> <5bdc1c8b1002260853q60226061pcfa48bdef414bb5a@mail.gmail.com> In-Reply-To: <5bdc1c8b1002260853q60226061pcfa48bdef414bb5a@mail.gmail.com> 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: 7bit Message-Id: <201002261827.27513.wonko@wonkology.org> X-Archives-Salt: 699708b1-0909-475c-bea5-19df495218bb X-Archives-Hash: ffd8ddf8374370b968c00889b597c734 Mark Knecht writes: > On Fri, Feb 26, 2010 at 8:01 AM, Alex Schuster > wrote: > > Okay, but it still states: > >> * SMART error logging > >> * SMART self-test > > > > So maybe smartctl -t long /dev/hda still works? Just give it a try. > > No, -t long fails the same way. Basically every time I try to use > smartctl on the drive it seems to issue one of these 3-line reports > about SectorIDNotFound in dmesg. My other machines don't do this. Not > a good sign I think... > > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } > hda: task_no_data_intr: error=0x10 { SectorIdNotFound }, > LBAsect=16777008, sector=18446744073709551615 > hda: possibly failed opcode: 0xb0 Uh-oh. Okay, I guess it just won't work then. > Could this have ANYTHING to do with kernel configuation? Is there > anything required at the kernel level that I might not have turned on? I'm pretty sure it has nothing to do with the kernel, but with your drive being incapable of the SMART commands. But I guess using badblocks is not that different in the end. The SMART selftest runs in the background and does not create disk I/O, but I think it does nothing so much different from badblocks. Wonko