This is taking quite a long time compared to the Ubiquiti firmwares. Is it just because there is not as much action lately on the Mikrotik forums? 
itâs normal compared to previous ROS releases =) just wait for a knockout 
rc - finalizing everything, testing and retestingâŚ
Well, as I see it, there are soooo many new things in 5.x and it Will take a while to get them all working perfectly.
More then that - I think everyone will agree - it is worth waiting for this release.
Just donât start talking about 6.x already. 
Concerning my projects - some of them are working on 5.0 rc and I definately benefit from nv2, and I can forgive some of the smaller glitches and simplify my setups so that they work better.
Another alternative - port OpenWrt on RB711, but trust me - it will be longer wait and I donât know if ever work perfectly. Although I have some OpenWrt solutions made work, but not for production use. Some of them are just to cut costs of L3-L4 upgrade, which is a bit crazy-pricedâŚ
The ROS 5 RC1 doesnât really deserve the name, The number of broken things in it clearly show its not anywhere near RC status.
ROS version have always been buggy as hell in the first ten or so point releases, Weâve only just updated from 3.30 to 4.10 and even then suffer from some fairly serious bugs that MT are âworkingâ on(Highlight: Being told to install RC1 on a production network), Weâve played around with ROS 5 in the lab and thatâs it, It wont be going ANYWHERE near our production setup till ROS 5.10~ and even then only after heavy testing.
Well I tested out 5.0 RC over the weekend and had some SERIOUS âethernetâ issues.
When plugged strait into the POE, I could connect to the Mikrotik fine. However, when I plug into 8 port switch, I kept losing connectivity via ethernet to the MT. Even tried MAC entry and still would drop out. Please note Mikrotik, 5.0 RC has serious issues with connectivity when going through switch.
did you connected by IP?.. MAC WinBox is instable by its nature, as Normis says =)
Yes I tried IP, as usual, and it would look like this after 5.0 RC
Reply -1ms
Reply -1ms
Reply -1ms
Reply -1ms
Reply -1ms (then I try to log in)
Reply -20ms
Reply -40ms
Time Out
Time Out
Time Out
Time Out
Reply -20ms
Time Out
Time Out
Time Out
Time Out
Time Out
After DOWNGRADING back to 4.11 everything was fine. This happened on (2) separate Mikrotiks, so I know that wasnât the problem. And it only seemed to happen when going through the 8-port switch. I canât think it would be any other problem than the firmware, because all else is fine after downgradingâŚ
wisp⌠i cannot account for your issues (unless it is POE related) but I can also tell you that I have 6 PtP links running rc1 without issue. My 7th link had an old RB532A that didnât like the upgrade to rc1 but I cannot say that it was rc1âs fault as I have not throughly troubleshot.
it seems to me you have tried rc1 on one set of RBs and experienced problems. iâm not sure your conclusion is entirely warranted at this time.
however, that is not to say rc1 doensât need work. it does. but i have not had STABILITY issues (as long as stay with nstreme and donât use nv2.)
when ROSv5 become stable, will I be able to upgrade from v4 with the my current setting without problem?
we still have to get to 5.0 stable as it is still in RC stage. At worst you should consider that precautions that had to be made form 2.9.x upgrade to 3.0 and then in turn 3.x to 4.0 upgrade should be taken. A lot has changed and some things are set to be changed.
@janisk: Just a question regarding upgrading 4.1x to v5.0 RC5. How long should we wait a router to reboot after uploading the routeros package? A few minutes ago with a brand new RB493G, Iâve uploaded the RC5 combined package (via Winbox files) and then ordered it to /system reboot. I waited almost thirty - forty seconds but it didnât restart. After recycling the power, router died; No second bootstrap beep and no longer detected by Winbox.
I was able to reflash it to 4.13 using netinstall but on second try to upgrade to RC5 (using ftp now) it happened again. This time I flashed it directly to RC5 via Netinstall. Now everything is back in order but I wonder; Is it a problem of the specific RouterOS version, is it the board, do I have to wait a bit longer during reboot or I missed something?
Thanks!
30 is not so much, remember that itâs installing all the packages you uploaded. wait a minute. also make sure that you have enough free space before upgrading. best is to check with serial console to see what is happening
Thanks for the tip normis. I donât remember exactly how long I waited but it was about half a minute.
How long is it safe to wait for a 680MHz model to reboot after its firmware got updated? Besides using the serial console, do you suggest any specific precautions for avoiding firmware corruption or even board damage?
Hi,
Just upgraded my RB433AH with combined package, it took about 3 minutes.
Regards, Grzegorz.
Three minutes after finished uploading the upgrade packages?
Thanks Grzegorz!
here every rb450g takes about 3 ~ 5 minutes at most!
Iâll keep that in mind next time. BTW this should be clearly specified in RouterOS upgrade documentation.
Thank you all, folks!
A few seconds of installing RoS 5.0RC5 ( combined packages ) on x86 platform with 160GB SATA drive and about 4-5 minutes on RB433 and RB333.
SATA HDD is a bit faster than NAND =)