zpool status -v shows:
Server:~ busty$ zpool status -v
status: One or more devices is currently being resilvered. The pool
will continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scrub: resilver in progress, 0,98% done, 26h14m to go
NAME STATE READ WRITE CKSUM
Collection DEGRADED 0 0 0
raidz1 DEGRADED 0 0 0
disk3s2 ONLINE 0 0 0
disk5s2 ONLINE 0 0 0
disk7s2 ONLINE 0 0 0
disk1s2 ONLINE 0 0 0
replacing DEGRADED 0 0 0
806745480046791602 FAULTED 0 0 0 was/dev/disk5s2
disk4 ONLINE 0 0 0
disk2s2 ONLINE 0 0 0
disk6s2 ONLINE 0 0 0
errors: No known data errors
Good info about letting the disk to be replaced in place until it's
done. My time was running up to send the disk away and it's somewhat
easier to just swap the disks, but I do have a spare SATA-port, so I
could do it the safer way next time.
Meanwhile, what to do with the "no such device in pool"?
On 15.10.14 20:49, Bjoern Kahl wrote:
> Hi 'Busty',
> Am 15.10.14 um 20:32 schrieb 'Busty' via zfs-macos:
>> In my pool, I had a disk that got a smart error (bad block), so
>> I pulled it out, installed a new one and made a "zpool replace
>> disk5s2 806745480046791602". (That number was shown when typing
>> "zpool status" as the missing device.)
>> The resilver process started, but it seems that the new disk is
>> faulty, because it disappears from the device list infrequently,
>> but still at least every 6 hours (I have Temperature Monitor
>> running which shows me all disks by serial number).
>> So I want to change it. But zpool detach <poolname> dev/disk5s2
>> gives the error "no such device in pool".
>> How can I abort the resilvering process? Or is there another way
>> to restart the resilvering with a new disk?
> Usually I would do in this situation exactly what you described:
> Detach the disk and attach a new one.
> "zpool detach" is supposed to detach any disk that can logically
> be detached (i.e. does not remove data that is stored only on that
> To diagnose further, you would need to show us "zpool status -v".
>> The original disk with the bad block is already on its way to
>> Western Digital (it was still in warranty).
> Generally, it is more wise to do the replace with the faulty disk
> still present. In case of trouble with another disk, it still
> holds most of the data and can provide good block if needed by the
> resilver process.
> Best regards
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.