I have a RB600 that was running ROS 3.22 that I decided to update. I first installed ROS 4.17, then ROS 5.2.
I have 4 wireless cards in this unit. Two R5H's for ptp links and 2 XR2's for ptmp links. One of the XR2's was running 10mhz channel width. After the upgrade, none of the clients would connect for more than a split second. The logs said disconnected due to extensive data loss. I tried adjusting the hardware retries, the disconnect timeout, adaptive noise immunity, etc. Nothing would help. I assumed it had something to do with ros 5.2 so I downgraded to 4.17.
After the downgrade, all the clients could connect again, but a new issue started. The routerboard would only run for a minute or two tops and it would reboot. At first it would give the error "router rebooted without proper shutdown(cause 1)" then it also started giving the error, "router was rebooted without proper shutdown by watchdog timer".
I tried downgrading to ros 3.3 but I am still getting the "router was rebooted without proper shutdown by watchdog timer".

This is causing some serious issues and some angry customers. I really need someone from mikrotik to respond asap.

I have started programming a spare RB600 to replace the one I have problems with but sitting here on the bench it is now rebooting at random with the same "router was rebooted without proper shutdown by watchdog timer" error.

Disabling the watchdog timer makes no difference, it still reboots and I still get the same error.

I've spent alot of money on mikrotik over the last few years and to be honest I'm getting fed up. I've sent messages to support and posted here on the forums but it seems impossible to get timely help. This isn't the first time I've been ignored but it might be the last.

join to the club...

I'm guessing, try to disabled the wireless cards and check for configuration of each one, sometimes it reboots because some card configuration problems, check the frequencies or re-configure the wireless

from 3.22 to 5.2 - it is like upgrading from Windows 3.11 to Windows 7 - with saving all the features. I would go for:
/system reset-configuration
/system routerboard upgrade
/system reboot

and then would start to configure my board from zero. What power supply are you using, sounds improbable, but anyway goot to check it.

from 3.22 to 5.2 - it is like upgrading from Windows 3.11 to Windows 7 - with saving all the features. I would go for:
/system reset-configuration
/system routerboard upgrade
/system reboot

and then would start to configure my board from zero. What power supply are you using, sounds improbable, but anyway goot to check it.

I thought about that, but when I started programming my spare RB600 and it started doing the same thing I dismissed that notion.
I've taken alot of time to search the forums and it seems as if this was a common problem with the RB600. While mikrotik admits there is an issue with some of the RB600's they don't state what it is. Not sure why they don't come out and say it.
I'm guessing this issue is why the board was discontinued so abrubtly. I personally think they should have some sort of trade in program for the people that got stuck with these faulty boards. It's frustrating to say the least.

R52H?..

Normis, I responded to your email with what you asked for but I still have yet to hear back from you.

The safer way to upgrade to 5.x is first from 3.x to 4.17.

Then from 4.17 all my devices went ok to v5.

I had some trouble going from v3 and < 4.16 to v5.

Best regards,

The safer way to upgrade to 5.x is first from 3.x to 4.17.

Then from 4.17 all my devices went ok to v5.

I had some trouble going from v3 and < 4.16 to v5.

Best regards,

Did you see the very first line of my very first post of this thread.

I have a RB600 that was running ROS 3.22 that I decided to update. I first installed ROS 4.17, then ROS 5.2.

Normis, I responded to your email with what you asked for but I still have yet to hear back from you.

Still waiting

Ticket#2011050666000569

from 3.22 to 5.2 - it is like upgrading from Windows 3.11 to Windows 7 - with saving all the features. I would go for:
/system reset-configuration
/system routerboard upgrade
/system reboot

and then would start to configure my board from zero. What power supply are you using, sounds improbable, but anyway goot to check it.

Just kidding? I start using debian 16 years ago and i have _desktop_ computer that 15 years old (only the system, not the hw and countinous upgraded to new releases now squeeze). In the last year i replace architecture from 32bit to amd64. This is possible. And, the hw not changed under this distribution(MT).
Eh.
And remind: this is _supported_ (upgrading).
And also: if you have 1200 device on your network you make personal assinstance every device if need to upgrade?

This is ridiculous, it's been nearly a month since I first posted.

This is ridiculous, it's been nearly a month since I first posted.

yes, and it's nearly a month since you replied to this topic, or to the ticket 2011050666000569

Support asked a question, but you didn't respond. Your last email to support was on May 19. Use netinstall to reinstall RouterOS to v5.4 and send us update on progress of the problem.

May 6th
May 13th
May 24th
May 25th
May 26th
May 28th
June 2nd

Above are the dates I have posted to this thread, not sure how you can say I haven't posted to this thread for a month?

Also I sent an email to support shortly after starting this thread with a supout file attached and I didn't get a response until May 14th. In that response you asked that I upgrade to 5.2 and send a supout file to support. I responded on May 19th and I sent that supout file as requested. I have yet to get a reply from support.

Now you say support asked me a question but I didn't respond? I'm confused, what was the question that I didn't respond to, feel free to post it here.

Now you want me to jump through more hoops and upgrade to 5.4.
Are there fixes for the issue in 5.4. What did supout file I already sent you show as the problem.

I haven't gotten any assistance on this issue and I have done everything you have asked. You just keep telling me to upgrade.

what new information did you give us in these posts:

This is a community forum, you need to write to support to get support.

the last email to you from support is the following:

Hello,

the file shows you are still running RouterOS v5.2

Please use Netinstall to upgrade to v5.2:
http://wiki.mikrotik.com/wiki/Manual:Netinstall

Netinstall will also make sure to fix any file system problems.

You did not send us the correct file, and after we told you about it, you did not respond.

Since the 14th I haven't received a single response from support that's why I posted to the forums. Either way according to your posts it looks like I was running v5.2 like you asked and that what it was running when I created the supout file.

And can you answer my question. What did the supout file show as the problem and are there any fixes in 5.4 for problem identified?