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
As of r24368-36b1dd75fd, noticed that sysupgrade -n leaves the old configuration in place after flash, which is not what -n is supposed to do.
OpenWrt version
r24368-36b1dd75fd
OpenWrt target/subtarget
qoriq/generic
Device
WatchGuard Firebox M300
Image kind
Self-built image
Steps to reproduce
Install a fresh build
touch /root/NUKEME
fetch e.g. the same build to /tmp/
sysupgrade -v -n /tmp/openwrt-qoriq-generic-watchguard_firebox-m300-squashfs-sysupgrade.img.gz
ls -l /root/
find NUKEME is still there.
Actual behaviour
sysupgrade -n does not erase/re-initialize the ext4 overlayfs on /dev/loop0 (which comes after the squashfs on /dev/mmcblk0p2.
Expected behaviour
Sysupgrade -n is supposed to clear previous settings and re-initialize the overlayfs.
Additional info
jffs2reset -y && reboot still seems to work (at least, mostly. I noticed that some files might hang around, e.g. /root/.ssh) for nuking the old overlayfs.
Also noticed that after installing the sdcard image, the overlayfs is ext4, but if I nuke the ext4, e.g. by "dd if=/dev/zero of=/dev/loop0" on the device and rebooting, the booting system notices no filesystem in /dev/loop0 where the overlayfs is expected, and it creates a f2fs filesystem instead of ext4, which seems weird.
Describe the bug
As of r24368-36b1dd75fd, noticed that sysupgrade -n leaves the old configuration in place after flash, which is not what -n is supposed to do.
OpenWrt version
r24368-36b1dd75fd
OpenWrt target/subtarget
qoriq/generic
Device
WatchGuard Firebox M300
Image kind
Self-built image
Steps to reproduce
Install a fresh build
touch /root/NUKEME
fetch e.g. the same build to /tmp/
sysupgrade -v -n /tmp/openwrt-qoriq-generic-watchguard_firebox-m300-squashfs-sysupgrade.img.gz
ls -l /root/
find NUKEME is still there.
Actual behaviour
sysupgrade -n does not erase/re-initialize the ext4 overlayfs on /dev/loop0 (which comes after the squashfs on /dev/mmcblk0p2.
Expected behaviour
Sysupgrade -n is supposed to clear previous settings and re-initialize the overlayfs.
Additional info
jffs2reset -y && reboot still seems to work (at least, mostly. I noticed that some files might hang around, e.g. /root/.ssh) for nuking the old overlayfs.
Diffconfig
Terms
The text was updated successfully, but these errors were encountered: