RB112 useless after upgrade to 2.9.25 broken package I guess

RouterOS Wireless Networking
1

I upgraded one RB112 from 2.9.24 to 2.9.25 and now its not working any suggestions how to fix this mess?

I guess the package was broken, now how do I fix it?

Here’s the terminal output

Reboot, yes? [y/N]:
system will reboot shortly

Rebooting…
Stopping services…
ERROR: installation of routeros-rb500-2.9.25 failed: broken package132
WARNING: package system-2.9.25 onuninstall script failed
11 packets tra
/etc/rc.d/rc.stop: 34: /etc/rc.d/rc.postinstall: not found
round-trip m
/etc/rc.d/rc.stop: 36: /bin/umount: not found

Now it keeps rebooting:
RouterBOOT booter 1.13

RouterBoard 112

CPU frequency: 175 MHz
Memory size: 16 MB

Press any key within 1 seconds to enter setup.
kernel not found
trying bootp protocol…d
kernel loading failed
C¡HHõÕÑ•É ==Q

2

try to reinstall your board using netinstall.

3

Thks a lot sergejs, that did the trick.

4

Does anybody has an idea why Mikrotik guys does not ZIP .npk files in order to avoid this “damaged” packages downloads in the future?

Is a lot easier to re-download a damaged ZIP that netinstall again a router, dont you think so?

Best

Jorge

5

Jorge, there are alreade zip package for both version x86 and ‘ns’.

6

I had to netinstall 3 2.9.18 to 2.9.25 upgrades this week on RB112’s. I did not change the file or redownload it, it worked on 3 of them, and 3 of them it failed on. Some I used FTP, others I used Winbox drag and drop, and it didn’t seem to matter (3 good ones were combinations of both also), and 1 was lost with a direct ethernet connection.

All the same downloaded file. Does MT have a checksum on the NPK file, or does it blindly install it?

7

Thks sergejs, but I guess you mean the “all packages” file isnt it?

And I guess the file that is or was damaged was the one hosted at Mikrotiks USA server; because I downloaded it again and upgrade again the RB112 and had the same result, then I tried to netinstall that same .npk and netinstall crashed, then I downloaded the .npk from Latvia server and everything just went OK.


Best

Jorge

8

That does make sense, I think I might have redownloaded the file after I had a problem from the first one now that you mention it.

9

well personnally i usually upgrade with ftp clients like smartftp other methods always give me some sort of error or the other. you guys should try that out too

10

Well … it was upgraded using a FTP client…
The Netinstall method was used after the routerOS got screwed up by the damaged .npk file.

Best

Jorge Boardman