Just use Netinstall to re-install the whole system, it's reasonably straightforward, perhaps familiarise yourself with it with another Mikrotik router before you get there. http://wiki.mikrotik.com/wiki/Manual:Netinstall Regards Paul -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Damien Gardner Jnr Sent: Wednesday, 4 March 2015 10:32 AM To: MikroTik Australia Public List Subject: Re: [MT-AU Public] CCR1009 crashing - how to debug? Hi Paul, I might try the reflash first - what's required to do that? If that doesn't fix it, i'll go with a routeros VM in my xenserver cluster for now. Thanks, Damien On 4 March 2015 at 10:24, Paul Julian <paul@oxygennetworks.com.au> wrote:
Damien is sounds like it's flocked, I would either do a total reflash or replace it.
Regards Paul
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Damien Gardner Jnr Sent: Wednesday, 4 March 2015 10:18 AM To: MikroTik Australia Public List Subject: [MT-AU Public] CCR1009 crashing - how to debug?
Hey All,
My CCR1009 rebooted 6 times overnight. I thought maybe it was a problem with 6.25, so upgraded to 6.27. That was a bad idea, as it took a remote hands power cycle to get back into it. I then did a downgrade (which took it all the way back to 6.21.1) Seemed ok, till I tried to scp the 6.25 files up to it. As soon as I went to view flash, it rebooted again. Interestingly it hasn't upgraded to 6.25, though i don't dare try to view the files on flash to see if they actually copied..
After much swearing and praying, it seems to be stable - so long as I do not try to use winbox. Seemed like as soon as i used winbox (or the http variant), the router would reboot. However now I can't even use winbox.
Seems to be stable if I don't try to login to it at all, so I think I'll leave it sit there for the day, and head to sydney tonight.
What can I do to try and work out WHY it's rebooting? All my logs say are: system,error,critical System rebooted because of kernel failure system,error,critical router was rebooted without proper shutdown, probably kernel failure
There's nothing else about the reboot at all. Is there any more debugging I can turn up for it?
If all else fails, I can shove my old little DL360G3 back in, and fire up quagga, but if there's a way to debug and fix it without heading to Sydney, that'd be nice ;)
Thanks,
Damien --
Damien Gardner Jnr VK2TDG. Dip EE. GradIEAust rendrag@rendrag.net - http://www.rendrag.net/ -- We rode on the winds of the rising storm, We ran to the sounds of thunder. We danced among the lightning bolts, and tore the world asunder _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
-- Damien Gardner Jnr VK2TDG. Dip EE. GradIEAust rendrag@rendrag.net - http://www.rendrag.net/ -- We rode on the winds of the rising storm, We ran to the sounds of thunder. We danced among the lightning bolts, and tore the world asunder _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au