Update Error

[thejamesk]

Anyone know how to resolve/fix this error I have when trying to update? :(

 

[Samuel Tai]

Try redownloading the update via the "Download Updates" button.

 

[thejamesk]

Try redownloading the update via the "Download Updates" button.

Rebooted system and also re-downloaded but still get this error when I press Apply Pending Update

 

[Samuel Tai]

Does your boot pool scrub clean? You could also try applying a manual update by downloading from http://download.freenas.org/11.3/STABLE/U3.1/FreeNAS-11.3-U3.1-manual-update.tar. SHA256 hash of this file is 980a8c789aa40b99eeccdae626fe3e11c570d4281daa628917e2b50be7a407d9.

 

[Alecmascot]

If I recall correctly; the update download is saved in the System Dataset.
Try changing the pool that the SD is assigned to.

 

[thejamesk]

If I recall correctly; the update download is saved in the System Dataset.
Try changing the pool that the SD is assigned to.

Can I scan my system dataset pool for errors? I seem to have a bug with MineOS permissions so suspect something may be messed up on there.

 

[thejamesk]

Does your boot pool scrub clean? You could also try applying a manual update by downloading from http://download.freenas.org/11.3/STABLE/U3.1/FreeNAS-11.3-U3.1-manual-update.tar. SHA256 hash of this file is 980a8c789aa40b99eeccdae626fe3e11c570d4281daa628917e2b50be7a407d9.

Thank's will consider manual update, WIll this mess up any my config/data? What is the process for scrub clean?

 

[SweetAndLow]

Thank's will consider manual update, WIll this mess up any my config/data? What is the process for scrub clean?

Manual update is the same as doing it through the GUI. You just download the iso instead of auto download.

And system->boot->actions->scrub will scrub your boot device.

 

[Samuel Tai]

Can I scan my system dataset pool for errors?

 

[Samuel Tai]

Manual update is the same as doing it through the GUI. You just download the iso instead of auto download.

Actually, please don't download the ISO. See the link I provided earlier for the manual update file.

WIll this mess up any my config/data?

As @SweetAndLow mentioned, a manual update does the same thing as a GUI update. Your pool and data should be safe, assuming you read the release notes for U3.1 and U3, and took the appropriate actions noted there.

 

[SweetAndLow]

Actually, please don't download the ISO. See the link I provided earlier for the manual update file.


As @SweetAndLow mentioned, a manual update does the same thing as a GUI update. Your pool and data should be safe, assuming you read the release notes for U3.1 and U3, and took the appropriate actions noted there.

I don't think the tar file is how you do what is referred to as a manual update. I think creating a new boot device with the new image and then selection upgrade from the prompt when you boot the new boot device is the way you do a manual upgrade.

 

[Samuel Tai]

I don't think the tar file is how you do what is referred to as a manual update. I think creating a new boot device with the new image and then selection upgrade from the prompt when you boot the new boot device is the way you do a manual upgrade.

That's a full emergency rebuild. The manual update is as described in the Guide, Section 7.14.6:

Go to https://download.freenas.org/ and find an update file of the desired version. Manual update file names end with -manual-update-unsigned.tar.​

 

[thejamesk]

View attachment 38830

I have completed a scrub, Am I right to assume any errors would flag up in notifications after the scrub completes. Currently after clicking Scrub Boot Pool nothing seems to happen other than a notifcation saying complete.

 

[thejamesk]

I have actually had a few issues installing MineOS likely due to permissions, Could something related to this have messed up my System Dataset which is set to the same pool as my plugins?

 

[Samuel Tai]

I have completed a scrub, Am I right to assume any errors would flag up in notifications after the scrub completes. Currently after clicking Scrub Boot Pool nothing seems to happen other than a notifcation saying complete.

You can see the outcome of the scrub by selection Boot Pool Status from the same pulldown used to initiate the scrub. If your boot pool displays all ONLINE, your scrub found no errors. You can also verify this from shell by running zpool status freenas-boot, which will explicitly list all the errors found during scrub.

 

[thejamesk]

You can see the outcome of the scrub by selection Boot Pool Status from the same pulldown used to initiate the scrub. If your boot pool displays all ONLINE, your scrub found no errors. You can also verify this from shell by running zpool status freenas-boot, which will explicitly list all the errors found during scrub.

Thank's I guess I will have to try a manual update as the scrub comes back with no errors. I have also just done a scrub on my system dataset pool and redownloaded the updates but still unable to install due to dataset error.

 

[thejamesk]

Unable to perform manual update due to this error.

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 663, in do_update
if ApplyUpdate(dest_extracted) is None:
File "/usr/local/lib/freenasOS/Update.py", line 1627, in ApplyUpdate
raise e
File "/usr/local/lib/freenasOS/Update.py", line 1559, in ApplyUpdate
if installer.InstallPackages(progressFunc=progressFunc, handler=install_handler) is False:
File "/usr/local/lib/freenasOS/Installer.py", line 1088, in InstallPackages
trampoline=self.trampoline) is False:
File "/usr/local/lib/freenasOS/Installer.py", line 823, in install_file
if pkgdb.RemovePackageFiles(pkgName) == False:
File "/usr/local/lib/freenasOS/Configuration.py", line 340, in RemovePackageFiles
cur.execute("SELECT path FROM files WHERE package = ? AND kind <> ?", (pkgName, "dir"))
sqlite3.DatabaseError: database disk image is malformed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 349, in run
await self.future
File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 386, in __run_body
rv = await self.method(*([self] + args))
File "/usr/local/lib/python3.7/site-packages/middlewared/schema.py", line 961, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 668, in file
await self.middleware.run_in_thread(do_update)
File "/usr/local/lib/python3.7/site-packages/middlewared/utils/run_in_thread.py", line 10, in run_in_thread
return await self.loop.run_in_executor(self.run_in_thread_executor, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.7/site-packages/middlewared/utils/io_thread_pool_executor.py", line 25, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 666, in do_update
raise CallError(str(e))
middlewared.service_exception.CallError: [EFAULT] database disk image is malformed

 

[Samuel Tai]

Ok, if a manual update doesn't work, and it's complaining about database corruption, you're left with no choice but to reinstall and reimport your pool and config.

 

[SweetAndLow]

Ok, if a manual update doesn't work, and it's complaining about database corruption, you're left with no choice but to reinstall and reimport your pool and config.

Will they even be able to import their config? I might suggest saving the original boot device off to the side. Then creating a whole new boot device and upload the config to that. Just in case the new database can't be uploaded.

 

[thejamesk]

Will they even be able to import their config? I might suggest saving the original boot device off to the side. Then creating a whole new boot device and upload the config to that. Just in case the new database can't be uploaded.

I think I shall keep the original boot drives to one side just to be safe!