Unable to Upgrade to 7.7

RouterOS General
1

Hi,

I have 5 units of RBwAP2nD (RBwAP2nDr2) installed in my home. All 4 are successfully upgraded to firmware 7.7, except for 1 unit although it is updated to 6.49.7 without any problem.

The log of the problematic wAP says these:

broken package wireless-7.7-mipsbe.npk
broken package security-7.7-mipsbe.npk
broken package routing-7.7-mipsbe.npk
broken package ipv6-7.7-mipsbe.npk
broken package dhcp-7.7-mipsbe.npk
broken package advanced-tools-7.7-mipsbe.npk
installed system
not enough space for upgrade

I have uninstalled these packages:

  • hotspot
    ppp

to make room.

But it still fail to upgrade, so how can I upgrade it?

2

you update the device on idiotic way: multiple packet instead just only one (on non-SMPIS device)

read all first,

backup the device with both .backup and .rsc and save files outside the rb
save also the inside files you want keep

delete all deletable inside the files folder on routerboard

download
https://download.mikrotik.com/routeros/6.48.6/all_packages-mmips-6.48.6.zip
and
https://download.mikrotik.com/routeros/6.49.7/routeros-mipsbe-6.49.7.npk

extract from all_packages-mmips-6.48.6.zip only the system, wireless, security and dhcp, files (the others do not matter) and copy only that on wAP,

on system / package select the button downgrade

when the device is rebooted,
copy routeros-mipsbe-6.49.7.npk inside and reboot with system / reboot

go to system / package and enable all packages, also if you do not use it,

go to system / routerboard and upgrade the bios, if is not already upgraded

reboot the device

copy back the .backup file on routerboard,
on files select the backup and press restore

when rebooted goto system / package / check for updates
select channel stable,
press download & install

and probably you have done.

go again to system / routerboard and upgrade the bios, if is not already upgraded, and reboot.

3

Other approach: Netinstall.

Make sure to first have the complete config exported (and CHECK it is complete).
Reapply config after netinstall via terminal, block by block (there may be some errors due to wrong sequence but they are rather easy to correct)

4

This could prove better approach. A fraction of devices become unstable after “normal” upgrades from v6 to v7 (instability can show even after a few upgrades in v7 branch) and things get back to stable after netinstall. The reason for it is not entirely known, but it does seem that internal configuration database can sometimes contain configuration which is not shown in UI … and can make v7 unstable.