[RESOLVED] Need help with sysupgrade failed by crontab on Linksys ea6350v3

hnyman · April 18, 2019, 12:02pm

Will not work for ea6350v3.

Using plain "mtd" is a historical practice that worked with the old simple small NOR flash devices.
With the current devices with NAND and also dual-boot (for some/most new Linksys devices), plain mtd is simply wrong.

For your specific device, the normal "sysupgrade" needs these device-specific steps in addition to the generic sysupgrade functions.

github.com

openwrt/openwrt/blob/master/target/linux/ipq40xx/base-files/lib/upgrade/linksys.sh#L30


      
          	#  if test $auto_recovery = no;
          	#      then bootipq;
          	#  elif test $boot_part = 1;
          	#      then run bootpart1;
          	#      else run bootpart2;
          	#  fi
          
          	case "$cur_boot_part" in
          	1)
          		fw_setenv -s - <<-EOF
          			boot_part 2
          			auto_recovery yes
          		EOF
          		printf "alt_kernel"
          		return
          		;;
          	2)
          		fw_setenv -s - <<-EOF
          			boot_part 1
          			auto_recovery yes
          		EOF

Note that usually/often kernel and the rootfs are written to different partitions, so the old style of monolithic mtd write is simply wrong.

Ps.
you might also read the device-specific thread about your device in order to find relevant pointers to the sysupgrade process, if you want to avoid the normal (and working) sysupgrade command.

Pps.
Unless you are lucky, an automatic timed sysupgrade done frequently sounds risky, especially if you continue to use the untested development snapshots from buildbot. Sooner or later you may brick the device.