From owner-freebsd-fs@FreeBSD.ORG  Tue Jan  6 15:50:45 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CE680D46
 for <freebsd-fs@freebsd.org>; Tue,  6 Jan 2015 15:50:45 +0000 (UTC)
Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.123])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "smtp-sofia.digsys.bg",
 Issuer "Digital Systems Operational CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 5977B6CA
 for <freebsd-fs@freebsd.org>; Tue,  6 Jan 2015 15:50:45 +0000 (UTC)
Received: from dcave.digsys.bg (dcave.digsys.bg [193.68.6.1])
 (authenticated bits=0)
 by smtp-sofia.digsys.bg (8.14.6/8.14.6) with ESMTP id t06FmeRE015964
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-fs@freebsd.org>; Tue, 6 Jan 2015 17:48:40 +0200 (EET)
 (envelope-from daniel@digsys.bg)
Message-ID: <54AC03D7.2020603@digsys.bg>
Date: Tue, 06 Jan 2015 17:48:39 +0200
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Subject: Re: zfs corruption after controller failure
References: <CALpPS7NiHJQ09KmitupYyixRYbPtdvVbVRCOPAqXUtqmSd4BVw@mail.gmail.com>
 <20FB5F2C-65D2-4F33-8D45-DD7FC34A5E2E@ultra-secure.de>
 <CALpPS7MObKeFPFYL7dMiGcKG40tFmJELCo782rWPO8wqcGtwmw@mail.gmail.com>
 <54ABFA82.2070401@internetx.com>
 <CALpPS7N-YUhJZUXaeJPY4aks+b_D1oLZ11+HxfHt2pnmJicaQw@mail.gmail.com>
 <54ABFF51.50708@internetx.com>
 <CALpPS7PPTSzZgVViy_8_4JosDsTxZ-RkbJJKt_SdBt27cLG1gg@mail.gmail.com>
In-Reply-To: <CALpPS7PPTSzZgVViy_8_4JosDsTxZ-RkbJJKt_SdBt27cLG1gg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 15:50:45 -0000



On 06.01.15 17:35, Fervent Dissent wrote:
> # zpool import -d /dev/diskid/
> #
> no error, no import

You do not need to use -d here, ZFS will try to look at all possible
block devices and will eventually find the metadata all by itself.

Maybe, you had some labeling on the disk? Or some partition (not
starting from block 0) on it, which contained your ZFS pool. In order to
ZFS to see the pool, you will need to recreate that partition first.

Your earlier post shows MBR partitioning, but not partition? Perhaps you
just need to remember what the partition was?

Daniel