February 17Feb 17 Community Expert On 10/17/2022 at 1:25 PM, ChatNoir said: You should remplace all the bz* files on your flash drives with one pulled from the release you are using. You can get the files in the zip here : https://unraid.net/downloadTHIS!!!! I just had the same issue with the bzfirmware checksum error.I installed the UNRAID USB Creator tool.Open the UNRAID USB Creator program.Selected the same Unraid version that I was using previously on my server.Used a NEW USB 2.0 flash drive on a USB 2.0 port "Black".Wrote the Unraid OS to the NEW flash drive.Copied the "Old" bz* & changes txt files on previously used USB flash drive to a backup location on my windows system labeled "OLD". Copied the 'New" bz* & changes txt files on the newly created USB flash drive to a backup location on my windows system.Deleted the "Old" bz* & changes txt files on previously used USB flash drive.Wrote the "New" bz* & changes txt files to the previously used USB flash drive, keeping all other files. Unmounted the USB flash drive. Plugged previously used USB flash drive, with the "New" bz* & changes txt files, into "Black" USB 2.0 port on server.Booted server and viola!My server booted up without any issues and was configured exactly as it was prior to the bx* checksum error.Thank you, thank you!
August 2Aug 2 I have had this issue for a while and ignored it. A hard reboot would always get past it. Until tonight when I tried to update to the latest version. I replaced all the bz files and the change file but the issue persists.I'm not sure why but I do not have a flash backup in Unraid Connect.What are my next steps to get back up and running?ETA: Not sure why but Unraid does not show that I have any license keys either. I bought a lifetime license a couple of years ago before the price went up. Edited August 2Aug 2 by medicmandan
August 2Aug 2 Community Expert 6 hours ago, medicmandan said:I have had this issue for a while and ignored it. A hard reboot would always get past it. Until tonight when I tried to update to the latest version. I replaced all the bz files and the change file but the issue persists.Try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.
August 2Aug 2 I backed up my current stick to my desktop, created a new USB (I had a brand new stick). It would not boot with a stock install. Kept telling me to install bootable media or something (should have grabbed a screenshot).Swapped my old one back in (for the 20th time) and it booted up just fine past the error.I don't like that this issue is probably still lingering out there. Did I miss something setting up the new one? The utility it pretty idiot proof.I have remedied my backup issue and now have a backup on Connect. Edited August 2Aug 2 by medicmandan
August 3Aug 3 Community Expert 12 hours ago, medicmandan said:Did I miss something setting up the new one? The utility it pretty idiot proof.The utility should create the flash drive correctly, but if it was previously used with some specific layouts, it may not work; in those cases, using Rufus should resolve the issue:Get the Unraid zip from https://docs.unraid.net/unraid-os/download_list/ - Open Rufus and change "Boot selection" to "Freedos"- Set the "Volume label" to UNRAID- set filesystem to FAT32- click START- once done, unpack the Unraid ZIP to the flash drive If you are booting UEFI nothing else you need to do, if you are booting legacy/CSM, run the make_bootable.bat as administrator first.
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.