Forum List Message List New Topic
dumdedumda
U-Boot: dmesg | grep -i 'bad' --> Bad eraseblock 72 at 0x000000900000
August 29, 2021 01:00AM
Getting bad eraseblock 72 when prepping installation of U-Boot 2017.07 for a new Pogoplug V4.

Google the error code and searched the forum and no dice. Any ideas on how to proceed?

Much appreciated. 

/tmp/tools # dmesg | grep -i 'bad'
<6>[    0.960000] Scanning device for bad blocks
<4>[    0.970000] Bad eraseblock 72 at 0x000000900000
<5>[    1.340000] UBI: number of bad PEBs:         0
<5>[    1.370000] UBI: number of PEBs reserved for bad PEB handling: 8
Reply Quote
bodhi
Re: U-Boot: dmesg | grep -i 'bad' --> Bad eraseblock 72 at 0x000000900000
August 29, 2021 01:26AM
dumdedumda,

Block 72 is way out away from u-boot. As the installation instruction metioned this. mtd0 is block 0 to 7.

Quote

4. Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M (8 blocks), don't flash u-boot, because you will almost certainly brick your box. Please post your question here (there is a work around for it).

Example of bad block in mtd0:
dmesg | grep -i 'bad'

[ 2.413231] Scanning device for bad blocks
[ 2.417731] Bad eraseblock 3 at 0x000000060000

This bad block is the 4th block which resides within mtd0 (block 0 to block 7). So u-boot should not be flashed.

So it is OK to install u-boot with bad block at 72.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: