Update failed

[tha_toadman]

I recently noticed that the 'Update' tab said there were updates ready to install. I went ahead and updated the box and it rebooted. After the reboot, I noticed a critical alert in the corner. I clicked on it and was told the following:

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

I ssh'ed into the box and extracted the following message from that file:

FATAL ERROR - The following SQL query failed: ALTER TABLE "services_fiberchanneltotarget" RENAME TO "services_fibrechanneltotarget";
The error was: no such table: services_fiberchanneltotarget
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 support:
- Nothing to migrate.
- Loading initial data for support.
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 directoryservice:
- Migrating forwards to 0054_auto__add_field_activedirectory_ad_allow_dns_updates.
> directoryservice:0054_auto__add_field_activedirectory_ad_allow_dns_updates
- Loading initial data for directoryservice.
Installed 0 object(s) from 0 fixture(s)
Running migrations for storage:
- Nothing to migrate.
- Loading initial data for storage.
Installed 0 object(s) from 0 fixture(s)
Running migrations for system:
- Migrating forwards to 0099_email_pwenc.
> system:0099_email_pwenc
- Migration 'system:0099_email_pwenc' is marked for no-dry-run.
- Loading initial data for system.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Migrating forwards to 0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget.
> services:0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget
! 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: = ALTER TABLE "services_fibrechanneltotarget" RENAME TO "services_fiberchanneltotarget"; []

! 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: services:0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget
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/services/migrations/0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget.py", line 11, in forwards
db.rename_table(u'services_fiberchanneltotarget', u'services_fibrechanneltotarget')
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/generic.py", line 375, in rename_table
self.execute(self.rename_table_sql % params)
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 386, in execute
return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: services_fiberchanneltotarget

Because of the versioning now with FreeNAS, I've reverted back to FreeNAS-9.3-STABLE-201511040813. It appears that FreeNAS-9.3-STABLE-201511280648 is whats complaining about the failed upgrade.

 

[dlavigne]

Please create a bug report at bugs.freenas.org that includes that message and post the issue number here.

 

[Ivan Pedersen]

I created https://bugs.freenas.org/issues/12618

 

[kraab]

Thought I would report I'm having the same issue, tried to update from 201511040813 to 201511280648 and received the same error. This is a newer installation, bought a new 16GB drive and reinstalled on 11/12/15, I did import my old config. No issues till running this update. Happy to provide any configuration data, let me know. (Also noted this unrelated warning; WARNING: Firmware version 16 does not match driver version 20 for /dev/mps0. Please flash controller to P20 IT firmware.)

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

FATAL ERROR - The following SQL query failed: ALTER TABLE "services_fiberchanneltotarget" RENAME TO "services_fibrechanneltotarget";
The error was: no such table: services_fiberchanneltotarget
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 support:
- Nothing to migrate.
- Loading initial data for support.
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 storage:
- Nothing to migrate.
- Loading initial data for storage.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Migrating forwards to 0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget.
> services:0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget
! 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: = ALTER TABLE "services_fibrechanneltotarget" RENAME TO "services_fiberchanneltotarget"; []

! 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: services:0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget
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/services/migrations/0184_auto__del_fiberchanneltotarget__add_fibrechanneltotarget.py", line 11, in forwards
db.rename_table(u'services_fiberchanneltotarget', u'services_fibrechanneltotarget')
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/generic.py", line 375, in rename_table
self.execute(self.rename_table_sql % params)
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 386, in execute
return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: services_fiberchanneltotarget

 

[ChiknNutz]

Refer to this thread which includes a link to a patch.

https://forums.freenas.org/index.ph...pdate-failed-how-to-repair.39773/#post-247599

 

[rsquared]

If you follow the bug report link from the previous post you can find instructions for a workaround. There's also a fix already that should be included in the next release.

As to the firmware error, the driver version for your HBA has been updated in this release, and you will need to flash the version 20 firmware to match the driver.

Edit to clarify, I meant the bugs.freenas.org link from post 3.

 

[mattbbpl]

(Also noted this unrelated warning; WARNING: Firmware version 16 does not match driver version 20 for /dev/mps0. Please flash controller to P20 IT firmware.)

For this, you will need to upgrade the firmware of your controller to the P20 IT firmware as the drivers were updated (from version 16) in the latest release.

 

[kraab]

Refer to this thread which includes a link to a patch.

https://forums.freenas.org/index.ph...pdate-failed-how-to-repair.39773/#post-247599

ChiknNutz, Thank you

Still lacking time update the firmware to v20, just wanted to include that as extra troubleshooting information..