From owner-freebsd-fs@freebsd.org Wed Jan 4 18:51:02 2017 Return-Path: Delivered-To: freebsd-fs@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 70508C9E7D4 for ; Wed, 4 Jan 2017 18:51:02 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 4227A1163 for ; Wed, 4 Jan 2017 18:51:02 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: by mail-io0-x229.google.com with SMTP id d9so460951513ioe.0 for ; Wed, 04 Jan 2017 10:51:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kateley-com.20150623.gappssmtp.com; s=20150623; h=reply-to:subject:references:to:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=YNnHk1+PpRqRAqdZ2xiZAnkelnfYgTFdzcqD6u9Cy8U=; b=NJMNbDWkib7yI/seLD/+XWq5BEvoRc6KdIXC2c2RFoiAKYbDjw7KMhSP7HxniXYYLc jr5TqlfABCrW3YOMB1FYdyvkCc2iCruq/NRpBrfWCiCGgJNP+s0OT7P3c3dpAl/IT8EK lDy/Xj4OWBfz62TVbNQhmjrIrEA4jFHS+TmruwCOpwSlAQPIaLvJ5Va3n9ElsaChMloY gqsSTpMIYpS+1kEFdOjq6WJ7V+XKdw9qQMvcUjtiYwbA2rOj+JnOFewNIpsZNKZSsQI0 VQtiimnXMbEtNaoDrY3TJjM/wLMVTu7A9yaKeUxP1oMEp0bVvqAiqZTZriZEndUsHxH3 vNHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=YNnHk1+PpRqRAqdZ2xiZAnkelnfYgTFdzcqD6u9Cy8U=; b=fIOmbI9ESHP7pXQS1y3hoacE3CCKleYcRcosjCJpW16zM/7OSrj3HcYyg4fJv9CH3Z lZhM2jYosi9A2Qm9zaIYU3cEO9AboPdbUnAGVKv7ND1rATiP5q2ym3eKlecsV0ZTslK2 prTCVWLxnvpbNWEg7ZcpNwTC31oatASpWoE1NUvOixhN1ev8vO2NP0AbP4MIuz4gEwlQ qGI1Md5nMS1NWFqTJcH83lLDXiSBoqfrwuYELls9WgltvwAuVFYFj9oTp8ybfUqXGbDR yd8IRyAuqrBBoHLR2Qk/rdsxUWGkJdT4hKDG5Cruqg0/6NYuKQNs4/E/EXeFAtyjoLAs gn1g== X-Gm-Message-State: AIkVDXJoX/h8Ty2kOf9rctAfJbbDUWGxe7QhD5Ol5XlDHiA/1uh5AYb/vag2nsdf1FGstw== X-Received: by 10.107.159.68 with SMTP id i65mr55730972ioe.153.1483555861205; Wed, 04 Jan 2017 10:51:01 -0800 (PST) Received: from Kateleyco-iMac.local (c-75-72-30-128.hsd1.mn.comcast.net. [75.72.30.128]) by smtp.googlemail.com with ESMTPSA id y134sm18922575iod.16.2017.01.04.10.51.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 10:51:00 -0800 (PST) Reply-To: linda@kateley.com Subject: Re: Unable to import degraded zpool References: <5e87711e-83e8-b813-2224-a3c7d00d6ad0@mediture.com> To: freebsd-fs@freebsd.org From: Linda Kateley Organization: Kateley Company Message-ID: <420baa88-c405-cb2d-a4e0-8bd6042b0020@kateley.com> Date: Wed, 4 Jan 2017 12:51:00 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <5e87711e-83e8-b813-2224-a3c7d00d6ad0@mediture.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2017 18:51:02 -0000 I would have tried omnios for this.. much closer to nexenta. If you can import the pool, sometimes I can just run zpool online on the UNAVAIL drive and have it pop in.. Linda On 1/4/17 12:13 PM, Arthur Ramsey wrote: > Hello, > > I had 2 pools on Nexenta 4. One pool caused Nexenta to boot loop, so > I decided to install FreeNAS 9.10.2. No idea why it starting acting > up: no changes were made nor was a scrub started. I've previously > migrated pools from Nexenta 4 to FreeNAS 9.3 without issue. FreeNAS > reported one of the pools reported as corrupted though all disks were > online, which is the pool that was causing the boot loop I think. I > recreated that pool since the data was more easily replaceable. I had > another pool that reported as online, but it failed to import with a > missing disk error and dmesg had errors about incompatible mediasize. > One disk was shown with the blkdev name (daXXpX) in the zfs import > output and zdb -l revealed what I thought was a label for an old pool, > so I did a zpool labelclear on it; however, it still failed to import > with the same error and as expected now reported as degraded. I then > tried FreeNAS 9.3.1 and got the same missing disk error, but nothing > interesting in dmesg: http://pastebin.com/w0VBcCfy, > http://pastebin.com/NH0uyULV. No combination of -f, -F, -n, -N, -X, > -T or -o readonly=on will import the pool on FreeNAS 9.3.1, FreeNAS > 9.10.2, OpenIndiana Hipster or Ubuntu 16.04.1. On FreeNAS, I had > vfs.zfs.recover=1 and vfs.zfs.debug=1. A memory test passed on the > machine and the recreated pool seemed to work OK, but I tried moving > the pool's disks to a known good machine running FreeNAS 9.3 and I had > the same result. > > # zpool import > pool: xensr > id: 17993649064102742628 > state: DEGRADED > status: The pool was last accessed by another system. > action: The pool can be imported despite missing or damaged devices. > The > fault tolerance of the pool may be compromised if imported. > see: http://illumos.org/msg/ZFS-8000-EY > config: > > xensr DEGRADED > mirror-0 DEGRADED > gptid/f3ececf5-a319-9266-b870-bc3259f24b68 ONLINE > 5862692444503195050 UNAVAIL cannot > open > mirror-1 ONLINE > mfisyspd6p1 ONLINE > gptid/7cbacbcb-30f8-b5cd-a569-c92eea865edd ONLINE > mirror-3 ONLINE > mfisyspd5p1 ONLINE > mfisyspd4p1 ONLINE > mirror-4 ONLINE > mfisyspd3p1 ONLINE > mfisyspd1p1 ONLINE > cache > 12574043822818177481 > spares > 11626098521560667599 > logs > mirror-2 ONLINE > mfisyspd8p1 ONLINE > mfisyspd7p1 ONLINE > > # zpool import -f xensr > cannot import 'xensr': one or more devices is currently unavailable > > Could it be a bug with importing non-exported degraded pools or > unreported corruption? I tried the FreeNAS IRC channel and got some > assistance, but no solution. I cannot get logged into their forums. > The OpenZFS advises to use platform specific mailing lists. I decided > to try this mailing list. > > > Thanks, > Arthur > > This e-mail and any attachments may contain CONFIDENTIAL information, > including PROTECTED HEALTH INFORMATION. If you are not the intended > recipient, any use or disclosure of this information is STRICTLY > PROHIBITED; you are requested to delete this e-mail and any > attachments, notify the sender immediately, and notify the Mediture > Privacy Officer at privacyofficer@mediture.com. > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"