Import fails: One or more devices are missing from the system.

[Rand]

Hi,

made a small mistake the other day and removed one of my log devices from a log mirror (at least i believe thats the issue).
After the next reboot the pool does not import any more:

Code:

zpool import
  pool: main
  id: 532750682860831602
  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:

  main  UNAVAIL  missing device
  mirror-0  ONLINE
  gptid/1e5d4965-fffb-11e5-be2a-000c2989f189  ONLINE
  gptid/205119e1-fffb-11e5-be2a-000c2989f189  ONLINE
  mirror-1  ONLINE
  gptid/3bbfa689-fffb-11e5-be2a-000c2989f189  ONLINE
  gptid/3daa8d02-fffb-11e5-be2a-000c2989f189  ONLINE
  mirror-2  ONLINE
  gptid/8ab274f1-fffb-11e5-be2a-000c2989f189  ONLINE
  gptid/8ca8cfeb-fffb-11e5-be2a-000c2989f189  ONLINE
  mirror-3  ONLINE
  gptid/a5a9f463-fffb-11e5-be2a-000c2989f189  ONLINE
  gptid/a78b5d84-fffb-11e5-be2a-000c2989f189  ONLINE
  logs
  gptid/db869fad-fffb-11e5-be2a-000c2989f189  ONLINE

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

If I had realized that while it was still online it would have been no problem to simply remove the log, but i cant do that on the offline pool.

I tried import -m but same error

Code:

zpool import -m main
cannot import 'main': one or more devices is currently unavailable

Code:

zdb -e main

Configuration for import:
  vdev_children: 6
  version: 5000
  pool_guid: 532750682860831602
  name: 'main'
  state: 0
  hostid: 2647831905
  hostname: ''
  vdev_tree:
  type: 'root'
  id: 0
  guid: 532750682860831602
  children[0]:
  type: 'mirror'
  id: 0
  guid: 5466945668241505192
  metaslab_array: 35
  metaslab_shift: 34
  ashift: 12
  asize: 2998440558592
  is_log: 0
  create_txg: 4
  children[0]:
  type: 'disk'
  id: 0
  guid: 10230651672595624498
  whole_disk: 1
  create_txg: 4
  path: '/dev/gptid/1e5d4965-fffb-11e5-be2a-000c2989f189'
  children[1]:
  type: 'disk'
  id: 1
  guid: 1756527158647505143
  whole_disk: 1
  create_txg: 4
  path: '/dev/gptid/205119e1-fffb-11e5-be2a-000c2989f189'
  children[1]:
  type: 'mirror'
  id: 1
  guid: 6508896232805161185
  metaslab_array: 39
  metaslab_shift: 34
  ashift: 12
  asize: 2998440558592
  is_log: 0
  create_txg: 17
  children[0]:
  type: 'disk'
  id: 0
  guid: 8385470632227501328
  whole_disk: 1
  create_txg: 17
  path: '/dev/gptid/3bbfa689-fffb-11e5-be2a-000c2989f189'
  children[1]:
  type: 'disk'
  id: 1
  guid: 4828272328576782523
  whole_disk: 1
  create_txg: 17
  path: '/dev/gptid/3daa8d02-fffb-11e5-be2a-000c2989f189'
  children[2]:
  type: 'mirror'
  id: 2
  guid: 8836469145574395383
  metaslab_array: 41
  metaslab_shift: 34
  ashift: 12
  asize: 2998440558592
  is_log: 0
  create_txg: 46
  children[0]:
  type: 'disk'
  id: 0
  guid: 8992288263158221271
  whole_disk: 1
  create_txg: 46
  path: '/dev/gptid/8ab274f1-fffb-11e5-be2a-000c2989f189'
  children[1]:
  type: 'disk'
  id: 1
  guid: 6766208102785060191
  whole_disk: 1
  create_txg: 46
  path: '/dev/gptid/8ca8cfeb-fffb-11e5-be2a-000c2989f189'
  children[3]:
  type: 'mirror'
  id: 3
  guid: 4515601781343340735
  metaslab_array: 44
  metaslab_shift: 34
  ashift: 12
  asize: 2998440558592
  is_log: 0
  create_txg: 57
  children[0]:
  type: 'disk'
  id: 0
  guid: 15032685074879007814
  whole_disk: 1
  create_txg: 57
  path: '/dev/gptid/a5a9f463-fffb-11e5-be2a-000c2989f189'
  children[1]:
  type: 'disk'
  id: 1
  guid: 1328111502974125995
  whole_disk: 1
  create_txg: 57
  path: '/dev/gptid/a78b5d84-fffb-11e5-be2a-000c2989f189'
  children[4]:
  type: 'missing'
  id: 4
  guid: 0
  children[5]:
  type: 'disk'
  id: 5
  guid: 13566463784014113451
  whole_disk: 1
  metaslab_array: 47
  metaslab_shift: 31
  ashift: 12
  asize: 399995043840
  is_log: 1
  create_txg: 79
  path: '/dev/gptid/db869fad-fffb-11e5-be2a-000c2989f189'
