Meh. It would be nice if they ship the devices with the individual packages installed by default instead of the bundled packages. That way you can “uninstall” what you want and just reboot to free up space.
There are too many packages installed by default to be able to be in-place upgraded. Here’s what’s there now:
Download SMIPS extra Packages zip file. Extract these:
Drag and drop the files to Files
Reboot
Install extra packages if you need them. See descriptions from here:
https://wiki.mikrotik.com/wiki/Manual:System/Packages
And when we have a network of hundreds of HAP lite ??
Mikrotik should provide a trouble free solution to this situation …
Do your hundreds of devices have custom packages installed? Normally there shouldn’t be any custom packages and no problem upgrading.
My instructions were based on hap lite factory defaults. There is not enough RAM to upgrade by default methods all factory configured packages. If you have hundreds on hap lites deployed, automate my instructions or hire someone that can do it for you.
I stopped buying hap lites because the hardware doesn’t have enough ram. IMHO mikrotik shouldn’t have factory images with so many packages installed on these low end devices
Will need to do a NetInstall otherwise 
My question was, does anyone have issues using “check for updates” with a device with factory installed version?
Because in the examples I either see custom package sets, or 6.48 beta versions.
I had this problem on my hAP mini (MUM freebie) but I solved it by one time doing an upgrade using only the separate packages I require instead of the combined package, and from then it upgrades using the one-click method without problem.
There is no wildly unusual config on it: 3 SSIDs each connecting to a VLAN on the ethernet connected to my router. It serves as an AP in the bedroom.
No routing, no NAT, almost no firewall.
I should have tried doing a reboot and then immediately an upgrade, the buildup of RAM usage (and fragmentation) during extended usage could have been just the trigger that pushed it over the limit. Note that the upgrade procedure is VERY CLOSE to the limit of RAM. That also explains why omitting a couple of small packages I do not use solved it for now.
Hi, fortunately I dont have 100s of device I have 10s of devices.
All device have default packages.
This issue didnt just start happening out of the blue.
Currently the best solution (without having to create scripts etc) is to login and drag only needed packages onto the device and reboot …
Yes,
from offset factory defaults.
Devices have been upgraded for consecutive number of years.
Last few years this problem is getting worse and worse ..
mongobongo: Did you ever try to reboot the device just before trying the update? That may solve it for now.
The reason I mention this is that MikroTik claim in many threads that they “always test an upgrade with a device running with default settings” and they claim it works.
But we as the users see it fail. So there must be something different between their testlab and “the field”. Apart from maybe some complex configurations, another difference likely is that they just netinstall their device with a test setup, and immediately try to upgrade. That has more chance of succeeding than trying to update a device that had been running for a couple of weeks and has used up or -fragmented RAM.
Yes, the first screenshot on my 10/6/2020 post was a default packages preinstalled on hap lite devices. No extra packages installed, had only ever done a simple NAT quickset config and check for update on that Mikrotik device and starting ~6months ago check for updates has been failing due to low disk space when trying to update.
I fully agree that on a typical SOHO device a few packages have no place to be installed as factory default. These include: mpls, routing and hotspot, they are clearly advanced stuff that vast majority of users will never need. In addition, these are quite probably not necessary for router to be initially set up and connected to internet, at which point they can be manually uploaded to the router. Many users won’t need a few additional packages (such as ppp and advanced-tools), but those might be needed for successful initial device setup, hence they should stay in the default installation list of packages.
As written in other threads, it was not good to make the “combined package” and thus make it impossible to remove packages and gain space.
Indeed as you point out, there are packages on this class of devices that have absolutely no business being there. But they do take up space.
In my opinion the package combining should never have happened, and instead there should have been a convenient package selection feature that retrieves the wanted packages from the download server without the hassle of downloading a bundle, unzipping, and uploading to the router. Just a list showing all available packages and click-to-install-this. Then it would not be such a hurdle to decide to remove something, it can always be re-installed.
But apparently the move is now further towards a “one package does it all”. In v7 there is just the “routeros” package that includes everything that was in the combined package, and more (e.g. the ntp package is now included as well). So the option of omitting what you don’t need is going away.
I understand that it is extra work to maintain exact dependency information and that some features introduce dependencies that are not obvious to a new user (e.g. some VPN types requiring DHCP). But then maybe there should be a “RouterOS v7 light” that just does not include all functionality, or else these “mini” devices should be abandoned.
I’ve got two devices with 16meg flash. Looking at “Files” both report around 12.6 used out of 16, but the actual files listed only amount to less than 100k. How do you see what is actually occupying flash?
This is not about 16M flash. That is not the problem (yet). You cannot see the RouterOS files that occupy the flash.
The issue is about devices with only 32M RAM (and 16M flash). These are the ones with the upgrading difficulties.
Yes of course,
the “golden rule” in most things IT related, if it does not work, restart it and try again
I’m in the category of “have 1000s of devices”. To be precise, close to 15.000 hAP Lites in our network. We are trying to upgrade them to 6.47.4, to no avail. No custom packages, nothing out of the ordinary.
We get told the CPEs have 7.3MB left and 7.4MB are needed. We need a way to package single .npk files into an upgrade package with just what we need. Would we ever consider MPLS on a hAP Lite? Not in a million years… so why not give us the ability to remove it from the upgrade package?
I have just tried lowering DNS cache from the default to 512kb, and free memory has actually decreased to below 7MB (was suggested in another thread). Rebooting does nothing to help either. Have disabled MPLS package, no noticeable difference.
We have a mix of 6.43.12 up to 6.46.1, due to the way we provision them with a custom-made app. We need 6.47.4 on our CPEs (actually, anything higher than 6.46.3 as that’s when the hostpot login redirect got fixed…).
Taking the mick now… can’t make its mind up as to how much free is free…
Last one and I’ll shut up until we have other views. I have tried to upgrade by downloading separate package files to a test CPE. This was fine until they would not all fit either, and had to do one set, reboot, then another set, reboot… with the added risk that a CPE could lose power at any time, breaking the process and leaving it in a corrupted state, as only some packages (if any got downloaded) would install.