-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0.1b4 to 2.0.1b6 failure to update #181
Comments
That's odd. |
Interestingly enough, after 3rd attempt it went through. |
Same issue again going from 2.0.1 to 2.0.2. Emailing you the link to the log. |
Well, my guess is undervoltage or bad SD card:
Trying to run |
That is strange because the last time this was happening, it was on a RPi3b w/8GB generic card and now it's the RPi5 w/64GB good quality card. I just recently upgraded my setup and actually ended up setting it up from scratch instead of restoring any back ups to avoid any possible conflicts. What else could be causing this? |
System -> Support info Suppose it's possible that it's a pi5 issue but when you wrote your previous post we've had to assume pi3 :) |
If you try the update again, does it show the same error in the logs? You could also try to ssh into the box, then do
Then try the update again. |
The initial post issue was on RPi3b, this is the same issue but now on RPi5 with a fresh install.
|
Just ran the update again, same result, hangs on the "restarting" page for about 10 secs and refreshes back to the 2.0.1 screen. I'll try to reinstall git |
Confirming that reinstalling git did solve the issue. Successfully updated to 2.0.2 after. |
How you would end up with a git binary that crashes is... rather strange to me. But I'm glad we at least have a workaround identified. |
Yea, not sure. It was a vanilla install too, didn't even generate an ssh pass for it yet because I was away. I tried to update to 2.0.2 when it came out and it didn't take, so I figured I'll wait until I get back from vacation to mess with it. Same result when I got back yesterday. |
The more I hear about this, the more I think it's a defective SD card |
Current:v2.0.1-beta.4(beta)
Board:Raspberry Pi 3 Model B Rev 1.2
Base:adsb-im-raspberrypi64-v1.0.0.img
Kernel:Linux adsb-feeder 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
Containers:
ghcr.io/sdr-enthusiasts/docker-adsb-ultrafeeder:latest-build-346
ghcr.io/sdr-enthusiasts/docker-flightradar24:latest-build-653
ghcr.io/sdr-enthusiasts/docker-piaware:latest-build-474
ghcr.io/sdr-enthusiasts/docker-radarbox:latest-build-629
SDR(s):
SDR(type: 'rtlsdr' address: '001:005', serial: '978')
SDR(type: 'rtlsdr' address: '001:006', serial: '1090')
Ultrafeeder args:
Env variables:
Memory:
total used free shared buff/cache available
Mem: 909Mi 508Mi 38Mi 80Mi 361Mi 256Mi
Swap: 99Mi 95Mi 4.0Mi
Storage:
Filesystem Size Used Avail Use% Mounted on
/dev/root 7.1G 4.5G 2.3G 67% /
devtmpfs 325M 0 325M 0% /dev
tmpfs 455M 0 455M 0% /dev/shm
tmpfs 182M 59M 124M 33% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mmcblk0p1 255M 32M 224M 13% /boot
When pressing the update (beta) button to update to beta 6, the typical screen comes up saying to stand by as it’s updating. After about 30 seconds, the page refreshes back to the main screen and the version is still beta 4.
The text was updated successfully, but these errors were encountered: