May 22, 20224 yr Updating 6.9.2 -> 6.10.1 Updating from GUI proceeds as normal until the server starts booting again. Partway through the Unraid boot, the console outputs a message, "bzimage checksum failed. Press enter key to reboot." This issue occurred on two different Unraid instances I have on 6.9.2. I was able to temporarily resolve by copying over the BZxxxxx files from the 6.9.2 release available from unraid.net to the flash drive. After this each server boots into Unraid correctly again. Tried updating again and the same issue happened. I seem to be unable to complete the update. Is there a known cause of this problem? Is there a manual way to update since the web GUI method is failing for me?
May 22, 20224 yr 1 hour ago, Foxglove said: Is there a manual way to update You can manually copy the bz* files and changes.txt from the 6.10.1 zip file onto your flash drive.
May 22, 20224 yr Author I tried copying the files from 6.10.1 originally, but it resulted in the same error. Let me try it one more time. I didn't grab the changes.txt file last time. Thanks for the suggestion.
May 22, 20224 yr Solution If that still gives the error, read through this thread: https://forums.unraid.net/topic/119502-bzimage-checksum-error/ I don't understand it, but it has worked for several people
May 22, 20224 yr Author I attempted it again. Copied 11 files from 6.10.1 image (10 BZ* files plus changes.txt) and got the same error about bzimage checksum. I'll check out this other forum solution and report back.
May 22, 20224 yr Author 3 hours ago, ljm42 said: If that still gives the error, read through this thread: https://forums.unraid.net/topic/119502-bzimage-checksum-error/ I don't understand it, but it has worked for several people Can confirm, this fixed *both* servers! Thank you very much. Solution was to open syslinux/syslinux.cfg add "intel_iommu=on iommu=pt" to the "append" line. Screenshot below for any future users. Let me know if I can append my problem to any open issue or provide any useful debugging info.
May 31, 20224 yr This fix, done exactly as the OP (@Foxglove) did, DID NOT resolve the issue for me. I ended up using the recovery procedure here => https://wiki.unraid.net/Manual/Changing_The_Flash_Device#Using_the_Flash_Creator To rollback to a backup of 6.9.2 from earlier in the week. FWIW, the currently advertised update of 6.10.1 (As of 31MAY22) still does NOT have the added syslinux.cfg line noted in this and the other (https://forums.unraid.net/topic/119502-bzimage-checksum-error/) forum posting. I would highly suggest the update stop being advertised for normal customers until this is resolved (I only say this since this is a paid product and not FOSS). Edited May 31, 20224 yr by Misak accuracy
September 16, 20223 yr G'Day, I also discovered the error when upgrading from 6.9.2 to 6.10.3. I added the intel_iommu=on iommu=pt to the boot and this appeared to allow me to progress further. However once the system was started the VM's did not run. the Libvert log indicates: "2022-09-16 06:24:53.891+0000: 7926: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-09-16 06:39:54.882+0000: 7924: error : qemuAgentCheckError:990 : internal error: unable to execute QEMU agent command 'guest-network-get-interfaces': this feature or command is not currently supported" My CPU is a Ryzen 9 3900X so the intel reference in the boot line concerned me. So I also tried booting with simply the iommu=pt appended and this also allowed the system to boot. However with the same error. I'm unsure what further information to provide here. Other than to say it was working fine with 6.9.2 and now after the upgrade to 6.10.3 it is not. Any assistance (hints) would be greatly appreciated. Thanks Peter
September 16, 20223 yr Community Expert I added the intel_iommu=on iommu=pt This should not make any difference with v6.10.3 since it's already the default.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.