Error upgrading to 9.10

Status
Not open for further replies.

Angate

Cadet
Joined
Apr 8, 2014
Messages
9
I ran the update for 9.10 and got an error alert.

What should I do to resolve?

Update failed. Check /data/update.failed for further details.

more /data/update.failed
FATAL ERROR - The following SQL query failed: INSERT INTO "_south_new_storage_encrypteddisk" ("encrypted_volume_id", "id", "encrypted_provider", "encrypted_disk_id") SELECT "encrypted_volume_id", "id", "encrypted_provider", "encrypted_disk_id" FROM "storage_encrypteddisk";
The error was: NOT NULL constraint failed: _south_new_storage_encrypteddisk.encrypted_disk_id
Running migrations for api:
- Nothing to migrate.
- Loading initial data for api.
Installed 0 object(s) from 0 fixture(s)
Running migrations for freeadmin:
- Nothing to migrate.
- Loading initial data for freeadmin.
Installed 0 object(s) from 0 fixture(s)
Running migrations for vcp:
- Nothing to migrate.
- Loading initial data for vcp.
Installed 0 object(s) from 0 fixture(s)
Running migrations for support:
- Nothing to migrate.
- Loading initial data for support.
Installed 0 object(s) from 0 fixture(s)
Running migrations for network:
--More--(12%)...skipping...
FATAL ERROR - The following SQL query failed: INSERT INTO "_south_new_storage_encrypteddisk" ("encrypted_volume_id", "id", "encrypted_provider", "encrypted_disk_id") SELECT "encrypted_volume_id", "id", "encrypted_provider", "encrypted_disk_id" FROM "storage_encrypteddisk";
The error was: NOT NULL constraint failed: _south_new_storage_encrypteddisk.encrypted_disk_id
Running migrations for api:
- Nothing to migrate.
- Loading initial data for api.
Installed 0 object(s) from 0 fixture(s)
Running migrations for freeadmin:
- Nothing to migrate.
- Loading initial data for freeadmin.
Installed 0 object(s) from 0 fixture(s)
Running migrations for vcp:
- Nothing to migrate.
- Loading initial data for vcp.
Installed 0 object(s) from 0 fixture(s)
Running migrations for support:
- Nothing to migrate.
- Loading initial data for support.
Installed 0 object(s) from 0 fixture(s)
Running migrations for network:
- Migrating forwards to 0019_auto__del_field_interfaces_int_carp.
> network:0019_auto__del_field_interfaces_int_carp
- Loading initial data for network.
Installed 0 object(s) from 0 fixture(s)
Running migrations for tasks:
- Nothing to migrate.
- Loading initial data for tasks.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Nothing to migrate.
- Loading initial data for account.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Migrating forwards to 0192_netbiosname_split.
> services:0191_auto__add_field_cifs_cifs_srv_netbiosname_b__add_field_cifs_cifs_srv_n
> services:0192_netbiosname_split
- Migration 'services:0192_netbiosname_split' is marked for no-dry-run.
- Loading initial data for services.
Installed 0 object(s) from 0 fixture(s)
Running migrations for directoryservice:
- Migrating forwards to 0060_auto__del_field_nt4_nt4_netbiosname.
> directoryservice:0058_auto__del_field_activedirectory_ad_netbiosname_b__del_field_activedire
> directoryservice:0059_auto__del_field_ldap_ldap_netbiosname_a__del_field_ldap_ldap_netbiosna
> directoryservice:0060_auto__del_field_nt4_nt4_netbiosname
- Loading initial data for directoryservice.
Installed 0 object(s) from 0 fixture(s)
Running migrations for jails:
- Migrating forwards to 0036_templates_to_10_3_release.
> jails:0034_templates_to_10
- Migration 'jails:0034_templates_to_10' is marked for no-dry-run.
> jails:0035_templates_mtree_to_10
- Migration 'jails:0035_templates_mtree_to_10' is marked for no-dry-run.
> jails:0036_templates_to_10_3_release
- Migration 'jails:0036_templates_to_10_3_release' is marked for no-dry-run.
- Loading initial data for jails.
Installed 0 object(s) from 0 fixture(s)
Running migrations for sharing:
- Nothing to migrate.
- Loading initial data for sharing.
Installed 0 object(s) from 0 fixture(s)
Running migrations for plugins:
- Nothing to migrate.
- Loading initial data for plugins.
--More--(36%)...skipping...
FATAL ERROR - The following SQL query failed: INSERT INTO "_south_new_storage_encrypteddisk" ("encrypted_volume_id", "id", "encrypted_provider", "encrypted_disk_id") SELECT "encrypted_volume_id", "id", "encrypted_provider", "encrypted_disk_id" FROM "storage_encrypteddisk";
The error was: NOT NULL constraint failed: _south_new_storage_encrypteddisk.encrypted_disk_id
Running migrations for api:
- Nothing to migrate.
- Loading initial data for api.
Installed 0 object(s) from 0 fixture(s)
Running migrations for freeadmin:
- Nothing to migrate.
- Loading initial data for freeadmin.
Installed 0 object(s) from 0 fixture(s)
Running migrations for vcp:
- Nothing to migrate.
- Loading initial data for vcp.
Installed 0 object(s) from 0 fixture(s)
Running migrations for support:
- Nothing to migrate.
- Loading initial data for support.
Installed 0 object(s) from 0 fixture(s)
Running migrations for network:
- Migrating forwards to 0019_auto__del_field_interfaces_int_carp.
> network:0019_auto__del_field_interfaces_int_carp
- Loading initial data for network.
Installed 0 object(s) from 0 fixture(s)
Running migrations for tasks:
- Nothing to migrate.
- Loading initial data for tasks.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Nothing to migrate.
- Loading initial data for account.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Migrating forwards to 0192_netbiosname_split.
> services:0191_auto__add_field_cifs_cifs_srv_netbiosname_b__add_field_cifs_cifs_srv_n
> services:0192_netbiosname_split
- Migration 'services:0192_netbiosname_split' is marked for no-dry-run.
- Loading initial data for services.
Installed 0 object(s) from 0 fixture(s)
Running migrations for directoryservice:
- Migrating forwards to 0060_auto__del_field_nt4_nt4_netbiosname.
> directoryservice:0058_auto__del_field_activedirectory_ad_netbiosname_b__del_field_activedire
> directoryservice:0059_auto__del_field_ldap_ldap_netbiosname_a__del_field_ldap_ldap_netbiosna
> directoryservice:0060_auto__del_field_nt4_nt4_netbiosname
- Loading initial data for directoryservice.
Installed 0 object(s) from 0 fixture(s)
Running migrations for jails:
- Migrating forwards to 0036_templates_to_10_3_release.
> jails:0034_templates_to_10
- Migration 'jails:0034_templates_to_10' is marked for no-dry-run.
> jails:0035_templates_mtree_to_10
- Migration 'jails:0035_templates_mtree_to_10' is marked for no-dry-run.
> jails:0036_templates_to_10_3_release
- Migration 'jails:0036_templates_to_10_3_release' is marked for no-dry-run.
- Loading initial data for jails.
Installed 0 object(s) from 0 fixture(s)
Running migrations for sharing:
- Nothing to migrate.
- Loading initial data for sharing.
Installed 0 object(s) from 0 fixture(s)
Running migrations for plugins:
- Nothing to migrate.
- Loading initial data for plugins.
Installed 0 object(s) from 0 fixture(s)
Running migrations for system:
! Migration system:0100_auto__chg_field_tunable_tun_value should not have been applied before system:0100_auto__add_field_advanced_adv_graphite but was.
- Migrating forwards to 0100_auto__chg_field_tunable_tun_value.
> system:0100_auto__add_field_advanced_adv_graphite
- Loading initial data for system.
Installed 0 object(s) from 0 fixture(s)
Running migrations for storage:
- Migrating forwards to 0058_auto__del_field_disk_id__chg_field_disk_disk_identifier__add_unique_di.
> storage:0056_remove_disabled_encryption
- Migration 'storage:0056_remove_disabled_encryption' is marked for no-dry-run.
> storage:0057_migrate_disk_id_to_identifier
- Migration 'storage:0057_migrate_disk_id_to_identifier' is marked for no-dry-run.
! Error found during real run of migration! Aborting.

