Am 24.04.26 um 12:33 schrieb Michael Balzer via OvmsDev:
The auto upgrade process could then do a store downgrade and _set a config variable to reflect the abort cause_ (should do so as well on other issues encountered, so we can inform the user).
Another / additional idea on this part: simply store the entire command
output as a file on /sd if available, else on /store if enough space
is left or on /store2 after a successful store migration.
Basically use BufferedShell::ExecuteCommand() or a StringWriter to
capture the command output(s), then save_file() to save the result to
a defined path.
That way we could make the full step result details available to users without a USB shell (display them in the web UI upgrade guide), and keep a way for us to get captured logs for analysis in case of issues.
The largest command output is that of store migrate, on my test module
this step's output was 9599 bytes in size. So this will generally work
on /store even with much more files than my test module has (which
already covers multiple vehicles).
Of course only unless /store is corrupted. But a corrupted /store
will normally also result in all writes being lost anyway, so no config
variable change would be kept, the auto upgrade would appear stuck in
step 1.
Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926