Belkin RT3200 / Linksys E8450 stuck in initramfs

I tried updating a happily-running Belkin RT3200 to 22.03.02. However, I'm stuck in initramfs, and nothing I've tried flashing from Luci, once that initramfs has booted, is taking hold - I'm always kicked back to initramfs after reboot.

Specifically, and this is probably where I went wrong, I flashed https://downloads.openwrt.org/releases/22.03.2/targets/mediatek/mt7622/openwrt-22.03.2-mediatek-mt7622-linksys_e8450-squashfs-sysupgrade.bin - resulting in the everlasting initramfs on reboot. I think the issue might have been that this wasn't the UBI image. The initramfs footer says it's OpenWrt 22.03.0-rc5 r19523-bfd070e7fa

Since then, I've tried the Recovery and Sysupgrade images from https://firmware-selector.openwrt.org/?version=22.03.2&target=mediatek%2Fmt7622&id=linksys_e8450-ubi (i.e. the UBI images), in that order, and also the 22.03.1 -installer.itb and -sysupgrade.itb images from https://github.com/dangowrt/owrt-ubi-installer/releases . Nothing seems to take hold - I'm always kicked back to the 22.03 rc5 initramfs.

Does anyone have a suggested next step? Is there anything from the above that I should try again, in case I am wrong about the order in which I tried flashing these?

Probably the device has crashed and is now waiting for you to report the reason of the crash to us :wink:

Please login via SSH and do this and share the output here:

