Visseroth
Guru
- Joined
- Nov 4, 2011
- Messages
- 546
I've been running FreeNAS since version 8 and have never had the problems or as many problems as I'm having now.
I'm running a SuperMicro X8DTH-i
48GB of RAM
Intel(R) Xeon(R) CPU X5690 @ 3.47GHz
RAIDz2 2X6 HGST 4TB Drives
RAIDz2 3X4 Samsung HD204UI's (old used for backups)
I was Previously was running 9.10.2-U6
I've been experiencing random reboots from which I have no idea why it's rebooting. I've looked at the logs and there's nothing to indicate why.
I've looked through previous forums, one guy suggested a log server. Great and novel idea. I'd love to have one up and going but I haven't been able to get one running the way I'd like and if I did it would be on this server which reboots. So no help there!
I don't understand why the logs aren't on the pool(s) so they can be looked through and kept for a set period of time?!?
After the reboot the system seriously hangs with the error "run_interrupt_driven_hooks; still waiting after 60 seconds for xpt_config"
When I decrypt the volume I get an error...
After the volume is decrypted the jails do not start nor do the jail's storage mount.
So either 11 is seriously buggy or I have a bad install.
Anyone have any thoughts or suggestions?
After this post I'm going to blow away my 11 install, roll back to 9.10.2-U6 and re-running the 11 update to see if I can get some of these errors to go away!
I'm running a SuperMicro X8DTH-i
48GB of RAM
Intel(R) Xeon(R) CPU X5690 @ 3.47GHz
RAIDz2 2X6 HGST 4TB Drives
RAIDz2 3X4 Samsung HD204UI's (old used for backups)
I was Previously was running 9.10.2-U6
I've been experiencing random reboots from which I have no idea why it's rebooting. I've looked at the logs and there's nothing to indicate why.
I've looked through previous forums, one guy suggested a log server. Great and novel idea. I'd love to have one up and going but I haven't been able to get one running the way I'd like and if I did it would be on this server which reboots. So no help there!
I don't understand why the logs aren't on the pool(s) so they can be looked through and kept for a set period of time?!?
After the reboot the system seriously hangs with the error "run_interrupt_driven_hooks; still waiting after 60 seconds for xpt_config"

When I decrypt the volume I get an error...
Code:
nvironment: Software Version: FreeNAS-11.0-U3 (c5dcf4416) Request Method: POST Request URL: http://XXX.XXX.XXX.XXX/storage/volume/3/unlock/?X-Progress-ID=(REMOVED) Traceback: File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py" in inner 39. response = get_response(request) File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _legacy_get_response 249. response = self._get_response(request) File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response 178. response = middleware_method(request, callback, callback_args, callback_kwargs) File "./freenasUI/freeadmin/middleware.py" in process_view 162. return login_required(view_func)(request, *view_args, **view_kwargs) File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/decorators.py" in _wrapped_view 23. return view_func(request, *args, **kwargs) File "./freenasUI/storage/views.py" in volume_unlock 1190. form.done(volume=volume) File "./freenasUI/storage/forms.py" in done 2627. _notifier.reload("disk") File "./freenasUI/middleware/notifier.py" in reload 281. return c.call('service.reload', what, {'onetime': onetime}, **kwargs) File "./freenasUI/middleware/notifier.py" in reload 281. return c.call('service.reload', what, {'onetime': onetime}, **kwargs) File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py" in call 233. raise CallTimeout("Call timeout") Exception Type: CallTimeout at /storage/volume/3/unlock/ Exception Value: Call timeout

After the volume is decrypted the jails do not start nor do the jail's storage mount.
So either 11 is seriously buggy or I have a bad install.
Anyone have any thoughts or suggestions?
After this post I'm going to blow away my 11 install, roll back to 9.10.2-U6 and re-running the 11 update to see if I can get some of these errors to go away!