From owner-freebsd-stable@freebsd.org Sun Jul 19 15:35:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A77009A57A5 for ; Sun, 19 Jul 2015 15:35:58 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37B781971 for ; Sun, 19 Jul 2015 15:35:58 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: by wibud3 with SMTP id ud3so70826762wib.1 for ; Sun, 19 Jul 2015 08:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=from:date:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=Nk0rmT6EVJ6s0fV++Dtout3RsdXnBgNwbE/JgtbxA70=; b=ZmF9NVl5OlCGWRkoAtGg91mlwEEPJSdN4VF4+VdVPkx1C+AMguryY6YchWMHRQWL6u TdBVg0HLDhxxi6sHwtydeCShaekSOi/fuNU9uLxwVmwUvFs6UH99GIDFm6koYZ39592J MyQdOywSDCxVeLSZqtKjTs1GkdiA726cNw18InYBignjsqzjdZm80Dzh0e+WrrbBCfgJ 1nkHpttI/Q3XSzvwMObnWZvYkJc7mStY8s8kvYkfIddDDKW/v3M0/jI0Bk5CGUub1Z4I 3T8cIOM5vyQW8RaRUMKvN5UA5kCJP2+2V9KTU8FfJllRFvVKmZepOeN+e1+2+zO09XqG sMJg== X-Received: by 10.194.120.198 with SMTP id le6mr48261010wjb.133.1437320156115; Sun, 19 Jul 2015 08:35:56 -0700 (PDT) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de. [188.193.109.133]) by smtp.gmail.com with ESMTPSA id ma15sm7427411wic.20.2015.07.19.08.35.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Jul 2015 08:35:55 -0700 (PDT) From: Marc UBM X-Google-Original-From: Marc "UBM" Bocklet Date: Sun, 19 Jul 2015 17:35:54 +0200 To: freebsd-stable Subject: Re: problem with geli and LSI controller Message-Id: <20150719173554.828f30bd2ae605897b7109e6@gmail.com> In-Reply-To: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 15:35:58 -0000 On Sun, 19 Jul 2015 17:34:32 +0200 Marc "UBM" Bocklet wrote: > Hi all, > > a few weeks ago our Highpoint Rocket Raid controller (hptrr) started > biting the dust (spurious channel resets). We bought a LSI 9201-16i > (mps) to replace it. Connected to the hptrr were 4 external e-sata > enclosures, configured in JBOD mode. Together with two disks connected > to the onboard SATA controller, this formed a geli encrypted raidz-2 > zpool. > Just now, I connected the disks to the mps controller. They show > up fine in dmesg. The problem is, when trying to attach the disks > formerly connected to the hptrr controller, geli is unable to find the > metadata on the disks and errors out with: > > "geli: Cannot read metadata from /dev/da4: Invalid argument" > > gpart show says "gpart: No such geom: da4" > > Trying to restore the geli metadata gives: > "geli: Provider size mismatch: wrong backup file?" > > Is it possible that the hptrr controller handled the disks in some > special way and it's only possible to read them there? > > Bye > Marc I forgot to add that the system is running: FreeBSD xxx 10.1-BETA1 FreeBSD 10.1-BETA1 #27 r271633: Mon Sep 15 22:34:05 CEST 2014 Bye Marc