From owner-freebsd-usb@FreeBSD.ORG Mon Apr 27 12:02:46 2015 Return-Path: Delivered-To: freebsd-usb@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 20FF285C for ; Mon, 27 Apr 2015 12:02:46 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 D64DF1A45 for ; Mon, 27 Apr 2015 12:02:45 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 90AB31FE023; Mon, 27 Apr 2015 14:02:43 +0200 (CEST) Message-ID: <553E2594.3080604@selasky.org> Date: Mon, 27 Apr 2015 14:03:32 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: kott , freebsd-usb@freebsd.org Subject: Re: usb write error References: <1430118496759-6007874.post@n5.nabble.com> <553E0EE0.60701@selasky.org> <1430133010408-6007910.post@n5.nabble.com> <553E1A22.7000402@selasky.org> <1430134369152-6007915.post@n5.nabble.com> <1430135707453-6007921.post@n5.nabble.com> In-Reply-To: <1430135707453-6007921.post@n5.nabble.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2015 12:02:46 -0000 On 04/27/15 13:55, kott via freebsd-usb wrote: > Hello - > >>From this command it shows the LBA is beyond disk size ? >>From this o/p it show disk address can go up to 0x3bafb0, whereas in the > Write command it accesses 0x3bafff? any idea why this may happen? > # gpart show /dev/da0 > => 40 3911600 da0 GPT (1.9G) > 40 3911600 - free - (1.9G) > > Kott Hi, 3911600 = 3BAFB0 So clearly: 0x3bafff is outside that range and cannot be read nor written. --HPS