anyone is working or have a easy way to upgrade ext4 version of the LEDE/OpenWRT distrib ?
I have just finished some espressobin board with the 18.06, all works very well, but I may have lost some bugfixes from the new release 18.06.1.
Have I any other choices that building new installation from scratch ?
The upgrade is impossible with the ext4 tar in the luci/web.
Is there some command lines possible to get in the way of a soft and easy upgrade from 18.06 to 18.06.1 ?
At least on x86 it's possible to use the ext4 images with the sysupgrade command, and that preserves settings. There's no technical difference between an 'upgrade' image and a 'factory' image unlike on many embedded systems. It seems for your target that is the same - there's just one image.
I'd say: back up your settings (sysupgrade or the web UI allow you to do that, store them on your local system, then try sysupgrade /path/to/default.img. That looks like it should work.
#!/bin/ash
echo >&2 User-installed packages are the following:
sed -ne '/^Package:[[:blank:]]*/ {
s///
h
}
/user installed/ {
g
p
}' /usr/lib/opkg/status
18.06.1 applied easily to my espressobin board and with only some easy scripting to do a full and secure upgrade !
Just needed the console access to get the full process endup, and have to set the parameters of the files to backup (/root and /etc/openvpn)
The actual sysupgrade do a full replacement of the root partition.
With this method the only missing tweak is how to resize2fs the partition after upgrade ?
May be having some more choice like, replace the content only with a rsync may have help.
For now I have to do the resize2fs offline, it is not possible from the device itself when the rootfs is already mounted.
The WiFi dying shouldn't happen (as in: I'd your settings were preserved it should come back up). So I assume the upgrade process didn't keep any of your settings?
I get an error without -F.
the common one of the check of the img saying it is not upgradable.
So I use the forced way.
I also lost the wifi because of the missing kmod after the upgrade...
I do not seing a way to get the upgrade of package in the first boot, in an automatic way.
The bad thing with the espresso bin and updating the ext4 sd OpenWRT is it format the all sd card.
If you have resized the rootfs partition or added a third partition to get an overlay, you will lost everything...
may be it is specific of the upgrade script of the espressobin board and might be fixed or enhanced.
This is because You probably unpacked the image before serving it to sysupgrade. There is small json data appended at the end of the *.img.gz file which is parsed by sysupgrade, and will be lost if You unpack the image.
This is how all OpenWrt images work, they have preconfigured amount of packages and the official image always has the same set of them. You can prepare image beforehand with Image Builder.
next try from 19-07-DEVEL to 19-07-DEVEL looks fine, and the third partition was not erased !
GREAT
here the log of the console from a sysupgrade with the WEBUI;
root@OpenWrt:/# killall: telnetd: no process killed
killall: dropbear: no process killed
Sending TERM to remaining processes ... rpcd dnsmasq netifd odhcpd ntpd sh ubus ubusd logd
Sending KILL to remaining processes ...
Switching to ramdisk...
[ 90.241609] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Performing system upgrade...
Reading partition table from bootdisk...
0+1 records in
0+1 records out
zcat: write error: Broken pipe
zcat: write: Broken pipe
Reading partition table from image...
2048+0 records in
2048+0 records out
zcat: write: Broken pipe
Writing image to /dev/mmcblk0p1...
zcat: write error: Broken pipe
zcat: write: Broken pipe
33280+0 records in
16+1 records out
Writing image to /dev/mmcblk0p2...
524544+0 records in
256+1 records out
Writing new UUID to /dev/mmcblk0...
4+0 records in
4+0 records out
zcat: write error: Broken pipe
zcat: write: Broken pipe
[ 121.894063] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
Upgrade completed
Rebooting system...
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[ 123.267113] reboot: Restarting system