Stuck in initramfs mode after doing sysupgrade

I have been running on my Linksys E8450 the 23.05.0 firmware and it has proven to not be very stable and I would have to reboot it daily to make sure it would die during the day when people are using it most.

I looked if there was an upgrade and I found 23.05.2. I downloaded the sysupgrade.bin file, flashed it using the GUI dashboard of openwrt by loggin in, clicking on the "system" menu from above, then clicking on "backup / flash firmware", then the last option on the bottom of that page "flash image" with this file: openwrt-23.05.2-mediatek-mt7622-linksys_e8450-squashfs-sysupgrade.bin

One thing that stood out was that a message in red that said:

Image check failed:

Sat Dec 15 21:02:11 UTC 2023 upgrade: Device linksys,e8450-ubi not supported by this image Sat Dec 15 21:02:11 UTC 2023 upgrade: Supported devices: linksys,e8450 Image check failed.

I had the option below it in another red box to force the upgrade. I checked it and did the upgrade as I am very well aware of the model router that I own.

Now upon completion, after logging back in, I am getting a yellow message box on top of the openwrt dashboard that states:

"System running in recovery (initramfs) mode.

No changes to settings will be stored and are lost after rebooting. This mode should only be used to install a firmware upgrade"

Now whatever I change doesn't stuck upon reboot.

A few questions I have are:

  1. Did I do something wrong and if so, what did i do wrong?
  2. How do i fix this problem?
  3. Should have I flashed something else besides a sysupgrade.bin file?

Many many thanks in advance for any assistance!

Use the ubi version instead. The install process has converted the flash filesystem to ubi, so you must use that build in order to save files. I'm not sure why non-ubi is even still around.

I just flashed:

"openwrt-23.05.2-mediatek-mt7622-mediatek_mt7622-rfb1-ubi-squashfs-sysupgrade.bin"

And this too is giving me the same initramfs mode problem.

Any suggestions on a next step?

