MX60W Stuck in initramfs mode

Hey all,

Recently flashed a MX60W with OpenWrt and am trying to flash the sysupgrade file but every time I do it still comes up in recovery mode. I have no clue why.
File in flashing in question is "openwrt-23.05.2-apm821xx-nand-meraki_mx60-squashfs-sysupgrade".

Any ideas? I did some digging on the forum and none of the solutions I have come across seem to be working. I tried via the 192.168.1.1 GUI as well as SCP the file across and running the command using SSH. Still no dice.

Thanks

Edit (Pastebin of Serial): https://pastebin.com/c7xEiuJf

Not sure that it will solve anything, but try installing the 22.03.6 sysupgrade image (instead of 23.05.2 that you've been using per your post). If that works, you should then be able to upgrade to 23.05.2 using the standard sysupgrade method.

Ok Ill give that a crack.

If it helps this is what happens when I load the sysupgrade through LuCI

- watchdog -
Watchdog does not have CARDRESET support
Sat Sep  3 03:04:23 UTC 2022 upgrade: Sending TERM to remaining processes ...
Sat Sep  3 03:04:27 UTC 2022 upgrade: Sending KILL to remaining processes ...
[  554.732049] stage2 (3874): drop_caches: 3
Sat Sep  3 03:04:33 UTC 2022 upgrade: Switching to ramdisk...
Sat Sep  3 03:04:35 UTC 2022 upgrade: Performing system upgrade...
[  557.164487] ubi0: attaching mtd3
[  559.314687] ubi0: scanning is finished
[  559.337422] ubi0: attached mtd3 (name "ubi", size 1021 MiB)
[  559.343032] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[  559.349896] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[  559.356569] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[  559.363332] ubi0: good PEBs: 8172, bad PEBs: 2, corrupted PEBs: 0
[  559.369405] ubi0: user volume: 5, internal volumes: 1, max. volumes count: 128
[  559.376597] ubi0: max/mean erase counter: 964/953, WL threshold: 4096, image sequence number: 1064289950
[  559.386046] ubi0: available PEBs: 0, total reserved PEBs: 8172, PEBs reserved for bad PEB handling: 158
[  559.395454] ubi0: background thread "ubi_bgt0d" started, PID 4489
UBI device number 0, total 8172 LEBs (1054384128 bytes, 1005.5 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
Volume ID 1, size 31 LEBs (3999744 bytes, 3.8 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "kernel", alignment 1
Volume ID 3, size 31 LEBs (3999744 bytes, 3.8 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 1014773760
Volume ID 4, size 7865 LEBs (1014773760 bytes, 967.7 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[  561.765550] reboot: Restarting system

No luck unfortunately. Same result with 22.03.6

Make sure the meraki_loadaddr uboot variable has been increased. The original value of 800000 will cause booting a modern (large) kernel from flash to crash.

What does an unsuccessful boot look like?

How does one change that variable? Also all logs I have I have posted in topics/replies above, I can get different ones if directed :slight_smile:
But so far it never fails to boot, just boots the wrong mode

Review instructions here.
https://openwrt.org/toh/meraki/mx60
use printenv, setenv, and saveenv uboot commands to change the environment.
The instructions are unnecessarily complicated, you only need the stuff related to owrt_510, i.e. newer versions of OpenWrt (not LEDE).

kernal volume not found
Volume recovery found at volume id 0

There is no volume in the UBI named "kernal"-- the non-recovery kernel volume installed by sysupgrade is called "kernel". Is that entered properly in the environment?

Ok retrying from the beginning of that guide. (my TFTP isnt connecting but Ill fix that seperately)

This is wht shows when I printenv

Problem resetting EMAC!
ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
*** ERROR: ping address not given
RESET is un-pushed

Set serverpath and run meraki_netboot to netboot

Hit any key to stop autoboot:  0
=> printenv
bootdelay=1
baudrate=115200
loads_echo=
preboot=echo;echo Set serverpath and run meraki_netboot to netboot;echo
nload=${netloadmethod} 200000 ${serverpath}u-boot-nand.bin
nupdate=nand erase 0 0x00200000 ;nand write 200000 0 0x00100000
nupd=run nload nupdate
kernel_addr=fc000000
fdt_addr=fc1e0000
ramdisk_addr=fc200000
pciconfighost=1
pcie_mode=RP:RP
pcie=enabled
netdev=eth0
netloadmethod=dhcp
ethact=ppc_4xx_eth0
ethaddr=00:01:73:01:23:41
boardtype=pcie
mtd_addr_r=0x4000000
kernel_size=0x400000
fdt_size=0x25000
meraki_bootargs=setenv bootargs root=/dev/ram console=ttyS0,${baudrate} ubi.mtd=ubi MERAKI_BOARD=buck mtdoops.mtddev=oops ${extra_bootargs}
meraki_bootfile=buck.bin
meraki_bootlinux=bootm ${meraki_loadaddr_kernel} ${meraki_loadaddr_ramdisk} ${meraki_loadaddr_fdt}
meraki_boot=run meraki_ubi meraki_bootargs ; run meraki_load1 meraki_checkpart meraki_bootlinux; run meraki_load2 meraki_checkpart2 meraki_bootlinux
meraki_checkpart=meraki checkpart ${meraki_loadaddr}
meraki_checkpart2=meraki checkpart ${meraki_loadaddr} skiphash
meraki_netboot=run meraki_load_net meraki_bootargs meraki_checkpart2 meraki_bootlinux
meraki_part_fdt_index=0
meraki_loadaddr_fdt=800400
meraki_loadaddr_kernel=810000
meraki_loadaddr_ramdisk=a00000
meraki_load1=ubi read ${meraki_loadaddr} part1
meraki_load2=ubi read ${meraki_loadaddr} part2
meraki_load_net=${netloadmethod} ${meraki_loadaddr} ${serverpath}${meraki_bootfile}
meraki_ubi=ubi part ubi
meraki_ubifile=buck-ubi.bin
meraki_ubi_loadfile=${netloadmethod} 200000 ${serverpath}${meraki_ubifile}
meraki_ubi_update_nand=nand erase 0x00240000 0x3fdc0000 ; nand write 200000 0x00240000 ${filesize}
meraki_ubi_update=run meraki_ubi_loadfile meraki_ubi_update_nand
meraki_update_part1=run meraki_ubi meraki_load_net meraki_write1
meraki_update_part2=run meraki_ubi meraki_load_net meraki_write2
meraki_write1=ubi write ${meraki_loadaddr} part1 ${filesize}
meraki_write2=ubi write ${meraki_loadaddr} part2 ${filesize}
mtdids=nand0=nand0
mtdparts=mtdparts=nand0:0x00200000@0(firmware),0x00040000@0x00200000(panic),0x3fdc0000@0x00240000(ubi)
serverpath=10.1.30.240:tftpboot/
ipaddr=192.168.1.1
serverip=192.168.1.101
gatewayip=192.168.1.1
netmask=255.255.255.0
factory_cmdline=setenv bootargs root=/dev/ram ramdisk_size=${factory_ramdisk_size} rw ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1 console=ttyS1,${baudrate}
factory_ramdisk_file=uRamdisk
factory_bootfile=uImage
factory_fdt_file=bluestone.dtb
factory_kernel_addr_r=0x400000
factory_fdt_addr_r=0x800000
factory_mtd_addr_r=0x4000000
factory_ramdisk_size=0x200000
factory_boot=tftp ${factory_kernel_addr_r} ${factory_bootfile};tftp ${factory_fdt_addr_r} ${factory_fdt_file};tftp ${factory_mtd_addr_r} ${factory_ramdisk_file};run factory_cmdline;bootm ${factory_kernel_addr_r} ${factory_mtd_addr_r} ${factory_fdt_addr_r}
lede_bootkernal=botm ${meraki_loadaddr_kernel} - ${meraki_loadaddr_fdt}
owrt_load1=ubi read ${meraki_loadaddr} kernel
owrt_load2=ubi read ${meraki_loadaddr} recovery
lede_bootkernel=bootm ${meraki_loadaddr_kernel} - ${meraki_loadaddr_fdt}
owrt_bootkernel=bootm ${meraki_loadaddr}
owrt_bootargs=setenv bootargs console=ttyS0,${baudrate} rootfstype=squashfs mtdoops.mtddev=oops
owrt_boot=run meraki_ubi owrt_bootargs; run owrt_load1 meraki_checkpart lede_bootkernel; run owrt_load2 owrt_bootkernel
owrt510_boot=run meraki_ubi owrt_bootargs; run owrt_load1 owrt_bootkernel; run owrt_load2 owrt_bootkernel
bootcmd=run owrt510_boot
meraki_loadaddr=1000000
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.08-00049-g0ee25dd Meraki MX60 (Jul 27 2012 - 14:59:20)

Environment size: 3621/131067 bytes
=>

Flashed per instructions and when I go to clean up the disk I get this error. Is this what you are referring too? @mk24

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 22.03.0, r19685-512e76967f
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# ubirmvol /dev/ubi0 -N part1
ubirmvol: error!: cannot find UBI volume "part1"
          error 2 (No such file or directory)
root@OpenWrt:/# [   36.510114] eth0: link is up, 1000 FDX
[   36.543335] br-lan: port 1(eth0.1) entered blocking state
[   36.548736] br-lan: port 1(eth0.1) entered disabled state
[   36.554441] device eth0.1 entered promiscuous mode
[   36.559249] device eth0 entered promiscuous mode
[   36.630794] br-lan: port 1(eth0.1) entered blocking state
[   36.636191] br-lan: port 1(eth0.1) entered forwarding state
[   37.529492] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
ls
bin      etc      lib      overlay  rom      sbin     tmp      var
dev      init     mnt      proc     root     sys      usr      www
root@OpenWrt:/# cd /dev
root@OpenWrt:/dev# ls
console      mtd2         ppp          ttyS1        ttyS5        ubi0_4
full         mtd2ro       ptmx         ttyS10       ttyS6        ubi_ctrl
hwrng        mtd3         pts          ttyS11       ttyS7        ubiblock0_3
i2c-0        mtd3ro       random       ttyS12       ttyS8        urandom
kmsg         mtdblock0    shm          ttyS13       ttyS9        watchdog
log          mtdblock1    stderr       ttyS14       ubi0         watchdog0
mtd0         mtdblock2    stdin        ttyS15       ubi0_0       zero
mtd0ro       mtdblock3    stdout       ttyS2        ubi0_1
mtd1         null         tty          ttyS3        ubi0_2
mtd1ro       port         ttyS0        ttyS4        ubi0_3
root@OpenWrt:/dev# cd /ubi0
/bin/ash: cd: can't cd to /ubi0: No such file or directory
root@OpenWrt:/dev# cd /ubi0

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