I attempted to upgrade from 2.9.13 to 2.9.17 this morning, and it didn’t work. or, it half-worked. or it fully worked… I just am not sure..
As usual, I uploaded the new .npk to the Routerboard 500 for 2.9.17, and issued a “/system reboot”. During the shutdown portion of the reboot, the kernel panicked; i couldn’t tell what process caused the panic, but there was just multiple, continuous spew of kernel-panic info across the serial console. After a bit, I power-cycled the unit, and it came back up.
Here’s the interesting part: On login, it shows 2.9.13 on the login banner.
But doing a “/system package print” I get:
[admin@sentry] > /system package print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 ppp 2.9.13
1 routeros-rb500 2.9.17
2 X rstp-bridge-test 2.9.13
3 webproxy-test 2.9.13
4 system 2.9.13
5 routerboard 2.9.13
6 advanced-tools 2.9.13
7 ntp 2.9.13
8 dhcp 2.9.13
9 hotspot 2.9.13
10 security 2.9.13
11 routing 2.9.13
12 X wireless 2.9.13
13 X routing-test 2.9.13
[admin@sentry] >
Note the 2.9.17 on the roueteros-rb500.
I was able to downgrade back to 2.9.13, and attempt the upgrade to 2.9.17 with the same results of kernel-panic’s and partial-(appearing) install.
Any advice on how to get everything up to 2.9.17 ??
the routeros-rb500 package is around for a while already, and as you can see by it’s size - it contains all packages. so you have to choose - to use one big package, or use many small packages. not all of them.
i don’t know where you got the small packages, but on the download page there is only the big package, and it even says - all in one package:
I disabled all packaged except for routeros-rb500 and system, because it would not let me disable all packages, and i rebooted as per your suggestion.
THis did not work, because the router was then unable to route, nor to fetch a DHCP address from my cable provider, so I was dead in the water til I re-enabled the relevant packages again.
Can someone out there running 2.9.17 do a /system package print, and confirm that they do indeed see all packages listed as 2.9.17, or if it’s a mix of that release and a/the previous release??
Alternatively, is there a place on this site that has prevoius OS releases posted?? I’d like to try doing an incremental release from 2.9.13 up through 2.9.17; I only have .13 and .17 here, as well as a few previous releases…
I uploaded 2.9.17 and rebooted 2 more times. The 2nd time, it didn’t kernel-panic on the way down during the reboot, and the install actually “took” and all packages now show as 2.9.17.
Nothing changed on my end; same procedure of SCP the image up there, and reboot. Not sure if the disable / re-enable of all the packages in the interim had an effect. But we’re good to go now…
dsdee, may be a kind of package conflict occures. In case that routeros-rb500 contains all other packages , why do you left the system package. I think that if the system package is 2.9.13 all others wont be upgraded. I suppose that in the case with only routeros-rb500 i system packages active , the system has had precedence and that’s why you haven’t any routing and dhcp abilities. OK?