system/routerboard/upgrade fails

RouterOS General
1

I’ve got a RB433 at firmware version 2.23. See below:

/system routerboard> print
       routerboard: yes
             model: "433"
     serial-number: "1A7601E12429"
  current-firmware: "2.23"
  upgrade-firmware: "2.26"

I type upgrade and answer ‘y’ and now I have this:

 /system routerboard> print
       routerboard: yes
             model: "433"
     serial-number: "1A7601E12429"
  current-firmware: "2.26"
  upgrade-firmware: "2.26"

After a reboot it ignores the upgrade and is back to 2.23.

 /system routerboard> print
       routerboard: yes
             model: "433"
     serial-number: "1A7601E12429"
  current-firmware: "2.23"
  upgrade-firmware: "2.26"

Is this a hardware problem? If not, any ideas on how to get the upgrade to “take”. The
router is 200 miles from our office and not easily accessible, so I would like to avoid having to replace it.

Has anyone encountered this problem? Any suggestions?

2

Hello Folks!

I did never end up in situations where I needed to use Netinstall, that is last resort in many cases others say.
But I have headed all kinds of other interesting problems. It is allways badwill for customers.

Here are my checklist when patching MT devices, works for RB411, RB333, RB600, RB450G, RB750 and RB150:

1. Do you really need to patch ? check the RouterOS changelog. It is a good idea to keep all on same level.

If you decide to proceed with patching:

2. Backup the configuration, you never know!
/
/export file=plain-backup.txt
/system backup save name=binary-backup

Howto backup license file I do not know, someone ?

Bring it out of the MT device, drag and drop or ftp/scp som some safe place.
Backup on regular basis can be scheduled, look for various scripts doing that.

3. Check routerboard current firmware. IMPORTANT! Current = Upgrade if not Upgrade firmware first.

/system routerboard print
routerboard: yes
model: “411”
serial-number: “167B01C49320”
current-firmware: “2.27”
upgrade-firmware: “2.29”

Here we got a problem, need to upgrade FW!

4. Check routerboard settings: All settings must have values, unknown is not accepted during a reboot the device will stuck.

/system routerboard settings print
baud-rate: 115200
boot-delay: 5s
boot-device: nand-if-fail-then-ethernet
enter-setup-on: any-key
cpu-frequency: (unknown)
boot-protocol: bootp
enable-jumper-reset: yes
force-backup-booter: yes
silent-boot: no

Even more problems, cpu-frequency unknown, hope you got text backup to read now what it should be.

5. Fix the known two problems above. Set the unknown.
/system routerboard settings set cpu-frequency=300MHz
/system routerboard settings print
baud-rate: 115200
boot-delay: 5s
boot-device: nand-if-fail-then-ethernet
enter-setup-on: any-key
cpu-frequency: 300MHz
boot-protocol: bootp
enable-jumper-reset: yes
force-backup-booter: yes
silent-boot: no

6. Update firmware.
/system routerboard upgrade
Do you really want to upgrade firmware? [y/n]
y
firmware upgraded successfully, please reboot for changes to take effect!

/system reboot
Reboot, yes? [y/N]:
y
system will reboot shortly


Rebooting…
Stopping services…
Restarting system.

7. Check firmware settings again.
/system routerboard print
routerboard: yes
model: “411”
serial-number: “167B01C49320”
current-firmware: “2.29”
upgrade-firmware: “2.29”

Looging fine!

8. Check the routerboard settings to.
/system routerboard settings print
baud-rate: 115200
boot-delay: 5s
boot-device: nand-if-fail-then-ethernet
enter-setup-on: any-key
cpu-frequency: 300MHz
boot-protocol: bootp
enable-jumper-reset: yes
force-backup-booter: no
silent-boot: no

All is now OK again, you should have a go now for patching routeros.

9. If you are still not up to lates firmware you can do the following, if you are goto point 10.
This is rated as dangerous, you will in several cases need physical access to the board if it fails.
In some cases it does not boot up correctly and locks itself in some sleeping state.

Try remove force backup boot, this one is dangerous, device can become unavailable over the network if something is wrong.
/system routerboard settings set force-backup-booter=no
/system routerboard settings print
baud-rate: 115200
boot-delay: 5s
boot-device: nand-if-fail-then-ethernet
enter-setup-on: any-key
cpu-frequency: 300MHz
boot-protocol: bootp
enable-jumper-reset: yes
force-backup-booter: no
silent-boot: no

/system routerboard upgrade
Do you really want to upgrade firmware? [y/n]
y
firmware upgraded successfully, please reboot for changes to take effect!

/system reboot
Reboot, yes? [y/N]:
y
system will reboot shortly


Rebooting…
Stopping services…
Restarting system.

Check the firmware again!

If device dissapairs from network you will now need to use the serial port and reset at boot button to login and see what is wrong.

10. Upload new routeros.

  1. Drag and drop.
  2. The Dude right click and pick upgrade
  3. scp/ftp it over to MT device

11. Perform the upgrade.
/system reboot
.
. Can take up to ten minutes.
.

12. Then login and check firmware level, is there a new one you need to upgrade FW.
/system routerboard print
.
.
/system routerboard settings print
.
.

13. If you need Update firmware.
/system routerboard upgrade

/system reboot
.
. Can take up to 5 minutes.
.

14. Check firmware level and settings again.
/system routerboard print

/system routerboard settings print

Good luck!