Trying to unlock volume causes reboot?

[Johan H]

Hi,

FreeNAS 9.10.2-U1

A power failure forced me to shutdown one of our FreeNAS servers. It was a correct controlled shutdown. The server is on UPS also.

After power was restored, the server was started up. After boot, I need to unlock the encrypted volume, as always. I enter the password and after few seconds, the server does not respond.
Ping is lost also. I assume the server is somehow rebooting? After reboot, I try to unluck again (GUI). Same result, server reboots.
Tested to boot 9.10.2 instead, same result, unlock = reboot.
Why is this happening?

Any ideas on how to proceed?
Can I unlock the volume from a shell and maybe see error messages?
Is there a log I can check for error messages?

 

[dlavigne]

Hardware specs?

Anything related in /var/log/messages?

 

[Johan H]

It's a HP NL54 with 4 Seagate Enterprise NAS 4Tb disks, running as a "backup replication" server to our main FreeNAS.

In the message file there is only the latest startup log, I can't see anything wrong in it.

I activated the "Show console messages in the footer:" function.
After boot, the last part of the log, before trying to unlock to volumes:

Feb 17 13:30:47 freenas2 kernel: bge0: link state changed to DOWN
Feb 17 13:30:47 freenas2 kernel: bge0: link state changed to DOWN
Feb 17 13:30:47 freenas2 kernel: bge0: link state changed to UP
Feb 17 13:30:47 freenas2 kernel: bge0: link state changed to UP
Feb 17 13:30:47 freenas2 ums0: <Mouse> on usbus3
Feb 17 13:30:47 freenas2 ums0: 3 buttons and [Z] coordinates ID=0
Feb 17 13:30:47 freenas2 ums1: <Mouse REL> on usbus3
Feb 17 13:30:47 freenas2 ums1: 3 buttons and [XYZ] coordinates ID=0
Feb 17 13:30:48 freenas2 GEOM_ELI: Device ada0p1.eli created.
Feb 17 13:30:48 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:30:48 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:30:48 freenas2 GEOM_ELI: Device ada1p1.eli created.
Feb 17 13:30:48 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:30:48 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:30:48 freenas2 GEOM_ELI: Device ada2p1.eli created.
Feb 17 13:30:48 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:30:48 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:30:49 freenas2 GEOM_ELI: Device ada3p1.eli created.
Feb 17 13:30:49 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:30:49 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:30:49 freenas2 ntpd[1873]: ntpd 4.2.8p9-a (1): Starting
Feb 17 13:30:54 freenas2 root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Feb 18 00:00:00 freenas2 syslog-ng[1451]: Configuration reload request received, reloading configuration;

When I try to unlock to volume, the console shows the following messages and then reboots the server:
(13:28 I unlocked the volume, the above log 13:30 is the log when the server has rebooted)

Feb 17 13:28:20 freenas2 GEOM_ELI: Device gptid/a9b8be21-6038-11e5-b113-2c27d715587d.eli created.
Feb 17 13:28:20 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:28:20 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:28:22 freenas2 GEOM_ELI: Device gptid/aaceb712-65b4-11e5-b9a6-2c27d715587d.eli created.
Feb 17 13:28:22 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:28:22 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:28:24 freenas2 GEOM_ELI: Device gptid/4bfdcab9-6741-11e5-96fe-2c27d715587d.eli created.
Feb 17 13:28:24 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:28:24 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:28:26 freenas2 GEOM_ELI: Device gptid/25ae14da-6b22-11e5-901f-2c27d715587d.eli created.
Feb 17 13:28:26 freenas2 GEOM_ELI: Encryption: AES-XTS 128
Feb 17 13:28:26 freenas2 GEOM_ELI: Crypto: software
Feb 17 13:28:27 freenas2 ZFS: vdev state changed, pool_guid=6884818884109338728 vdev_guid=8640593125221120681
Feb 17 13:28:27 freenas2 ZFS: vdev state changed, pool_guid=6884818884109338728 vdev_guid=4819973807021938455
Feb 17 13:28:27 freenas2 ZFS: vdev state changed, pool_guid=6884818884109338728 vdev_guid=2709979057187919346
Feb 17 13:28:27 freenas2 ZFS: vdev state changed, pool_guid=6884818884109338728 vdev_guid=6976031324072986850

 

[Johan H]

Still have not been able to unlock my drives... :-(
Any ideas?

I don't know if it matters, but I should add that during the shutdown, a replication from another FreeNAS was in progress.
It was interupted by the shutdown.

 

[dlavigne]

If you still haven't resolved this, it is worth making a bug report at bugs.freenas.org. If you report it, please post the bug # here.

 

[Johan H]

Reported as a bug, #21816