zdb: can't open 'main': No such file or directory

I tried simply attaching the old log ssd again but its not being recognized any more since it has been used in another system already :/

Anything I can do to fix this? Or is that drop pool and load data from backup ?

Thanks:)

 

[ethereal]

-m Allows a pool to import when there is a missing log device.
Recent transactions can be lost because the log device will
be discarded.

https://www.freebsd.org/cgi/man.cgi?zpool(8)

 

[Rand]

Thanks but tried that, see OP, didn't help;)

 

[ethereal]

yeah sorry i just noticed that

 

[Rand]

no problem, thanks for trying:)

 

[ethereal]

if you have problems with reattaching the ssd log because it was in another system was that a zfs ?

because zpool labelclear might help

zpool labelclear [-f] device

Removes ZFS label information from the specified device. The device
must not be part of an active pool configuration.

-f Treat exported or foreign devices as inactive.

 

[Rand]

No, ESX VSan.

Hm might work nevertheless.
I'll give it a try.

 

[ethereal]

if you get the labelclear maybe you can add it again

 

[ethereal]

did you try import -f main ?

zpool import [-o mntopts] [-o property=value] ... [-d dir | -c cachefile]
[-D] [-f] [-m] [-N] [-R root] [-F [-n]] pool | id [newpool]

Imports a specific pool. A pool can be identified by its name or the
numeric identifier. If newpool is specified, the pool is imported
using the name newpool. Otherwise, it is imported with the same name
as its exported name.

If a device is removed from a system without running "zpool export"
first, the device appears as potentially active. It cannot be deter-
mined if this was a failed export, or whether the device is really in
use from another host. To import a pool in this state, the -f option
is required.

 

[Rand]

Yes, same result as -m.
And labelclear did not help either.

 

[ethereal]

zpool import

-F Recovery mode for a non-importable pool. Attempt to return
the pool to an importable state by discarding the last few
transactions. Not all damaged pools can be recovered by using
this option. If successful, the data from the discarded
transactions is irretrievably lost. This option is ignored if
the pool is importable or already imported.

 

[ethereal]

you could possibly try exporting then importing your pool

 

[Rand]

-F same error, and how would i export it when its not known to the system because it cant be imported?:)

 

[MrToddsFriends]

made a small mistake the other day and removed one of my log devices from a log mirror (at least i believe thats the issue).

Out of curiosity: Any further insight what actually went wrong? I would have expected that a missing device from a mirror SLOG would not have catastrophic consequences (admittedly I never used SLOG devices so far).

Were you able to import your pool or did you have to go the restore from backup route?

 

[Rand]

Nope -> restore is still running;)

 

[rs225]

Did you try -f -m ? You might have needed both.

 

[Rand]

yep, same error message

 

[rs225]

Very strange. Did you ever try it with both SLOGs removed?

 

[Rand]

Yep, no luck either :/

 

[cyberjock]

Are there any missing vdevs in that zpool import list? The message its spitting out is normally a sign of disks/vdevs being unavailable. Being that no vdevs are appearing with disks missing I have to assume that vdevs are missing.