My update stops at 66% since v12.0

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
What update??
 

NAS_warrior

Explorer
Joined
Sep 29, 2016
Messages
64
When I try to update/upgrade to next version. (System>Update>Apply Pending Update)
It says I have new updates available:
OperationName
Upgradebase-os-12.0-RELEASE-e3f03f19956748b5b3c90860eb00274a -> base-os-12.0-U1-764c3b0625e2dd9a62409cc2790a9747
Upgradefreebsd-pkgdb-12.0-RELEASE-e3f03f19956748b5b3c90860eb00274a -> freebsd-pkgdb-12.0-U1-764c3b0625e2dd9a62409cc2790a9747
Upgradefreenas-pkg-tools-12.0-RELEASE-e3f03f19956748b5b3c90860eb00274a -> freenas-pkg-tools-12.0-U1-764c3b0625e2dd9a62409cc2790a9747

It start normally and then stops on 66.67% and can stay there forever.
My Version is TrueNAS-12.0-STABLE.
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
Does it complete the download phase?
 

NAS_warrior

Explorer
Joined
Sep 29, 2016
Messages
64
"Does it complete the download phase? "
Yep!
I had also tried with the manual update via downloaded file but had the same result.
My system is based on HP Microserver G8.
The secondary instance which I run over VMware ESX 6.7u1 (tested over ESX 7.0.1 too) have not such issue.
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
Seems to me I read some posts about the G8 - perhaps you should search here on that and see if it turns up something useful...
 

NAS_warrior

Explorer
Joined
Sep 29, 2016
Messages
64
All in vain... this somehow is connected with a still ruining service which prevent the update.
The logging did not provide enough data to get a clue what's stuck.
 
Joined
Oct 22, 2019
Messages
3,641
Check if the Exec option is disabled for your root dataset.

When relocating the .system dataset, it will inherit the "Exec=off" option of your top-level root dataset.

If you end up having to re-enable "Exec=on" for the top-level root dataset, you might need to move your .system dataset to the boot pool, and then back to the data pool.

Or you can just skip all of that and use the following command in the Shell:
zfs set exec=on mainpool/.system

Replace "mainpool" with the name of your actual pool in which the System Dataset resides.
 
Last edited:
Joined
Oct 22, 2019
Messages
3,641
Ups!!! Where to find .system dataset file????

It's not a file. It's a special hidden dataset, known as "System Dataset" in the GUI options.

Find out where you chose to keep it:
Menu > System > System Dataset > select (or review) the pool

It's either on your boot-pool, or more likely, on one of your data pools. I use the pool name "mainpool" as an example if you prefer to use the Shell to issue a one-time command to give the System Dataset (.system) Exec permissions. (See my previous post for the zfs command)
 
Top