PSA: Updates to 9.10.1-U1 are currently flaky

Status
Not open for further replies.

WTM

Cadet
Joined
Dec 28, 2015
Messages
5
Unfortunately I did not read the forum before updating :-(. Got the error also. Did a rollback. When verifying the installation I also get:

The following Inconsistencies were found in your Current Install:
List of Files/Directories/Symlinks not Found:
/compat/linux/proc/.donotremove
List of Permission Errors:
/compat/linux/proc Expected MODE: 0755, Got: 0555

Hope that in the next update this will be fixed also.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Unfortunately I did not read the forum before updating :-(. Got the error also. Did a rollback. When verifying the installation I also get:

The following Inconsistencies were found in your Current Install:
List of Files/Directories/Symlinks not Found:
/compat/linux/proc/.donotremove
List of Permission Errors:
/compat/linux/proc Expected MODE: 0755, Got: 0555

Hope that in the next update this will be fixed also.
I recommend that someone file a bug for this detail. Maybe it's just noise, but it'd be nice to know for sure.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Looks good enough, thanks!
 
Joined
Sep 28, 2016
Messages
1
Also have the same problem, though the install verified with no issues. Just have the Critical alert stuck.
It was a fresh install from a few days ago too.

Code:
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 jails:
- Nothing to migrate.
- Loading initial data for jails.
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 sharing:
- Nothing to migrate.
- Loading initial data for sharing.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Migrating forwards to 0024_add_media_user_and_group.
> account:0024_add_media_user_and_group
- Migration 'account:0024_add_media_user_and_group' 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: account:0024_add_media_user_and_group
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/account/migrations/0024_add_media_user_and_group.py", line 14, in forwards
	group.save()
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 545, in save
	force_update=force_update, update_fields=update_fields)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 573, in save_base
	updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 654, in _save_table
	result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 687, in _do_insert
	using=using, raw=raw)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/manager.py", line 232, in _insert
	return insert_query(self.model, objs, fields, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 1514, in insert_query
	return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 903, 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", line 376, in execute
	execute = Database.Cursor.execute(self, query, params)
django.db.utils.IntegrityError: UNIQUE constraint failed: account_bsdgroups.bsdgrp_group



Edit: I just read the other thread, I guess I'll stick with this until U2 comes out - Are there critical things I'm now missing due to this failure?
 
Last edited:

raidflex

Guru
Joined
Mar 14, 2012
Messages
531
Why has this update not been pulled due to the amount of issues?
 

Hobbel

Contributor
Joined
Feb 17, 2015
Messages
111
just for info. Have a new FreeNAS installied in August (2016) with 9.10.1 ISO and updated to 9.10.1-U1 (GUI) 2 days ago. No problems with the installation/update. :)
(Only problem was: the iSCSI LUNs had "auto" before and after the update all LUNS had "0")
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419

Frankjacques

Cadet
Joined
Sep 30, 2016
Messages
3
Same here, i tought nice an update, but it broke luns for all esx'is , which in turn those datastores where used in guest, so all hell broke loose, esx's hosts froze and had to hard reboot the whole company .... not a nice thing... ill try to revert since all iscsi luns are down on latest.. ill have to get a dev box next time since this is prod. ;) i know i know but whos gonna pay 20k for something not that stable..

EDIT: reverted to 9.10.1 NOT U1, and all luns came back
 
Last edited:

ucrbuffalo

Dabbler
Joined
Jun 30, 2016
Messages
36
I'm wondering if my issue originated here or not...
My machine mainly serves as a file server and PMS machine. I had an issue where Plex was crashing on playback and giving me an exit code 1. Still haven't figured out what that is, so I went into the WebGUI and updated the PMS plugin and also updated the OS. From that point forward, all I've had are issues. I'm still booting in the last update, but now I still can't play anything on Plex. Is this from the U1 update??
 

Ryan Vaughan

Dabbler
Joined
Sep 20, 2016
Messages
21
My update is not allowing to system to mount root from boot volume Anyway to fix other than a reinstall and import zfs volumes. This was after updating to u1.
 

Skymax16

