Can't change a CRS309-1G-8S+IN to SwOS

As this device boots very slow into RouterOS and I do not need any feature beyond switching I would like to run the devise with SwOS.

But unfortunately I am too stupid to flip the boot switch:

[admin@MikroTik] > /system/routerboard/settings/set boot-os=swos 
failure: not allowed by device-mode

SwOS is updates to 2.17 and RouterOS is 7.17.1

See here, same problem:
http://forum.mikrotik.com/t/cannot-change-boot-mode-to-swos/181666/1

Hello,
I changed the boot settings in RouterOS ( version: 7.18.2 ) using the command-line (/system routerboard settings set boot-os=swos) and reboot (/system reboot).
After rebooting, the device failed to boot properly. I was only able to recover it by performing a hardware reset (holding the reset button during power-up until the USER LED started blinking).

Thank you in advance for your help and support.

Did you also change using device mode setting for routerboard to yes ??
I assume you did but since you did not mention it, I’m just checking.

Logically it should have been changed before you can do other routerboard changes.

Subject: CRS309-1G-8S+ SwOS boot issue resolved after RouterOS 7.19beta7 firmware update.

Hello,
I’d like to report a successful resolution regarding the SwOS boot issue on my CRS309-1G-8S+IN, and share observations that may help clarify its behavior.

Summary:

While running RouterOS 7.18.2 (stable), I attempted to switch to SwOS using the following CLI commands:

 /system routerboard settings set boot-os=swos



failure: not allowed by device-mode

To enable the SwOS/RouterOS transition for dual-boot starting from RouterOS version 7.17, you need use the following command:

 
 /system device-mode update routerboard=yes



update: turn off power or reboot by pressing reset or mode button in 4m38s to activate changes
– [Q quit|D dump|C-z pause]

Turn off power, turn on again then type the following command:


 /system routerboard settings set boot-os=swos 



 /system reboot 



Reboot, yes? [y/N]:
y
system will reboot shortly

However, the device did not boot into SwOS. It became unresponsive, with no web interface, no serial console output and no boot beeps. The only way to bring the CRS309-1G-8S+IN back online was to perform a manual hardware reset (holding the reset button for ~5 seconds until the USER LED started blinking), which brought the device back into RouterOS 7.18.2.

Resolution:

I upgraded the device to RouterOS 7.19beta7, and also performed a RouterBOARD 7.19beta7 firmware upgrade.

After this, I attempted the same SwOS switch procedure again:

/system routerboard settings set boot-os=swos
/system reboot

This time, the device successfully booted into SwOS 2.17p, without requiring any reset. I then completed a regular upgrade to SwOS 2.17 via the web interface.

Following this, I downgraded back to RouterOS 7.18.2 and RouterBOARD firmware 7.18.2 , and confirmed that:

  • SwOS 2.17 continues to work


  • The SwOS image remains present

I can now switch freely between RouterOS and SwOS using:

/system routerboard settings set boot-os=swos
/system reboot

This switching was not possible prior to the firmware upgrade done under RouterBOARD firmware 7.19beta7. (SwOS image is embedded within the RouterBOARD firmware)


Additional Note:

SwOS does not emit an audible beep during boot, unlike RouterOS. This lack of confirmation led to initial confusion, as I assumed the boot had failed when it was actually successful.


Thanks again for your help and support.

Works for me, thank you littleredfox.

If you use the following command

/system/device-mode/update routerboard=yes

You will then have 4:59 seconds to reboot and you can now use SwitchOS change your bootOS through Winbox.

I am having similar problems with a CRS-317-1G-16S+; however, using littleredfox’s procedure isn’t working for me. I have updated to the latest development build available (7.19rc2 and rc3 both don’t work), but when I tell it to reboot into SwOS it just hangs. I need to get a USB-C-to-Serial adapter so I can check the console but I suspect it’s the same thing.