KiwiSDR fails to update from 1.390 to current 1.442 [bad filesystem, fixed]

Haven't had the KiwiSDR in service for sometime. Reconnected everything and noticed that the version remains at 1.390 for a few days now. The web admin interface reports v1.442 is available and I expected an auto-update to occur, but to no avail. I just tried force software build selection and when I looked at the log I found the following, any help would be appreciated.

KiwiSDR server log

Tue Mar 16 17:28:26 00:02:52.495 ....   UPDATE: checking for updates

Tue Mar 16 17:28:27 00:02:53.505 ....   UPDATE: version changed (current 1.390, new 1.442), but check only

Tue Mar 16 17:28:27 00:02:53.508 ....   task update_task:P3:T003(-) exited by returning

Tue Mar 16 17:28:30 00:02:56.774 ....   UPDATE: force build by admin

Tue Mar 16 17:28:30 00:02:56.778 ....   UPDATE: checking for updates

Tue Mar 16 17:28:31 00:02:57.789 ....   UPDATE: version changed (forced), current 1.390, new 1.442

Tue Mar 16 17:28:31 00:02:57.793 ....   UPDATE: building new version..

Tue Mar 16 17:28:31 00:02:57.796 ....   rx_server_user_kick rx=-1

Tue Mar 16 17:28:38 00:03:04.809 ....   UPDATE: build error, check /root/build.log file, status=0x00008000 WIFEXITED=1 WEXITSTATUS=128

Tue Mar 16 17:28:38 00:03:04.809 ....   task update_task:P3:T003(-) exited by returning


The /root/build.log file reports

======== checking for update

Tue Mar 16 17:28:30 UTC 2021

======== building

Tue Mar 16 17:28:36 UTC 2021

Removing Makefile.1

error: inflate: data stream error (incorrect data check)

error: failed to read delta base object aaccb048afb50732e540a9441301df09367e6595 at offset 3362672 from .git/objects/pack/pack-dc29286ae34f34254eadae9bdc8e8d5b12d17a13$

error: failed to read object 4b6532961990483bd18f8cd74e4ff28dc08c40d8 at offset 5153008 from .git/objects/pack/pack-dc29286ae34f34254eadae9bdc8e8d5b12d17a13.pack

fatal: packed object 4b6532961990483bd18f8cd74e4ff28dc08c40d8 (stored in .git/objects/pack/pack-dc29286ae34f34254eadae9bdc8e8d5b12d17a13.pack) is corrupt

Comments

  • Almost certainly a trashed filesystem. I can fix it, but can't connect at the moment. Can you get it back online?

  • Thanks jks


    I have it back online, however not registered with any of the public sites currently. Let me know what you need maybe via DM.

  • I'm trying to rebuild, but the compiler is crashing multiple times during the rebuild (while compiling some of the more complex source code). This is extremely bad. When I rerun the build it eventually gets further on. So it's probably not damaged compiler files.

    Any chance this Kiwi is running hot?

  • Nothing hot to the touch. Is there a thermocouple anywhere onboard that reports and can be accessed?

    thanks again for you help.

  • I looked for a V1.442 image to download to put it on an sdcard to reimage the kiwi but I wasn't able to locate one. Do you think this would possibly work?

  • It's a huge headache to construct sd card images of the current release. So I don't do it often. v1.390 was the last. We all depend on the autoupdate over the network.

    The build is progressing now, but very slowly. Something seems to be taking a lot of cache space in main memory. I don't understand why. There are no processes that seem out of place.

    wxbeaz
  • I guess it is best if I don't muck around on the admin interface while you are watching the build?

  • Okay, it running v1.442 now. The build ran without problems. Including at the very end where a lot of memory is needed to construct the final files. Super slow though. I don't get it. Let's see how it does from here.

  • Much appreciated!

    I need to take it offline to do some home network reconfiguration.

    Do you have a feeling this is going to be a reoccurring issue with new updates for my kiwi?

  • jksjks
    edited March 16

    Let's wait and see. If so, we should just reinstall the entire system from an sd image and update.

  • So it automatically updated to v1.443 and took the usual amount of time to build. So I think we can call this one good for now.

  • Great news, thanks again for your help!

Sign In or Register to comment.