[Solved] - CCR1036 upgrade (silently) fails

RouterOS General
1

Hi folks,

I have one CCR1036-12G-4S which has issues with its upgrade process:

[admin@vdg-rtr01-pa2] > /system package print                    
Flags: X - disabled 
 #   NAME                    VERSION                    SCHEDULED              
 0   ntp                     6.29.1                                            
 1 X ppp                     6.29.1                                            
 2   dhcp                    6.29.1                                            
 3   ipv6                    6.29.1                                            
 4   mpls                    6.29.1                                            
 5   security                6.29.1                                            
 6   advanced-tools          6.29.1                                            
 7   user-manager            6.29.1                                            
 8   system                  6.29.1                                            
 9   openflow                6.29.1                                            
10   multicast               6.29.1                                            
11   routing                 6.29.1                                            


[admin@vdg-rtr01-pa2] > /system package update check-for-updates 
  current-version: 6.29.1
   latest-version: 6.31

[admin@vdg-rtr01-pa2] > /system package update download          
  current-version: 6.29.1
   latest-version: 6.31
           status: Downloaded, please reboot router to upgrade it

But … if I reboot the router, it is still stuck with version 6.29.1.

What could I do with that ?

Thanks !

2

Hi,

a pragmatic way to solve this would be:

Export your config.
Do a netinstall with new RouterOS.
Import your config.

If this device is mission critical, try this at first with a spare device to ensure the exported configuration works flawlessly with the new RouterOS version.

Ape

3

Hi Ape,
Thanks for your reply !

I thought about changing the router with a spare, but I’d like to know first what could I do in order to debug.

The colo datacenter is quite far away, and I’d like to explore anything that could be remotely feasible, first :slight_smile:

4

Hi,

okay - I understand :wink:

Did you upload the new packages via Winbox/FTP or did you used “Check for updates” button?
Normally uploading the .npk-File and rebooting the device does the trick.
Sorry for asking this dumb question, but did you use the right npk-file for the CCR’s system architecture (I think it’s tile)?

You can enable debug logging in “/system logging”, maybe you’ll get told what’s wrong.

Ape

5

I used the “check for updates” button, and “download and upgrade” then.
I will try to manually upload the (right) .npk files, and let you know what happens :slight_smile:


Logging is not useful at all :frowning:

6

Hi again,


I uploaded routeros-tile-6.31.npk by FTP on the router (and erased any old .npk on it), and issued a reboot… still no effect, stuck in 6.29.1 :frowning:

7

Hi,

I’m sorry to hear that.

Have a look at http://forum.mikrotik.com/t/problem-updating-routeros-6-25-to-6-27-on-a-mikrotik-x86-based-architecture-server/86090/1
It might be some conflicting files.

If you can dismiss this possibility I think you should write to support@mikrotik.com


Ape

8

Hi !

Thanks for the link, I will have a look on it, and see if I can have something successful :slight_smile:

Regards,

Acontios

9

Well, seems that it was that !

I removed the .npk I previously uploaded, leaving the disk without any NPK.
And then, I made the “check for updates” + “download&upgrade” process from /system packages, and everything worked.

Thanks for your help, Ape ! :slight_smile:

10

Great! It’s always a pleasure to help.

Please prefix the title of your first post with “[solved]”, so other people looking for a similar problem can see at a glance that this thread describes an approved solution. Thank you!

Ape

11

Done :slight_smile:

12

Sorry to bring this Topic on to again.
I just had a similar Problem. But my CCR didn’t reboot when I clicked on “Reboot”, so an upgrade wasn’t possible. Upgrading via “check for updates” did a proper reboot so the upgrade worked.

Are you sure that your CCR did a reboot? I just want to find out if it may be a bug or if my CCR is just crazy.

  • Mat
13

The CCR did really reboot, yes :slight_smile:
I guess it may be a bug on your side.

14

Okay, thanks for the reply.

  • Mat