Date: Thu, 7 Sep 2017 12:44:45 +0300 From: Christos Chatzaras <chris@cretaforce.gr> To: freebsd-questions@freebsd.org Subject: Re: problem booting from 2nd drive Message-ID: <82B48C2A-831E-40F6-B04F-B05DA96153E8@cretaforce.gr> In-Reply-To: <3C1CBEC1-5AD4-4280-8F2C-1934CD800754@cretaforce.gr> References: <4B828DE3-C784-45A9-A01B-F944DAFE1601@cretaforce.gr> <8a798574-5d68-d6a3-259f-e971d1e30e4e@fjl.co.uk> <AA43F3D2-3C09-4A6E-844E-4491EDA36562@cretaforce.gr> <ED4107AC-165C-4234-8794-0FFD65B2E790@fjl.co.uk> <3C1CBEC1-5AD4-4280-8F2C-1934CD800754@cretaforce.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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. >> >> 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).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82B48C2A-831E-40F6-B04F-B05DA96153E8>