bzimage checksum error

[spalmisano]

I set up a second unRAID server recently and today shut it down to add an SSD as a cache drive. On restart I get to the unRAID boot screen, get through /bzroot...ok and then end up (eventually) at an error message reading that bzimage fails its checksum and to press any key to restart. There are several pages of messages leading up to that, but the scroll is too fast to parse anything.

 

I installed originally as 6.9.2 and then updated to the latest release candidate.

 

Ive tried to boot from the USB stick in multiple ports on that server with the same issue, and its completely readable from another computer. Ive copied its contents off just in case. There doesn't seem to be a log or other diagnostic information on the boot USB.

 

If the bzroot executable was corrupted somehow can I simply unpack one from the RC build and copy that over? 

 

Any ideas are welcomed, and let me know what diagnostic info I can provide.

This server isn't doing anything critical yet, but I do want it back in action.

 

Thanks.

Edited February 3, 2022 by spalmisano

[ChatNoir]

10 hours ago, spalmisano said:

can I simply unpack one from the RC build and copy that over? 

Yes.

 

You can find the direct link there : https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6100-rc2-available-r1565/?do=findComment&comment=16648

[spalmisano]

I was able to find a link to the zip and extract over the existing files, with the same result.

The same checksum failure also occurred when creating a fresh install of the RC using the Windows USB creator and a new USB stick.

 

I created another fresh install with the stable branch and it seems to be working now. I was able to transfer my license key to the new stick, and most of the Docker/VM configs were still present on boot. It rebooted successfully without intervention a few times with the new stick and stable build, so Im keeping it there instead of moving to the RC for now.

 

If details about the hardware or other diagnostic information would be helpful for diagnosing a potential RC issue, let me know and I’ll collect whatever is needed.

 

Marking as solved.

[Squid]

did you also copy over the md5 files?

[spalmisano]

I did, and also tried creating an RC install on the new stick, and then copying over the delta files from the old stick. Each time resulted in the same checksum error. Im guessing there was something incorrect or incomplete with how I was hacking at things.

[dunklesToast]

Having the same issue after upgrading to 6.10.0-rc2. Server won't boot due to a checksum error. Pulled the USB out of the Server and calculated the checksums myself. Can't find any issues so I wonder why this is happening on while booting the server.

[ChatNoir]

29 minutes ago, dunklesToast said:

Having the same issue after upgrading to 6.10.0-rc2. Server won't boot due to a checksum error. Pulled the USB out of the Server and calculated the checksums myself. Can't find any issues so I wonder why this is happening on while booting the server.

Did you check your memory is OK ?

Did you try from another USB port (USB2 ideally) ?

[dunklesToast]

Haven't checked it on another USB Port honestly. The Port I've used is a USB 2.0 Port. For now I've reverted to 6.9.2 which works.

[spalmisano]

7 minutes ago, dunklesToast said:

Haven't checked it on another USB Port honestly. The Port I've used is a USB 2.0 Port. For now I've reverted to 6.9.2 which works.

I tried each of the ports on my r710 and had the same checksum error. Only when I moved back to 6.9.2 did it start working.

[dunklesToast]

Yea I also use a R710. Interestingly, the update worked well for a friend of mine, @Noim who should have the identical Hardware I have.

[spalmisano]

12 minutes ago, dunklesToast said:

Yea I also use a R710. Interestingly, the update worked well for a friend of mine, @Noim who should have the identical Hardware I have.

 

Mod/Dev team: Sounds like there are several of us with similar gear and experiences with the RC. If you want us to supply anything diagnostic or try something that will help diagnose, let us know.

[JamesDaMan]

 

Yes having the same problem......  Hope they get it fixed in RC3.    If anyone get it fixed running RC2+ please report back, thanks!

[willum0330]

Same issue. I tried to update from 6.9.2 using web gui to 6.10.0 RC3 and at first got a boot failure. Took USB out and using the UnRaid USB creator tool, created a new USB and then copied over the customizations. Now I have the bzroot checksum error. I have a T610 , that will work fine on 6.9.2… but was really wanting to try ARM emulation… the reason for updating… I have 64Gb of Ram, and mem test passes fine. 

Edited March 15, 2022 by willum0330

[willum0330]

I have isolated the problem to be something with the hardware virtualization that is used by UNRAID to support VMs. I started by resetting my BIOS on my T610, created a fresh USB install and booted 6.10.0 RC3 and it booted successively. I then copied over all my configurations, plugins, etc. and booted again - again, it booted successfully. I went through to see if everything was working. I noticed that my VM's hadn't come online. At the top of the web-gui, it indicated that the hardware did not support KVM. I figured at this point that the resetting of the BIOS must have disabled the virtualization options. I went in the BIOS and enabled the virtualization technology on the processor and rebooted. The UNRAID boot splash came up and continued to boot normally until it hits the bzroot checksum failed. This is the ONLY change I made, so it must be related to the enablement of the virtualization technology in the BIOS. Now what???

