RouterOS version 7.2.1 has been released in “v7 stable” channel!
Before an upgrade:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What’s new in 7.2.1 (2022-Apr-06 11:52):
*) filesystem - improved long-term filesystem stability and data integrity;
To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device
Please keep this forum topic strictly related to this particular RouterOS release.
RB5009 partitioning issue is a known problem and will be fixed in future releases. There is no need to mention it again and again in forum topics. We are aware of the issue.
This is wonderful news. Thanks Normis, strods & whole Mikrotik team working on this issue, some of whom probably had a busy weekend hunting down bugs (more like finding a needle in a scrap yard with this one I’m sure) for the rest of us.
I just want to know if it would be possible to maybe share some more information about what was fixed/changed with this update? We obviously don’t have the same insider information as RouterOS developers so we don’t know how impactful this change could really be. Is it worth upgrading potentially dozens/hundreds of routers already on 7.2 to this new release or is it only recommended for new upgrades? Is this patch intended to fix the corruption on upgrade/reboot issue, or is it a broader & more general change which may or may not have this effect and we will just have to test? Any hints or pointers to address these types of questions will be greatly appreciated.. The only hint we have right now is the use of the word “improved” rather than “fixed” in the changelog and even that is quite vague as it doesn’t really convey the extensiveness of the changes.
Maybe you can just help us weigh out our options and point us in a preferred direction depending what scenarios we are already in, given the potential significance this single issue (or its fix) can have.
Thank you.
Update: successfully upgraded my home RB5009 plus a few other local devices without any data loss thus far (Yipee!). Results are looking very promising thus far. Still too scared to try any remote devices for now, I’ll think about it while waiting for some more more forum comments/feedback
Nothing new, the 7.x topics have some “lost all configuration” issue
But for the few device I have with 7.x is never happened,
but for some of my device (neat 1 on 100) happen from upgrading 6.44.6 to 6.46.8,
and the problem is on the missing “ssh host key”…
Just I remember now something like netinstall for do faster installation do not generate ssh host key on first RouterOS boot on old version…
“improved something” means “fixed something” in MT-changelog-words. Nobody knows what was fixed actually. Why should anyone install this testing release? Without knowing what was a) improved or changed?? How can anyone judge a difference between 7.2 and 7.2.1? MT staff keeps commenting here but give no additional info to this very vague changelog entry.
because it's the only Mikrotik with multiple ethernet ports that can be powered via micro usb
because it's used by thousands because it's the cheapest entry point for learning Mikrotik
I posted it because prior to 7.2, I could just winbox the smips .npk to files over the mac address, and reboot and it would upgrade.
I've enabled the dhcp client now, and upgraded via system packages.
There are Mikrotik devices that are only accessible on the Layer 2 network, and I'm just advising I had to enable Layer 3 networking to install this.