From owner-freebsd-questions@freebsd.org Thu Sep 7 09:44:48 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 648D9E14867 for ; Thu, 7 Sep 2017 09:44:48 +0000 (UTC) (envelope-from chris@cretaforce.gr) Received: from smtp3.cretaforce.gr (smtp3.cretaforce.gr [138.201.155.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.cretaforce.gr", Issuer "RapidSSL SHA256 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04E40182 for ; Thu, 7 Sep 2017 09:44:47 +0000 (UTC) (envelope-from chris@cretaforce.gr) Received: from server1.cretaforce.gr (server1.cretaforce.gr [138.201.248.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.cretaforce.gr", Issuer "RapidSSL SHA256 CA" (not verified)) by smtp3.cretaforce.gr (Postfix) with ESMTPS id 10972207DE for ; Thu, 7 Sep 2017 12:44:46 +0300 (EEST) Received: by server1.cretaforce.gr (Postfix, from userid 109) id 0336427350; Thu, 7 Sep 2017 12:44:46 +0300 (EEST) Received: from [192.168.1.6] (unknown [62.103.227.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: chris@cretaforce.gr) by server1.cretaforce.gr (Postfix) with ESMTPSA id D4F3A2734A for ; Thu, 7 Sep 2017 12:44:45 +0300 (EEST) From: Christos Chatzaras Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: problem booting from 2nd drive Date: Thu, 7 Sep 2017 12:44:45 +0300 References: <4B828DE3-C784-45A9-A01B-F944DAFE1601@cretaforce.gr> <8a798574-5d68-d6a3-259f-e971d1e30e4e@fjl.co.uk> <3C1CBEC1-5AD4-4280-8F2C-1934CD800754@cretaforce.gr> To: freebsd-questions@freebsd.org In-Reply-To: <3C1CBEC1-5AD4-4280-8F2C-1934CD800754@cretaforce.gr> Message-Id: <82B48C2A-831E-40F6-B04F-B05DA96153E8@cretaforce.gr> X-Mailer: Apple Mail (2.3273) X-Bogosity: Ham X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 09:44:48 -0000 >> Sorry, I meant hex dump of GPT. I suspect you might find they are the = same, but at different locations. See my post giving the possible = reasons why the boot code gives the messages you are getting. Its got to = be one of those, but which? I'd compile a new version of the loader that = printed out the reason for failure, but this is not suitable for = everyone. >>=20 >> I'm just guessing. Mr Block of this parish is the expert on the GPT = loader. hexdump -C -n 512 /dev/ada0p1 and hexdump -C -n 512 /dev/ada1p1 show the same result. I install the bootcode in another server in both disks again and the = boot was successful from 2nd drive. These 2 servers have only different motherboard (the server with the = problem has Fujitsu D3401-H2 and the server without the problem has = Fujitsu D3401-H1) and different disks (the server with the problem has = Seagate ST4000NM0245-1Z2107 and the the server without the problem has = Seagate ST4000NM0024-1HT178). The BIOS for server with problem is = V5.0.0.12 R1.8.0 for D3401-H2x (Release Date: 05/15/2017) and BIOS for = server without problem is V5.0.0.11 R1.21.0 for D3401-H1x (Release = Date: 05/15/2017).=