hAP ac² upgrade from 6.49.2 -> 7.1.1 issues

RouterOS Beginner Basics
1

Today I finally felt brave enough to try 7.1.1 out of one of the devices in my possession and imemdiately ran into issue.
Seems like these devices cannot be upgraded (not supported by 7.x) or packages are in upgarde branch simply broken?

20:14:37 system,error broken package security-7.1.1-arm.npk 
20:14:37 system,error broken package dhcp-7.1.1-arm.npk 
20:14:37 system,error broken package wireless-7.1.1-arm.npk 
20:14:37 system,error broken package ipv6-7.1.1-arm.npk 
20:14:37 system,info installed system-7.1.1 
20:14:37 system,error not enough space for upgrade 
20:14:37 system,info router rebooted

Tried to upgarde multiple times, rebooted like there was no tomorrow, nothing…

2

Did you “unbundle” installation of ROS v6 on this device? ROS v7 comes as bundled installation but unbundled install can not be bundled again. Netinstall is your friend … or so they say.

3

Yes, I did unbundled install as these devices have very little flash available and I wanted to be conservative on space wasted.
Cannot do netinstall as all configuration would be lost then, and I would really hate to gather them for netinstall and reconfigure them manually.

Fair enough, will stay on 6.x then and consider upgarde “not supported” for my scenario.
It really sucks and documentation doe snot say anything about possible implications of unbundled installs by package.

4

I don’t know what do you have on it, I didn’t have any issue with the update. this is not net-install.
2022-01-17_15-40-14.png

5

Have you tried to delete all backups and logs before the upgrade? That’s what I had to do on my RB941-2nD otherwise the package wouldn’t fit.

6

Yes, of course I did, this is all I have on the flash:

I don’t store any backups or logs locally. :wink:

7

What you can do:


  1. create (binary) backup of your current config and fetch file off device
  2. netinstall to exactly same version
  3. install needed extra packages (ipv6)
  4. restore backup created in step #1
  5. upgrade to ROS v7

In theory you could netinstall device to v7 in step #2, ROS is supposed to convert config also when restoring from backup. In this case step #5 would not be necessary.

8

If you uninstall the ipv6 and/or wireless package first, it may free up enough space for the upgrade to be successful.

9

That would probably erase the corresponding config as well?


Yeah, probably, but I still don’t quite get it.
Why make upgrades so complicated.
Upgrading between 6.4x versions is really straightforward, why make 7.x that complicated?
To me it looks quite funny, first develop it for ages and then make upgrading so inconvenient that most of the users would not bother :smiley:

10

The problem with unbundling is that upgrade process tries to find upgrade candidates for all upgrade packages … if new version comes with all needed packages, then this is not a problem. If new version lacks some packages (in case of ROS v7 that’s most of packages), this becomes a problem. Unbundling was never officially supported nor encouraged. So I guess MT isn’t keen on supporting it either.

11

Would you please point me to the exact page in documentation, stating it?
I tried to search for it, but did not find any references, taht it is not supported or there would be implications.
Otherwise I would have not done that ~2 years ago…

Anyway, thank you evereybody for your input.
I weighted pros and cons and as v7 does not bring anything usefeul to the table, at least for me, I decided not bother…

12

Possibly (although I have sometimes had such config reappear after the packages are reinstalled), but for things like IPv6 or wireless you could easily do an /export from the command line for those sections only and paste it back in after upgrading if it doesn’t reappear on its own.

13

Read what I wrote and you quoted in most verbose way … I didn’t write MT discouraged or explicitly denied that unbundling could be done. AFAIK unbundling process was discovered by forum users, had nothing to do with any of official documentation.

14

Also since RouterOS v7 beta was first released back in September 2019 it has been known that the ability to install the individual packages (system, wireless, dhcp, etc) is gone and everything is in one monolithic package, only making upgrades easy from the v6 bundle package, unless the device has a lot of free space. If you set up your hap ac2 two years ago, that was after it was common knowledge that MikroTik was doing this with v7.

15

Actually this worked… :smiley:
And after that I simply restored binary backup (which I made prior), to get wireless and ipv6 config back.




I don’t remeber exactly when I actually did it (they are fairly old), what I do remember, I did it before first v7 public betas appeared and first day I got these before putting into use.


Anyway, apaprently I found a way, which would work and I also mentioned it here, so if anybody else runs into the same issue, would know it as well.
Thank you everybody for your contribution, would have not been able to do it that smoothly without you.

16

Thanks, this thread helped me to solve the same issue.