On Mon, Sep 21, 2009 at 3:37 AM, <casper....@sun.com> wrote: > > > > >The disk has since been replaced, so now: > >k...@localhost:~$ pfexec zpool import > > pool: chronicle > > id: 11592382930413748377 > > state: DEGRADED > >status: One or more devices contains corrupted data. > >action: The pool can be imported despite missing or damaged devices. The > > fault tolerance of the pool may be compromised if imported. > > see: http://www.sun.com/msg/ZFS-8000-4J > >config: > > > > chronicle DEGRADED > > raidz2 DEGRADED > > c9t2d0 FAULTED corrupted data > > c9t1d0 ONLINE > > c9t0d0 ONLINE > > c9t4d0 ONLINE > > c9t5d0 ONLINE > > c9t3d0 ONLINE > > > >but "pfexec zpool import -f chronicle" still fails with the same message. > > > > That sounds like a bug; if ZFS can recover then zpool import should > also work. > > So what was wrong with the broken disk? Not just badly plugged in? > > Cas[er > > The disk physically failed. When I powered the system on, it made frighteningly loud clicking sounds and would not be acknowledged by any system I was running, like it wasn't even there.
- Kyle
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
