[admin@MikroTik] > /system package update
[admin@MikroTik] /system package update> print
channel: stable
installed-version: 6.47.9
latest-version: 6.49.5
status: ERROR: not enough disk space, 7.1MiB is required and only 6.3MiB is free
[admin@MikroTik] /system package update>
I already did a soft config reset, and disabled every package that I could:
[admin@MikroTik] > /system package
[admin@MikroTik] /system package> print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 routeros-smips 6.47.9
1 system 6.47.9
2 X ipv6 6.47.9
3 wireless 6.47.9
4 X hotspot 6.47.9
5 X mpls 6.47.9
6 X routing 6.47.9
7 X ppp 6.47.9
8 dhcp 6.47.9
9 security 6.47.9
10 X advanced-tools 6.47.9
[admin@MikroTik] /system package>
Also, removed all files from /file, but it still does not have enough space.
In the next step, I tried to reinstall (and upgrade the OS) using netinstall. Followed the steps here: https://www.youtube.com/watch?v=gzlLbIf3Dbk and it simply does not work. I used the latest stable netinstall64-7.1.5 with routeros-7.1.5-smips image. After netinstall told me that it was ready with the installation, I rebooted the router and this is what I see:
MikroTik RouterOS 6.47.9 (c) 1999-2020 http://www.mikrotik.com/
[?] Gives the list of available commands
command [?] Gives help on the command and list of arguments
[Tab] Completes the command/word. If the input is ambiguous,
a second [Tab] gives possible options
/ Move up to base level
.. Move up one level
/command Use command at the base level
mar/27/2022 09:30:30 system,error,critical router was rebooted without proper shutdown
[admin@MikroTik] > /system package update
[admin@MikroTik] /system package update> print
channel: stable
installed-version: 6.47.9
latest-version: 6.49.5
status: ERROR: not enough disk space, 7.1MiB is required and only 6.3MiB is free
[admin@MikroTik] /system package update>
The linked thread is somehow obsolete, unbundled installs can not be upgraded to v7.
So netinstall seems the only way. Follow the manual and beware that netinstall is a very fragile process. So do make verything “by the book” and be prepared to do it multiple times. And make sure you have both configuration backup and text export at hand. Also winbox (v7 requires winbox version 3.35, v6 is happy with slightly older winbox versions), it’ll help with getting hAP lite configured after netinstall. If you’ll go to ROS v7 (I’m not recommending it right now to users with less ROS experience), then go with default setup and use text export of current config as reminder for any fine tuning necessary (restoring setup from binary backup seems to leave some traces of setup which can cause instability).
After you manage to upgrade ROS (whichever version), do upgrade routerboot as well.
A hint: it is very hard to get the “button press” timing right. As you still have full control over your device, set /system routerboard settings set boot-device=try-ethernet-once-then-nand … device will go into netinstall mode after reboot without pressing the button and if everything else is fine (netinstall binary running on your computer, it’s correctly setup, computer is connected to ether1 of hAP lite, etc.), it’ll appear in netinstall window.
The setting mentioned reverts to default nand-if-fail-then-ethernet after reboot sequence though.
Another detail: if you go with v7 and find your device later to enter reboot loop, you’ll likely have to upgrade routerboot to latest v6 … which means netinstalling device to 6.49.5, upgrading routerboot and later upgrading to v7 (either via ROS built-in upgrade command or via netinstall).
In that topic, they recommend this: “4. Upgrade using only this packages taking them from the all packages zip:” - but where is that zip file? The whole update can be downloaded as a single npk file.
After pressing the reset button for about 20 seconds, the device showed up in the netinstall program. After that, netinstall allowed me to upgrade, using the npk file. At the end of the process, it displayed “Ready” status. There was no error message. I think that I did everything right. If you think that there is a possibility, that I did something wrong, then please be more specific.
I do not need my old config. I have enough experience to build up a working config from scratch. If fact, I usually start with “/system/reset-configuration no-defaults=yes” with any new MikroTik device that I buy. Configuration is not a problem. The problem is that I cannot upgrade the OS.
I did check the default config checkbox in netinstall (just to make sure that it removes my old config completely as part of the upgrade process). I also tried to upgrade to the latest v6 version but it fails too. The behaviour is the same: netinstall displays the device, then I select the OS image, press install, and finally netinstall writes “Ready” status. But nothing else happens, the router OS version is not changed.
You mean /system/routerboard/upgrade - I’m aware of that, but that is available after the OS upgrade only. And the OS upgrade does not work.
Thanks for the tip. I’ll try that, just to be sure. However, the device DID APPEAR in netinstall, and the netinstall program did uplodad the image, and finally it displayed “READY” status. But nothing was upgraded.
All right, I hope that it will not enter an infinite boot loop.
For each architecture and each ROS version (the 6.x.y series) there are two download links: Main package and Extra packages. The former links .npk, the later links .zip.
Before the last image, I waited about 2 minutes to see if the device reboots itself, but nothing happens. Also tried to press the reset button, but it does nothing. Then I power off + power on again to reboot, and it comes up - with RouterOS v6
I wonder why MikroTik does not provide smaller images for devices with less flash memory, and why they make it possible to make the image smaller for devices where there is plenty of space. There must be technical reasons, I’m sure.
Another interesting fact: I actually bought two HAP LITE devices about two years ago. They are not just the same type, they are from the same batch. I could install v7 on the other, using the /system package upgrade download menu. It was seamless.
Because they provide single package image for all devices of certain architecture. Some architectures have numerous members with quite different peripherial hardware (wireless, different switch chips). And every Mikrotik device has the same set of functionality (but wildly differ with regard to performance).
This is one of biggest advantages of MT compared to other vendors. But yes, it does come with cost. It might turn out it’s too high.
And then there’s the fact that price/performance ratio is one of greatest in the industry. And driving production costs down helps in this equation. Hence use of small flash storage and smaller amount of memory. But this drive will cause soem sorrow as well, we all know that even though hAP ac2 is capable of running wifiwave2 drivers (specially the early devices which come with 256MB RAM), it quite probably won’t happen due to tiny flash size, 16MB is simply too tiny. I’ve got one of these beasties, unbundled install of 6.49.3 with quite some packages left out (routing, mpls, hotspot … combined they use up around 1MB when uncompressed) and yet my flash is only 700KB free. BTW, more than half of space is used by wireless package (total uncompressed size of packages inside that bundle is 10.8MB, wireless alone is 6.6MB).
I see too much different MAC address.. is a collage???
48:8F:5A:6C:9B:2E ether1
48:8F:5A:6C:9B:2F ether2
48:8F:5A:6C:9B:31 ether3
just missing
48:8F:5A:6C:9B:32 ether4
and
48:8F:5A:6C:9B:33 wlan1
remove all other cables from hap and disable all other network interface on PC used before open and use netinstall.
sometime when apparently netinstall install instantly the software and the device appear as “ready”
simply close netinstall, reopen netinstall, select the device and click again on install
Not a collage. 48:8F:5A:6C:9B:2E is ether1. That port was used with netinstall. After device was rebooted, I connected the same cable to a LAN port, because winbox does not work with ether1 (with the default config). Exactly one cable was connected to the device throughout the whole process, but in the last step, I had to change port from ether1 to a different LAN port. This is why you see two MAC adddresses. One for ether1 WAN port, and the other for a LAN port.
I think nothing is missing - I connected exactly two ports, and I see exactly two MAC addresses. What else should I see?
As I wrote before, I followed the instructions by the word. Wifi was disabled on the PC. There was only a single NIC card enabled in windows, with a static address, and the bootp client address was configured to a different address. Netinstall was started as administrator.
(Side note: it is not the first time that I used netinstall. I have already used netinstall for many other MikroTik devices. But this is the first one that fails.)
This was the exact version that I was using. If you look at my first image it says "MikroTik Netinstall for RouterOS v7.1.5" in the title. (I also tried the latest rc5 version, it makes no difference.)
Do you think that it might be a hardware failure? I doubt it, because there are no error messages anywhere, and the router actually works with the currently installed OS version. But it might be the case.
