Can anyone explain how the following came about, and/or how to get rid of it?> # zpool import > pool: zboot > id: 13206787560157218571 > state: UNAVAIL > action: The pool cannot be imported due to damaged devices or data. > config: > > zboot UNAVAIL insufficient replicas > mirror UNAVAIL corrupted data > c5t0d0s1 ONLINE > c5t4d0s0 ONLINE > > pool: zboot > id: 10153722744283128478 > state: UNAVAIL > action: The pool cannot be imported due to damaged devices or data. > config: > > zboot UNAVAIL insufficient replicas > mirror UNAVAIL corrupted data > c5t0d0s0 ONLINE > c5t4d0s0 ONLINE > # zpool import -f zboot > cannot import ''zboot'': more than one matching pool > import by numeric ID instead > # zpool import -f 10153722744283128478 zboot1 > cannot import ''zboot'' as ''zboot1'': invalid vdev configuration > # zpool import -f 13206787560157218571 zboot1 > cannot import ''zboot'' as ''zboot1'': invalid vdev configuration >I was trying to get zfsboot working on an x4500, and after fighting with it for 3 days, discovered this. Any ideas? -Drew
Drew Schatt wrote:> Can anyone explain how the following came about, and/or how to get rid > of it? >What does zdb show? Also, do the partitions look like for c5t0d0? Did something get overlapped? Regards, markm
On Mar 21, 2008, at 7:20 PM, Mark J Musante wrote:> Drew Schatt wrote: >> Can anyone explain how the following came about, and/or how to get >> rid of it? >> > > What does zdb show? Also, do the partitions look like for c5t0d0? > Did something get overlapped?This came about after attempting to use zfsboot from a jumpstart image on two different thumpers. Basically, it was completely boned, probably due to a typo during one of the various jumpstart attempts. However, I was extremely confused by the fact that c5t4d0 was the mirror on both pools, and that both of them had the same name (zboot). Also, it''s completely impossible to drop the zboot pool from the systems, I had to use fdisk to delete the fdisk partition on all 48 drives to get rid of the problem. Thought I''d put it out for others to see. My personal thought is that the zfsboot stuff doesn''t have quite the same error checking that the normal zfs tools do. Thanks. -Drew