Hi,

I managed to brick a couple of my new RBMetal5SHPn units today, and need help resurrecting them. Out of the box, they've got v5.26 on them, so I attempted to bring them up to 6.29.1. I copied the packages (from all_packages_mipsbe-6.29.1.zip) over to it, and did "system routerboard upgrade", then "system reboot". I figured it was something to do with RouterBoot, then realised I wasn't actually copying the .fwf file over too.

If I actually copy the .fwf file over, the upgrade works fine of course. So yeah, I've stupidly run "system routerboard upgrade" without actually giving it a firmware file to work from. Strangely, the terminal responded saying the upgrade was successful, so I went ahead with the reboot as normal.. and now it (and 2 others) are bricked.

I've tried using netinstall to go recover (have tried netinstall/ROS from both 6.29.1, and 5.26). The NetInstall bit seems to work, but the unit just won't come back afterwards.

Any ideas?

This is not likely the cause, just a coincidence. You don't have to ever upload FWF files to upgrade RouterBOOT, because the latest FWF file is automatically included in the RouterBOARD.npk package that you use.

After you netinstall them, check if the wireless SSID is visible, maybe they are available from wireless side.

This is not likely the cause, just a coincidence. You don't have to ever upload FWF files to upgrade RouterBOOT, because the latest FWF file is automatically included in the RouterBOARD.npk package that you use.

After you netinstall them, check if the wireless SSID is visible, maybe they are available from wireless side.

I've had a similar issue on Metal2's and Metal9's after a config reset via the button. More often than not, the device comes back up without it's default config. I've had to mac-telnet in and manually set the ip address.

This is not likely the cause, just a coincidence. You don't have to ever upload FWF files to upgrade RouterBOOT, because the latest FWF file is automatically included in the RouterBOARD.npk package that you use.

Ahh, thank you for clarifying this for me. I was wondering why I've never had to specifically deploy a FWF before. Not sure its just a coincidence though, I killed 3 (with witnesses!), and then tried upgrading the fwf file first (while still on v5.26), rebooting, then going to v6.x and it worked fine (multiple times).

After you netinstall them, check if the wireless SSID is visible, maybe they are available from wireless side.

Wireless isn't enabled on them yet (straight out of the box, was just upgrading rOS in preparation for capsmanv2. These units won't even give me the post beeps - even after netinstall.

I've had a similar issue on Metal2's and Metal9's after a config reset via the button. More often than not, the device comes back up without it's default config. I've had to mac-telnet in and manually set the ip address.

Sounds slightly different to this situation, I can't mac-telnet to the affected firewalls - they don't POST correctly (no beeps) the APs appear to be dead, and don't even show up in a winbox browse.

update: resetting the config fixes the no-POST problem - thanks gtj, I'd always assumed the config was automatically blatted by netinstall, so hadn't considered a config reset.