Cadet
Joined
Dec 22, 2015
Messages
8
Same error

Running migrations for services:
- Migrating forwards to 0198_iscsi_expunge_lun_auto.
> services:0198_iscsi_expunge_lun_auto
- Migration 'services:0198_iscsi_expunge_lun_auto' is marked for no-dry-run.
- Loading initial data for services.
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:
- Nothing to migrate.
- Loading initial data for system.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Migrating forwards to 0024_add_media_user_and_group.
> account:0024_add_media_user_and_group
- Migration 'account:0024_add_media_user_and_group' 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: account:0024_add_media_user_and_group
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
update.failed: unmodified: line 1
 

IZON

Cadet
Joined
Apr 17, 2016
Messages
4
I updated and got this:

Code:
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 directoryservice:																							
- Nothing to migrate.																											  
- Loading initial data for directoryservice.																					  
Installed 0 object(s) from 0 fixture(s)																							
Running migrations for services:																									
- Migrating forwards to 0198_iscsi_expunge_lun_auto.																			  
> services:0198_iscsi_expunge_lun_auto																							
- Migration 'services:0198_iscsi_expunge_lun_auto' is marked for no-dry-run.													  
- Loading initial data for services.																							  
Installed 0 object(s) from 0 fixture(s)  


I cant see how this is "Oct. 2, 2016, 9:49 a.m. - Update failed. Check /data/update.failed for further details."
I think it looks OK?
 

Free as in Nas

Dabbler
Joined
May 11, 2012
Messages
42
How severe are the current issues? Is the system not booting for people post upgrade or are there just sporadic errors in the logs post boot?
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
I'm sure it's booting for most.
 

VoodooFX

Dabbler
Joined
Nov 17, 2012
Messages
15
like many of you, I had the same critical error, but since the system was showing the latest version with no apparent issues, I didn't put that much thought into it... until I tried to start a Jail-Virtualboxed Ubuntu from the web interface, only to get that unspecified error occurred (something along the lines). Immediately changed the boot back to prev. version and everything is back to normal. Will wait for the next fix/version/release.
 

Tenek

Explorer
Joined
Apr 14, 2014
Messages
97
Guys, I'm here to clarify a few questions. 9.3->9.10 update failed for me yesterday. I'm able to boot into previous environment. And I was told it is good enough and I sit tight and wait for u2. This is what I have in boot menu right now:
D1256974_07580024_192650

My next step would be: selecting 9.3 stable environment and clicking Activate. That way system will be booted by default over there? It is safe for me do it, since I didn't have any configuration updates since failure.
A few questions:
- Some people say in this topic "I rolled-back", activating previous environment stands for "rolling-back here" or something else?
- Is so, I don't understand why some people have issues after going to previous version, since it is a snapshot (right?) it should bring exactly to the previous (i.e. workable) state without leftovers from the failed upgrade.
- do I need to remove somehow failed environment (see the last row: FreeNas-<blah-blah>)?
- Technically activating prev. environment boots system from a snapshot? Does it mean that my system will be forked? This is form documentation?:
* FreeNAS now uses ZFS for the boot device(s), also supporting selection and mirroring of one or more boot devices for greater reliabilty. The features of ZFS are also utilized to provide cloned "boot environments" which allow the system to be rolled back (or even forked) to different OS versions.
- Overall I would like to confirm if I can use (update configurations, install jails etc) activated previous environment without any drawbacks. And I will be OK apply apply a new freenas version (U2) to it as soon as it is available.
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Well, they'll be fixed with -U2, hopefully, which is currently in testing, AFAIK.
 

Frankjacques

Cadet
Joined
Sep 30, 2016
Messages
3
Well, they'll be fixed with -U2, hopefully, which is currently in testing, AFAIK.

for the lun part i think u2 is fixing it :

#17369 Bug Ready For Release Critical iscsi lun delete causes automatic renumbering; lun mapping abruptly broken
#17819 Bug Ready For Release Critical iSCSI LUN ID's all set to 0

also take note of
#16178 Bug Ready For Release Important Remove kernel support for 10/100 ethernet hardware
 
Status
Not open for further replies.
Top