Hey all,
I have an LDF-5nd "(ath79/mikrotik) mikrotik (routerboard-ldf-5nd)" that has faithfully been in service for years, and has been up for 182 days. However, it has been unable to upgrade past 3.25.2.0.I've tried the intermediate releases as they came out, as well as the current 3.25.8.0. It just says 'error' and doesn't update. It downloads the firmware listing, but just errors out when you click 'fetch and update' saying "ERROR: Unknown error". All other nodes are upgrading perfectly via this method. I also tried the manual download to computer and upload to the node, and it just silently fails, no error message. The node is sitting a almost no load, and has free ram and flash. I have pulled the support data, but don't know what to do with it. Should I just upload it here, or email it to someone.
The node name is KV3T-5G-LDF5.
Thanks in advance for the help.
I have an LDF-5nd "(ath79/mikrotik) mikrotik (routerboard-ldf-5nd)" that has faithfully been in service for years, and has been up for 182 days. However, it has been unable to upgrade past 3.25.2.0.I've tried the intermediate releases as they came out, as well as the current 3.25.8.0. It just says 'error' and doesn't update. It downloads the firmware listing, but just errors out when you click 'fetch and update' saying "ERROR: Unknown error". All other nodes are upgrading perfectly via this method. I also tried the manual download to computer and upload to the node, and it just silently fails, no error message. The node is sitting a almost no load, and has free ram and flash. I have pulled the support data, but don't know what to do with it. Should I just upload it here, or email it to someone.
The node name is KV3T-5G-LDF5.
Thanks in advance for the help.
Another way is to SCP the sysupgrade.bin file to the /tmp folder on your ldf.
Then ssh into the node and enter
sysupgrade /tmp/
From there you should see success or an error message.
root@NC8Q-R2H7:~# sysupgrade --help
Usage: /sbin/sysupgrade [<upgrade-option>...] <image file or URL>
/sbin/sysupgrade [-q] [-i] [-c] [-u] [-o] [-k] <backup-command> <file>
upgrade-option:
-f <config> restore configuration from .tar.gz (file or url)
-i interactive mode
-c attempt to preserve all changed files in /etc/
-o attempt to preserve all changed files in /, except those
from packages but including changed confs.
-u skip from backup files that are equal to those in /rom
-n do not save configuration over reflash
-p do not attempt to restore the partition table after flash.
-k include in backup a list of current installed packages at
/etc/backup/installed_packages.txt
-T | --test
Verify image and config .tar.gz but do not actually flash.
-F | --force
Flash image even if image checks fail, this is dangerous!
--ignore-minor-compat-version
Flash image even if the minor compat version is incompatible.
-q less verbose
-v more verbose
-h | --help display this help
backup-command:
-b | --create-backup <file>
create .tar.gz of files specified in sysupgrade.conf
then exit. Does not flash an image. If file is '-',
i.e. stdout, verbosity is set to 0 (i.e. quiet).
-r | --restore-backup <file>
restore a .tar.gz created with sysupgrade -b
then exit. Does not flash an image. If file is '-',
the archive is read from stdin.
-l | --list-backup
list the files that would be backed up when calling
sysupgrade -b. Does not create a backup file.
root@NC8Q-R2H7:~#
73, Chuck
... performing upgrade, shutting down all connections...
[broken pipe]
For my own education, If I did run into an error, where would I go to see the error message?
Thanks again!
Using the sysupgrade command in OpenWRT is now contra-indicated.
Use the sideload method.
Simply browse to the folder containing the sysupgrade firmware and enter:
scp -P2222 aredn-20250902-251de847-ath79-mikrotik-mikrotik_routerboard-lhg-5hpnd-xl-squashfs-sysupgrade.bin root@nc8q-mvhs-kettering.local.mesh:/tmp/local_firmware
Then browse to the remote node and click: Fetch and Update.
:-|
3s, Chuck
It's the only one of my nodes that has that issue.