I saw some other posts that mentioned this issue and they were told to ssh into the router and type a few commands:
cat /sys/fs/pstore/*
rm /sys/fs/pstore/*
reboot

Here is the outcome:
OpenWrt 23.05.0, r23497-6637af95aa

root@OpenWrt:~# cat /sys/fs/pstore/*
Panic#1 Part1
<5>[ 0.921675] 0x000000320000-0x000000340000 : "senv"
<5>[ 0.927031] 0x000000360000-0x000000380000 : "bootseq"
<5>[ 0.932713] 0x000000500000-0x000002300000 : "firmware1"
<5>[ 0.969085] 0x000002300000-0x000004100000 : "firmware2"
<5>[ 1.005495] 0x000004100000-0x000005a00000 : "data"
<5>[ 1.036604] 0x000005a00000-0x000006e00000 : "mfg"
<6>[ 1.195152] mtk_soc_eth 1b100000.ethernet eth0: mediatek frame engine at 0xffffffc0094a0000, irq 141
<6>[ 1.205070] i2c_dev: i2c /dev entries driver
<3>[ 1.210646] mtk-wdt 10212000.watchdog: IRQ index 0 not found
<6>[ 1.216506] mtk-wdt 10212000.watchdog: Watchdog enabled (timeout=31 sec, nowayout=0)
<6>[ 1.226654] NET: Registered PF_INET6 protocol family
<6>[ 1.232690] Segment Routing with IPv6
<6>[ 1.236368] In-situ OAM (IOAM) with IPv6
<6>[ 1.240323] NET: Registered PF_PACKET protocol family
<6>[ 1.245431] 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.258571] 8021q: 802.1Q VLAN Support v1.8
<6>[ 1.263983] pstore: Using crash dump compression: deflate
<6>[ 1.279822] mtk-pcie 1a143000.pcie: host bridge /pcie@1a143000 ranges:
<7>[ 1.286413] mtk-pcie 1a143000.pcie: Parsing ranges property...
<6>[ 1.292267] mtk-pcie 1a143000.pcie: MEM 0x0020000000..0x0027ffffff -> 0x0020000000
<6>[ 1.427959] mtk-pcie 1a143000.pcie: PCI host bridge to bus 0000:00
<6>[ 1.434186] pci_bus 0000:00: root bus resource [bus 00-ff]
<6>[ 1.439682] pci_bus 0000:00: root bus resource [mem 0x20000000-0x27ffffff]
<7>[ 1.446581] pci_bus 0000:00: scanning bus
<6>[ 1.450661] pci 0000:00:00.0: [14c3:3258] type 01 class 0x060400
<6>[ 1.456717] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x1ffffffff 64bit pref]
<7>[ 1.466945] pci_bus 0000:00: fixups for bus
<7>[ 1.471150] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 0
<6>[ 1.477888] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
<7>[ 1.485922] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
<7>[ 1.492840] pci_bus 0000:01: scanning bus
<6>[ 1.497086] pci 0000:01:00.0: [14c3:7915] type 00 class 0x000280
<6>[ 1.503304] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
<6>[ 1.510644] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
<6>[ 1.517991] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
<6>[ 1.526009] pci 0000:01:00.0: supports D1 D2
<6>[ 1.530280] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
<7>[ 1.536940] pci 0000:01:00.0: PME# disabled
<6>[ 1.541442] 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.585007] pci_bus 0000:01: fixups for bus
<7>[ 1.589219] pci_bus 0000:01: bus scan returning with max=01
<6>[ 1.594831] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
<7>[ 1.601470] pci_bus 0000:00: bus scan returning with max=01
<6>[ 1.607066] pci 0000:00:00.0: BAR 0: no space for [mem size 0x200000000 64bit pref]
<6>[ 1.614722] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x200000000 64bit pref]
<6>[ 1.622732] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x201fffff]
<6>[ 1.629517] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x200fffff 64bit pref]
<6>[ 1.637349] pci 0000:01:00.0: BAR 2: assigned [mem 0x20100000-0x20103fff 64bit pref]
<6>[ 1.645178] pci 0000:01:00.0: BAR 4: assigned [mem 0x20104000-0x20104fff 64bit pref]
<6>[ 1.653003] pci 0000:00:00.0: PCI bridge to [bus 01]
<6>[ 1.657965] pci 0000:00:00.0: bridge window [mem 0x20000000-0x201fffff]
<7>[ 1.664897] pcieport 0000:00:00.0: assign IRQ: got 146
<6>[ 1.670043] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
<7>[ 1.676156] pcieport 0000:00:00.0: enabling bus mastering
<7>[ 1.681592] mtk-pcie 1a143000.pcie: msi#0 address_hi 0x0 address_lo 0x44d6d0c0
<6>[ 1.688992] pcieport 0000:00:00.0: PME: Signaling with IRQ 146
<7>[ 1.694928] pcieport 0000:00:00.0: saving config space at offset 0x0 (reading 0x325814c3)
<7>[ 1.703121] pcieport 0000:00:00.0: saving config space at offset 0x4 (reading 0x100006)
<7>[ 1.711122] pcieport 0000:00:00.0: saving config space at offset 0x8 (reading 0x6040000)
<7>[ 1.719210] pcieport 0000:00:00.0: saving config space at offset 0xc (reading 0x10000)
<7>[ 1.727125] pcieport 0000:00:00.0: saving config space at offset 0x10 (reading 0xc)
<7>[ 1.734778] pcieport 0000:00:00.0: saving config space at offset 0x14 (reading 0x0)
<7>[ 1.742435] pcieport 0000:00:00.0: saving config space at offset 0x18 (reading 0x40010100)
<7>[ 1.750691] pcieport 0000:00:00.0: saving config space at offset 0x1c (reading 0x4200000)
<7>[ 1.758867] pcieport 0000:00:00.0: saving config space at offset 0x20 (reading 0x20102000)
<7>[ 1.767137] pcieport 0000:00:00.0: saving config space at offset 0x24 (reading 0x0)
<7>[ 1.774792] pcieport 0000:00:00.0: saving config space at offset 0x28 (reading 0x0)
<7>[ 1.782446] pcieport 0000:00:00.0: saving config space at offset 0x2c (reading 0x0)
<7>[ 1.790095] pcieport 0000:00:00.0: saving config space at offset 0x30 (reading 0x0)
<7>[ 1.797749] pcieport 0000:00:00.0: saving config space at offset 0x34 (reading 0x50)
<7>[ 1.805489] pcieport 0000:00:00.0: saving config space at offset 0x38 (reading 0x0)
<7>[ 1.813142] pcieport 0000:00:00.0: saving config space at offset 0x3c (reading 0x20192)
<6>[ 1.821711] mtk-pcie 1a145000.pcie: host bridge /pcie@1a145000 ranges:
<7>[ 1.828264] mtk-pcie 1a145000.pcie: Parsing ranges property...
<6>[ 1.834106] mtk-pcie 1a145000.pcie: MEM 0x0028000000..0x002fffffff -> 0x0028000000
<6>[ 2.061610] mtk-pcie 1a145000.pcie: Port1 link down
<6>[ 2.066695] mtk-pcie 1a145000.pcie: PCI host bridge to bus 0001:00
<6>[ 2.072898] pci_bus 0001:00: root bus resource [bus 00-ff]
<6>[ 2.078388] pci_bus 0001:00: root bus resource [mem 0x28000000-0x2fffffff]
<7>[ 2.085271] pci_bus 0001:00: scanning bus
<7>[ 2.091068] pci_bus 0001:00: fixups for bus
<7>[ 2.095261] pci_bus 0001:00: bus scan returning with max=00
<6>[ 2.101441] mtk_hsdma 1b007000.dma-controller: MediaTek HSDMA driver registered
<6>[ 2.152373] mt7530-mdio mdio-bus:00: configuring for fixed/2500base-x link mode
<6>[ 2.162155] mt7530-mdio mdio-bus:00: Link is Up - 2.5Gbps/Full - flow control rx/tx
<6>[ 2.170863] mt7530-mdio mdio-bus:00 lan1 (uninitialized): PHY [mt7530-0:00] driver [MediaTek MT7531 PHY] (irq=147)
<6>[ 2.191567] mt7530-mdio mdio-bus:00 lan2 (uninitialized): PHY [mt7530-0:01] driver [MediaTek MT7531 PHY] (irq=148)
<6>[ 2.211960] mt7530-mdio mdio-bus:00 lan3 (uninitialized): PHY [mt7530-0:02] driver [MediaTek MT7531 PHY] (irq=149)
<6>[ 2.232353] mt7530-mdio mdio-bus:00 lan4 (uninitialized): PHY [mt7530-0:03] driver [MediaTek MT7531 PHY] (irq=150)
<6>[ 2.252897] mt7530-mdio mdio-bus:00 wan (uninitialized): PHY [mt7530-0:04] driver [MediaTek MT7531 PHY] (irq=151)
<6>[ 2.264169] DSA: tree 0 setup
<5>[ 2.267962] UBI: auto-attach mtd10
<5>[ 2.271380] ubi0: default fastmap pool size: 10
<5>[ 2.275927] ubi0: default fastmap WL pool size: 5
<5>[ 2.280624] ubi0: attaching mtd10
<5>[ 2.342500] ubi0: scanning is finished
<3>[ 2.346273] ubi0 error: 0xffffffc00855f0bc: the layout volume was not found
<3>[ 2.353285] ubi0 error: 0xffffffc008562d38: failed to attach mtd10, error -22
<3>[ 2.360458] UBI error: cannot attach mtd10
<7>[ 2.365847] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
<7>[ 2.373360] Please append a correct "root=" boot option; here are the available partitions:
<7>[ 2.381734] 1f00 512 mtdblock0
<7>[ 2.381740] (driver?)
<7>[ 2.388262] 1f01 256 mtdblock1
<7>[ 2.388266] (driver?)
<7>[ 2.394798] 1f02 512 mtdblock2
<7>[ 2.394802] (driver?)
<7>[ 2.401323] 1f03 512 mtdblock3
<7>[ 2.401327] (driver?)
<7>[ 2.407858] 1f04 1024 mtdblock4
<7>[ 2.407862] (driver?)
<7>[ 2.414389] 1f05 128 mtdblock5
<7>[ 2.414393] (driver?)
<7>[ 2.420915] 1f06 128 mtdblock6
<7>[ 2.420918] (driver?)
<7>[ 2.427446] 1f07 128 mtdblock7
<7>[ 2.427450] (driver?)
<7>[ 2.433977] 1f08 30720 mtdblock8
<7>[ 2.433981] (driver?)
<7>[ 2.440502] 1f09 30720 mtdblock9
<7>[ 2.440505] (driver?)
<7>[ 2.447032] 1f0a 25600 mtdblock10
<7>[ 2.447037] (driver?)
<7>[ 2.453649] 1f0b 20480 mtdblock11
<7>[ 2.453653] (driver?)
<0>[ 2.460262] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
<2>[ 2.468515] SMP: stopping secondary CPUs
<0>[ 2.472430] Kernel Offset: disabled
<0>[ 2.475907] CPU features: 0x0,00001000,00000802
<0>[ 2.480430] Memory Limit: none
root@OpenWrt:~# rm /sys/fs/pstore/*
root@OpenWrt:~# reboot
root@OpenWrt:~# Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.

After doing this, I am still in initramfs mode.

Easiest (and the most sure) way to get rid of the pstore files in RAM is to physically power-off the router.

1 Like

Thank you, that worked great!

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