Just a friendly warning/reminder to anyone looking to upgrade ROS on production equipment. Try it on a test RB in your shop/lab first! Just tried upgrading v2.9.46 to v3.0 to try to correct a problem with a script…it rendered the RB unbootable and I had to climb the tower, retrieve it and completely reload everything via netinstall.
If you can’t get to your RB with a serial cable to diagnose it via console, don’t upgrade without trying it on non-critical equipment.
I realized there could be configuration issues or changes that need to be made, but I didn’t realize a non-booting RB due to upgrade was a possibility. Is there any official documentation/acknowledgment from MT about problems like this?
Gurus, if you’ve had a problem like this, post a quick line here with the original ROS version, what version you attempted to upgrade to, what happened and what you did to fix it. Maybe we can save the next guy some time and frustration…
It has been posted many many times. You need to upgrade to 2.9.51 Before upgrading to version 3.x. If you were really trying to upgrade to 3.0 then shame on you. That version is obsolete.
I’m only trying to provide some useful information to those who may not know. I’ve used this forum for reference for years and never seen anything about upgrade issues to the degree I experienced them until after the fact when I was looking for a solution. Probably a lot more equipment out there running on old software like that than anyone realizes. As this can render your operation “dead in the water”, I didn’t figure a little reminder and a little bit of personal experience was out of line.
Anyone else have any useful information about this problem (personal experience, how to avoid it, etc.)?
