Date: Thu, 30 Oct 2014 10:09:32 -0700 From: Jin Guojun <jguojun@sbcglobal.net> To: Robert Mulholland <bobmulholland@hushmail.com>, "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org> Subject: Re: BTX Loader Hangs or Halts Message-ID: <1414688972.68684.YahooMailNeo@web180904.mail.ne1.yahoo.com> In-Reply-To: <a094de31e6044ae8036ad3315389cad8@smtp.hushmail.com> References: <a094de31e6044ae8036ad3315389cad8@smtp.hushmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Are you booting from USB DVD. If so, you may try a SATA DVD. =0A=0A=0A=0AOn= Sunday, October 26, 2014 10:44 PM, Robert Mulholland <bobmulholland@hushma= il.com> wrote:=0A =0A=0A=0AI=E2=80=99m attempting to install FreeBSD 10.0 o= n an HP/Compaq machine that has an Athlon64 x 2 processor, proprietary moth= erboard. With a WD3200AAKS drive (320 GB) installed, I get the message BTX= Loader Starting =E2=80=A6 and the system hangs. With a WD1000FYPS the BTX= Loader halts and I get a display of all the registers. I=E2=80=99m bootin= g from a DVD. Both disks tested fine in other machines. The system has 4 = GB on memory. Anyone have any ideas as to what=E2=80=99s happening? Is th= e Athlon64 x2 not supported?=0A=0A Thanks in advance= - Bob Mulholland=0A=0A=0A_______________________________________________= =0Afreebsd-hardware@freebsd.org mailing list=0Ahttp://lists.freebsd.org/mai= lman/listinfo/freebsd-hardware=0ATo unsubscribe, send any mail to "freebsd-= hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Sat Nov 1 22:44:44 2014 Return-Path: <owner-freebsd-hardware@FreeBSD.ORG> Delivered-To: freebsd-hardware@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 98F9FE1A; Sat, 1 Nov 2014 22:44:44 +0000 (UTC) Received: from potato.growveg.org (potato.growveg.org [62.49.247.163]) (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 584BCF62; Sat, 1 Nov 2014 22:44:44 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD)) (envelope-from <john@potato.growveg.org>) id 1XkhPG-000IBC-Qi; Sat, 01 Nov 2014 22:44:26 +0000 Date: Sat, 1 Nov 2014 22:44:26 +0000 From: John <freebsd-lists@potato.growveg.org> To: freebsd-hardware@freebsd.org Subject: gptboot: invalid backup GPT header Message-ID: <20141101224426.GA69717@potato.growveg.org> Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: John <john@potato.growveg.org> X-SA-Exim-Connect-IP: <locally generated> X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hardware>, <mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware/>; List-Post: <mailto:freebsd-hardware@freebsd.org> List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, <mailto:freebsd-hardware-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Nov 2014 22:44:44 -0000 Hello lists, Not sure if this is a hardware problem or a filesystem problem, so have cc'd to freebsd-fs@ The "problem" is on newly-installed freebsd 10.1 RC3. I say "problem" in inverted commas because it's not stopping it from booting and the server seems to run allright, I'm wondering if it's anything to worry about. As well as seeing gptboot: invalid backup GPT header *before* beastie starts, I see the following in dmesg: GEOM: mfid1: corrupt or invalid GPT detected. GEOM: mfid1: GPT rejected -- may not be recoverable. There are 4 disks installed - mfid0,1,2 & 3. mfid0 is a regular ufs gpt based disk. mfid1,2 and 3 together form a zfs raidz array. A thread on https://forums.freenas.org/index.php?threads/gpt-table-is-corrupt-or-invalid-error-on-bootup.12171/ describes a similar problem - the thing is though the "erroring" disk is not a GPT disk, and the one in the example was. # gpart list mfid1 gpart: No such geom: mfid1. # ls -la /dev/mfid* crw-r----- 1 root operator 0x62 Nov 1 13:37 /dev/mfid0 crw-r----- 1 root operator 0x66 Nov 1 13:37 /dev/mfid0p1 crw-r----- 1 root operator 0x67 Nov 1 13:37 /dev/mfid0p2 crw-r----- 1 root operator 0x68 Nov 1 13:37 /dev/mfid0p3 crw-r----- 1 root operator 0x63 Nov 1 13:37 /dev/mfid1 crw-r----- 1 root operator 0x64 Nov 1 13:37 /dev/mfid2 crw-r----- 1 root operator 0x65 Nov 1 13:37 /dev/mfid3 # zpool status pool: vms state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM vms ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 mfid1 ONLINE 0 0 0 mfid2 ONLINE 0 0 0 mfid3 ONLINE 0 0 0 errors: No known data errors Should I worry? -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1414688972.68684.YahooMailNeo>