Kernel update fails with "Invalid hash given"

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Kernel update fails with "Invalid hash given"

This topic contains 6 replies, has 2 voices, and was last updated by  Heiner Moderator 10 months, 3 weeks ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • 12. November 2017 at 16:58 #32432

    Current kernel is:

    #### KERNEL ####
    Linux PiServer 4.4.20-v7+ #908 SMP Wed Sep 7 14:44:27 BST 2016 armv7l GNU/Linux

    Update using Max2Play Raspberry Pi settings page fails:

    Kernel Update started
    Installation started - This Messages refreshes every 3 seconds to show current installation status. When finished this message disappears.
    2017-11-12 14:39:38|
    *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
    *** Performing self-update
    *** Relaunching after update
    *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
    *** Invalid hash given
    Finished - Reboot needed! Click here to Reboot Now
    
    Custom parameter Kernel removed
    UPDATE ENDED - CHECK ABOVE LOG FOR ERRORS

    Any ideas? Or should I just not bother to update?

    14. November 2017 at 11:10 #32472

    Hi TJH,

    Please try updating the Max2Play system first. Then, try updating the Kernel again.

    14. November 2017 at 14:45 #32481

    I did update Max2Play first and also the non-kernel update but the kernel update still fails with the invalid hash message and the kernel stays at 4.4.20 😞

    14. November 2017 at 17:22 #32487

    Hi TJH,

    What image did you start with? If you did not configure a lot, you could burn a fresh 2.44 image which should have Kernel 4.4.41-v7+ from the start.

    14. November 2017 at 20:23 #32489

    Lots of configs of course! Squeezebox, Spotify, NAS, etc etc.

    Can I back up all the settings at once then restore them after a clean reinstall?

    20. November 2017 at 16:51 #32551

    Did a clean install of the latest Max2Play image and all now updates OK.

    3 RPis, 3 installs = a whole day reconfiguring (Server Pi2 with HiFiberry Dac+ phone, Zero player with HiFiberry Digi, Pi3 with screen as controller, plus Squezebox and SB Radio). A way of preserving and passing on things like player/server name, fixed IP address, WIFi login, Squeezebox login and plugins details, Spotify login etc etc would save a lot of time. Is there any way Max2Play could ask about these during installation and load them up? (As if you haven’t enough to do already!)

    Thanks for a great system keeping home streaming alive and affordable (ie for those of us not in the Sonos league).

    24. November 2017 at 16:22 #32619

    Hi TJH,

    Sorry about the late response. Your previous reply must have gotten lost during my brief vacation.

    Currently we mainly recommend making a back-up file with the simple image burner premium plugin for Max2Play. We originally built it to quickly burn new SD cards with fresh images, but we also included a button to save your current install of Max2Play as an .img. This way, you can either save it to a USB storage, a SambaShare, your existing SD or just burn a fresh one with a back-up.

    There are also a few buttons to save or restore settings for things like the Squeezebox Server, but backing up is your safest bet for now 😉

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.

Register here