So it seems it lost the WiFi configuration and the hostname, but retained other state like the authorized keys and root password.
J
Posts made by Jason R. Coombs
-
RE: After Warp Core upgrade, device unreachableposted in Omega Talk
-
RE: After Warp Core upgrade, device unreachableposted in Omega Talk
So it's expected that one will have to factory reset after installing the upgrade? That's probably worth mentioning in the announcement and in the updater script.
-
After Warp Core upgrade, device unreachableposted in Omega Talk
Today I ran the upgrade. Here's what I saw in the output:
BusyBox v1.26.2 () built-in shell (ash) ____ _ ____ / __ \___ (_)__ ___ / __ \__ _ ___ ___ ____ _ / /_/ / _ \/ / _ \/ _ \ / /_/ / ' \/ -_) _ `/ _ `/ \____/_//_/_/\___/_//_/ \____/_/_/_/\__/\_, /\_,_/ W H A T W I L L Y O U I N V E N T ? /___/ ----------------------------------------------------- Ω-ware: 0.1.10 b160 ----------------------------------------------------- root@Koin:~# oupgrade --latest > Device Firmware Version: 0.1.10 b160 > Checking latest version online... > Repo Firmware Version: 0.2.0 b176 > Comparing version numbers > New firmware version available, need to upgrade device firmware > Downloading new firmware ... /usr/bin/oupgrade: local: line 377: not in a function --2018-03-28 15:45:02-- http://repo.onion.io/omega2/images/omega2p-v0.2.0-b176.bin Resolving repo.onion.io... 52.216.160.162 Connecting to repo.onion.io|52.216.160.162|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 7340207 (7.0M) [application/octet-stream] Saving to: '/tmp/omega2p-v0.2.0-b176.bin' /tmp/omega2p-v0.2.0-b176.bin 100%[=====================================================================================>] 7.00M 1.71MB/s in 4.1s 2018-03-28 15:45:06 (1.71 MB/s) - '/tmp/omega2p-v0.2.0-b176.bin' saved [7340207/7340207] > Starting firmware upgrade.... Saving config files... killall: watchdog: no process killed Sending TERM to remaining processes ... udhcpc udhcpc dnsmasq rpcd mountd ntpd oupgrade Terminated root@Koin:~# ubusd askfirst logd netifd odhcpd uhttpd device-client avahi-daemon onion-helper Sending KILL to remaining processes ... askfirst Switching to ramdisk... Performing system upgrade... Unlocking firmware ... Writing from <stdin> to firmware ... Appending jffs2 data from /tmp/sysupgrade.tgz to firmware.. Upgrade completed Rebooting system... umount: can't unmount /dev/pts: Resource busy umount: can't unmount /dev: Resource busyAfter waiting for the light to stop blinking and stay on solid, I tried to connect, but the device is no longer responding to mDNS requests. It seems to be disconnected from the network or has lost its name.
Is this experience expected? If so, a notice in the announcement would be nice.
Any other suggestions on what may have gone wrong? I don't have non-ascii characters in my WiFi SSID or password.