[antpk]

On 3/15/2022 at 11:58 PM, willum0330 said:

I have isolated the problem to be something with the hardware virtualization

I think you are onto something here. I was having the same problem when i needed to replace my usb. I turned off virtualization support and was able to boot.

 

I went further, the kernel panic was about iommu. So I tried adding this to the boot args:

 

intel_iommu=on iommu=pt

 

I can now boot with virtualization on.

 

Hope this helps.

 

Edited March 19, 2022 by antpk
Adding screenshot of boot

[blaine07]

On 3/19/2022 at 1:40 PM, antpk said:

I think you are onto something here. I was having the same problem when i needed to replace my usb. I turned off virtualization support and was able to boot.

 

I went further, the kernel panic was about iommu. So I tried adding this to the boot args:

 

intel_iommu=on iommu=pt

 

I can now boot with virtualization on.

 

Hope this helps.

 

Thank you, all the thanks for this!

 

So, I had my 6.10rc4 stick in my T610 die. Made a new USB and ran into the issues discussed in thread. Above was fix. 
 

What are long term effects of adding these snippets to ARGS? They were not there before and everything was fine; prior to this USB stick dying.

Is this, above fix, going to have adverse effects or cause other issues moving forward?

[willum0330]

On 3/19/2022 at 2:40 PM, antpk said:

I think you are onto something here. I was having the same problem when i needed to replace my usb. I turned off virtualization support and was able to boot.

 

I went further, the kernel panic was about iommu. So I tried adding this to the boot args:

 

intel_iommu=on iommu=pt

 

I can now boot with virtualization on.

 

Hope this helps.

 

blaine07 - YOU GOT IT! Working for me as well - finally! Everything seems to be up and running and VM's came online without any complaint! Thanks for taking the time to look into this further

[Tommy10606]

On 3/19/2022 at 2:40 PM, antpk said:

I think you are onto something here. I was having the same problem when i needed to replace my usb. I turned off virtualization support and was able to boot.

 

I went further, the kernel panic was about iommu. So I tried adding this to the boot args:

 

intel_iommu=on iommu=pt

 

I can now boot with virtualization on.

 

Hope this helps.

 

 

This worked AMAZINGLY!!! Thank you so much! When booting, I had to wait for it to give me my boot options for GUI/CLI/SAFEMODE, and when I saw those, I moved down with my arrow keys so it would not boot automatically. I then hovered over what I wanted to boot and hit tab. This allowed me to add the 2 arguments that you had. After wards, it booted perfectly!

[casualsix]

Worked for my R710 also. thanks, 

[Zeroeth]

Thankyou very much for sharing this! It worked perfectly 🙂

 

I just upgraded my R710 server from 6.9.2 to 6.10.0-rc5 and ran into this exact same issue. Server wouldn't boot due to a checksum error.

 

 

Added the 2 arguments:

intel_iommu=on iommu=pt

 

on the boot option by pressing tab to edit the options and the Server is up again!

 

 

 

 

[JamesDaMan]

Fixed my r510 with 128GB of ram!!!

 

 

Thanks SO!!!!! Much!

[wil56k]

On 4/29/2022 at 7:16 AM, Zeroeth said:

Thankyou very much for sharing this! It worked perfectly 🙂

 

I just upgraded my R710 server from 6.9.2 to 6.10.0-rc5 and ran into this exact same issue. Server wouldn't boot due to a checksum error.

 

 

Added the 2 arguments:

intel_iommu=on iommu=pt

 

on the boot option by pressing tab to edit the options and the Server is up again!

 

 

This fixed my issue on R710 with 32GB (6.10rc4)

On 4/29/2022 at 7:16 AM, Zeroeth said:

 

 

Edited May 2, 2022 by wil56k
add unraid version

[blaine07]

I wish I understood exactly what was going on here and if adding these ARGS is going to cause more issues later.

[ajtish]

Been having these same errors on my Dell R510 ever since upgrading to the 6.10 RCs a few weeks ago. I could sometimes get the system to boot and kept hoping that one of the releases would clear the issue up. I ordered a replacement flash drive thinking my drive was starting to go bad as one of the times I performed a chkdsk on the flash drive from my Windows PC and the server booted properly. This trick got the server to boot without any meddling!

 

My server is a Dell R510 BIOS v1.14.0

Edited May 7, 2022 by ajtish

[kreene1987]

I am having this issue on 6.10 stable on my R510.

 

edit: fixed extra space in first try and now I am up and running... phew!

Edited May 18, 2022 by kreene1987