To: linux-kernel@vger.kernel.org
From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
Subject: Re: Getting error message "Cannot read inode bitmap". Someone able
 to help?
Date: Tue, 03 Aug 2010 11:20:07 +0200
Message-ID: <i38n5j$pui$1@dough.gmane.org>
References: <i2nj7d$lpi$1@dough.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100721 SeaMonkey/2.0.6
In-Reply-To: <i2nj7d$lpi$1@dough.gmane.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1115
Lines: 21

Manuel Reimer wrote:
> With my first try (ext2 on target disk) I got the error "Cannot read
> inode bitmap". The kernel reported this error for the *target* device
> (the brand new SATA hard drive). I did a second try and reformated the
> target drive to ext3 and, again, I got the same error. So I installed
> "smartmontools" into my running live system and checked the drive. The
> new drive has no "reallocated sectors" but several read errors (about 500).

Sorry for the spam (maybe I'm on the wrong ML at all... don't know...) 
but I fixed this on my own. I didn't expect the new disk to be the 
reason for this problem, but after checking for badblocks I got a value 
far over 1000 of bad blocks.

So I'll send this disk back to the vendor to get my money back and get a 
new one...

Nice to know, that Linux was *not* the reason for those errors.

Yours

Manuel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/