Galen
2009-Aug-19 20:51 UTC
[zfs-discuss] Unable to import zpool - yet there should be enough parity!
I have a raidz1 zpool ("Companion") I am unable to import. One of the
disks has physically failed and cannot be recognized by any computer,
and it is unlikely physical repairs or data recovery is possible.
No other disks are reporting errors. One other disk (not the failed
one) threw occasional errors during random reads, so I did a block
level copy onto a new disk with identical capacity from another
machine while the Solaris box was offline. It completed with no errors
and the newly cloned disk works perfectly. (I''ve done this before on
other pools without issues.)
So, at this time, all but one of the disks is present and fully
functioning and reporting no errors. A raidz1 should be able to
tolerate one disk failure. I have tried turning ZFS recovery mode on,
as well as tried deleting /etc/zfs/zpool.cache.
Can anybody give me an idea why I can''t import the zpool? Anything I
can do to make it import, or at least recover the data?
----------
Below are some of the more useful bits of output from the Solaris box:
~~~
galen at solaribyte:~# zpool import
pool: Companion
id: 10109802473793101402
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see: http://www.sun.com/msg/ZFS-8000-EY
config:
Companion UNAVAIL insufficient replicas
raidz1 UNAVAIL corrupted data
c12d0p0 ONLINE
c8t0d0s2 ONLINE
c13d0p0 ONLINE
c7t0d0p0 ONLINE
c15d0p0 ONLINE
7254945103704914877 ONLINE
~~~
galen at solaribyte:~# zpool import -f 10109802473793101402
cannot import ''Companion'': invalid vdev configuration
~~~
galen at solaribyte:~# zpool import -f Companion
cannot import ''Companion'': invalid vdev configuration