The image file is corrupt



  • Hey,

    I'm kind of unable to update via GUI. I get following message:

    Link: http://screencast.com/t/z5Rfb0j9b1PV
    Link: http://screencast.com/t/zXWRVmlWV7C0

    Any ideas what to do?

    Cheers,
    Szop



  • I upgraded a 2GB nanobsd OK just now:
    Version 2.1-BETA1 (i386)
    built on Mon Jan 14 11:26:01 EST 2013
    FreeBSD 8.3-RELEASE-p5

    You are on the latest version.
    Platform nanobsd (2g)

    Maybe the build was in the process of putting the 4G image on the server at the time? Is it still happening?



  • Timing coincides with that file being uploaded into place, just caught it at the wrong time.



  • Bad Luck Szop  ;D

    Thanks for the replies,
    Szop



  • Interestingly, for the last 30 minutes at least (around 201301151100Z), my 2G nanoBSD system has been telling me there is an update available to Mon Jan 14 23:44:56 EST 2013. But when I select "Invoke Auto Upgrade" I get "The image file is corrupt" "Update cannot continue". So there seems to now be a significant time interval between when the build puts the little file on the server that tells it a new version is available, and the time that the various nanobsd snapshot files actually get there.
    If this is a regular feature of the build timing now, then it will confuse quite a few people. It would be better if the images can go up first, then the version files.
    (or maybe this build died part way through, and its a one-off problem)


  • Rebel Alliance Developer Netgate

    This is how it works now:

    • All of the image files are uploaded, update files are not touched yet.
    • Once the images are uploaded, ln is used to symlink the various update "latest-*" files to the ones just uploaded
    • After the images have been linked, then the version files are copied.

    If the version file shows an image as new, it really should be new at that point.

    In this case, it appears that something caused the upload to die and the file didn't actually make it to the snapshot server, so it linked to a file that doesn't exist. It'll fix itself on the next snapshot run.



  • Thanks JimP - working now. I noticed that the nanobsd_vga file links were not appearing, a couple of "-vga" that should be "_vga", IMHO. I made a pull request in pfsense-tools.



  • and now the latest nanoBSD VGA update images are appearing nicely in http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/.updaters/. All is well with the snapshot updating world.


Locked