From owner-freebsd-stable@FreeBSD.ORG Sat Oct 11 16:40:45 2014 Return-Path: Delivered-To: freebsd-stable@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 C6F0D383 for ; Sat, 11 Oct 2014 16:40:45 +0000 (UTC) Received: from mout.web.de (mout.web.de [212.227.15.3]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.web.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63735BB9 for ; Sat, 11 Oct 2014 16:40:44 +0000 (UTC) Received: from [10.0.0.2] ([91.60.11.245]) by smtp.web.de (mrweb004) with ESMTPSA (Nemesis) id 0MH2Fm-1XQMbH0GjC-00Domo for ; Sat, 11 Oct 2014 18:35:25 +0200 Subject: Re: 3 TB USB disk From: Marc Santhoff To: freebsd-stable@freebsd.org In-Reply-To: References: <5438FAC6.3000807@chef-ingenieur.de> Content-Type: text/plain; charset="ISO-8859-15" Date: Sat, 11 Oct 2014 18:33:29 +0200 Message-ID: <1413045209.5590.5.camel@puma.das.netz> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:qON8koixBpjEiw0smbOGh2XvYMlhuAnlRalJNbO0X8N3RvO1cVU hQAu9aajEDGNBeQ7a9y+/IpGY4mDakXoO2SnA7CKjmeYHBNFelbm9v+8bwQlPTwvp+ro71k R7TKtSTpGZQJ0Lu86NqxmW91D74Y/zu23/BBEVz1C0LoqVxvOUgN9MGHjZ05BzOyFZ/P4gX bE5UUJEQFSkxRl7tclphQ== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Oct 2014 16:40:45 -0000 On Sa, 2014-10-11 at 10:26 +0000, Holger Kipp wrote: > Hi Thomas, > > > On 11.10.2014, at 11:46, "Thomas Krause" wrote: > > > > Hi, > > I connected a 3TB USB disk to a FreeBSD 9.3 server. The drive is > > recognized as 2 disks (da0: 2 TB and da1: 1TB). What is > > wrong here? > > You might need to convert the disk to GPT. It might also be the case > that the USB disk enclosure itself does not support larger disks. It's most probably the controller chip in the enclosure that cannot handle the size of the disk. Seen that myself once, the enclosure was not specified for any disk size. After buying the same model but looking for a specifiaction saying "up to 4 GB" anything worked nicely having one disk wiht full capacity. -- Marc Santhoff