You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying sysupgrade on my ZBT WE1026, with SD-Card installed, and swap file active on it, silently does not succeed.
However, as I am using 'sysupgrade -v -n -f /tmp/some_pars.tar.gz /tmp/fw.bin'
the files from some_pars.tar.gz are applied to unmodified system, resulting in inconsistencies.
Doing swapoff before
sysupgrade fixed my problem.
sysupgrade should at least issue an error message, when it does not succeed.
As I suspect, that unsuccessful umount of my block device with swap-file open is the culprit.
The text was updated successfully, but these errors were encountered:
I‘ve read the description multiple times and I am still not sure what the problem is. Can you please describe exactly what the problem is and which error messages you received?
In other words: Active swapfile (or any open file ?) prevents sysupgrade to flash new image.
Howver, the files in "... -f /tmp/some_pars.tar.gz..." were applied to the flash mem.
Which caused inconsistent content of flash mem.
No erorr messages to be seen, but system rebooted.
So, in fact two issues: sysupgrade may not succceed, without any error messages, but reboots.
However, although no successful flash of image, new files from "/tmp/some_pars.tar.gz" written to flash.
_non_atomic operation here, causing inconsistent content of flash.
reinerotto:
Trying sysupgrade on my ZBT WE1026, with SD-Card installed, and swap file active on it, silently does not succeed.
However, as I am using 'sysupgrade -v -n -f /tmp/some_pars.tar.gz /tmp/fw.bin'
the files from some_pars.tar.gz are applied to unmodified system, resulting in inconsistencies.
Doing swapoff before
sysupgrade fixed my problem.
sysupgrade should at least issue an error message, when it does not succeed.
As I suspect, that unsuccessful umount of my block device with swap-file open is the culprit.
The text was updated successfully, but these errors were encountered: