From owner-freebsd-geom@freebsd.org Sat Apr 22 19:44:22 2017 Return-Path: Delivered-To: freebsd-geom@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 4A687D4BB99 for ; Sat, 22 Apr 2017 19:44:22 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F932CC1 for ; Sat, 22 Apr 2017 19:44:21 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8E1AC2848A; Sat, 22 Apr 2017 21:44:19 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id BD8A628480; Sat, 22 Apr 2017 21:44:18 +0200 (CEST) Subject: Re: glabel problem To: Lee Brown Cc: freebsd-geom@freebsd.org References: <58FABB3A.6040704@quip.cz> <58FBAAE7.9090508@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <58FBB292.4090308@quip.cz> Date: Sat, 22 Apr 2017 21:44:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2017 19:44:22 -0000 Lee Brown wrote on 2017/04/22 21:38: > On Sat, Apr 22, 2017 at 12:11 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> This is really strange. It seems faulty to me. >> >> There are other things you can try: >> 1) try to create gpt partition of a small size - about 4GB a test geli on >> it. If it works then try to destroy this partition and create it again but >> big, about 10MB smaller than the device size (maybe there is some problem >> at the end of the device) >> >> 2) if it is not working with geli, try it with simple gpart GPT + newfs >> UFS or with ZFS. Once you have ZFS on it, you can put some files on it and >> then run zfs scrub - if device is faulty there should be some checksum >> errors in zpool status output. >> > > Thanks for that tip. 4GB worked and after some chopping I found over 8GB > failed. > Therefore I believe I've purchased an 8GB flash disk that's been engineered > to report 1TB. > I very much appreciate your help Miroslav -- lee It's sad. I hope you can return it to the seller and get your money back!