Understanding mtd bad blocks

...and not bricking your device.

(Because I've done that already).

Got a new NSA325v2 and I see some bad blocks. I'd like to load the Arch kirkwood UBoot, or the bodhi UBoot, but I want to confirm my understanding here first. And that is:

That uboot flashed mtd0 only and that bad blocks else where should not brick the device.

From dmesg I see that I have two bad blocks, but from the addresses that they are in mtd5 and mtd6.

[   13.999538] Scanning device for bad blocks
[   14.009360] Bad eraseblock 100 at 0x000000c80000
[   14.019657] Bad eraseblock 200 at 0x000001900000
[   14.071008] Creating 9 MTD partitions on "orion_nand":
[   14.076174] 0x000000000000-0x000000100000 : "uboot"
[   14.081479] 0x000000100000-0x000000180000 : "uboot_env"
[   14.087029] 0x000000180000-0x000000200000 : "key_store"
[   14.092631] 0x000000200000-0x000000280000 : "info"
[   14.097748] 0x000000280000-0x000000c80000 : "etc"
[   14.102850] 0x000000c80000-0x000001680000 : "kernel_1"
[   14.108336] 0x000001680000-0x000004640000 : "rootfs1"
[   14.113803] 0x000004640000-0x000005040000 : "kernel_2"
[   14.119286] 0x000005040000-0x000008000000 : "rootfs2"

What do you all think? :)

TIA

T

technosf,

> [ 13.999538] Scanning device for bad blocks
> [ 14.009360] Bad eraseblock 100 at
> 0x000000c80000
> [ 14.019657] Bad eraseblock 200 at
> 0x000001900000

True, these bad blocks are not in mtd0, so it is safe to flash u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)