RB's freezing on 4.16 upgrades

Hi folks

Just want to find out if any of you have been experiencing routerboards freezing when upgrading them to RouterOS 4.16? We have had 2 x RB493AH, 1 x RB450G and 1 x RB600A freeze after the upgrade.

To do the upgrade we run this script:

/system scheduler
add comment="" disabled=no interval=0s name=upgrade1 on-event="/system routerboard upgrade" policy=reboot,read,write,policy,test,password,sniff,sensitive start-date=feb/03/2011 \
    start-time=04:17:00
add comment="" disabled=no interval=0s name=reboot2 on-event="/system reboot" policy=reboot,read,write,policy,test,password,sniff,sensitive start-date=feb/03/2011 start-time=\
    04:20:00
add comment="" disabled=no interval=0s name=reboot1 on-event="/system reboot" policy=reboot,read,write,policy,test,password,sniff,sensitive start-date=feb/03/2011 start-time=\
    04:00:00
add comment="" disabled=no interval=0s name=remove1 on-event=remove1 policy=ftp,reboot,read,write,policy,test,winbox,password,sniff,sensitive start-date=feb/03/2011 start-time=\
    04:40:00
..
/system script
add name=remove1 policy=ftp,reboot,read,write,policy,test,winbox,password,sniff,sensitive source="/system scheduler remove reboot1\r\
    \n/system scheduler remove reboot2\r\
    \n/system scheduler remove upgrade1\r\
    \n/system scheduler remove remove1\r\
    \n/system script remove remove1"

From what we can tell, it does the RouterOS upgrade fine, but then it crashes/freezes on the firmware upgrade.

Any info would be appreciated.

+1.

We have same problems. You reboot the board directly from power supply and solved. Its a hard problem with remote RBs x(

But doesn’t the script hang waiting for someone to press “y” for the upgrade command?

Or does ROS, when running this command via a script automatically know to bypass the [y/n] prompt?

I had a 493AH hang up like this on a winbox Downgrade from 5.0rc9 to 4.16. I heard the router reboot but it didn’t respond to any network traffic. When I tok a look at it, every other switch light was on whether there was a physical link or an empty port. A manual power cycle fixed it.

RouterOS automatically bypasses the [y/n] prompt.
Its good(for me, bad for you) to hear that other people are also experiencing the same problem. I just wish MT would help in some way other than asking for a serial terminal cable to be plugged in during the outage.