Now this is interesting...
On the same RB411 device running RouterOS 3.30 with ar7100-2.23.fwf uploaded, I decided to issue the firmware update command but wait a while before rebooting. Here's what I did:
[admin@rb411] > /file print
# NAME TYPE SIZE CREATION-TIME
0 ar7100-2.23.fwf .fwf file 40136 jan/14/2010 11:43:52
1 ABC1-XYZ.key .key file 203 dec/31/2009 16:14:52
[admin@rb411] > /system routerboard print
routerboard: yes
model: "411"
serial-number: "1234567890AB"
current-firmware: "2.20"
upgrade-firmware: "2.23"
[admin@rb411] > /system routerboard upgrade
Do you really want to upgrade firmware? [y/n]
y
firmware upgraded successfully, please reboot for changes to take effect!
[admin@rb411] > /system routerboard print
routerboard: yes
model: "411"
serial-number: "1234567890AB"
current-firmware: "2.23"
upgrade-firmware: "2.23"
[admin@rb411] >
I then kept my session open, did NOT reboot the device, but just waited for 3 to 3 1/2 minutes, then did this:
[admin@rb411] > /system routerboard print
routerboard: yes
model: "411"
serial-number: "1234567890AB"
current-firmware: "2.20"
upgrade-firmware: "2.23"
[admin@rb411] >
I tried it again, issuing the upgrade command, then doing
/system routerboard print repeatedly afterward. For the first 3 min. or so, the print output always showed
current-firmware: "2.23", but around 3 to 3 1/2 minutes later, suddenly and without warning, the
current-firmware reverted to
"2.20" again.
Could this be related to whatever the problem is that's causing the firmware update to fail on reboot too?
Puzzled,
Aaron out.