! Since you have a database that does not support running
! schema-altering statements in transactions, we have had
! to leave it in an interim state between migrations.

! You *might* be able to recover with: (migration cannot be dry-run; cannot discover commands)
! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
! NOTE: The error which caused the migration to fail is further up.
Error in migration: storage:0057_migrate_disk_id_to_identifier
Traceback (most recent call last):
File "/usr/local/www/freenasUI/manage.py", line 42, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle
ignore_ghosts = ignore_ghosts,
File "/usr/local/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app
success = migrator.migrate_many(target, workplan, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 256, in migrate_many
result = migrator.__class__.migrate_many(migrator, target, migrations, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 331, in migrate_many
result = self.migrate(migration, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 133, in migrate
result = self.run(migration, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 114, in run
return self.run_migration(migration, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 84, in run_migration
migration_function()
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 60, in <lambda>
return (lambda: direction(orm))
File "/usr/local/www/freenasUI/../freenasUI/storage/migrations/0057_migrate_disk_id_to_identifier.py", line 38, in forwards
db.alter_column(u'storage_encrypteddisk', 'encrypted_disk_id', self.gf('django.db.models.fields.CharField')(max_length=100))
File "/usr/local/lib/python2.7/site-packages/south/db/sqlite3.py", line 232, in alter_column
name: self._column_sql_for_create(table_name, name, field, explicit_name),
File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 47, in _cache_clear
return func(self, table, *args, **opts)
File "/usr/local/lib/python2.7/site-packages/south/db/sqlite3.py", line 113, in _remake_table
self._copy_data(table_name, temp_name, renames, added)
File "/usr/local/lib/python2.7/site-packages/south/db/sqlite3.py", line 149, in _copy_data
self.quote_name(src),
File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 282, in execute
cursor.execute(sql, params)
File "/usr/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
return self.cursor.execute(sql, params)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/sqlite3_ha/base.py", line 372, in execute
execute = Database.Cursor.execute(self, query, params)
django.db.utils.IntegrityError: NOT NULL constraint failed: _south_new_storage_encrypteddisk.encrypted_disk_id
 

Tenek

Explorer
Joined
Apr 14, 2014
Messages
97
I'm having the same issue after trying to update from 9.3 to 9.10 (auto update). Servers seems functioning but no UI. I checked suggested bug link above and it seems has to be fixed by now. What the best next step for me here? Download 9.10/STABLE/9.10.1-U1/x64/
and try to update manually?
Also if newer version is available with the fix, why auto-update didn't suggest me it at fist place?
 

Tenek

Explorer
Joined
Apr 14, 2014
Messages
97
Also, pardon my stupid question. I didn't use FreeNas much since 0.7. This times, every time you update freenas it creates a new load point? And keeps old in case it fails. In my case 9.3->9.10 failed. but I was able to load old configuration (FreeNAS-9.3-STABLE-201605170422). Is that configuration completely free from failed update? If I go to "system->update", I see current train as "FreeNAS-9.10-STABLE" with pending updates available. I guess it will fail the same way if I try it again. And I can keep happily using it? Can someone point me to some documentation about that topic?

If so, great. But that bring me to the main issues, how I can upgraded to the newer version if automatic upgrade failed?
It failed with the error in the original post. Also I was getting an error message: {"error": true, "events": [], "message": "Error: no such column: system_settings.stg_sysloglevel"} when starting GUI.
 
Last edited:

gpsguy

Active Member
Joined
Jan 22, 2012
Messages
4,472
What you did, was what we would have recommended you do. See this thread for more details - https://forums.freenas.org/index.ph...-are-currently-flaky.46358/page-2#post-317600

Shortly after 9.10.1-U1 was released last week, a number of issues were discovered. The developers are working on a -U2 update to resolve them. For now, stick with the version you are running.

In my case 9.3->9.10 failed. but I was able to load old configuration (FreeNAS-9.3-STABLE-201605170422). Is that configuration completely free from failed update?
 

Tenek

Explorer
Joined
Apr 14, 2014
Messages
97
@gpsguy
Thank you for confirming! I will sit tight. It is awesome that old configuration is available now days.
And I will reapply new version to the old configuration. Just making sure that no manual rollback is necessary.
 
Last edited:
Status
Not open for further replies.
Top