Thank you so much dear mkx for your answer above;The only procedure, which guarantees success (once the fragile procedure starts to work) is netinstall ...
Thank you so much dear pe1chl for your answer above;Is your device on a network connected to internet? Did you already try to just use System->Packages->Check for Updates->Download&Install ?
(without sending files to the device yourself, just let it fetch the update automatically)
For this to work, IP->DNS has to be configured with valid data (or the DNS servers have to be automatically set there) and the device needs outbound access to internet.
You must configure the DNS servers in IP->DNS. When there is nothing in Servers and Dynamic Servers, enter one or more servers like 8.8.8.8 or 1.1.1.1 there.
But, I can not automatically updated my devices from the inside it by ( Check For Updates ) !!?
And, I usually face some problems;
Like a problem: ( ERROR: could not resolve dns name ) !!?
Or a problem: (ERROR: bad HTTP response ) !!?
So, can you help me to solve that problem?
Thank you so much dear kalamaja for your answer above;1. Download all_packages-mipsbe-6.46.2.zip
2. Unzip the package
3. Upload only those packages into router Files section that are enabled and needed in your setup
4. Reboot
Thank you so much dear pe1chl for your answer above;You must configure the DNS servers in IP->DNS. When there is nothing in Servers and Dynamic Servers, enter one or more servers like 8.8.8.8 or 1.1.1.1 there.
And of course you must be able to reach internet from the device. So in Tools->Ping try to ping 8.8.8.8. That must work. When not, fix it first.
(check IP->Routes etc)
No. That is something you have to debug locally.
Thank you so much dear pe1chl for your answer above;
Yes, I have already used the method that you mentioned and tried repeatedly.
And, when I do a ping to an address like ( 8.8.8.8 ) or another seen, the result always is " Timeout " !!?
Really, I don't know why?
So, can you help me to solve that problem?
It is much better to check ping mikrotik.com as it checks not only Internet access but also a DNS resolver.....
And of course you must be able to reach internet from the device. So in Tools->Ping try to ping 8.8.8.8. That must work. When not, fix it first.
(check IP->Routes etc)
It is much better to check ping mikrotik.com as it checks not only Internet access but also a DNS resolver.....
And of course you must be able to reach internet from the device. So in Tools->Ping try to ping 8.8.8.8. That must work. When not, fix it first.
(check IP->Routes etc)
Thank you so much pe1chl for your interested.No. That is something you have to debug locally.
Thank you so much BartoszP for your interested.It is much better to check ping mikrotik.com as it checks not only Internet access but also a DNS resolver.
Thank you so much CZFan for your interested.No, you need to ping an IP address first, then you know you have connectivity, then you can test name resolution
Thank you so much aquilesopkarg for your reply.No. That is something you have to debug locally.[/u]
Thank you so much CZFan for your interested.Contact one closest to you for this and other Mikrotik problems you are experiencing
https://mikrotik.com/consultants
Thank you so much raymondr15 for your interested.If I get the "not enough disk space" error then I just reboot the device and then run the update straight after the reboot and it works.
Thank you so much macsrwe for your interested.Maybe you have log space configured very large, and rebooting deletes the logs.
Once again...Let me repeat myself: the only procedure which guarantees successful ROS upgrade on devices with very low disk space is netinstall. There have been ROS versions which were too big to allow any kind of ROS version change (either upgrade or downgrade) and lack of space was caused simply by too big packages.
Longer term solution is to "unbundle" ROS installation (i.e. install individual packets which are really needed on the device instead of main package which is a bundle of many packages and not all of them are probably needed). Disabling packages is not sufficient.
But even "unbundling" can fail in case of extremely low free storage space.
The solution of rebooting device immediately prior to starting upgrade procedure helps if RAM is low ... reboot helps to free up RAM which allows to download upgrade packages (these are temporarily stored to RAM disk) but doesn't help with shortage of non-volatile storage (i.e. built-in flash disk).
Netinstall is nothing to fear ... remember to create backup and to pull backup file off the device before starting netinstall. After successful installation of new ROS, restore device configuration from backup file.
Once again...Recommendation is that when performing netinstall, management PC is connected directly to device being upgraded (and that's the only connection of that device). In this case it's not hard to upload backup file after netinstall is done.
Indeed netinstall is a painful procedure when normal upgrade over IP network should just work ... many users complained about it many times and MT staff did see complaints. But sh**t happens and netinstall is there to help to get out of it.
Once again...Sometimes one would wish there is a kind of "soft netinstall" where you can upload one or more packages and an initial .rsc file to a device that is still under control, and then request that it is completely re-installed from that data without an attempt to "install over the current state".
But sadly it isn't possible.
Fortunately it *is* possible to netinstall without access to the reset button, by setting the boot to "try ethernet once then nand" and doing a reboot, with netinstall running on the PC.
But yes, you need to do that from a PC connected to the ethernet side of the device. It cannot be done "over the air".
Once again...Unfortunately, sometimes you can't do what you want to do.
Perhaps you need to buy a different model router with more memory in it; then it will do what you want it to do.
Yeah, I know that but I told you that the problem is the Master device will be zero Formatted ;((
And, I can't connect to it after formatted ;(
Thank you so much dear mkx for your interested;When you are connected directly to the netinstall-ed device, you can connect using winbox via MAC connectivity.
Once Again ._.Please stop posting your boilerplate replies with only appreciation of the previous post, you are just wasting your time with that!
Spend that time on fixing your network (so you can try the builtin package update feature) or else go to the site and do the netinstall.
You are not going to solve it by nagging the users on the forum.
Thank you so much Jotne for your interested.I did just downgrade to a smaller package, then upgrade to latest. Did work fin for me, but my break config for others.