Failed SLOG disk

[Honza M.]

Hello,
can someone help. After power down and power up I fount, that ZIL disk failed. I tried connect them to my pc but not working. I try everything what i found but not success and at this time i cannot import Pool. Is there a procedure, how to remove ZIL disk and import pool whithout them.

Thank you very much.
Honza


[root@freenas] ~# zpool import
pool: Volume1
id: 15489944136667600351
state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
devices and try again.
see: http://illumos.org/msg/ZFS-8000-6X
config:

Volume1 UNAVAIL missing device
raidz2-0 ONLINE
gptid/46addbd5-1e6a-11e5-b936-001e67a722ed ONLINE
gptid/4750c596-1e6a-11e5-b936-001e67a722ed ONLINE
gptid/47ebb391-1e6a-11e5-b936-001e67a722ed ONLINE
gptid/48871993-1e6a-11e5-b936-001e67a722ed ONLINE
gptid/491e1a19-1e6a-11e5-b936-001e67a722ed ONLINE
gptid/49b8db39-1e6a-11e5-b936-001e67a722ed ONLINE
cache
gptid/49dc2143-1e6a-11e5-b936-001e67a722ed

Additional devices are known to be part of this pool, though their
exact configuration cannot be determined.

 

[Honza M.]

So I found correct procedure. If someone will look for, there it is

[root@freenas] ~# zpool import -m Volume1
[root@freenas] ~# zpool status
pool: Volume1
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 1h46m with 0 errors on Sun Dec 13 01:46:17 2015
config:

NAME STATE READ WRITE CKSUM
Volume1 DEGRADED 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/46addbd5-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/4750c596-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/47ebb391-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/48871993-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/491e1a19-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/49b8db39-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
logs
4482330999645640905 UNAVAIL 0 0 0 was /dev/gptid/4b6fceb7-1e6a-11e5-b936-001e67a722ed
cache
gptid/49dc2143-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0

errors: No known data errors

pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Fri Dec 25 03:45:04 2015
config:

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

errors: No known data errors
[root@freenas] ~# zpool clear Volume1
[root@freenas] ~# zpool remove Volume1 4482330999645640905
[root@freenas] ~# zpool status
pool: Volume1
state: ONLINE
scan: scrub repaired 0 in 1h46m with 0 errors on Sun Dec 13 01:46:17 2015
config:

NAME STATE READ WRITE CKSUM
Volume1 ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/46addbd5-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/4750c596-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/47ebb391-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/48871993-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/491e1a19-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
gptid/49b8db39-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0
cache
gptid/49dc2143-1e6a-11e5-b936-001e67a722ed ONLINE 0 0 0

errors: No known data errors

pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Fri Dec 25 03:45:04 2015
config:

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

errors: No known data errors
[root@freenas] ~#

 

[jgreco]

That's not actually the correct procedure. To detach a SLOG device, you should use the GUI and simply detach the device. This allows the middleware to understand what's going on.

 

[velocity08]

That's not actually the correct procedure. To detach a SLOG device, you should use the GUI and simply detach the device. This allows the middleware to understand what's going on.

@jgreco
what if its not showing in the GUI any more?

Had a similar issue with test box we where working on with a RaidZ 4 drives + single ZIL.
We removed the ZIL intentionally to see what would happen.
The Pool was no longer visable in the GUI and we where not able to import via GUI.

What's the correct procedure in this instance when the ZIL drive dies or is removed without being gracefully removed from the pool?

""Cheers
G

 

[jgreco]

You probably need to use the CLI to forcibly detach or reattach or whatever the appropriate resolution is.

Loss of a SLOG device shouldn't be a fatal issue, to the best of my knowledge.