segmentation fault when running awk???

[alexmc]

So I have a FreeNas 9.1.0 system which, of course, should be updated to a more recent version. However I tried and can't. it seems to be a bit confused about something when displaying the status and this is causing the upgrade to fail.

[root@freenas2 ~]# env -u TZ uptime |awk -F', load averages:' '{ print $1 }'
Segmentation fault: 11

(This works fine on another freenas box I have which is 9.3)

I can run awk by itself and it seems to run fine. I am *guessing* there is corruption on my USB boot drive and that the awk binary is corrupt. Can anyone suggest ways of confirming this?

Should it be possible to create a brand new USB flash disk with 9.10 on and just swap them round giving the disks to the new OS and not worry about 'upgrading' the old flash drive's software

thanks

 

[alexmc]

Here is the error in context

Environment:

Software Version: FreeNAS-9.1.0-RELEASE-x64 (dff7d13)
Request Method: GET
Request URL: http://freenas2.local.owal.co.uk/system/info/?dojo.preventCache=1471607461748


Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
109. response = middleware_method(request, callback, callback_args, callback_kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py" in process_view
165. return login_required(view_func)(request, *view_args, **view_kwargs)
File "/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
25. return view_func(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/system/views.py" in system_info
104. sysinfo = _system_info(request)
File "/usr/local/www/freenasUI/../freenasUI/system/views.py" in _system_info
76. "awk -F', load averages:' '{ print $1 }'", shell=True)
File "/usr/local/lib/python2.7/subprocess.py" in check_output
575. raise CalledProcessError(retcode, cmd, output=output)

Exception Type: CalledProcessError at /system/info/
Exception Value: Command 'env -u TZ uptime | awk -F', load averages:' '{ print $1 }'' returned non-zero exit status 139

 

[dlavigne]

I'd try installing the latest STABLE on a new stick. That way you'll be up-to-date and on a new stick...