Se a execução de sudo zpool clear WD_1TB
não funcionar, tente:
$ sudo zpool clear -nFX WD_1TB
onde esses parâmetros não documentados significam:
-F
: (undocumented forclear
, the same as forimport
) Rewind. 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.-n
: (undocumented forclear
, the same as forimport
) Used with the-F
recovery option. Determines whether a non-importable pool can be made importable again, but does not actually perform the pool recovery. For more details about pool recovery mode, see the -F option, above. and then try to re-import again:-X
(undocumented): Extreme rewind. The effect of -X seems to be that some extremely lengthy operation is attempted, that never finishes. In some cases, a reboot was necessary to terminate the process.-V
(undocumented): Option by UTSLing, when used forimport
it makes the pool got imported again, but still without an attempt at resilvering.
Fonte: Problema do pool com falhas do ZFS e man zpool
.
$ zpool import WD_1TB
Se não ajudar, tente os seguintes comandos para remover o zpool inválido:
$ zpool list -v
$ sudo zfs unmount WD_1TB
$ sudo zpool destroy -f WD_1TB
$ zpool detach WD_1TB disk1s2
$ zpool remove WD_1TB disk1s2
$ zpool remove WD_1TB /dev/disk1s2
$ zpool set cachefile=/etc/zfs/zpool.cache WD_1TB
Finalmente, se nada ajudar, remova o arquivo /etc/zfs/zpool.cache
(opcional) e reinicie o computador.
Relacionados:
- zfs-osx / zfs no GitHub: zpool: a E / S do conjunto está suspensa no momento
- zfsonlinux / zfs no GitHub: A remoção do dispositivo de cache falha
- Como se livrar da piscina fantasma?
- exportação e importação do zfs entre diferentes controladores
- Como eu gero o arquivo /etc/zfs/zpool.cache
- Universidade de Princeton: Solução de problemas do ZFS