From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from a.ns.miles-group.at ([95.130.255.143] helo=radon.swed.at) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Y2Gsa-0003Ig-4p for linux-mtd@lists.infradead.org; Sat, 20 Dec 2014 10:03:20 +0000 Message-ID: <54954950.2030800@nod.at> Date: Sat, 20 Dec 2014 11:02:56 +0100 From: Richard Weinberger MIME-Version: 1.0 To: Oleksij Rempel , t kevin , linux-mtd@lists.infradead.org Subject: Re: Get error -74 (ECC error) during ubiattach References: <549540F1.4040107@nod.at> <549548D5.8070109@rempel-privat.de> In-Reply-To: <549548D5.8070109@rempel-privat.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am 20.12.2014 um 11:00 schrieb Oleksij Rempel: > Am 20.12.2014 um 10:27 schrieb Richard Weinberger: >> Hi! >> >> Am 20.12.2014 um 04:43 schrieb t kevin: >>> So for uncorrectable ECC error ( e.g., bad block) the only way out is >>> to do a fresh ubiformat? >>> For device like harddisk you get bad blocks all the time, if it is not >>> in the critical sector things can be fixed as much as possible by fsck >>> so I was looking for something like fsck.ubifs. >> >> An uncorrectable ECC error means that more bits flipped than your ECC >> algorithm can fix. > > At same time uncorrectable ECC error mean, the page was erase and there > is no ECC sum. Something should be written to create ECC. Which would be a driver bug and needs fixing. Thanks, //richard