Error in FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.xz?

[NASbox]

Has anyone been successful in using FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.xz?

The GUI Update procedure returns:
Error: The Firmware is Invalid

with the following SHA256:
16031894a134abd5b0266278b5f11d223850fb24ae0121b50b56de7a390522b9

According to the download page at sourceforge
FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.xz 2012-12-13 82.8 MB

However after attempting to download the file several times, I keep getting
a different file size: 79.4 MB (83,285,604 bytes)

Anyone any suggestions?

 

[toddos]

What are you upgrading from? If you're coming from 8.2 beta3 or newer, you need to use the txz file. From the release notes:

The GUI upgrade format changed in 8.2.0-BETA3 from xz to txz. What
this means is that if you are attempting to do a GUI upgrade to
8.3.0-RELEASE from 8.2.0-BETA3 or later use the .txz version of the
GUI_Upgrade file. If you are upgrading from any previous version use
the .xz file.

 

[NASbox]

[Solved] Error in FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.xz

Thanks toddos! That was the problem... I missed the change in the documentation

I was updating from Config FreeNAS-8.0.4-RELEASE-p2-x64, if that
change wasn't confusing enough...

• The size info on the SF is different from what I downloaded
• The package FreeNAS-8.3.0-RELEASE-x64.GUI_Upgrade.xz worked (didn't need txz)

Anyway problem is solved, and hopefully if anyone else has the same
problem google will pick up this post.

 

[TDPsGM]

Hey NASbox / toddos,

I just tried to upgrade from FreeNAS-8.0.2-RELEASE-amd64 (8288)
using
FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.xz

my SHA256 came out to:
528D981D742C0E3A84B50474B8953BE9AD0B9E5987AE2721F34ED7CB5A488F3D

and it is the same as the value in the
FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.xz.sha256.txt
that I downloaded.

That is nothing close to what you first posted. Do these things change?

I am getting a "Invalid firmware or checksum" message when I try to use it.

 

[cyberjock]

Nope.. the OP was making a mistake between the .txz and the .xz. Only 1 character difference between the two.. Attention to detail gets the job done right the first time.

 

[TDPsGM]

Ok, I just ran the hash on the txz that he should have used, and I get:
16031894A134ABD5B0266278B5F11D223850FB24AE0121B50B56DE7A390522B9
FreeNAS-8.3.0-RELEASE-p1-x64.GUI_Upgrade.txz

... that is the same as what he posted in the first post, so it should have worked -- Regardless, he is fine but it doesn't explain my issue.

Why would my attempt be throwing an "Invalid firmware or checksum" error message?

All my ducks seem to be lining up.
I followed all the steps in the 8.3.0 manual with regards to the update:
Section 2.6.1 Preparing for the Upgrade

I am using the *.xz version as my current install is PRE 8.2.0-BETA3 ....

I am not sure what it is I am doing wrong.
I can still do the CD option, but I'd like to see if I can get it to work this way.

Any ideas anyone?

 

[TDPsGM]

As per the 8.3.0 Release manual, it suggested that if things don't go right that I was to enter shell and use the code:

more /var/log/messages

I see that it attempted to run the firmware, but I am not really sure what it is that I am looking for.
I have attached a photo of the messages that were logged.
The update was attempted at the log time stamp of 09:07:27

Does this help?

 

[paleoN]

I just tried to upgrade from FreeNAS-8.0.2-RELEASE-amd64 (8288)

FreeNAS-8.0.2-RELEASE-amd64 is ancient. See this [post=36212]post by survive[/post] if you really want to upgrade. Personally, I would just install 8.3 on a 2[sup]nd[/sup] stick.

 

[TDPsGM]

I realize it is old. I have been tinkering.
That being said, this might be a good time to test the "Exporting" of a zPool rather than Upgrading the system.

Being that it is a much older Release do you think saving the config file will still work on the newer 8.3.0 Release if I were to import it?
... or is the only way to find out is to go ahead and try it?
(Non-critical data -- I am just hear to learn before I commit important stuff)

Thanks for the help.

 

[TDPsGM]

Being that it is an older release - for the heck of it, I tried the GUI update using version 8.0.3 / 8.0.4 / 8.2.0
and none of them are working.

I would have thought that going from 8.0.2 to 8.0.3 would have worked.

I can't help but think I am missing something else here.
I know it has been a while, but I am pretty sure that I initially installed the 64bit version.

This may sound dumb, but does someone want to look at this image and confirm for me that that IS what is currently installed?



The other thing I was wondering was about my USB drive.
I am using a Sanddisk 4GB cruzer-edge
http://www.sandisk.com/products/usb/drives/cruzer-edge/

Here is another one that I have and what Windows is reporting the capacity that it has:



Could it be possible that it is one of those drives that is a little on the lean side for storage capacity and is causing the issue?

What do you think - anyone?

 

[William Grzybowski]

Being that it is an older release - for the heck of it, I tried the GUI update using version 8.0.3 / 8.0.4 / 8.2.0
and none of them are working.

I would have thought that going from 8.0.2 to 8.0.3 would have worked.

I can't help but think I am missing something else here.
I know it has been a while, but I am pretty sure that I initially installed the 64bit version.

This may sound dumb, but does someone want to look at this image and confirm for me that that IS what is currently installed?

View attachment 1653

There were dozens of bug fixes in the firmware upgrade since then. Just save config, install 8.3 fresh and be done with it.