Belkin RT3200 / Linksys E8450 stuck in initramfs (2)

Installing and Using OpenWrt
1

The output from cat /sys/fs/pstore/* is:

@OpenWrt:~# cat /sys/fs/pstore/*
Panic#1 Part1
<5>[    0.893397] 0x000000000000-0x000000080000 : "Preloader"
<5>[    0.899513] 0x000000080000-0x0000000c0000 : "ATF"
<5>[    0.904893] 0x0000000c0000-0x000000140000 : "u-boot"
<5>[    0.910731] 0x000000140000-0x0000001c0000 : "u-boot-env"
<5>[    0.916946] 0x0000001c0000-0x0000002c0000 : "factory"
<5>[    0.923384] 0x000000300000-0x000000320000 : "devinfo"
<5>[    0.928981] 0x000000320000-0x000000340000 : "senv"
<5>[    0.934285] 0x000000360000-0x000000380000 : "bootseq"
<5>[    0.939896] 0x000000500000-0x000002300000 : "firmware1"
<5>[    0.975227] 0x000002300000-0x000004100000 : "firmware2"
<5>[    1.010830] 0x000004100000-0x000005a00000 : "data"
<5>[    1.041008] 0x000005a00000-0x000006e00000 : "mfg"
<3>[    1.111086] mtk_soc_eth 1b100000.ethernet: generated random MAC address 5a:eb:93:47:b1:5f
<6>[    1.119643] mtk_soc_eth 1b100000.ethernet eth0: mediatek frame engine at 0xffffffc011ce0000, irq 37
<6>[    1.130369] i2c /dev entries driver
<6>[    1.135183] mtk-wdt 10212000.watchdog: Watchdog enabled (timeout=31 sec, nowayout=0)
<6>[    1.146650] NET: Registered protocol family 10
<6>[    1.152060] Segment Routing with IPv6
<6>[    1.155797] NET: Registered protocol family 17
<6>[    1.160282] 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.173388] 8021q: 802.1Q VLAN Support v1.8
<6>[    1.178771] pstore: Using crash dump compression: deflate
<6>[    1.193878] mtk-pcie 1a143000.pcie: host bridge /pcie@1a143000 ranges:
<7>[    1.200442] mtk-pcie 1a143000.pcie: Parsing ranges property...
<6>[    1.206287] mtk-pcie 1a143000.pcie:      MEM 0x0020000000..0x0027ffffff -> 0x0020000000
<6>[    1.230847] mtk-pcie 1a143000.pcie: PCI host bridge to bus 0000:00
<6>[    1.237051] pci_bus 0000:00: root bus resource [bus 00-ff]
<6>[    1.242531] pci_bus 0000:00: root bus resource [mem 0x20000000-0x27ffffff]
<7>[    1.249402] pci_bus 0000:00: scanning bus
<6>[    1.253450] pci 0000:00:00.0: [14c3:3258] type 01 class 0x060400
<6>[    1.259487] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x1ffffffff 64bit pref]
<7>[    1.268340] pci_bus 0000:00: fixups for bus
<7>[    1.272531] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 0
<6>[    1.279235] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
<7>[    1.287252] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
<7>[    1.294078] pci_bus 0000:01: scanning bus
<6>[    1.298310] pci 0000:01:00.0: [14c3:7915] type 00 class 0x000280
<6>[    1.304496] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
<6>[    1.311816] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
<6>[    1.319140] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
<6>[    1.327103] pci 0000:01:00.0: supports D1 D2
<6>[    1.331365] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
<7>[    1.337998] pci 0000:01:00.0: PME# disabled
<6>[    1.342479] 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.385714] pci_bus 0000:01: fixups for bus
<7>[    1.389900] pci_bus 0000:01: bus scan returning with max=01
<6>[    1.395487] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
<7>[    1.402099] pci_bus 0000:00: bus scan returning with max=01
<6>[    1.407687] pci 0000:00:00.0: BAR 0: no space for [mem size 0x200000000 64bit pref]
<6>[    1.415339] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x200000000 64bit pref]
<6>[    1.423335] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x201fffff]
<6>[    1.430123] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x200fffff 64bit pref]
<6>[    1.437947] pci 0000:01:00.0: BAR 2: assigned [mem 0x20100000-0x20103fff 64bit pref]
<6>[    1.445773] pci 0000:01:00.0: BAR 4: assigned [mem 0x20104000-0x20104fff 64bit pref]
<6>[    1.453590] pci 0000:00:00.0: PCI bridge to [bus 01]
<6>[    1.458555] pci 0000:00:00.0:   bridge window [mem 0x20000000-0x201fffff]
<3>[    1.465443] pcieport 0000:00:00.0: of_irq_parse_pci: failed with rc=-22
<7>[    1.472048] pcieport 0000:00:00.0: assign IRQ: got 0
<6>[    1.477022] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
<7>[    1.483125] pcieport 0000:00:00.0: enabling bus mastering
<6>[    1.489066] mtk-pcie 1a145000.pcie: host bridge /pcie@1a145000 ranges:
<7>[    1.495616] mtk-pcie 1a145000.pcie: Parsing ranges property...
<6>[    1.501449] mtk-pcie 1a145000.pcie:      MEM 0x0028000000..0x002fffffff -> 0x0028000000
<6>[    1.609656] mtk-pcie 1a145000.pcie: Port1 link down
<6>[    1.614672] mtk-pcie 1a145000.pcie: PCI host bridge to bus 0001:00
<6>[    1.620848] pci_bus 0001:00: root bus resource [bus 00-ff]
<6>[    1.626341] pci_bus 0001:00: root bus resource [mem 0x28000000-0x2fffffff]
<7>[    1.633207] pci_bus 0001:00: scanning bus
<7>[    1.638401] pci_bus 0001:00: fixups for bus
<7>[    1.642579] pci_bus 0001:00: bus scan returning with max=00
<6>[    1.648505] mtk_hsdma 1b007000.dma-controller: Using 3 as missing dma-requests property
<6>[    1.656769] mtk_hsdma 1b007000.dma-controller: MediaTek HSDMA driver registered
<6>[    1.714514] mt7530 mdio-bus:00 lan1 (uninitialized): PHY [mt7530-0:00] driver [MediaTek MT7531 PHY] (irq=145)
<6>[    1.734386] mt7530 mdio-bus:00 lan2 (uninitialized): PHY [mt7530-0:01] driver [MediaTek MT7531 PHY] (irq=146)
<6>[    1.754219] mt7530 mdio-bus:00 lan3 (uninitialized): PHY [mt7530-0:02] driver [MediaTek MT7531 PHY] (irq=147)
<6>[    1.774079] mt7530 mdio-bus:00 lan4 (uninitialized): PHY [mt7530-0:03] driver [MediaTek MT7531 PHY] (irq=148)
<6>[    1.794138] mt7530 mdio-bus:00 wan (uninitialized): PHY [mt7530-0:04] driver [MediaTek MT7531 PHY] (irq=149)
<6>[    1.805877] mt7530 mdio-bus:00: configuring for fixed/2500base-x link mode
<6>[    1.812950] DSA: tree 0 setup
<6>[    1.813126] mt7530 mdio-bus:00: Link is Up - 2.5Gbps/Full - flow control rx/tx
<6>[    1.816776] xhci-mtk 1a0c0000.usb: xHCI Host Controller
<6>[    1.828445] xhci-mtk 1a0c0000.usb: new USB bus registered, assigned bus number 1
<6>[    1.837539] xhci-mtk 1a0c0000.usb: hcc params 0x01403198 hci version 0x96 quirks 0x0000000000210010
<6>[    1.846635] xhci-mtk 1a0c0000.usb: irq 31, io mem 0x1a0c0000
<6>[    1.852782] hub 1-0:1.0: USB hub found
<6>[    1.856594] hub 1-0:1.0: 2 ports detected
<6>[    1.860875] xhci-mtk 1a0c0000.usb: xHCI Host Controller
<6>[    1.866132] xhci-mtk 1a0c0000.usb: new USB bus registered, assigned bus number 2
<6>[    1.873532] xhci-mtk 1a0c0000.usb: Host supports USB 3.0 SuperSpeed
<6>[    1.879850] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
<6>[    1.888282] hub 2-0:1.0: USB hub found
<6>[    1.892062] hub 2-0:1.0: 1 port detected
<5>[    1.897104] UBI: auto-attach mtd10
<5>[    1.900522] ubi0: attaching mtd10
<5>[    1.980713] ubi0: scanning is finished
<3>[    1.987378] ubi0 error: 0xffffffc010528aac: too large reserved_pebs 752, good PEBs 200
<3>[    1.995303] ubi0 error: 0xffffffc0105288e4: volume table check failed: record 5, error 9
<3>[    2.003383] Volume table record 5 dump:
<3>[    2.007219] 	reserved_pebs   752
<3>[    2.010437] 	alignment       1
<3>[    2.013481] 	data_pad        0
<3>[    2.016531] 	vol_type        1
<3>[    2.019575] 	upd_marker      0
<3>[    2.022618] 	name_len        11
<3>[    2.025753] 	name            rootfs_data
<3>[    2.029666] 	crc             0x971d97fc
<3>[    2.033527] ubi0 error: 0xffffffc01052cf9c: failed to attach mtd10, error -22
<3>[    2.040671] UBI error: cannot attach mtd10
<7>[    2.045618] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
<7>[    2.053096] Please append a correct "root=" boot option; here are the available partitions:
<7>[    2.061498] 1f00             512 mtdblock0 
<7>[    2.061500]  (driver?)
<7>[    2.068031] 1f04             256 mtdblock1 
<7>[    2.068033]  (driver?)
<7>[    2.074562] 1f08             512 mtdblock2 
<7>[    2.074564]  (driver?)
<7>[    2.081087] 1f0c             512 mtdblock3 
<7>[    2.081089]  (driver?)
<7>[    2.087617] 1f10            1024 mtdblock4 
<7>[    2.087619]  (driver?)
<7>[    2.094141] 1f14             128 mtdblock5 
<7>[    2.094143]  (driver?)
<7>[    2.100670] 1f18             128 mtdblock6 
<7>[    2.100672]  (driver?)
<7>[    2.107199] 1f1c             128 mtdblock7 
<7>[    2.107201]  (driver?)
<7>[    2.113724] 1f20           30720 mtdblock8 
<7>[    2.113726]  (driver?)
<7>[    2.120256] 1f24           30720 mtdblock9 
<7>[    2.120257]  (driver?)
<7>[    2.126792] 1f28           25600 mtdblock10 
<7>[    2.126793]  (driver?)
<7>[    2.133403] 1f2c           20480 mtdblock11 
<7>[    2.133405]  (driver?)
<0>[    2.140024] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
<2>[    2.148280] SMP: stopping secondary CPUs
<0>[    2.152195] Kernel Offset: disabled
<0>[    2.155676] CPU features: 0x00000002,04002004
<0>[    2.160023] Memory Limit: none
2

To me it looks like there is something wrong with the "normal" firmware's filesystem, actually the overlay/ part "rootfs_data". Easiest might be to clear the pstore files from initramfs, and use the initramfs instance to reflash a normal sysupgrade firmware.

Alternatively, you might try UBI removing the rootfs_data volume and trying to get it recreated at the next boot.

3

im having this problem my self but when i run cat /sys/fs/pstore/* i get cat: can't open '/sys/fs/pstore/*': No such file or directory

4

Look into ubi debug/info commands and try to figure out if there is something wrong with the file systems.

5

i ran log read and found these
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.745741] nand: found bad block 0xf
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.749534] nand: found bad block 0x10
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.753533] nand: found bad block 0x12
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.757413] nand: found bad block 0x13
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.761283] nand: found bad block 0x14
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.765170] nand: found bad block 0x15
Fri Oct 14 22:44:42 2022 kern.info kernel: [ 1.898800] [BBT] 74 available blocks in BMT pool
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.908003] [BBT] BMT.v2 is written into PBA:0x3ff
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.916651] 12 fixed-partitions partitions found on MTD device 1100d000.snfi
Fri Oct 14 22:44:42 2022 kern.err kernel: [ 1.923732] OF: Bad cell count for /snfi@1100d000/partitions
Fri Oct 14 22:44:42 2022 kern.err kernel: [ 1.929418] OF: Bad cell count for /snfi@1100d000/partitions
Fri Oct 14 22:44:42 2022 kern.err kernel: [ 1.935568] OF: Bad cell count for /snfi@1100d000/partitions
Fri Oct 14 22:44:42 2022 kern.err kernel: [ 1.941242] OF: Bad cell count for /snfi@1100d000/partitions
Fri Oct 14 22:44:42 2022 kern.err kernel: [ 1.947115] OF: Bad cell count for /snfi@1100d000/partitions
Fri Oct 14 22:44:42 2022 kern.err kernel: [ 1.952781] OF: Bad cell count for /snfi@1100d000/partitions
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.958605] Creating 12 MTD partitions on "1100d000.snfi":
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.964087] 0x000000000000-0x000000080000 : "Preloader"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.970217] 0x000000080000-0x0000000c0000 : "ATF"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.975618] 0x0000000c0000-0x000000140000 : "u-boot"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.981454] 0x000000140000-0x0000001c0000 : "u-boot-env"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.987684] 0x0000001c0000-0x0000002c0000 : "factory"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.994129] 0x000000300000-0x000000320000 : "devinfo"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 1.999729] 0x000000320000-0x000000340000 : "senv"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 2.005058] 0x000000360000-0x000000380000 : "bootseq"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 2.010628] 0x000000500000-0x000002300000 : "firmware1"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 2.046269] 0x000002300000-0x000004100000 : "firmware2"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 2.081874] 0x000004100000-0x000005a00000 : "data"
Fri Oct 14 22:44:42 2022 kern.notice kernel: [ 2.112052] 0x000005a00000-0x000006e00000 : "mfg"
but my problem is i cant seem to get out of recovary mode no matter what firmware i try just keeps putting make into recovary
logread