raidz2 + encryption + faulted drive; re-importing & resilvering 11.1-U4

[bitsquirrel]

Hello so I have an encrypted raidz2 pool with a faulted drive (da0).

I wanted to upgrade the entire array, but ran into snags.
What I did was, detach the entire array, reboot, and attempt to get the new drives to work.
The new 12TB SAS drives appear to not spin up; I think that is a "pin3 PWDIS" problem here:
https://www.tomshardware.com/news/hdd-sata-power-disable-feature,36146.html

Anyway, that's only one of my concerns. The second is how I got the array back up.
I'm running FreeNAS 11.1-U4.
On bootup the volume wasn't there - no surprise since I hadn't detached it.
When I tried to import the pool with 7/8 drives, I got an error that a particular volume was missing in the GUI.
I tried dropping down into shell, and did:
geli attach -K /path/to/geli.key -p /dev/da1 # for da1..da7
The weird thing was, it didn't seem to prompt for a passphrase at this point.
Then I did a:
zpool import -d /dev/; zpool import -f bu
Which I found here: https://github.com/zfsonlinux/zfs/issues/5567
And that seems to work:

Code:

# zpool status
  pool: bu
 state: DEGRADED
status: One or more devices could not be opened.  Sufficient replicas exist for
		the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://illumos.org/msg/ZFS-8000-2Q
  scan: scrub repaired 0 in 0 days 10:02:29 with 0 errors on Sun Aug  5 10:02:55 2018
config:
		NAME					  STATE	 READ WRITE CKSUM
		bu						DEGRADED	 0	 0	 0
		  raidz2-0				DEGRADED	 0	 0	 0
			13617012186723571818  UNAVAIL	  0	 0	 0  was /dev/gptid/d00af52c-f3f4-11e7-a858-001fbc11f330.eli
			da1p2.eli			 ONLINE	   0	 0	 0
			da2p2.eli			 ONLINE	   0	 0	 0
			da3p2.eli			 ONLINE	   0	 0	 0
		  raidz2-1				ONLINE	   0	 0	 0
			da4p2.eli			 ONLINE	   0	 0	 0
			da5p2.eli			 ONLINE	   0	 0	 0
			da6p2.eli			 ONLINE	   0	 0	 0
			da7p2.eli			 ONLINE	   0	 0	 0

So this looks good. But it's not showing up in the GUI.
Now to replace the faulted drive? First I check the partitioning.

Code:

# gpart show /dev/da1
=>		40  7814037088  da1  GPT  (3.6T)
		  40		  88	   - free -  (44K)
		128	 4194304	1  freebsd-swap  (2.0G)
	4194432  7809842688	2  freebsd-zfs  (3.6T)
  7814037120		   8	   - free -  (4.0K)

That's the default, I guess, since I didn't set up swap partitions specifically.
I copied the partitioning from da1 to da0 as so:
gpart backup da1 | gpart restore -F da0
Which I found here:
https://forums.freebsd.org/threads/copying-partitioning-to-new-disk.60937/
And then, I'm about to initialize geli on... I guess it'd be /dev/da0p2?
geli init -K /root/save/geli.key /dev/da0p2
But then I realize I don't really know what I'm doing, and I decided to stop before going any further.
Can anyone tell me how to know exactly what FreeNAS did by default when I set up the encrypted raidz2 and how to replace this faulted drive?

In case it helps:

Code:

# geli list da1p2.eli
Geom name: da1p2.eli
State: ACTIVE
EncryptionAlgorithm: AES-XTS
KeyLength: 256
Crypto: hardware
Version: 7
UsedKey: 0
Flags: NONE
KeysAllocated: 932
KeysTotal: 932
Providers:
1. Name: da1p2.eli
   Mediasize: 3998639452160 (3.6T)
   Sectorsize: 4096
   Mode: r1w1e1
Consumers:
1. Name: da1p2
   Mediasize: 3998639456256 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1

 

[m0nkey_]

Replacing an encrypted drive is covered in the documentation: http://doc.freenas.org/11/storage.html#replacing-an-encrypted-drive

 

[pro lamer]

Correct me if I am wrong but I guess ATM the case of the OP seems to need a bit more care than just following the manual since sth has been done already via command line.

Sent from my mobile phone

 

[bitsquirrel]

Yeah I read that, but I can't view the volume in the GUI because of the faulted drive causing an import failure, so I can't do GUI-based steps. Unless I can somehow trick the GUI into acknowledging this pool is there and online.

 

[pro lamer]

Unless I can somehow trick the GUI into acknowledging this pool is there and online.

There is some old thread:

I will export

Code:

# zpool export poolname

And finally, bring it in to the GUI with the autoimporter so FreeNAS can use it.

but I don't know if it is safe or up to date... Unless someone else confirms I would treat that one as a last resort solution...

Sent from my mobile phone

 

[bitsquirrel]

Turns out that upgrading to latest FreeNAS fixed the "faulted volume import" problem. Thanks!