What's new

Buffer I/O error on device mtdblock

  • 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!

panhead20

Occasional Visitor
After enabling and formatting the jffs partition, these errors are reported when booting. Is this a problem? Is there a way to repair/deallocate the bad blocks?

Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock6, sector 0
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock6, logical block 0
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock6, sector 8
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock6, logical block 1
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock6, sector 16
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock6, logical block 2
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock6, sector 24
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock6, logical block 3
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock6, sector 0
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock6, logical block 0
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock4, sector 0
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock4, logical block 0
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock4, sector 8
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock4, logical block 1
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock4, sector 16
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock4, logical block 2
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock4, sector 24
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock4, logical block 3
Dec 31 16:00:19 kernel: end_request: I/O error, dev mtdblock4, sector 0
Dec 31 16:00:19 kernel: Buffer I/O error on device mtdblock4, logical block 0
 
Your log mentions errors for two different partitions, so you might be having more issues than just the jffs partition itself. I recommend reflashing your firmware, then trying to reformat jffs again.

You didn't specify which router you have, so I cannot deduce which partitions these two are. One of these two partitions could also potentially be your settings partition, in which case you will have to reset your router to factory defaults using either mtd-erase, or the WPS button.
 
Thank you Merlin. This is an RT-AC66U. I will try your re-flash suggestion when I get home from work this evening.
 
Thank you Merlin. This is an RT-AC66U. I will try your re-flash suggestion when I get home from work this evening.

mtd4 contains the firmware

Code:
mtd0: 00040000 00010000 "pmon"
mtd1: 00010000 00010000 "nvram"
mtd2: 02000000 00020000 "linux"
mtd3: 01ecc3f0 00020000 "rootfs"
mtd4: 02000000 00020000 "trx"
mtd5: 02000000 00020000 "jffs2"
mtd6: 03f00000 00020000 "brcmnand"

Since there are errors at the start of mtd4, I suspect your problem is with the firmware. Reflashing has a good chance of fixing this.
 
swap partition generates buffer I/O errors

Strange, when I enable a swap partition in the jffs/scripts/post-mount script the boot log report the buffer I/O errors. If I remove the script the errors are not reported. The swap partition is on an external flash drive partition (type 82). The swap partition appears to be working, free reports proper total and free values and the Tools/Sysinfo tab reports swap usage 0.00 / 497.84 MB.
Errors are reported right before the swap partition is enabled.

RT-AC66U/3.0.04.354.27 Merlin

Dec 31 16:00:14 kernel: EXT3-fs: Unrecognized mount option "umask=0000" or missing value
Dec 31 16:00:14 hotplug[548]: USB /dev/sda1(ext3) failed to mount at the first try!
Dec 31 16:00:14 kernel: kjournald starting. Commit interval 5 seconds
Dec 31 16:00:14 kernel: EXT3 FS on sda1, internal journal
Dec 31 16:00:14 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 31 16:00:14 hotplug[548]: USB ext3 fs at /dev/sda1 mounted on /tmp/mnt/sda1
Dec 31 16:00:14 kernel: end_request: I/O error, dev mtdblock6, sector 0
Dec 31 16:00:14 kernel: Buffer I/O error on device mtdblock6, logical block 0
Dec 31 16:00:14 kernel: end_request: I/O error, dev mtdblock6, sector 8
Dec 31 16:00:14 kernel: Buffer I/O error on device mtdblock6, logical block 1
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock6, sector 16
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock6, logical block 2
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock6, sector 24
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock6, logical block 3
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock6, sector 0
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock6, logical block 0
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock4, sector 0
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock4, logical block 0
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock4, sector 8
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock4, logical block 1
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock4, sector 16
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock4, logical block 2
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock4, sector 24
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock4, logical block 3
Dec 31 16:00:15 kernel: end_request: I/O error, dev mtdblock4, sector 0
Dec 31 16:00:15 kernel: Buffer I/O error on device mtdblock4, logical block 0
Dec 31 16:00:15 rc_service: hotplug 548:notify_rc restart_nasapps
Dec 31 16:00:15 kernel: Adding 509784k swap on /dev/sda2. Priority:-1 extents:1 across:509784k
 
Last edited:
You could try manually erasing the JFFS partition, tho your errors do point at a problem in the firmware partition rather than the JFFS one.

Code:
mtd-erase -d jffs2
reboot
 
You could try manually erasing the JFFS partition, tho your errors do point at a problem in the firmware partition rather than the JFFS one.

Why would the errors only be reported if I enable a swap partition? Kernel attempting to write into those partitions when setting up the swap partition?
 
Why would the errors only be reported if I enable a swap partition? Kernel attempting to write into those partitions when setting up the swap partition?

