sysupgrade.tgz => pretty sure the file is there! Not having any luck mounting this partition - but that's me, hunting to figure it out. That aside, I did see,
root@OpenWrt:/tmp# firstboot switch2jffs
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/mtdblock10 is not mounted
/dev/mtdblock10 will be erased on next mount
So somehow it is set to erase on reboot? We want it saved, right?
LOL - me neither. Blind leading the blind ... . Trying something - failsafe, see what mount_root says there! Rather odd result, after clean sysupgrade, failsafe ...
mount_root: no usable overlay filesystem found, using tmpfs overlay
Really seems like rootfs_data is broken somehow. But I may be wrong!
But, in spite of what the link says (about out of date), I did see (in failsafe),
The JFFS2 mounting code expects a special marker sequence 0xdeadc0de at the beginning of the rootfs_data partition, if this byte sequence is found; the entire rootfs_data partition is erased and reformatted as JFFS2.
So it's saving the file, to the correct place, but telling it to erase!
It's aligned (to 0x0), like it should be! And ... sysupgrade doesn't trash my info, it is maintained! Also, in the log now,
[ 7.213561] jffs2_scan_eraseblock(): End of filesystem marker found at 0x2000
[ 7.228071] jffs2_build_filesystem(): unlocking the mtd device...
[ 7.228149] done.
[ 7.244316] jffs2_build_filesystem(): erasing all blocks after the end marker...
[ 47.686327] done.
[ 47.705140] jffs2: notice: (449) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 47.737432] mount_root: overlay filesystem has not been fully initialized yet
[ 47.757073] mount_root: switching to jffs2 overlay
[ 47.796909] overlayfs: upper fs does not support tmpfile.
As it should be! So all good - sigh. Time for a ... LOL.
When I push this, was there a name change needed also?
Thanks!
And PS, I'm not so sure this isn't a sysupgrade bug. Thinking about it ... it says to me that the padding used to determine the start of rootfs_data is not consistent between writing (storing backup data), and reading .. agreed?
This is because it asked if you want to erase jffs2 and you said yes lol
I did some digging on this...
switch2jffs doesn't exist anymore, not as a parameter or a hook or script or anything...
the mount_root program handles all those features now (through libfstools)
Here is the firstboot script from 10 years ago
compared to today
Now it literally just calls jffs2reset which takes no parameters, however has two actions
if /overlay is mounted, erases files
if /overlay is not mounted, marks the partition for deletion on next mount
You are kidding, right? It was next on my list, never got to it before the blow up. But will get it restored and working, NP. Just need to crack the case open again - dang it!
Well, except for git that is . Figured I'll rebased my ravpower branch to hootoo now, thought that made sense. Now I have a bunch of commits. Arrgh, git kills me!
$ git reset --hard arrmo/hootoo-tm05
HEAD is now at 8f23744452 ramips: Add support for HooToo TM05
$ git checkout ravpower-wd03
Previous HEAD position was 8f23744452 ramips: Add support for HooToo TM05
Switched to branch 'ravpower-wd03'
Your branch is up to date with 'arrmo/ravpower-wd03'.
$ git rebase hootoo-tm05
First, rewinding head to replay your work on top of it...
Applying: ramips: Add support for HooToo TM05
Using index info to reconstruct a base tree...
M package/boot/uboot-envtools/files/ramips
M target/linux/ramips/image/Makefile
M target/linux/ramips/image/mt7620.mk
M target/linux/ramips/mt7620/base-files/etc/board.d/02_network
M target/linux/ramips/mt7620/config-4.14
M target/linux/ramips/mt7620/config-5.4
Falling back to patching base and 3-way merge...
Auto-merging target/linux/ramips/image/mt7620.mk
CONFLICT (content): Merge conflict in target/linux/ramips/image/mt7620.mk
Auto-merging package/boot/uboot-envtools/files/ramips
error: Failed to merge in the changes.
Patch failed at 0001 ramips: Add support for HooToo TM05
hint: Use 'git am --show-current-patch' to see the failed patch
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Here would happen the magic: you had to skip the old, superseded HooToo commit!
$ git rebase --skip
Applying: ramips: Add support for RAVPower WD03
$ git log
commit 45566406e0aebbbfec99bd492e12867f1ca45f89 (HEAD)
Author: Russell Morris <rmorris@rkmorris.us>
Date: Tue Jul 14 21:23:53 2020 -0500
ramips: Add support for RAVPower WD03
Signed-off-by: Russell Morris <rmorris@rkmorris.us>
commit 8f237444520a795dba410c830ec42d315f39811e (arrmo/hootoo-tm05, hootoo-tm05)
Author: Russell Morris <rmorris@rkmorris.us>
Date: Tue Dec 24 18:38:36 2019 -0600
ramips: Add support for HooToo TM05
The HooToo TM05 is a battery powered router, with an Ethernet and USB port.
Vendor U-Boot limited to 1.5 MB kernel size, so use lzma loader (loader-okli).
MAC assignment based on vendor firmware,
2.4 GHz, *:b4 (factory 0x04)
LAN/label, *:b4 (factory 0x28)
WAN, *:b5 (factory 0x2e)
Specifications:
SOC: MediaTek MT7620N
.
.
.