On 2013-Jan-08 21:30:57 -0800, John Giannandrea wrote:
>Notice that in the absence of the faulted da2 the OS has assigned da3 to da2
>etc. I suspect this was part of the original problem in creating a label with
>two da2s
The primary vdev identifier is tha guid. Tha path is of secondary
impor
Gregg Wonderly wrote:
> Have you tried importing the pool with that drive completely unplugged?
Thanks for your reply. I just tried that. zpool import now says:
pool: d
id: 13178956075737687211
state: FAULTED
status: The pool metadata is corrupted.
action: The pool cannot be im
Have you tried importing the pool with that drive completely unplugged? Which
HBA are you using? How many of these disks are on same or separate HBAs?
Gregg Wonderly
On Jan 8, 2013, at 12:05 PM, John Giannandrea wrote:
>
> I seem to have managed to end up with a pool that is confused abut
I seem to have managed to end up with a pool that is confused abut its children
disks. The pool is faulted with corrupt metadata:
pool: d
state: FAULTED
status: The pool metadata is corrupted and the pool cannot be opened.
action: Destroy and re-create the pool from
a backup source.