I have no idea. I don't see any relation between the two either.
 
Have the same errors after enabling swap on my PLATINUM My Drive 2.5' drive.

dmesg | grep error

Code:
end_request: I/O error, dev mtdblock6, sector 0
Buffer I/O error on device mtdblock6, logical block 0
end_request: I/O error, dev mtdblock6, sector 8
Buffer I/O error on device mtdblock6, logical block 1
end_request: I/O error, dev mtdblock6, sector 16
Buffer I/O error on device mtdblock6, logical block 2
end_request: I/O error, dev mtdblock6, sector 24
Buffer I/O error on device mtdblock6, logical block 3
end_request: I/O error, dev mtdblock6, sector 0
Buffer I/O error on device mtdblock6, logical block 0
end_request: I/O error, dev mtdblock4, sector 0
Buffer I/O error on device mtdblock4, logical block 0
end_request: I/O error, dev mtdblock4, sector 8
Buffer I/O error on device mtdblock4, logical block 1
end_request: I/O error, dev mtdblock4, sector 16
Buffer I/O error on device mtdblock4, logical block 2
end_request: I/O error, dev mtdblock4, sector 24
Buffer I/O error on device mtdblock4, logical block 3
end_request: I/O error, dev mtdblock4, sector 0
Buffer I/O error on device mtdblock4, logical block 0
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock6, sector 8
end_request: I/O error, dev mtdblock6, sector 16
end_request: I/O error, dev mtdblock6, sector 24
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock4, sector 0
end_request: I/O error, dev mtdblock4, sector 8
end_request: I/O error, dev mtdblock4, sector 16
end_request: I/O error, dev mtdblock4, sector 24
end_request: I/O error, dev mtdblock4, sector 0
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock6, sector 8
end_request: I/O error, dev mtdblock6, sector 16
end_request: I/O error, dev mtdblock6, sector 24
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock4, sector 0
end_request: I/O error, dev mtdblock4, sector 8
end_request: I/O error, dev mtdblock4, sector 16
end_request: I/O error, dev mtdblock4, sector 24
end_request: I/O error, dev mtdblock4, sector 0
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock6, sector 8
end_request: I/O error, dev mtdblock6, sector 16
end_request: I/O error, dev mtdblock6, sector 24
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock4, sector 0
end_request: I/O error, dev mtdblock4, sector 8
end_request: I/O error, dev mtdblock4, sector 16
end_request: I/O error, dev mtdblock4, sector 24
end_request: I/O error, dev mtdblock4, sector 0
end_request: I/O error, dev mtdblock6, sector 0
Buffer I/O error on device mtdblock6, logical block 0
end_request: I/O error, dev mtdblock6, sector 8
Buffer I/O error on device mtdblock6, logical block 1
end_request: I/O error, dev mtdblock6, sector 16
Buffer I/O error on device mtdblock6, logical block 2
end_request: I/O error, dev mtdblock6, sector 24
Buffer I/O error on device mtdblock6, logical block 3
end_request: I/O error, dev mtdblock6, sector 0
Buffer I/O error on device mtdblock6, logical block 0
end_request: I/O error, dev mtdblock4, sector 0
Buffer I/O error on device mtdblock4, logical block 0
end_request: I/O error, dev mtdblock4, sector 8
Buffer I/O error on device mtdblock4, logical block 1
end_request: I/O error, dev mtdblock4, sector 16
Buffer I/O error on device mtdblock4, logical block 2
end_request: I/O error, dev mtdblock4, sector 24
Buffer I/O error on device mtdblock4, logical block 3
end_request: I/O error, dev mtdblock4, sector 0
Buffer I/O error on device mtdblock4, logical block 0
end_request: I/O error, dev mtdblock6, sector 0
Buffer I/O error on device mtdblock6, logical block 0
end_request: I/O error, dev mtdblock6, sector 8
end_request: I/O error, dev mtdblock6, sector 16
end_request: I/O error, dev mtdblock6, sector 24
end_request: I/O error, dev mtdblock6, sector 0
end_request: I/O error, dev mtdblock4, sector 0
Buffer I/O error on device mtdblock4, logical block 0
end_request: I/O error, dev mtdblock4, sector 8
end_request: I/O error, dev mtdblock4, sector 16
end_request: I/O error, dev mtdblock4, sector 24
end_request: I/O error, dev mtdblock4, sector 0
 
I see now that when using the "device path" /dev/partion it just works as it should be. Normally I'm using labels or UUID in fstab and this is what causes these errors. Strange but true look at this vid.

http://www.sendspace.com/file/9t7f28

Now everything works well and for me it's not a problem using the device path because I only have one USB drive attached. Does nobody else has these errors when using UUID?
 

Similar threads

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