Hi,

My HAP ac2 running on 7.13 is about to run out of space. Is Mikrotik aware of that? Maybe it would be a good idea to exclude ppp and routing from the main package bundle?

This was discovered long ago (as soon as 7.13 came out). I certainly hope MT reads the comments in release topic they created themselves ... and I hope will do something about it.

Beware that when space runs out, you won't be able to change configuration. And device might become unstable (rebooting for no actual reason). Or anything else.

It seems that the hAP ac2 is the most affected by this problem.
Maybe part of the issue is that the flash isn't 16MB to start with, it is only 15.3MB on that device.
(no idea why, it could be due to limitations of the processor, memory-mapped IO, boot code, whatever)

OF COURSE MikroTik know about this! But they are in a state of denial.
I have written my concerns about 16MB flash devices many times, but the only reply you can get is
like "we make sure it fits, we test every release with default config and it always is OK" etc.

The 7.13 version makes it worse because now the "old" wireless config has been made a separate package while
the "new" code is still a mandatory part of the main package. So now you have 2 config menus, one for
the old and one for the new, again taking up more space. Which already was nearly 0 in 7.12 and below.

Still, for those that have a hAP ac2 and do not want to migrate to the new WiFi, I would recommend staying
at 7.12.1 and not upgrade until that becomes absolutely necessary.

Is a downgrade possible from 7.13 to 7.12.1?

Maybe part of the issue is that the flash isn't 16MB to start with, it is only 15.3MB on that device.

I think it's the matter of Mebi vs Mega. 16*10⁶ Bytes=15.258789 MiB.

The thing is that storage producers use MB and MiB interchangable and don't tell which is it. And MT is to blame here as it reports capacity using wrong unit as well.

Is a downgrade possible from 7.13 to 7.12.1?

It is possible. But you have to take extra care of uploading appropriate packages. Also beware that some settings you may have done in 7.13 won't be backported to 7.12 (because config converter in 7.12 isn't aware of certain new features, such as renaming /interface/wifiwave2 to /interface/wifi).

Beware that when space runs out, you won't be able to change configuration. And device might become unstable (rebooting for no actual reason). Or anything else.

The last time it ran out of space it didn't come up after the reboot. So one needs to be careful not to run out of space because it effectively bricks the device.

Maybe part of the issue is that the flash isn't 16MB to start with, it is only 15.3MB on that device.

I think it's the matter of Mebi vs Mega. 16*10⁶ Bytes=15.258789 MiB.

It isn't. One does not even have to know what the exact unit is, just by looking at System->Resources in the field "Total HDD Size" it will show 16MB in almost all models but it shows 15.3MB in the hAP ac2.
So it does not matter if it is MiB or MB in reality, it is just less.

About downgrade: it depends on what kind of configuration you have.
When you are just using it as a basic home router with NAT and WiFi and no special config I would recommend to just do a netinstall without keeping configuration, and start completely fresh from defaults.
You can do a "/export show-sensitive file=filename" and download the filename.rsc file to your computer before doing that, and have the filename.rsc alongside in an editor while doing the new configuration (so you do not forget things).
If desired, you can also copy/paste some section of the export to your new setup, like a VPN setup or similar.

When the config is complicated, you could do a netinstall with "keep config" or you could download the 7.12.1 npk file and upload it to the router, and also in the packages section do a "remove" on the wireless or wlan package of 7.13, then click "downgrade".
But the abovementioned netinstall and fresh start method will give you the most free space.

Maybe part of the issue is that the flash isn't 16MB to start with, it is only 15.3MB on that device.

I think it's the matter of Mebi vs Mega. 16*10⁶ Bytes=15.258789 MiB.

The thing is that storage producers use MB and MiB interchangable and don't tell which is it. And MT is to blame here as it reports capacity using wrong unit as well.

Would that not constitute as false advertising?

eg. "Routerboard that has 16MB Flash storage" when in reality it's 15.2Mib.

D53G-5HacD2HnD is having the same issue - only 596 KiB reported free after upgrading to v7.13, total storage is 15.3MiB, on the MT's Product page on website its showing MB

And I have written several times my concerns about integrating the wifi module into the default package. why they opted for this I can't understand without insights into their architecture. extract the whole wifi part as extra package and all be good again.

Indeed!
Also I do not understand why they made everything one routeros package.
I can understand why they merged packages like security, dhcp, ppp and ipv6 from the v6 version in to the main package: there are just too many inter-dependencies between features all over the place and those specific packages.
But why "routing" (BGP/OSPF/etc), "hotspot", and "mpls" were put in the routeros package, I do not understand.
Probably 95% of the users is never going to use those, now that they focused so much on home routers.
These should have remained optional packages...

@t0mm13b https://www.gbmb.org/mb-to-mib Afaik any storage device is advertised in MB/GB/TB sizes, not in MiB/GiB/TiB.

That is wrong. Internal memory is in MB but "external" storage like flash is always in MiB.
When you buy a "16MB flash card" it will be 16000000000 bytes, not 17179869184.
That would make it 14.9MB instead of 16MB.
However, that is all that is going on here. As mentioned, the hAP ac2 reports less space than all the other 16MB models.

Someone marked this topic as SOLVED although it's NOT.

I think only the original poster (YOU) can mark it "solved".
Anyway, did you try a netinstall to 7.12.1 ?

I haven't tried netinstall option yet. I'm waiting for Mikrotik's response on how they're planning to address this problem. 7.14beta uses even more space than 7.13 so eventually, more and more users will be affected by this problem unless a sustainable solution is found.

Worst case scenario I will be forced to upgrade from ac2 to ax2. Maybe that's what business people from Mikrotik want.

I do not expect that they will provide you with a useful reply or solution.
As I wrote before, concern has been expressed about decisions and about the ac2 and the only response is denial.

