No RouterOS version shown

RouterOS General
1

Hi,
I got one RB433 which was working correctly as a ap router for several years, so I didn’t needed to look into it.
Unfortunately yesterday I found that one of my client cannot connect to this one.

I tried different channels - no luck.
I tried changing several wireless settings - he doesn’t even try to connect.

So I try to reboot this RB. And it died… When I got near it, and connected with cable, I couldn’t find it.
But when I disconnected PSU and connected again RB woke up.

Before I will go to clients place, I wanted to update RB, but I can’t check it’s actual RouterOS version.
No version near Identity at top of Winbox, in System>Resources, no package version visible, no version in terminal.
Same when connecting via web.
I saw some bad blocks but 1,8% shouldn’t be a problem.

Can someone help me with that?
Two more clients are connected properly to a different wireless interface.

2

Perfect candidate for a netinstall

3

Does it matter which version will I choose?
Should it be the newest stable or maybe 5.26?

And when I tried to do backup file I got this:

echo: backup,critical error creating backup file: could not read all configuration files
4

I’d use bugfix 6.38.7 with latest netinstall.

Looks like NAND is corrupted on your 433; netinstall is exactly what will fix that by reformatting it and reinstalling ROS from scratch.

5

Definitively not 5.26. It’s so many years old.

Use the latest version (either bugfix or current).


Since backup cannot complete properly you can run a /export to export the whole configuration as commands.

You will have to manually run them after the netinstall but it’s still faster than configuring the router from scratch.

6

One more thing: newest Netinstall from General Section at Mikrotik Download page has “tile” at end of it’s name (netinstall-6.38.7-tile.zip). Should I bother this?

7

No, that’s the version you need. There’s only one netinstall platform AFAIK.

8

It turned out, that major problem is with MT at client’s site. I make it work, and it connected to the problematic RB433 without any issues.

I left the RB433 without netinstall, because I found that it also has faulty ether1, only PoE working :slight_smile:

I found a solution with using a RouterBOOT update but sending routeros .npk file instead. One guy had written it is possible, but no one confirmed.
Do you guys have any knowledge about this?
Since right now RB433 base is working I don’t want to try on this and eventually brick RB.

9

You could send the NPK file through the serial port if you configure a PPP server in the router. Then you will get an IP address and can connect and send files.
But I very much doubt that a RouterOS upgrade can fix a non working port.

10

More faith, Normis :smiley:

My general problem is not non-working port. The problem is that RB433 is acting weird like it doesn’t show RouterOS version anywhere, it doesn’t boot up after soft reboot, and it gives error while doing a backup. So pukkita and Cha0s advised me to make netinstall to this RB. But when I got near it I found out that ether1 is broken, there is no link, only PoE. So that’s why I would like to make install different way.

I could also try to copy .npk file normally through winbox, but I am afraid of that because of

echo: backup,critical error creating backup file: could not read all configuration files

, and 1,8% bad blocks, and also I don’t know the routerOS version.
Maybe my fears are unfounded?