From owner-freebsd-fs@FreeBSD.ORG Wed Nov 19 15:43:29 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1D4AE38 for ; Wed, 19 Nov 2014 15:43:28 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0078.outbound.protection.outlook.com [157.56.111.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87D1294B for ; Wed, 19 Nov 2014 15:43:27 +0000 (UTC) Received: from DM2PR0801MB0944.namprd08.prod.outlook.com (25.160.131.27) by DM2PR0801MB0944.namprd08.prod.outlook.com (25.160.131.27) with Microsoft SMTP Server (TLS) id 15.1.16.15; Wed, 19 Nov 2014 15:43:19 +0000 Received: from DM2PR0801MB0944.namprd08.prod.outlook.com ([25.160.131.27]) by DM2PR0801MB0944.namprd08.prod.outlook.com ([25.160.131.27]) with mapi id 15.01.0016.006; Wed, 19 Nov 2014 15:43:19 +0000 From: "Pokala, Ravi" To: "jose@we.lc.ehu.es" , Borja Marcos Subject: Re: BIOS booting from disks > 2TB Thread-Topic: BIOS booting from disks > 2TB Thread-Index: AQHQBA+Kh8Fld4MMbk2TOr3Zp8LvCg== Date: Wed, 19 Nov 2014 15:43:18 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.6.141106 x-originating-ip: [24.6.178.251] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0801MB0944; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:DM2PR0801MB0944; x-forefront-prvs: 04004D94E2 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(24454002)(189002)(377454003)(51704005)(62966003)(97736003)(31966008)(106356001)(99286002)(101416001)(77156002)(4396001)(77096003)(66066001)(107046002)(46102003)(36756003)(2656002)(86362001)(19580395003)(54356999)(92726001)(122556002)(20776003)(99396003)(120916001)(64706001)(21056001)(19580405001)(83506001)(2501002)(105586002)(50986999)(95666004)(106116001)(87936001)(40100003)(92566001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0801MB0944; H:DM2PR0801MB0944.namprd08.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: panasas.com Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 15:43:29 -0000 >Date: Wed, 19 Nov 2014 10:06:43 +0100 >From: Jos? Mar?a Alcaide >To: freebsd-fs@freebsd.org >Subject: Re: BIOS booting from disks > 2TB >Message-ID: <17A2AC72-AD70-480A-9BAC-9CC8EAFD572F@we.lc.ehu.es> >Content-Type: text/plain; charset=3Dus-ascii > >On Nov 19, 2014, at 8:06 AM, Pokala, Ravi wrote: > >> When you perform your installation, just make sure to select the GPT >> option for partitioning. The installer (either `bsdinstall' (for stock >> FreeBSD), or `pc-sysinstall' (for PC-BSD / FreeNAS)) should create both >> primary (near start-of-disk) and backup (at end-of-disk) GPT tables, and >> install the appropriate bootstrap code in the proper locations. >>=20 > >Yes, bsdinstall flawlessly creates both primary and backup GPT tables >even using disks > 2 TB, by virtue of the FreeBSD kernel. The problem >arises at the first stages of booting, when gptboot tries to compare the >primary and backup tables *using the BIOS disk services*, which are not >able to reach anything after the 2 TB limit. As a consequence gptboot >fails, stating that it did not find the GPT backup table. Jos=E9: Ah, I see what you're saying. That sounds reasonable. I never saw those warnings, because the version of the PMBR that I'm using at work is fairly old; it pre-dates the code to check the backup GPT if the primary is invalid [r239060]. The fact that this message is coming up at all means the primary GPT is broken. :-( Borja: I'd try booting from a different device (network, USB), then see if `gpart show' is able to list the partitions on the drive in question. If it is, then the secondary GPT is okay, and you may be able to use `gpart backup' to save out the parsed partition table. You could then use `gpart restore' to re-write the partition table to both primary and backup locations. I say that having never actually *done* it, so proceed with caution, and let us know what happens. Good luck! -Ravi >-- >Jose M. Alcaide