Pool not unlockable after update (11.2U6->11.3U1), but maybe it was not working before

[senior_hombre]

Hi,
my freeNAS (11.2 U6) was not responding lately, i also had this alert:
"Boot Pool Status Is ONLINE: One or more devices has experienced an error resulting in data corruption. Applications may be affected."

The data corruption seems to be on the usb-boot-drive, so i stored my config and prepared for a reinstallation of freeNAS on a new usb-stick. But before i do that (because i am currently waiting for the new usb drive to arrive via mail) i wanted to see if updateing the system from 11.2 U6 to 11.3 U7 has any effect. The update itself went well, i also got this new error after the reboot:
"Boot Pool Status Is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected."

But the real problem is, i cannot unlock my storage volume pool!

When i click on storage->pool i can select the pool and click "unlock" then i type in my password but i just get the message: "error unlocking".
There are no error messages in the console.

On Storage->Discs i can see all my harddrives, btw.

I do not now what is wrong here, what can i try next?

 

[PhiloEpisteme]

Hi @senior_hombre, check out my resource about debugging encryption problems. If you are not able to resolve your issue from that reply here with the commands you ran and their full output, those debugging steps will be super helpful.

My guess is that when you upgraded your system you neglected to restore your encryption keys. Check the User Guide on information about encryption and the importance of backing up your keys so that you can unlock the pool in sort of situation.

 

[senior_hombre]

I did saved the encryption keys... i have a file called geli and from and older backup also a recovery file.

I tried the first command from your guide (Identifying Disks) and got no result at all.

gpart show gives me this:

Code:

=>        34  7814037101  ada0  GPT  (3.6T)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)
  7814037128           7        - free -  (3.5K)

=>        34  7814037101  ada1  GPT  (3.6T)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)
  7814037128           7        - free -  (3.5K)

=>        34  7814037101  ada2  GPT  (3.6T)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)
  7814037128           7        - free -  (3.5K)

=>        34  7814037101  ada3  GPT  (3.6T)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)
  7814037128           7        - free -  (3.5K)

=>        34  7814037101  ada4  GPT  (3.6T)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)
  7814037128           7        - free -  (3.5K)

=>        34  7814037101  ada5  GPT  (3.6T)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)
  7814037128           7        - free -  (3.5K)

=>      34  31266749  da0  GPT  (15G)
        34      1024    1  freebsd-boot  (512K)
      1058         6       - free -  (3.0K)
      1064  31265712    2  freebsd-zfs  (15G)
  31266776         7       - free -  (3.5K)

The Identifying the correct Key(s) command also gives no result.

 

[PhiloEpisteme]

When you say gives no result what do you mean? Can you paste the full commands and output? Even if it is empty output.

 

[jeto]

I got the same error and figured out it was just the way my browser was interacting with the unlock dialog. Try to use another browser to unlock.

 

[PhiloEpisteme]

@jeto that is interesting indeed. What version of FreeNAS have you experienced this with and what browser? What was the interaction like?

 

[senior_hombre]

I got the same error and figured out it was just the way my browser was interacting with the unlock dialog. Try to use another browser to unlock.

Thank you, works for me!
Firefox was not working but chromium does!

edit: I am using freeNAS 11.3U1 (current stable train release)
Firefox is version: 74.0 (does not work)
and Chromium: 80.0.3987.132 (openSUSE Build) (unlocking works)
my OS: openSUSE Tumbleweed

 

[senior_hombre]

When you say gives no result what do you mean? Can you paste the full commands and output? Even if it is empty output.

I was right back at the prompt, no output from the command whatsoever... just copied the command from the code-block in the guide

 

[senior_hombre]

But i think this is a good time to check if there are still any corrupted files or broken devices... so what can i do to check all of them?

zpool status -v:

Code:

pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:10:56 with 0 errors on Fri Mar 20 16:45:51 2020
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          da0p2     ONLINE       0     0     0

errors: No known data errors

  pool: volume1
 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 0 days 03:07:04 with 0 errors on Sun Mar 15 12:07:06 2020
config:

        NAME                                                STATE     READ WRITE CKSUM
        volume1                                             ONLINE       0     0     0
          raidz2-0                                          ONLINE       0     0     0
            gptid/866e6a31-0b69-11e4-ba7c-d050992651aa.eli  ONLINE       0     0     0
            gptid/87541e15-0b69-11e4-ba7c-d050992651aa.eli  ONLINE       0     0     0
            gptid/8836f602-0b69-11e4-ba7c-d050992651aa.eli  ONLINE       0     0     0
            gptid/89146692-0b69-11e4-ba7c-d050992651aa.eli  ONLINE       0     0     0
            gptid/89f40bcc-0b69-11e4-ba7c-d050992651aa.eli  ONLINE       0     0     0
            gptid/8ad5782b-0b69-11e4-ba7c-d050992651aa.eli  ONLINE       0     0     0

errors: No known data errors

 

[jeto]

@jeto that is interesting indeed. What version of FreeNAS have you experienced this with and what browser? What was the interaction like?

It occured during the upgrade from 11..2-U7 to 11.3 Release. I got a "error unlocking" and sadly dont have a screenshot of the rest of the error. I looked it up and find the browser tip. I think this bug is adressed in 11.3-U1 but can´t find a ticket for it.

 

[jeto]

It occured during the upgrade from 11..2-U7 to 11.3 Release. I got a "error unlocking" and sadly don't have a screenshot of the rest of the error. I looked it up and find the browser tip. I think this bug is adressed in 11.3-U1 but can´t find a ticket for it.

Found it: Jira Ticket . It occured in Safari under macOS.

 

[PhiloEpisteme]

But i think this is a good time to check if there are still any corrupted files or broken devices... so what can i do to check all of them?

A scrub will determine if your pool is in fine shape.

 

[PhiloEpisteme]

Hi @jeto I wanted to follow up with something I recently learned. There exists a significant bug in 11.3-U1 and 11.3-U2 where if you have a locked, encrypted pool and export a different pool it will wipe your locked, encrypted pool. You can find the bug report here; the fix here; and release notes referring to it in 11.3-U2.1.