From nobody Thu Sep 16 20:39:08 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A3A9317CAD90 for ; Thu, 16 Sep 2021 20:39:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f45.google.com (mail-ot1-f45.google.com [209.85.210.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H9TTV46bLz4qrK for ; Thu, 16 Sep 2021 20:39:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f45.google.com with SMTP id x10-20020a056830408a00b004f26cead745so9945197ott.10 for ; Thu, 16 Sep 2021 13:39:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iCcvONmgHU1B1z+j82umw8gqHQ/1mq4KSMPEpVGSkPY=; b=bd/J8tVL+sqfr/c0FlYARDi/y7lTiqS+6yh2bGKFC3H7/dESnMB0JDFrWHWMOmx1Xx QEAPLRz7h1r0aUD7EDWcdFPrWFmF3LdLS2Jb/tzg4nIYof6XsmJ/ftiYtFLR05S9daUH Icd4OCBnsgxmLH3ea3Wl6YkUUOj5U17FT2Ltw+dTh7UBkAoHXNoZ9OWnAUSga0RaWHrB 904REictiYmer9dB7MjEs1lGOHhzh7lQiTTWM+dkbxUeQh7UBc/fdAH2/lZ2y1xkO/tw DAEKmkMG7a+b68RPCoNa8Dr/I7j3In7YnaLZFEeccIM86/cIjdNXU3JrEQHvrdm1uXIG xpRw== X-Gm-Message-State: AOAM530OBr/0IRYwo1AJbfKaPaXsN2lDJJHLjXZPkZJfJUea7ZJkb1CE 6d7MvuMApSjz36DLgqz2XG+g/arrJu3r9otzeXA= X-Google-Smtp-Source: ABdhPJwx9mAFQHxlsnxZLpTt+PD57LS9+Q5swTDJSIIzfaHD1GoF7b1w9rWhgoBRtrcqL/o8RTSycA0Rtg8KZ2VudoI= X-Received: by 2002:a9d:411d:: with SMTP id o29mr6419091ote.111.1631824759970; Thu, 16 Sep 2021 13:39:19 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Thu, 16 Sep 2021 14:39:08 -0600 Message-ID: Subject: Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy: "no such pool" To: Mark Millard Cc: freebsd-current Content-Type: multipart/alternative; boundary="000000000000275f3c05cc22cfa2" X-Rspamd-Queue-Id: 4H9TTV46bLz4qrK X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000275f3c05cc22cfa2 Content-Type: text/plain; charset="UTF-8" On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current < freebsd-current@freebsd.org> wrote: > What do I go about: > > QUOTE > # zpool import > pool: zopt0 > id: 18166787938870325966 > state: FAULTED > status: One or more devices contains corrupted data. > action: The pool cannot be imported due to damaged devices or data. > see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5E > config: > > zopt0 FAULTED corrupted data > nda0p2 UNAVAIL corrupted data > > # zpool status -x > all pools are healthy > > # zpool destroy zopt0 > cannot open 'zopt0': no such pool > END QUOTE > > (I had attempted to clean out the old zfs context on > the media and delete/replace the 2 freebsd swap > partitions and 1 freebsd-zfs partition, leaving the > efi partition in place. Clearly I did not do everything > require [or something is very wrong]. zopt0 had been > a root-on-ZFS context and would be again. I have a > backup of the context to send/receive once the pool > in the partition is established.) > > For reference, as things now are: > > # gpart show > => 40 937703008 nda0 GPT (447G) > 40 532480 1 efi (260M) > 532520 2008 - free - (1.0M) > 534528 937166848 2 freebsd-zfs (447G) > 937701376 1672 - free - (836K) > . . . > > (That is not how it looked before I started.) > > # uname -apKU > FreeBSD CA72_4c8G_ZFS 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #4 > releng/13.0-n244760-940681634ee1-dirty: Mon Aug 30 11:35:45 PDT 2021 > root@CA72_16Gp_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 > arm64 aarch64 1300139 1300139 > > I have also tried under: > > # uname -apKU > FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #12 > main-n249019-0637070b5bca-dirty: Tue Aug 31 02:24:20 PDT 2021 > root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 > arm64 aarch64 1400032 1400032 > > after reaching this state. It behaves the same. > > The text presented by: > > https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5E > > does not deal with what is happening overall. > So you just want to clean nda0p2 in order to reuse it? Do "zpool labelclear -f /dev/nda0p2" --000000000000275f3c05cc22cfa2--