Worst case scenario I will be forced to upgrade from ac2 to ax2. Maybe that's what business people from Mikrotik want.

Maybe MikroTik can start a sort of exchange program where they offer minimum 50% discount to entice people to upgrade from ac2 to ax2 if they swap their hAP ac2 for ax2

...wishful thinking !

...or offer to purchase ROS compatible flash memory to replace it on board

In case of the ac2 it could even have been an option to install a USB stick that can offload part of the storage requirement...

But why "routing" (BGP/OSPF/etc), "hotspot", and "mpls" were put in the routeros package, I do not understand.
Probably 95% of the users is never going to use those, now that they focused so much on home routers.
These should have remained optional packages...

That's the point. Many of MTs recent wifi AX products focus on SOHO.

Maybe basic routing stuff should remain like Filters, Nexthops, RouterID, Rules, Settings and Tables but other parts as part of extended routing optional package and also Dot1X and RADIUS can be optional.

Hi! I hope someone from MT is aware of this issue. I´d like to add, that my WAPac (ARM Version, RBwAPG-5HacD2HnD, r3) is also affected.
After upgrading to 7.14b4 516 KiB are left from 15.3MB.
Only routeros and wifi-qcom-ac are installed. Everything is working until now, but I don´t know for how long...

I had to remain on legacy wireless package to have container package because it not fit with wifi-qcom-ac and my config.

Maybe basic routing stuff should remain ...

None of routing stuff should remain in basic package, none are used by vast majority of SOHO users (who are primary users of infamous 16MB flash ARM wifi devices). And that includes dot1x, radius and any other (mostly) corporate stuff.

IMO running containers on 128MB RAM devices with wireless (hAP ac2, cAP ac, etc. nominally have 128MB RAM) is silly.

Such exercises look just like those photographs from 3rd world showing guys transporting mountains of goods on a moped. Yes, somehow some manage to fo it, but nobody in their right minds are requesting from moped producers to officially support that.

I'm running containers on Chateau LTE12 which has 256MB RAM size but just 16MB flash, have no problem with RAM while containers are running, constantly 2 are running as DNS service (Pi-hole and Unbound - recursive) and periodically starting some others, so far RAM is not issue but flash is.

Afaik for basic routing setup you don't need additional tools on linux so there is no extra space to gain by just removing options. Maybe better to separate VPNs into separate packages and then let users to decide which will install for their needs. Also some supporting drivers for devices that are not part of MT hardware can be also optional packages, like external LTE modems support as bundle package, etc...

I'm running containers on Chateau LTE12 which has 256MB RAM size but just 16MB flash, have no problem with RAM while containers are running, constantly 2 are running as DNS service (Pi-hole and Unbound - recursive) and periodically starting some others, so far RAM is not issue but flash is.

Afaik for basic routing setup you don't need additional tools on linux so there is no extra space to gain by just removing options. Maybe better to separate VPNs into separate packages and then let users to decide which will install for their needs. Also some supporting drivers for devices that are not part of MT hardware can be also optional packages, like external LTE modems support as bundle package, etc...

I do hav PIhole/unbound running off pi which is plugged directly into ethernet port.

what's your experience like with running containers on Chateau (owner of same device here... ) ?

what's your experience like with running containers on Chateau (owner of same device here... ) ?

Positive after some ROS version upgrades, at beginning was troubles due to some bugs related to containers.
I had to tweak configurations to have small RAM usage, on Pi-hole DNS cache is disabled since it's upstream is Unbound which owns cache and Unbound is tweaked for RAM and cores usage. Containers config has ram-high=80M and it's enough for me.
DNS performance mostly depends on network quality here (which over LTE isn't always best).

There is a solution without cutting features. I own hAP ac2 and out of curiosity I looked at drivers section of ARM RouterOS. There is for example prestera_dx_max.ko file taking 687 KB of space. Then quectel_mhi.ko of 148 KB. These drivers are not needed for hAP ac2. How about making a list of drivers (files?) not needed for each device. Then during install procedure, installer using this list, would not install unnecessary files onto "precious" 15.3 MB flash. I'm not sure how simple that would be as the npk file is compressed and it would need to be repacked in RAM before install. Also space savings would be less than 687+148 KB due to compression. But probably more than these two files are unnecessary for hAP ac2, so maybe it would do the job.
Another solution would be allowing to install optional packages onto (encrypted?) partition on USB drive. Moving wifi-qcom-ac there would save almost 3 MB.

The issue probably is that .npk packages are mostly a read-only compressed filesystem that is copied to the flash in its entirety and then are mounted at runtime (with the appropriate code to de-compress files on access).
So, it is not a simple matter of "during installation see which drivers are required and delete the remainder", as there is no support to delete files in the compressed filesystem.
If a .npk would be just like a .deb or .rpm (a compressed archive that is being unpacked during install) it would be easy.

Some drivers are shared by a lot of things, there is no separate driver for each chip or device. One big driver.

Firmware is per chipset.

It isn't

Whatever is the situation, something has to be done. Denying the problem no longer works.

Our team of experts is working on this issue at this very moment. As to "why", many products were designed years ago, but only are released now. When designing devices with 16MB SPI chips, at that moment there was no issue yet. Today we are designing devices with more storage, but they will reach customers after "some time" as you can imagine.

Don't tell us you were not aware, and were not warned, about possible space issues on 16MB flash devices!
It was discussed on the forum from the time those were released. Remember the original MikroTik products usually had 64MB or 128MB flash.

Our team of experts is working on this issue at this very moment.

Thanks for the update. I know it's not an easy problem to "just fix". But the 16MB problem has been on a slow simmer for "some time" .

It isn't

I do not understand. What else?