Some errors after update 9.2.1->9.3

[HolyK]

Hi!

I just did update from 9.2.1 to 9.3-STABLE-201504100216 and got a GUI popup with error bellow when unlocking encrypted volume.

Environment: Software Version: FreeNAS-9.3-STABLE-201504100216 Request Method: POST Request URL: http://192.168.2.4/storage/volume/2/unlock/?X-Progress-ID=28d8aa59-1451-4b38-89dd-e47a4bf93461 Traceback: File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File "/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py" in process_view 157. 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 22. return view_func(request, *args, **kwargs) File "/usr/local/www/freenasUI/../freenasUI/storage/views.py" in volume_unlock 1086. form.done(volume=volume) File "/usr/local/www/freenasUI/../freenasUI/storage/forms.py" in done 2576. _notifier.restart("system_datasets") File "/usr/local/www/freenasUI/../freenasUI/middleware/notifier.py" in restart 364. self._simplecmd("restart", what) File "/usr/local/www/freenasUI/../freenasUI/middleware/notifier.py" in _simplecmd 239. f() File "/usr/local/www/freenasUI/../freenasUI/middleware/notifier.py" in _restart_system_datasets 5217. systemdataset = self.system_dataset_create() File "/usr/local/www/freenasUI/../freenasUI/middleware/notifier.py" in system_dataset_create 5383. assert volume.vol_fstype in ('ZFS') Exception Type: AssertionError at /storage/volume/2/unlock/ Exception Value:

Also in the console i got following error(s)

Apr 20 20:45:17 HolyNAS kernel: GEOM_ELI: Device gptid/0f79f96b-xxxxxxxxxxxxxxxxxx.eli created.
Apr 20 20:45:17 HolyNAS kernel: GEOM_ELI: Encryption: AES-XTS 128
Apr 20 20:45:17 HolyNAS kernel: GEOM_ELI: Crypto: hardware
Apr 20 20:45:19 HolyNAS kernel: GEOM_ELI: Device gptid/0fff42cb-xxxxxxxxxxxxxxxxxx.eli created.
Apr 20 20:45:19 HolyNAS kernel: GEOM_ELI: Encryption: AES-XTS 128
Apr 20 20:45:19 HolyNAS kernel: GEOM_ELI: Crypto: hardware
Apr 20 20:45:26 HolyNAS notifier: Stopping collectd.
Apr 20 20:45:32 HolyNAS notifier: Waiting for PIDS: 3252.
Apr 20 20:45:32 HolyNAS notifier: Starting collectd.
Apr 20 20:45:33 HolyNAS ix-warden: zfs set mountpoint=none redmirror/jails/.warden-template-pluginjail
Apr 20 20:45:33 HolyNAS ix-warden: zfs rename -f redmirror/jails/.warden-template-pluginjail redmirror/jails/.warden-template-pluginjail-9.2-x64
Apr 20 20:45:33 HolyNAS ix-warden: mv /mnt/redmirror/jails/.warden-template-pluginjail /mnt/redmirror/jails/.warden-template-pluginjail-9.2-x64
Apr 20 20:45:33 HolyNAS notifier: mv: rename /mnt/redmirror/jails/.warden-template-pluginjail to /mnt/redmirror/jails/.warden-template-pluginjail-9.2-x64: No such file or directory
Apr 20 20:45:33 HolyNAS ix-warden: zfs set mountpoint=none redmirror/jails/.warden-template-portjail
Apr 20 20:45:34 HolyNAS ix-warden: zfs rename -f redmirror/jails/.warden-template-portjail redmirror/jails/.warden-template-portjail-9.2-x64
Apr 20 20:45:34 HolyNAS ix-warden: mv /mnt/redmirror/jails/.warden-template-portjail /mnt/redmirror/jails/.warden-template-portjail-9.2-x64
Apr 20 20:45:34 HolyNAS notifier: mv: rename /mnt/redmirror/jails/.warden-template-portjail to /mnt/redmirror/jails/.warden-template-portjail-9.2-x64: No such file or directory

I've replaced part of the gptid string by "x"es.
Volume got normally unlocked and i can see the data on it in a good shape.
That volume holds jails and some temp/shared data, but nothing *that* critical
I have one more encrypted volume with a bit important data which i did not attempted to unlock yet because of the described situation. Can i unlock that volume without worries or should i do more tests of the first one?

Some more commands

[root@HolyNAS] ~# zpool status redmirror
pool: redmirror
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details.
scan: scrub repaired 0 in 1h38m with 0 errors on Fri Apr 17 04:44:00 2015
config:

NAME STATE READ WRITE CKSUM
redmirror ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
gptid/0f79f96b-xxxxxxxxxxxxxxxxxxxxxxxxx.eli ONLINE 0 0 0
gptid/0fff42cb-xxxxxxxxxxxxxxxxxxxxxxxxx.eli ONLINE 0 0 0

errors: No known data errors

[root@HolyNAS] ~# camcontrol devlist
<ATA WDC WD30EZRX-00D 0A80> at scbus0 target 0 lun 0 (pass0,da0) //second pool
<ATA WDC WD30EZRX-00D 0A80> at scbus0 target 1 lun 0 (pass1,da1) //second pool
<ATA WDC WD30EZRX-00D 0A80> at scbus0 target 2 lun 0 (pass2,da2) //second pool
<ATA WDC WD30EZRX-00D 0A80> at scbus0 target 3 lun 0 (pass3,da3) //second pool
<ATA WDC WD30EZRX-00D 0A80> at scbus0 target 4 lun 0 (pass4,da4) //second pool
<ATA WDC WD30EZRX-00D 0A80> at scbus0 target 5 lun 0 (pass5,da5) //second pool
<WDC WD20EFRX-68EUZN0 80.00A80> at scbus1 target 0 lun 0 (pass6,ada0) //redmirror
<WDC WD20EFRX-68EUZN0 80.00A80> at scbus2 target 0 lun 0 (pass7,ada1) //redmirror
< USB DISK 2.0 PMAP> at scbus4 target 0 lun 0 (pass8,da6) //some miscs, not important
<USB Flash DISK 1100> at scbus5 target 0 lun 0 (pass9,da7) //OS device
<USB Flash DISK 1100> at scbus6 target 0 lun 0 (pass10,da8) //OS device

Update process followed:
- Backed up /data/geli/* and config file
- Downloaded latest ISO, created bootable USB with it
- Booted from the flash, selected two new 16GB sticks (mirror) and performed installation
- After system start i've uploaded config and system restarted and performed DB update
- I saw some error message during the proccess but it was too fast. It did not repeated after another reboot.
- Restored /data/geli/*
- Both pools were already visible under volumes so i did not "imported" but just attempted to unlock and got error mentioned above, pool unlocked anyway.


So, jus tignore, or ignore but report or do some more diggin' ?

Thanks

HolyK

 

[dlavigne]

You shouldn't be getting a traceback so that should be reported in a bug report.

 

[HolyK]

Ok, done - #9333 ... i'll keep the second pool locked just to be safe

 

[HolyK]

Eeeeh, i can not update the bugreport any more after the latest William's comment.

BTW: I did another restart and the error did not occurred any more. Both pools unlocked w/o issues and are perfectly health, or at least they seem to be :]

 

[cyberjock]

I can't even access that bug ticket!

 

[Ericloewe]

I can't even access that bug ticket!

Works fine for me.

 

[cyberjock]

Yeah, someone is messing with stuff in the bug system I think. It works for me now too.