From owner-freebsd-fs@FreeBSD.ORG Tue Jan 6 15:38:28 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B1D43F1 for ; Tue, 6 Jan 2015 15:38:28 +0000 (UTC) Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 36E9C2E5 for ; Tue, 6 Jan 2015 15:38:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id EB9A84C4C80C; Tue, 6 Jan 2015 16:38:25 +0100 (CET) X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de Received: from mx1.internetx.com ([62.116.129.39]) by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYt2XPeyVFEB; Tue, 6 Jan 2015 16:38:23 +0100 (CET) Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.internetx.com (Postfix) with ESMTPSA id 712A94C4C7E4; Tue, 6 Jan 2015 16:38:23 +0100 (CET) Message-ID: <54AC015D.50708@internetx.com> Date: Tue, 06 Jan 2015 16:38:05 +0100 From: InterNetX - Juergen Gotteswinter Reply-To: jg@internetx.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Fervent Dissent Subject: Re: zfs corruption after controller failure References: <20FB5F2C-65D2-4F33-8D45-DD7FC34A5E2E@ultra-secure.de> <54ABFA82.2070401@internetx.com> <54ABFF51.50708@internetx.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 15:38:28 -0000 Still using -T , why? Did you check the Zpool manpage? You wont find it there Good Luck, hope you got a Backup. Am 06.01.2015 um 16:35 schrieb Fervent Dissent: > # zpool import -d /dev/diskid/ > # > no error, no import > > # zpool import -d /dev/diskid/ -N -o readonly=on -f -R /tb -F -T 3697688 tb > cannot import 'tb': no such pool available > > > tb is the pool name, I'll try those scripts later > > On Tue, Jan 6, 2015 at 11:29 PM, InterNetX - Juergen Gotteswinter > > wrote: > > -T is an undocumentated and so for it should be considered as unstable > or even something which can easily break things. theres a reason why its > not documentated very likely. > > dl;dr - its something i whouldnt touch... > > What Output do you get from a simple zpool import ? You did everything > you tried until now with "readonly=on" ? > > If everything seems to be broken, you could give the zfs forensic > scripts a try... its already broken, cant get worse anymore. > > Am 06.01.2015 um 16:11 schrieb Fervent Dissent: > > I tried these, and some variations of them, and it gave the error the > > pool does not exist. > > zpool import -N -o readonly=on -f -R /pool > > zpool import -N -o readonly=on -f -R /pool -F -T > > > > On Tue, Jan 6, 2015 at 11:08 PM, InterNetX - Juergen Gotteswinter > > >> wrote: > > > > > external usb drive (for sure cheap consumer desktop one) > > > cheap (maybe even buggy) usb controller > > > non-mirrored / raidz > > > probably cheap hardware at all (no ecc, like rainer mentioned for example) > > > > what do you expect. zfs is very tolerant, but some basics should be > > taken care of... > > > > but even with a single disk it should be possible to recover / import > > the pool at least read only > > > > > > > > Am 06.01.2015 um 16:06 schrieb Fervent Dissent: > > > I've had power lose before and a previous bad controller cause > > multiple > > > problems. The drive would disappear or go offline. I would clear > > it and go > > > on no problem. This is the first failure that I have not been able to > > > recover from. > > > > > > On Tue, Jan 6, 2015 at 11:01 PM, Rainer Duffner > > > >> > > > wrote: > > > > > >> > > >>> Am 06.01.2015 um 15:58 schrieb Fervent Dissent < > > >> walkerindarkness@gmail.com > > >>: > > >>> > > >>> I have a external disk that was on a cheap usb controller, that > > >> controller > > >>> died. > > >> > > >> > > >> Maybe I’m mistaken, but I though that if your pool only has a > > single disk > > >> and that disk/pool shows errors or becomes > > unreadable/corrupted/whatever > > >> you cannot recover it. > > >> > > >> Same for not using ECC memory… > > >> > > >> > > >> > > >> > > > _______________________________________________ > > > freebsd-fs@freebsd.org > > > mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > > To unsubscribe, send any mail to > > "freebsd-fs-unsubscribe@freebsd.org > > > >" > > > > > > > > >