Firmware Update Failed: ValueError: hour must be in 0..23

[mashimus]

Hi,

I'm trying to update my firmware to 9.1.1 using GUI Upgrade on my MicroServer N36L.

Current Build: FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty)
I'm using the following file to update: FreeNAS-9.1.1-RELEASE-x64.GUI_Upgrade.txz

The update process completed the 2 steps and reboots, but after reboot the firmware is still 8.3.1. I checked /var/log/messages and couldn't find anything.

I checked the /data folder and found the following in update.failed file:

[root@freenas ~]# cd /data
[root@freenas /data]# ls -lrt
total 2484
-rw-r----- 1 root wheel 171008 May 5 2012 factory-v1.db
drwxrwxr-x 2 root operator 512 May 5 2012 .snap
drwxr-xr-x 2 root wheel 512 May 18 2012 ssh
-rw-r--r-- 1 root wheel 867960 Dec 17 16:02 rrd_dir.tar.bz2
-rw-r--r-- 1 root wheel 34 Dec 17 16:05 update.failed
drwxr-xr-x 2 root wheel 512 Dec 17 16:08 zfs
-rw-r----- 1 root operator 217088 Dec 17 16:46 freenas-v1.db
[root@freenas /data]# cat update.failed
ValueError: hour must be in 0..23

Any suggestions on what I can do to fix this error? Or am I looking in the wrong place?

Thanks!

 

[mashimus]

I also tried to update to 8.3.2 and the same thing happened, but I got more information from the update.failed file:

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 443, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.p
y", line 382, 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 196, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py",
line 232, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python2.7/site-packages/South-0.7.5-py2.7.egg/south/manag
ement/commands/migrate.py", line 107, in handle
ignore_ghosts = ignore_ghosts,
File "/usr/local/lib/python2.7/site-packages/South-0.7.5-py2.7.egg/south/migra
tion/__init__.py", line 199, in migrate_app
applied_all = check_migration_histories(applied_all, delete_ghosts, ignore_g
hosts)
File "/usr/local/lib/python2.7/site-packages/South-0.7.5-py2.7.egg/south/migra
tion/__init__.py", line 72, in check_migration_histories
for h in histories:
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line
118, in _result_iter
self._fill_cache()
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line
892, in _fill_cache
self._result_cache.append(self._iter.next())
File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line
291, in iterator
for row in compiler.results_iter():
File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py"
, line 763, 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 838, in execute_sql
return list(result)
File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py"
, line 832, in <lambda>
result = iter((lambda: cursor.fetchmany(GET_ITERATOR_CHUNK_SIZE)),
File "/usr/local/lib/python2.7/site-packages/django/db/backends/sqlite3/base.p
y", line 38, in parse_datetime_with_timezone_support
dt = parse_datetime(value)
File "/usr/local/lib/python2.7/site-packages/django/utils/dateparse.py", line
85, in parse_datetime
return datetime.datetime(**kw)
ValueError: hour must be in 0..23

 

[cyberjock]

Have you tried rebooting?

What does "date" say?

 

[mashimus]

Yes, rebooted several times.

[root@freenas ~]# date
Tue Dec 17 21:46:31 EST 2013

 

[cyberjock]

Just for sh*ts and giggles, can you do a sha256 sum of the upgrade file on your machine and verify it matches the sum from iXsystems?

 

[mashimus]

Just for sh*ts and giggles, can you do a sha256 sum of the upgrade file on your machine and verify it matches the sum from iXsystems?

Just did it:

D:\>sha256sum.exe FreeNAS-9.1.1-RELEASE-x64.GUI_Upgrade.txz
09a2cbda126a332d1e9f6fe7406d660b9b8e565494248c6d9602f20eb2448601 *FreeNAS-9.1.1-RELEASE-x64.GUI_Upgrade.txz

It's a match

 

[cyberjock]

Can you post system specs please?

 

[mashimus]

Can you post system specs please?

HP MicroServer N36L
AMD Athlon II Neo N36L (1.3 Ghz) K325
8GB ECC RAM
4x 3TB Hitachi SATA HDD in RAIDZ1
2x 2TB Samsung SATA HDD in Mirror

Do you need more info?

Thanks

 

[cyberjock]

Nope. That looks good. You're really short on RAM for the amount of storage space you have. But I don't think that's causing your problems.

I'd say there's 3 possible situations:

1. If you've done any tunables or sysctls you may have put the system in a position where it's not stable enough for the actual update.
2. Your USB stick is bad and it's failing to update for some reason.
3. You have some kind of issue related to your hardware and software that is causing it to fail. For example, if your system is too slow and the update scripts are timing out.

I'd say you have 3 easy options:

1. Keep what you have and be happy the system works.
2. Try installing FreeNAS to either a new USB stick(importing your config file) or the same USB stick via CD-ROM upgrade as that shouldn't fail.
3. Upgrade your hardware and try this whole thing again.

I will tell you that you are very limited with that setup. You can put 16GB om that system, and I'd highly recommend you do so. The 1GB of RAM per TB of disk space says you shouldhave 16GB of RAM. 8GB of RAM is the minimum for ZFS per the manual. You could also choose to build a whole new system that can better handle your load both now and in the future. You can expect that each FreeNAS update will probably slow down your server's performance and you already very short on CPU and RAM resources.

In your case, if you are okay with not saturating Gb LAN you will probably be safe with just a RAM upgrade to 16GB and then doing a software update. But don't expect performance miracles. Going from FreeNAS 8.x to FreeNAS 9.x is akin to upgrading from XP to Vista or Windows 7 to Windows 8. It's a big step and there's a definite increase in system resources consumed. Your system is almost definitely going to be slower with the update, but also faster with more RAM. Which one is going to have a larger impact on performance is anyone's guess.

I'd definitely be wary of using your server with the amount of storage it has with just 8GB of RAM. That makes me pucker a little.

 

[dlavigne]

I checked the /data folder and found the following in update.failed file:

[root@freenas ~]# cd /data
[root@freenas /data]# ls -lrt
total 2484
-rw-r----- 1 root wheel 171008 May 5 2012 factory-v1.db
drwxrwxr-x 2 root operator 512 May 5 2012 .snap
drwxr-xr-x 2 root wheel 512 May 18 2012 ssh
-rw-r--r-- 1 root wheel 867960 Dec 17 16:02 rrd_dir.tar.bz2
-rw-r--r-- 1 root wheel 34 Dec 17 16:05 update.failed
drwxr-xr-x 2 root wheel 512 Dec 17 16:08 zfs
-rw-r----- 1 root operator 217088 Dec 17 16:46 freenas-v1.db
[root@freenas /data]# cat update.failed
ValueError: hour must be in 0..23

Any suggestions on what I can do to fix this error? Or am I looking in the wrong place?

Please create a report at bugs.freenas.org that contains that file and post the issue number here.