I would guess it's due to this, right from your boot log:
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x000000080000
nand_read_bbt: bad block at 0x000002200000
nand_read_bbt: bad block at 0x0000033e0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =27607040
scan filesys at 161000
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
[...]
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
I would guess it's due to this, right from your boot log:
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x000000080000
nand_read_bbt: bad block at 0x000002200000
nand_read_bbt: bad block at 0x0000033e0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =27607040
scan filesys at 161000
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
[...]
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
I would guess it's due to this, right from your boot log:
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x000000080000
nand_read_bbt: bad block at 0x000002200000
nand_read_bbt: bad block at 0x0000033e0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =27607040
scan filesys at 161000
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
[...]
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
you can flash through download fw to /tmp by wget command
Or copy fw to usb and flash to dd or mtd write command.
Due to your router log ...too may 3rd fw, you need erase jffs2 and brcmnand partitions, also due many btt badblocks then fw also backup in ddwrt partition or nandimage. If you able landing on cfe promt then :
flash -noheader...........to nflash1.trx.
Here my log so long time, some nvram mod,back up and compare before adjust.also i see no data_board partition leading kong fw miss detecting correct fw.
Posted: Thu Dec 06, 2018 0:22 Post subject: I cant flash it
deslatha wrote:
rejuas wrote:
jwh7 wrote:
I would guess it's due to this, right from your boot log:
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x000000080000
nand_read_bbt: bad block at 0x000002200000
nand_read_bbt: bad block at 0x0000033e0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =27607040
scan filesys at 161000
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
[...]
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
you can flash through download fw to /tmp by wget command
Or copy fw to usb and flash to dd or mtd write command.
Due to your router log ...too may 3rd fw, you need erase jffs2 and brcmnand partitions, also due many btt badblocks then fw also backup in ddwrt partition or nandimage. If you able landing on cfe promt then :
flash -noheader...........to nflash1.trx.
Here my log so long time, some nvram mod,back up and compare before adjust.also i see no data_board partition leading kong fw miss detecting correct fw.
check: cat /proc/mtd // to see full partitions
i cannot flash it!
how to make an smaller image?
even better, can you build a smaller image for me?