Unable to load api/v1.0/system/bootenv/status status: 500

[avalon60]

I have replace the 2 USB sticks I had mirrored in my Freenas box with 2 of the same brands and sizes. I installed FreeNAS 9.3 on one of them, booted up then uploaded a previously save config file.
The other USB drive is empty and plugged in to the back of the board.

Now I get this error message : 'Unable to load api/v1.0/system/bootenv/status status: 500'

I also get this when I click the View Disks tab 'Unable to load api/v1.0/system/storage/disk status: 500'

Update: I found that updating the system from 9.3 to 9.10 has cured the error.
I would have thought that uploading a previously saved config file which was FreeNAS 9.10 , would have made the system 9.10, but it was still showing as 9.3.

Now I am getting and error saying that the update failed: CRITICAL: May 22, 2016, 9:48 a.m. - Update failed. Check /data/update.failed for further details.

 

[ethereal]

possibly a bug in 9.3 - can you update - or try 9.10

 

[ethereal]

possibly because you mixed a 9.10 config file with 9.3 freenas.

what does /data/update.failed say ?

 

[ethereal]

I would have thought that uploading a previously saved config file which was FreeNAS 9.10 , would have made the system 9.10, but it was still showing as 9.3.

no the configuration holds your information on pools, shares, etc

to upgrade the system requires you to update in the gui or using an iso - this will update the boot discs files with the never version

 

[avalon60]

possibly because you mixed a 9.10 config file with 9.3 freenas.

what does /data/update.failed say ?

I don't know, how do I get to that,...in a shell, and if so what are the commands

 

[ethereal]

less /data/update.failed

should work

 

[avalon60]

less /data/update.failed

should work

Yes it did:

ps: cannot mmap corefile
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
ps: empty file: Invalid argument
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:
- Migrating forwards to 0003_auto__add_field_support_support_email.
> support:0003_auto__add_field_support_support_email
- Loading initial data for support.
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:
- Migrating forwards to 0003_auto__add_field_support_support_email.
> support:0003_auto__add_field_support_support_email
- 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 0060_auto__del_field_nt4_nt4_netbiosname.
> storage:0051_auto__add_field_task_task_excludesystemdataset
> services:0156_auto__add_field_iscsitargetextent_iscsi_target_extent_blocksize
__add_f
> services:0157_auto__del_field_iscsitarget_iscsi_target_logical_blocksize
> services:0158_auto__add_field_afp_afp_srv_homename
:
> services:0159_auto__add_field_nfs_nfs_srv_v4_krb
> services:0160_pwencrypt
- Migration 'services:0160_pwencrypt' is marked for no-dry-run.
> services:0161_auto__chg_field_cifs_cifs_srv_bindip
> services:0162_auto__add_field_iscsitargetextent_iscsi_target_extent_rpm
> services:0163_auto__add_field_ssh_ssh_host_dsa_key_cert_pub__add_field_ssh_ss
h_host_
> services:0164_nfs_srv_v4_krb_fix
- Migration 'services:0164_nfs_srv_v4_krb_fix' is marked for no-dry-run.
> services:0165_auto__add_field_snmp_snmp_v3__add_field_snmp_snmp_v3_username__
add_fie
> services:0165_fix_ddns_domains_delimiters
- Migration 'services:0165_fix_ddns_domains_delimiters' is marked for no-dry-ru
n.
> services:0166_pwencrypt
- Migration 'services:0166_pwencrypt' is marked for no-dry-run.
> services:0167_auto__add_field_ups_ups_powerdown
> services:0168_snmp_v3_literal
- Migration 'services:0168_snmp_v3_literal' is marked for no-dry-run.
> services:0169_auto__add_field_iscsitargetportal_iscsi_target_portal_discovery
authmet
> services:0170_copy_discovery_fields
:
> services:0171_auto__del_field_iscsitargetglobalconfiguration_iscsi_discoverya
uthmeth
> services:0172_auto__add_field_iscsitargetextent_iscsi_target_extent_serial
! 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:
! 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:0172_auto__add_field_iscsitargetextent_iscsi_target
_extent_serial
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__.p
y", line 399, in execute_from_command_line
:
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.p
y", 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", lin
e 220, in migrate_app
success = migrator.migrate_many(target, workplan, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
ne 256, in migrate_many
result = migrator.__class__.migrate_many(migrator, target, migrations, datab
ase)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
:
result = migrator.__class__.migrate_many(migrator, target, migrations, datab
ase)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
ne 331, in migrate_many
result = self.migrate(migration, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
ne 133, in migrate
result = self.run(migration, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
ne 114, in run
return self.run_migration(migration, database)
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
ne 84, in run_migration
migration_function()
File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", li
ne 60, in <lambda>
return (lambda: direction(orm))
File "/usr/local/www/freenasUI/../freenasUI/services/migrations/0172_auto__add
_field_iscsitargetextent_iscsi_target_extent_serial.py", line 23, in forwards
for target in orm['services.iSCSITarget'].objects.all():
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line
:
96, in __iter__
self._fetch_all()
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line
857, in _fetch_all
self._result_cache = list(self.iterator())
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line
220, in iterator
for row in compiler.results_iter():
File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py"
, line 713, in results_iter
for rows in self.execute_sql(MULTI):
File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py"
, line 786, in execute_sql
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", lin
e 372, in execute
execute = Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such column: services_iscsitarget.iscsi_tar
get_portalgroup_id
(END)

I hope you can make something of the above.

 

[ethereal]

i haven't got a clue what that means - but i still think the problem is with the way you updated.

can you resort to an older boot environment ? one which is 9.3 with a 9.3 configuration.

then try and update again in the gui to 9.10

 

[ethereal]

or install 9.10 to your empty usb and use that one to boot with

 

[avalon60]

I can install 9.3 onto a USB stick, but my last 2 saved config files are the updated ones to 9.10. If I do a new install and not install the saved file it will me I have to star over again, which I would rather not do.

 

[avalon60]

or install 9.10 to your empty usb and use that one to boot with

I tried doing that before and when I wanted to upload the saved config file it wouldn't upload saying something about it was newer than what I was installing or something along those lines.

 

[ethereal]

if you have a config file for 9.10 then install 9.10 to new usb and upload config

 

[avalon60]

i haven't got a clue what that means - but i still think the problem is with the way you updated.

can you resort to an older boot environment ? one which is 9.3 with a 9.3 configuration.

then try and update again in the gui to 9.10

Yes I could do that again, but then I would have the Critical error again. Do you think I should do that then?

 

[ethereal]

how many boot environments do you have on your disk?

 

[avalon60]

how many boot environments do you have on your disk?

I have the default one , then below that there is FreeNAS- with a great long line of letters and numbers.

 

[ethereal]

you said that you loaded your 9.10 config file to the 9.3 system - which is a newer format.

that's maybe the problem - at least try rolling back and trying again with an environment that worked then updating to 9.10

 

[avalon60]

you said that you loaded your 9.10 config file to the 9.3 system - which is a newer format.
that's maybe the problem - at least try rolling back and trying again with an environment that worked then updating to 9.10

I only have 2 config backups and they are both the updated ones with 9.10.

 

[ethereal]

1. go back to 9.3 boot environment with a working 9.3 configuration

2. update to 9.10 in the gui - this will update your boot disc to 9.10 and update your configuration file to 9.10

 

[avalon60]

I only have 2 config backups and they are both the updated ones with 9.10.

 

[ethereal]

do you know how to view your boot environments?