Report on __nand_correct_data: uncorrectable ECC error

[Enrico Rovere]

Hi,

I was checking the logs on my DNS-320L, and found a couple errors in KernelLog and SystemLog (both attached), relative to mtdblock0. 

Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: blk_update_request: I/O error, dev mtdblock0, sector 248
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: blk_update_request: I/O error, dev mtdblock0, sector 0
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: blk_update_request: I/O error, dev mtdblock0, sector 8
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: Buffer I/O error on dev mtdblock0, logical block 0, async page read
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: Buffer I/O error on dev mtdblock0, logical block 66, async page read
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: Buffer I/O error on dev mtdblock0, logical block 66, async page read
Feb  5 19:49:05 DNS-320L-032050 user.err kernel: __nand_correct_data: uncorrectable ECC error

I've been looking at past threads on this group on the matter, and learned D-Link cheaped on the NAND for this box, hence the premature failures of the blocks. Thought I'd report this to the developer. Still, I have a question.

Since the errors are only on mtdblock0, and apparently that's where u-boot resides, wouldn't the box even boot with this many damaged blocks? I read here https://groups.google.com/forum/#!msg/alt-f/xBULQIdEax8/UMqZv0HsAgAJ speculating a different ECC technique is used on those blocks, and I imagine that's the reason linux kernel is unhappy with them.

Should I worry about this issue, considering the box is only a couple months old? I could revert back to D-Link firmware and claim warranty, if that was the case.

Thanks in advance,

Enrico