Hi Rich,
I don't think anyone can say definitively how this problem resolved,
but I believe that the dd command overwrote some of the disk label,
as you describe below.
Your format output below looks like you relabeled the disk and maybe
that was enough to resolve this problem.
I have had succe
>How did you decide it is okay and that zfs saved you? Did you
>NOT post some further progress in your recovery?
I made no further recovery attempts, the pool imported cleanly after
rebooting, or so i thought [1] as a zpool status showed no errors and i
could read data from the drive again.
On
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Jim Klimov
>
> Purely speculating, I might however suggest that your disk was
> dedicated to the pool completely, so its last blocks contain
> spare uberblocks (zpool labels) and that might hel
2012-07-12 14:20, RichTea wrote:
I meant to use dd to copy an image (around 500Mb) to a USB disk but
instead wrote over a non raided zfs disk!
Below is various status output's: My question is how after a reboot did
the disk / zpool recover with from what I have seen so far no corruption
at all
Hi All,
I hope this is the correct place for this question as I think it was ZFS
that saved me.
A little while ago I did some thing very silly in a moment of non
concentration...
I meant to use dd to copy an image (around 500Mb) to a USB disk but instead
wrote over a non raided zfs disk!
This of
