From owner-freebsd-geom@FreeBSD.ORG Fri May 16 19:39:02 2014 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C4D8923D for ; Fri, 16 May 2014 19:39:02 +0000 (UTC) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 2B211211B for ; Fri, 16 May 2014 19:39:01 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 211DA3ADD8; Fri, 16 May 2014 12:38:51 -0700 (PDT) From: "Ronald F. Guilmette" To: John-Mark Gurney Subject: Re: GEOM_PART: Integrity check failed (ada2, MBR) In-Reply-To: <20140516130346.GB43976@funkthat.com> Date: Fri, 16 May 2014 12:38:51 -0700 Message-ID: <97826.1400269131@server1.tristatelogic.com> Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 19:39:02 -0000 In message <20140516130346.GB43976@funkthat.com>, John-Mark Gurney wrote: >> The result of the above operations is as follows: >> >> May 15 21:53:33 segfault kernel: ada2 at ata5 bus 0 scbus5 target 0 lun 0 >> May 15 21:53:33 segfault kernel: ada2: AT >A-8 SATA 3.x device >> May 15 21:53:33 segfault kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA >5, PIO 8192bytes) >> May 15 21:53:33 segfault kernel: ada2: 31MB (65134 512 byte sectors: 16H 63S >/T 64C) > >Wow, I just noticed this... FreeBSD is only seeing it as a 31MB drive >instead of a 1TB drive... This is probably the problem... OHHHHH! Wow! Yea. That is MESSED UP! Good eye there! I hadn't noticed THAT! >What do "diskinfo /dev/ada2" and "camcontrol identify ada2" return? I have created files containing those two outputs. Please fetch them here: ftp://ftp.tristatelogic.com/pub/ada2.diskinfo ftp://ftp.tristatelogic.com/pub/ada2.camcontrol >If it really does return that the disk is only 31MB, we need to track this >down, and this is why we're failing the integrity check of the MBR.. I don't know how to properly read/interpret these outputs, so your further guidance would be greatly appreciated. I will say however that it does appear to me that both programs _are_ indeed viewing the drive in question as (perhaps) containing only 31MB... which is indeed seriously messed up. (It is absolutely the case that the drive in question is indeed a 1TB drive.)