From owner-freebsd-questions@FreeBSD.ORG Thu Feb 14 16:01:35 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F08E7C1D for ; Thu, 14 Feb 2013 16:01:35 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 96CCECF4 for ; Thu, 14 Feb 2013 16:01:35 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r1EG1MRB070604; Thu, 14 Feb 2013 09:01:22 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r1EG1MjQ070601; Thu, 14 Feb 2013 09:01:22 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 14 Feb 2013 09:01:22 -0700 (MST) From: Warren Block To: Scott Bennett Subject: Re: 3 TB disk troubles In-Reply-To: <201302141233.r1ECXVXx020101@mp.cs.niu.edu> Message-ID: References: <201302141233.r1ECXVXx020101@mp.cs.niu.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 14 Feb 2013 09:01:22 -0700 (MST) Cc: freebsd-questions@freebsd.org, joar.jegleim@gmail.com X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2013 16:01:36 -0000 On Thu, 14 Feb 2013, Scott Bennett wrote: > The confusing thing is that the kernel says it's a 3 TB device, > but the utility programs say otherwise. There are more than a few SATA to USB adapters that are not capable of dealing with larger devices. I've seen at least one that could not handle a 1T drive. Now that larger drives are becoming more common, the limits are often shown on the device box or description. The kernel may still identify the device correctly, possibly with different capacity detection. As mentioned, ESATA or just bypassing the SATA/USB/Firewire adapter and connecting directly to the drive should give the full capacity.