From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261405AbVETQEf (ORCPT ); Fri, 20 May 2005 12:04:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261488AbVETQEf (ORCPT ); Fri, 20 May 2005 12:04:35 -0400 Received: from ns9.hostinglmi.net ([213.194.149.146]:54706 "EHLO ns9.hostinglmi.net") by vger.kernel.org with ESMTP id S261405AbVETQE1 (ORCPT ); Fri, 20 May 2005 12:04:27 -0400 Date: Fri, 20 May 2005 18:06:23 +0200 From: DervishD To: Linux-kernel Subject: Hard disk LBA sector count is not always the same Message-ID: <20050520160623.GA63@DervishD> Mail-Followup-To: Linux-kernel Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i Organization: DervishD X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns9.hostinglmi.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - dervishd.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi all :)) I'm having a problem with my primary hard disk: it inconsistently reports the number of addressable LBA sectors. At times it reports 156301488 (let's call it '301' from now on) which is the correct one (I think) and other times it reports 156299375 (I'll call this one 299 from now on), a difference of 2103 sectors. But this is not arbitrary, I have reproduced the problem. I've done it using a self-compiled 2.4.29 kernel and a 2.6.10-1-k7 kernel from Debian unstable. These are the steps: STEP 1: From a fully powered off machine, I boot into my 2.4.29 kernel. The kernel log shows the 299 number, as well as does both hdparm -i and hdparm -I. No matter how many times I reboot these numbers maintain given I always reboot into 2.4.29. STEP 2: I reboot into my Debian system, using 2.6.10 kernel, and now kernel logs show 301 number, as does hdparm -I. But hdparm -i shows the 299 number. STEP 3: I reboot again into my Debian system. This time all places show the 301 number: the kernel logs, hdparm -i and -I. STEP 4: I reboot into my 2.4.19 kernel, and this time ALL places, again, show the 301 number. No matter how many times I reboot into 2.4.29 again or even 2.6 (Debian), these numbers doesn't change. I've done the same but starting from full power-off into Debian, and the things went like if we start from STEP 2 above. The only thing I've seen in the Debian logs that may explain this problem are: current capacity is 156299375 native capacity is 156301488 But I don't know why this happens... The disk (Seagate ST380021A, 80GB, UDMA100) is not showing symptoms of a coming failure, it works ok and no data corruption has happened (yet...), but I'm worried. Is this a known issue of 2.4 kernels? Am I doing anything wrong? Any other detail about hardware, logs, etc. you must know? Thanks a lot in advance :))) Raúl Núñez de Arenas Coronado -- Linux Registered User 88736 | http://www.dervishd.net http://www.pleyades.net & http://www.gotesdelluna.net It's my PC and I'll cry if I want to...