I am getting the following repeated messages in dmesg despite not having any nand mounted on my MS2110 ("OpenWrt SNAPSHOT r27453-732f539fb7"):
[76938.702095] ecc_sw_hamming_correct: uncorrectable ECC error
[76938.707700] ecc_sw_hamming_correct: uncorrectable ECC error
[76938.713409] ecc_sw_hamming_correct: uncorrectable ECC error
[165439.302697] mtdblock: MTD device 'uboot' is NAND, please consider using UBI block devices instead.
Is there a process that keeps on poking the nand despite nothing being mounted from it?
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noexec,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
/dev/md0 on / type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
sys on /sys type sysfs (rw,relatime)
#cat /proc/mtd
dev: size erasesize name
mtd0: 000e0000 00020000 "uboot"
mtd1: 00020000 00020000 "uboot_env"
mtd2: 0ff00000 00020000 "ubi"
#nanddump /dev/mtd0
ECC failed: 215
ECC corrected: 29
Number of bad blocks: 0
Number of bbt blocks: 0
Not printing binary garbage to tty. Use '-a'
or '--forcebinary' to override.
#nanddump /dev/mtd1
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Not printing binary garbage to tty. Use '-a'
or '--forcebinary' to override.
#nanddump /dev/mtd2
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 2
Number of bbt blocks: 0
Not printing binary garbage to tty. Use '-a'
or '--forcebinary' to override.