ERROR: not enough disk space, 7.7MiB is required and only 7.3MiB is freeToo late sorry - my post got stuck in the moderation queue and I gave up waiting for it - ended up doing a netinstall, which worked.please post "/system package print" and "/file print" just to be 100% sure you didn't miss something
There isn't enough space to do that. This is a remote router. Netinstall is not an option.Remove unwanted packages. Remove all removable files. Put newer single system package only and reboot. Then add rest of required packages and reboot again.
That's how I managed to resolve the problem. By only downloading the absolute minimum packages required for the next version and rebooting. You only need system and security for most purposes. Wireless too for non-ethernet connected devices.May be don't include modules disabled by default in RouterOS package forsmips?
advanced-tools, hotspot, mpls, routing, security-- that modules can be uploaded separately.
In recent versions security package depends on dhcp packageThat's how I managed to resolve the problem. By only downloading the absolute minimum packages required for the next version and rebooting. You only need system and security for most purposes. Wireless too for non-ethernet connected devices.May be don't include modules disabled by default in RouterOS package forsmips?
advanced-tools, hotspot, mpls, routing, security-- that modules can be uploaded separately.
Even if DHCP package is installed but disabled, upgrade won't proceed ... so DHCP package has to be installed/enabled before performing upgrade.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.In recent versions security package depends on dhcp packageEven if DHCP package is installed but disabled, upgrade won't proceed ... so DHCP package has to be installed/enabled before performing upgrade.
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.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.
Hi, fortunately I dont have 100s of device I have 10s of devices.Do your hundreds of devices have custom packages installed? Normally there shouldn't be any custom packages and no problem upgrading.
Yes,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.
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.My question was, does anyone have issues using "check for updates" with a device with factory installed version?
This is not about 16M flash. That is not the problem (yet). You cannot see the RouterOS files that occupy the flash.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?
Yes of course,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.
In 6.47 that capability is actually still there!We get told the CPEs have 7.3MB left and 7.4MB are needed. Weneeda 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?
What's new in 6.47.6 (2020-Oct-21 10:41):
*) cap - fixed L2MTU path discovery;
*) crs3xx - fixed hardware offloaded LACP bonding on Ethernet interfaces for CRS354 devices;
.........
*) radius - added "Service-Type" attribute to Access-Request for IPv4 and IPv6 DHCP servers;
*)smips - reduced RouterOS main package size;
*) switch - fixed Ethernet padding for small packets;
.........
I have the exact same problem. Tried 3 different newer versions (stable and long-term) but nothing worked.有相同的问题试图升级from 6.47.* 6.48.3. The same issue as the person above, I've got hundreds of these devices deployed in customer's homes and there is just no space left. Even after manually disabling all the unneeded packages, and manually dragging only the required upgrade files(1% space left over)and rebooting then logging in to find the update packages are removed from the files directory, and the system remains at the same version it was before. I've tried the instructions above on multiple hap lites and all of them do the same thing. They will not upgrade.
There is no way we can schedule an on-site for each of these devices installed in the field to intrude into a customer's home so we can sit and fiddle around with their router trying to do a netinstall, that's why we setup remote administration and the dude server to monitor them in the first place, it's not feasible.
If a smaller upgrade package doesn't come, we're gonna be left with no choice but to just junk all these devices and replace them with something else.
Cost wise, it's going to be far cheaper to simply re-deploy with a different device than to have an on-site tech sit and manually fiddle with each of these until we can finally get them to upgrade.
Thankfully, it's only our residential customers that have ever had hap lites deployed to.
It works like that on the more capable devices that have only 16MB of flash but do have a reasonable amount (128MB or more) of RAM.I have the exact same problem. Tried 3 different newer versions (stable and long-term) but nothing worked.
Auto-update should copy files to ram if I understand correctly but it doesnt work
Ok I understand that it has limited capabilities due to low flash and ram size.These devices realistically are at the end of the road. You can limp by when you install only separate packages (only what you need) instead of the bundled package, but it brings only very little and they will be in trouble again.
The best move is to replace them with a newer device, e.g. for the hAP Lite that would be the hAP ac2 or ac3.
Don't get another "lite" model or other out-dated device with only 64MB of RAM, it will quicky get in the same trouble.
It sounds like bad design/marketing from the manufacturer.Low cost home wireless AP with dual chain 2.4GHz wireless, powered by USB
The home Access Point lite (hAP lite) is an ideal little device for your apartment, house or office.
I don't care about updated features but I care about security updates.Which probably does not matter anyway, as you will not be using all those updated features.
When you are using it as a basic access point on a home network (bridge mode, behind an ISP-provided NAT router), and you had already updated it in the last two years or so, there is really nothing to worry about.I don't care about updated features but I care about security updates.
Thanks for the update! Any indication why?All other optional packages, that were available for SMIPS, are now integrated in the big package.
But it is unlikely that you can just upgrade to that version without running out of space, choose the "backup, netinstall, restore backup" path instead.
Ahh, fantastic! Why didn't I think of that soonerPrepare a new and better router with new RouterOS and ship it to the site. Tell them to throw the hAP Lite in the bin, where it belongs.
