Firmware upgrade problem

Michael Vowles

Hi All,

Tried to upgrade my firmware using oupgrade, it successfully downloaded but upon starting the upgrade it gets stuck on
killall: watchdog: no process killed
Sending TERM to remaining processes ...

Any help would be greatly appreciated.

Boken Lin

@Michael-Vowles There shouldn't be a problem with that. It just takes a while for the firmware to be flashed and for the device to reboot. I'm hoping that you didn't disconnect the Omega when it's updating... otherwise you might have bricked it...

Lazar Demin

@Michael-Vowles Judging by the messages you posted it seems like you ran oupgrade on the terminal when connected via ssh or the terminal on the console?

The Omega shuts down all of the networking functionality in order to flash the new firmware, so it would close down your SSH connection/Console session, and then perform a reboot.

Once it reboots (the amber LED on the Omega will stop flashing and remain on), the update should be complete.

Kit Bishop

@Michael-Vowles I had similar experience to you but can basically confirm what @Lazar-Demin said. I too was connected via an SSH session (from PuTTY)

It takes a while to do the upgrade
The process shuts down the SSH connection during the upgrade
Should definitely NOT disconnect/depower Omega until upgrade completes
When upgrade is complete, reconnect to Omega - all should be OK

Kit Bishop

I did have one small issue from the upgrade.
I keep a USB memory stick connected to my Omega. It appears at /dev/sda1
So, I always have access to it, I have done the following:

Created a directory: /usb
Added the following line to my profile file: mount /dev/sda1 /usb
This way my usb is always available when I restart the Omega.

However, the oupgrade process removed my /usb directory.
Not a big issue - I just recreated the directory.

However, it does lead to the question(s):
Why was the directory deleted? And is there a better recommended place to create directories that you want to stay around over an upgrade?

Lazar Demin

@Kit-Bishop the current firmware upgrade process will erase everything outside of the /etc directory. Even some of the files in /etc might get overwritten if the firmware needs to update it.

Currently, there's no safe place to keep directories that you want to persist between upgrades. I thought that /root might be good but users have reported that it gets overwritten as well...

We're working on a way to have an option to choose between a full wipe and just an upgrade but we're still a ways away from releasing that. Wanted to let you guys know that it's on our docket tho!

Kit Bishop

@Lazar-Demin All good, thanks. Useful to know. That will stop me putting anything I want to keep permanently on the system, I'll just put it on the USB instead and then if needed be will recreate the mount directory after an upgrade. Not a major issue nor an onerous task

By the way, a general THANKS to you and all the other Omega staff who respond quickly and helpfully to all the various questions/issues.

Lazar Demin

@Kit-Bishop You're welcome !

We're all super excited to see people actively using the Omega, we wanna help in any way we can!

Michael Vowles

Thanks for the replies guys after more playing around it looks like it updated correctly.

Eric

Hi,
My Omega was working fine but I thought that I should make sure I have the latest version so I did an update with the command line oupgrade but since it was on version xxx.215 (sorry I cant access anymore) it was recommending to used oupgrade -force to get the latest version.

Similar to @Michael-Vowles, I got the same output:
killall: watchdog: no process killed
Sending TERM to remaining processes ... {process appear here}

So I wait 30 minutes at least to make sure it complete his update but since them I can't connect anymore. So I did a reset button. The led went off, start blinking very fast for a few second, moderate for another few seconds and steady. Also try the power off/on but didn't work.

Since than I cant connect anymore. Did a few things to troubleshoot:

Check for a WIFI OMEGA-xxxxxx in case it have done a factory reset. (No).
Check my router/dhcp for any particular IP address it may have change.
Run a Network IP Scanner (still nothing).

Unfortunately, I only received 1 OMEGA with a mini dock. So I'm stock presently waiting for 2 others Omega to arrive with the docs.

Is there a factory sequence button I can try?

Any help would be greatly appreciated.
Thanks,

Eric

UPDATE: I was able to used the serial connection to regain access to the Omega. At first sight the firmware b219 installed correctly but the WIFI configuration was gone. I did the reconfiguration with wifisetup.

root@Omega-1874:/# wifisetup
Onion Omega Wifi Setup

Select from the following:
1) Scan for Wifi networks
2) Type network info
q) Exit

Selection: 1
Scanning for wifi networks...
Command failed: Not found
Failed to parse message data
WARNING: Variable 'results' does not exist or is not an array/object

ERROR: no networks detected... try again in a little while

???

Eric

UPDATE 2:

Look like my wireless interface WLAN0 is gone. Even after a reboot and power off.

=======================================================
BusyBox v1.23.2 (2015-11-15 19:35:31 UTC) built-in shell (ash)
   ____       _             ____
  / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
 / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 W H A T  W I L L  Y O U  I N V E N T ? /___/

   Ω-ware: 0.0.4 b219

root@Omega-1874:/# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 40:A3:6B:C1:18:74
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B )  TX bytes:0 (0.0 B )
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:192 errors:0 dropped:0 overruns:0 frame:0
          TX packets:192 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13056 (12.7 KiB)  TX bytes:13056 (12.7 KiB)

root@Omega-1874:/#

Boken Lin

Hi @Eric-Phenix, can you send me the out put of cat /etc/config/wireless? Thanks.

Eric

@Boken-Lin I was able to manage to do a Factory reset via the console (which is awesome btw) and this time the interface show up. If it crash again I send the file minus my personal info. So I'm good for now.

Thanks!

Ivan Lim

Hi All,

How long will this process take...typically? This has been my second attempt. The last attempt, i waited for about an hour before i power cycled it and now it appears to be doing the same thing.

Appreciate some help here.

Thanks All

Lazar Demin

@Ivan-Lim typically, after the firmware has been downloaded, it will take about 5min to flash the new image.

Your screenshot above is the expected output. What happened when you rebooted the Omega?

Ivan Lim

@Lazar-Demin Well after waiting overnight, i unplugged it and restarted it today. Looking at the terminal, it appears that the update didnt happen. Did i miss a step?

Lazar Demin

@Ivan-Lim can you try connecting via serial and then running oupgrade on the command line?

Paul Sheldon

So today I decided to update both of my Omega's

First one went well and did a complete major update / reboot cycle / minor update / reboot cycle before allowing login to console to check everything was fine

Second one started the major update then the putty session started reporting ;'wrong values' scrolling down the page and then what looked like a reboot, putty shut down omega left on, now I can connect to com port but get no display.

Ideas please?

Boken Lin

Hi @Paul-Sheldon, can you show us a screenshot of the error message or copy and paste the output on your PuTTY screen here? That's not what it's supposed to do, and let's see if we can figure out what the problem is.

Paul Sheldon

Hi, apologies for delay in posting reply. I get the following in PuTTY

upload-1e048184-47cd-463f-be84-6b2ae5794ef4