Belkin RT3200 (aka. Linksys E8450) random crashes

SebTM · January 17, 2022, 12:11pm

Hello,

I got a Belkin RT3200 as they have really nice specs for the price (if available - GER). The setup went really smooth using the UBI installer provided on GitHub (https://github.com/dangowrt/linksys-e8450-openwrt-installer) - thanks very much for that!

Now I get random crashes where the complete router gets stuck or luci is not working (4/5XX) and in logread I get constant new messages like this:

Mon Jan 17 02:21:35 2022 kern.warn kernel: [20523.545686] print_req_error: 34353 callbacks suppressed
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.545693] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.563301] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.575053] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.585826] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.596576] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.608276] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.619036] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.630770] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.641523] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.653218] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:35 2022 kern.warn kernel: [20523.665648] buffer_io_error: 34347 callbacks suppressed
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.666240] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.679089] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.687680] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.695278] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.703946] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.711575] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.720229] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.727848] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.735385] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:35 2022 kern.err kernel: [20523.744056] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.warn kernel: [20528.555613] print_req_error: 34401 callbacks suppressed
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.555621] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.572530] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.583283] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.595062] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.605814] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.616988] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.627737] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.639519] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.650263] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.662034] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:40 2022 kern.warn kernel: [20528.675710] buffer_io_error: 34410 callbacks suppressed
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.675716] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.689535] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.697154] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.704693] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.713321] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.720942] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.729537] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.737155] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.744690] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:40 2022 kern.err kernel: [20528.753279] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.warn kernel: [20533.565684] print_req_error: 34421 callbacks suppressed
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.565692] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.582670] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.593415] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.605165] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.615899] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.627631] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.638372] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.650111] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.660844] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.672607] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:45 2022 kern.warn kernel: [20533.685572] buffer_io_error: 34416 callbacks suppressed
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.685579] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.699364] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.706976] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.714561] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.723126] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.730754] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.739384] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.747005] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.754565] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:45 2022 kern.err kernel: [20533.763169] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.warn kernel: [20538.575628] print_req_error: 34440 callbacks suppressed
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.575636] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.592517] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.603332] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.615067] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.625817] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.637595] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.648341] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.660075] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.670818] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.682544] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mon Jan 17 02:21:50 2022 kern.warn kernel: [20538.695525] buffer_io_error: 34440 callbacks suppressed
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.696051] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.708891] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.717513] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.725110] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.733701] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.741352] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.749995] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.757622] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.765158] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Mon Jan 17 02:21:50 2022 kern.err kernel: [20538.773797] Buffer I/O error on dev mtdblock2, logical block 32, async page read

I now found out that I can trigger this by restarting the interface "br-lan". After that this behavior starts directly and the router gets in a semi-crashed state (IPv6 e.g. stops working, IPv4-DHCP works fine, as well as PPPoE keeps the connection)

I searched a bit around for more debugging information I can provide but what I found was " /sys/fs/pstore/" which is empty and dumping mtd2 (hexdump) what I can do - but I wanted to ask if this contains sensible data like passwords before attaching it as I use the device already?

Device Information:

Model	Linksys E8450 (UBI)
Architecture	ARMv8 Processor rev 4
Target Platform	mediatek/mt7622
Firmware Version	OpenWrt SNAPSHOT r18125-b764cb9e5b / LuCI Master git-21.322.38385-6507b1f
Kernel Version	5.10.80

I also saw the upgrade possibilities by using "Attended Sysupgrade" to get the latest snapshot but as far as I know from the Software-Updates and another device docs I own it's not recommended to do so? (Maybe this is an exception because of the stability issues?)

Thanks for your help!
Keep safe

Edit: As recommended in IRC I also reported at the UBI-Installer-Repo: https://github.com/dangowrt/linksys-e8450-openwrt-installer/issues/64

Borromini · January 17, 2022, 12:19pm

Looks like a bad blocks issue, but UBI should handle that. When you google the Buffer I/O error thing you'll find some older threads on these forums but this seems by design, so it looks like that's not the error you're looking for.

Better just share logread output when restarting the network, maybe that could point to the culprit.

SebTM · January 17, 2022, 12:33pm

Thanks, as this error was the only consistent/occurring after I thought this would be different in this case - I reproduced the error by restarting again - here is the full log:
https://pastebin.com/g7TTBY7u (to long for here)

After that I tried restarting the network via ssh (service network restart) and collected the service overview while "crashed":

/etc/init.d/blockd                 enabled     running
/etc/init.d/boot                   enabled     stopped
/etc/init.d/bootcount              enabled     stopped
/etc/init.d/cron                   enabled     stopped
/etc/init.d/dnsmasq                enabled     running
/etc/init.d/done                   enabled     stopped
/etc/init.d/dropbear               enabled     running
/etc/init.d/firewall               enabled     stopped
/etc/init.d/fstab                  enabled     stopped
/etc/init.d/gpio_switch            enabled     stopped
/etc/init.d/led                    enabled     stopped
/etc/init.d/log                    enabled     running
/etc/init.d/network                enabled     running
/etc/init.d/odhcpd                 enabled     running
/etc/init.d/rpcd                   enabled     running
/etc/init.d/sysctl                 enabled     stopped
/etc/init.d/sysfixtime             enabled     stopped
/etc/init.d/sysntpd                enabled     running
/etc/init.d/system                 enabled     stopped
/etc/init.d/ucitrack               enabled     stopped
/etc/init.d/uhttpd                 enabled     running
/etc/init.d/umount                 enabled     stopped
/etc/init.d/urandom_seed           enabled     stopped
/etc/init.d/urngd                  enabled     running
/etc/init.d/wpad                   enabled     running

I also tried restarting uhttpd (service uhttpd restart) but nothing really helped, so I had to reboot the device again to fix it. After a reboot I can't find any I/O errors in the logs.

Edit: FYI

root@router:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "bl2"
mtd1: 00140000 00020000 "fip"
mtd2: 00100000 00020000 "factory"
mtd3: 07d00000 00020000 "ubi"

Would it be an idea to rerun the ubi-installer to ensure I didn't did something wrong which leads to this?

SebTM · January 28, 2022, 12:35pm

Switching to the latest snapshot resolved the issue (see GitHub issue for details) and even after some tests I can't reproduce the issue anymore so seems resolved

justinkb · January 29, 2022, 11:47am

just happened for me randomly on the snapshot included with 0.6.2 prerelease. could not access luci anymore, could still ssh into the device to reboot it however

system · February 8, 2022, 11:47am

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.