cat /sys/fs/pstore/*
rm /sys/fs/pstore/*
reboot

The device should then come up booting into the production firmware again.

1 Like

I'm really grateful to you - that was exactly the problem. You shouldn't spend time looking through the error log, as I think it's just down to me trying to flash the wrong image (non-UBI .bin, onto a UBI device). I think it'd be nice if https://firmware-selector.openwrt.org/?version=22.03.2&target=mediatek%2Fmt7622&id=linksys_e8450 carried a big warning that this is just the non-UBI version and probably shouldn't be used.

Perhaps Luci's warning banner that "this is just an initramfs LUCI, nothing will persist" could also say that "If you're seeing this repeatedly, try logging in over SSH and viewing/clearing the contents of
/sys/fs/pstore/* "

But for future reference, here's the pstore log:

cat /sys/fs/pstore/*

Panic#1 Part1
<5>[    0.905373] 0x000000000000-0x000000080000 : "Preloader"
<5>[    0.911486] 0x000000080000-0x0000000c0000 : "ATF"
<5>[    0.916850] 0x0000000c0000-0x000000140000 : "u-boot"
<5>[    0.922722] 0x000000140000-0x0000001c0000 : "u-boot-env"
<5>[    0.928913] 0x0000001c0000-0x0000002c0000 : "factory"
<5>[    0.935373] 0x000000300000-0x000000320000 : "devinfo"
<5>[    0.940939] 0x000000320000-0x000000340000 : "senv"
<5>[    0.946256] 0x000000360000-0x000000380000 : "bootseq"
<5>[    0.951849] 0x000000500000-0x000002300000 : "firmware1"
<5>[    0.987182] 0x000002300000-0x000004100000 : "firmware2"
<5>[    1.022805] 0x000004100000-0x000005a00000 : "data"
<5>[    1.053002] 0x000005a00000-0x000006e00000 : "mfg"
<3>[    1.123105] mtk_soc_eth 1b100000.ethernet: generated random MAC address [REDACTED]
<6>[    1.131613] mtk_soc_eth 1b100000.ethernet eth0: mediatek frame engine at 0xffffffc011d00000, irq 37
<6>[    1.142348] i2c /dev entries driver
<6>[    1.147150] mtk-wdt 10212000.watchdog: Watchdog enabled (timeout=31 sec, nowayout=0)
<6>[    1.158599] NET: Registered protocol family 10
<6>[    1.164029] Segment Routing with IPv6
<6>[    1.167731] NET: Registered protocol family 17
<6>[    1.172252] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
<6>[    1.185361] 8021q: 802.1Q VLAN Support v1.8
<6>[    1.190711] pstore: Using crash dump compression: deflate
<6>[    1.205996] mtk-pcie 1a143000.pcie: host bridge /pcie@1a143000 ranges:
<7>[    1.212568] mtk-pcie 1a143000.pcie: Parsing ranges property...
<6>[    1.218403] mtk-pcie 1a143000.pcie:      MEM 0x0020000000..0x0027ffffff -> 0x0020000000
<6>[    1.242970] mtk-pcie 1a143000.pcie: PCI host bridge to bus 0000:00
<6>[    1.249159] pci_bus 0000:00: root bus resource [bus 00-ff]
<6>[    1.254654] pci_bus 0000:00: root bus resource [mem 0x20000000-0x27ffffff]
<7>[    1.261522] pci_bus 0000:00: scanning bus
<6>[    1.265575] pci 0000:00:00.0: [14c3:3258] type 01 class 0x060400
<6>[    1.271602] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x1ffffffff 64bit pref]
<7>[    1.280451] pci_bus 0000:00: fixups for bus
<7>[    1.284651] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 0
<6>[    1.291344] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
<7>[    1.299356] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
<7>[    1.306197] pci_bus 0000:01: scanning bus
<6>[    1.310420] pci 0000:01:00.0: [14c3:7915] type 00 class 0x000280
<6>[    1.316608] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
<6>[    1.323933] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
<6>[    1.331252] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
<6>[    1.339214] pci 0000:01:00.0: supports D1 D2
<6>[    1.343480] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
<7>[    1.350109] pci 0000:01:00.0: PME# disabled
<6>[    1.354594] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
<7>[    1.393002] pci_bus 0000:01: fixups for bus
<7>[    1.397188] pci_bus 0000:01: bus scan returning with max=01
<6>[    1.402773] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
<7>[    1.409383] pci_bus 0000:00: bus scan returning with max=01
<6>[    1.414971] pci 0000:00:00.0: BAR 0: no space for [mem size 0x200000000 64bit pref]
<6>[    1.422623] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x200000000 64bit pref]
<6>[    1.430619] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x201fffff]
<6>[    1.437407] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x200fffff 64bit pref]
<6>[    1.445230] pci 0000:01:00.0: BAR 2: assigned [mem 0x20100000-0x20103fff 64bit pref]
<6>[    1.453055] pci 0000:01:00.0: BAR 4: assigned [mem 0x20104000-0x20104fff 64bit pref]
<6>[    1.460873] pci 0000:00:00.0: PCI bridge to [bus 01]
<6>[    1.465838] pci 0000:00:00.0:   bridge window [mem 0x20000000-0x201fffff]
<3>[    1.472725] pcieport 0000:00:00.0: of_irq_parse_pci: failed with rc=-22
<7>[    1.479330] pcieport 0000:00:00.0: assign IRQ: got 0
<6>[    1.484303] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
<7>[    1.490407] pcieport 0000:00:00.0: enabling bus mastering
<6>[    1.496353] mtk-pcie 1a145000.pcie: host bridge /pcie@1a145000 ranges:
<7>[    1.502904] mtk-pcie 1a145000.pcie: Parsing ranges property...
<6>[    1.508737] mtk-pcie 1a145000.pcie:      MEM 0x0028000000..0x002fffffff -> 0x0028000000
<6>[    1.616955] mtk-pcie 1a145000.pcie: Port1 link down
<6>[    1.621973] mtk-pcie 1a145000.pcie: PCI host bridge to bus 0001:00
<6>[    1.628152] pci_bus 0001:00: root bus resource [bus 00-ff]
<6>[    1.633643] pci_bus 0001:00: root bus resource [mem 0x28000000-0x2fffffff]
<7>[    1.640510] pci_bus 0001:00: scanning bus
<7>[    1.645703] pci_bus 0001:00: fixups for bus
<7>[    1.649879] pci_bus 0001:00: bus scan returning with max=00
<6>[    1.655792] mtk_hsdma 1b007000.dma-controller: Using 3 as missing dma-requests property
<6>[    1.664069] mtk_hsdma 1b007000.dma-controller: MediaTek HSDMA driver registered
<6>[    1.721130] mt7530 mdio-bus:00 lan1 (uninitialized): PHY [mt7530-0:00] driver [MediaTek MT7531 PHY] (irq=145)
<6>[    1.740996] mt7530 mdio-bus:00 lan2 (uninitialized): PHY [mt7530-0:01] driver [MediaTek MT7531 PHY] (irq=146)
<6>[    1.760857] mt7530 mdio-bus:00 lan3 (uninitialized): PHY [mt7530-0:02] driver [MediaTek MT7531 PHY] (irq=147)
<6>[    1.780714] mt7530 mdio-bus:00 lan4 (uninitialized): PHY [mt7530-0:03] driver [MediaTek MT7531 PHY] (irq=148)
<6>[    1.800775] mt7530 mdio-bus:00 wan (uninitialized): PHY [mt7530-0:04] driver [MediaTek MT7531 PHY] (irq=149)
<6>[    1.812473] mt7530 mdio-bus:00: configuring for fixed/2500base-x link mode
<6>[    1.819541] DSA: tree 0 setup
<6>[    1.819719] mt7530 mdio-bus:00: Link is Up - 2.5Gbps/Full - flow control rx/tx
<6>[    1.823343] xhci-mtk 1a0c0000.usb: xHCI Host Controller
<6>[    1.835000] xhci-mtk 1a0c0000.usb: new USB bus registered, assigned bus number 1
<6>[    1.844104] xhci-mtk 1a0c0000.usb: hcc params 0x01403198 hci version 0x96 quirks 0x0000000000210010
<6>[    1.853193] xhci-mtk 1a0c0000.usb: irq 31, io mem 0x1a0c0000
<6>[    1.859340] hub 1-0:1.0: USB hub found
<6>[    1.863139] hub 1-0:1.0: 2 ports detected
<6>[    1.867423] xhci-mtk 1a0c0000.usb: xHCI Host Controller
<6>[    1.872673] xhci-mtk 1a0c0000.usb: new USB bus registered, assigned bus number 2
<6>[    1.880071] xhci-mtk 1a0c0000.usb: Host supports USB 3.0 SuperSpeed
<6>[    1.886387] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
<6>[    1.894802] hub 2-0:1.0: USB hub found
<6>[    1.898576] hub 2-0:1.0: 1 port detected
<5>[    1.903621] UBI: auto-attach mtd10
<5>[    1.907035] ubi0: attaching mtd10
<5>[    1.986937] ubi0: scanning is finished
<3>[    1.993565] ubi0 error: 0xffffffc010526c3c: too large reserved_pebs 752, good PEBs 200
<3>[    2.001475] ubi0 error: 0xffffffc010526a74: volume table check failed: record 5, error 9
<3>[    2.009569] Volume table record 5 dump:
<3>[    2.013405] 	reserved_pebs   752
<3>[    2.016623] 	alignment       1
<3>[    2.019667] 	data_pad        0
<3>[    2.022716] 	vol_type        1
<3>[    2.025761] 	upd_marker      0
<3>[    2.028805] 	name_len        11
<3>[    2.031946] 	name            rootfs_data
<3>[    2.035858] 	crc             0x971d97fc
<3>[    2.039781] ubi0 error: 0xffffffc01052b12c: failed to attach mtd10, error -22
<3>[    2.046933] UBI error: cannot attach mtd10
<7>[    2.051892] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
<7>[    2.059369] Please append a correct "root=" boot option; here are the available partitions:
<7>[    2.067745] 1f00             512 mtdblock0 
<7>[    2.067747]  (driver?)
<7>[    2.074280] 1f04             256 mtdblock1 
<7>[    2.074282]  (driver?)
<7>[    2.080806] 1f08             512 mtdblock2 
<7>[    2.080808]  (driver?)
<7>[    2.087338] 1f0c             512 mtdblock3 
<7>[    2.087340]  (driver?)
<7>[    2.093870] 1f10            1024 mtdblock4 
<7>[    2.093871]  (driver?)
<7>[    2.100394] 1f14             128 mtdblock5 
<7>[    2.100396]  (driver?)
<7>[    2.106934] 1f18             128 mtdblock6 
<7>[    2.106935]  (driver?)
<7>[    2.113464] 1f1c             128 mtdblock7 
<7>[    2.113466]  (driver?)
<7>[    2.119989] 1f20           30720 mtdblock8 
<7>[    2.119990]  (driver?)
<7>[    2.126517] 1f24           30720 mtdblock9 
<7>[    2.126519]  (driver?)
<7>[    2.133047] 1f28           25600 mtdblock10 
<7>[    2.133049]  (driver?)
<7>[    2.139658] 1f2c           20480 mtdblock11 
<7>[    2.139660]  (driver?)
<0>[    2.146280] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
<2>[    2.154535] SMP: stopping secondary CPUs
<0>[    2.158452] Kernel Offset: disabled
<0>[    2.161933] CPU features: 0x00000002,04002004
<0>[    2.166279] Memory Limit: none

Yes, that's exactly what it was.

I like the idea, but adding yet another conditional header to all the themes (like the "no root password set" and "initramfs running" warning banners) is not such a good option. Actually there has been a suggestion for a generic notification framework which can take care of this and many other warnings:

Hm, as you are not the first one to fall into that problem I agree, something has to be improved there. Just removing the non-UBI image is not an option, because (I believe) some people may actually be using it (?). I guess adding a warning about that to the README.md of the installer in github might be the best and easiest thing to do for now...

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