What's new

Startup system log question

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

DarnellG

Regular Contributor
Below is a part of my startup system log. Everything seems to be running fine but are the 2 "bad block table" lines anything to be concerned with? I'm running the 384.14 merlin firmware on a RT-AX88U.

5:11 kernel: jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
May 5 05:05:11 kernel: fuse init (API version 7.23)
May 5 05:05:11 kernel: io scheduler noop registered (default)
May 5 05:05:11 kernel: brd: module loaded
May 5 05:05:11 kernel: loop: module loaded
May 5 05:05:11 kernel: nand: device found, Manufacturer ID: 0xef, Chip ID: 0xda
May 5 05:05:11 kernel: nand: Unknown W29N02GV
May 5 05:05:11 kernel: nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
May 5 05:05:11 kernel: bcm63xx_nand ff801800.nand: Adjust timing_1 to 0x65324458 timing_2 to 0x80040e54
May 5 05:05:11 kernel: bcm63xx_nand ff801800.nand: detected 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, BCH-4
May 5 05:05:11 kernel: Bad block table found at page 131008, version 0x01
May 5 05:05:11 kernel: Bad block table found at page 130944, version 0x01

May 5 05:05:11 kernel: >>>>> For primary mtd partition rootfs, cferam/vmlinux.lz mounted as JFFS2, vmlinux fs mounted as UBIFS <<<<<
May 5 05:05:11 kernel: Secondary mtd partition rootfs_update detected as JFFS2 for cferam/vmlinux source and UBIFS for vmlinux filesystem
May 5 05:05:11 kernel: setup_mtd_parts: misc indx 2 name misc3 nvram configured size 1
May 5 05:05:11 kernel: setup_mtd_parts: name misc3 configured size 0x00100000 offset 0xF600000
May 5 05:05:11 kernel: setup_mtd_parts: misc indx 1 name misc2 nvram configured size 63
May 5 05:05:11 kernel: setup_mtd_parts: name misc2 configured size 0x03f00000 offset 0xB700000
 
That's normal. On startup it checks to see if there is a bad block table present on the device. If there isn't it creates one.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top