From owner-freebsd-current@freebsd.org Fri Mar 31 22:37:42 2017 Return-Path: Delivered-To: freebsd-current@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 5603DD27ECC for ; Fri, 31 Mar 2017 22:37:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward2m.cmail.yandex.net (forward2m.cmail.yandex.net [IPv6:2a02:6b8:b030::19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E74BEFAD for ; Fri, 31 Mar 2017 22:37:41 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp3h.mail.yandex.net (smtp3h.mail.yandex.net [84.201.186.20]) by forward2m.cmail.yandex.net (Yandex) with ESMTP id 43BDE21402; Sat, 1 Apr 2017 01:37:29 +0300 (MSK) Received: from smtp3h.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp3h.mail.yandex.net (Yandex) with ESMTP id 8221F440E49; Sat, 1 Apr 2017 01:37:27 +0300 (MSK) Received: by smtp3h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 5BrzMvO8Bt-bRImlgi1; Sat, 01 Apr 2017 01:37:27 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1490999847; bh=zOV2fjc5vYmvhShLu2SgF14KecsQzm2195JHgnkIktc=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=ou6hK11yw95+9+ty4nk5CxUd4C4Gd0wZKC1EuozjhboAdog6diMgkGBBwWWf3mgpf 4OMEieKNREmVvp/Y5o4r1e+EEdC2tuVuAUzx7bKv3qYPC2hfrvGkFwlu44Lw2jt03q 91AyY7N9KitVXxAz8jl8g8WPFpHklPwSQE4eJiPM= Authentication-Results: smtp3h.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: GEOM has amnesia To: Chris H , FreeBSD CURRENT References: <6b1476532d8534c90a48b8353d9f0db2@ultimatedns.net> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Sat, 1 Apr 2017 01:36:54 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <6b1476532d8534c90a48b8353d9f0db2@ultimatedns.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JRqLa4A52BwdoRQFOiFIR4h4qtvpdKrTE" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 22:37:42 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JRqLa4A52BwdoRQFOiFIR4h4qtvpdKrTE Content-Type: multipart/mixed; boundary="Ae5n7VGeqMqm1QfpHnv57KHURQkTRC7A1"; protected-headers="v1" From: "Andrey V. Elsukov" To: Chris H , FreeBSD CURRENT Message-ID: Subject: Re: GEOM has amnesia References: <6b1476532d8534c90a48b8353d9f0db2@ultimatedns.net> In-Reply-To: <6b1476532d8534c90a48b8353d9f0db2@ultimatedns.net> --Ae5n7VGeqMqm1QfpHnv57KHURQkTRC7A1 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 01.04.2017 00:58, Chris H wrote: > So. I spin up an old 11 server I have sitting in the closet, with > this external drive attached to it. I do *NOT* get the corrupt GPT > message. So I blank/partition/newfs the external drive && > mount the partitions individually to /mnt && restore again. When I > reboot to the external drive still connected to the old 11 server, > I do *NOT* receive the corrupt GPT message. WooHoo! I think. > So I re-attach the drive to the new 12 server. Reboot, and can't > boot to it && get the corrupt GPT message. >=20 > GEOM seems to be broken in 12, maybe even (recent) 11. As the 11 > server I used for testing is ~9 mos out. >=20 > What can I do to (help?) fix this mess? Just a guess, BIOS on the system, where FreeBSD 12 is installed overwrites the last sector of your disks. I have seen such reports, and always this was the cause. You can do the following steps to make sure: * on the old 11 system with the sane GPT save the last sector to some fil= e. * reboot, save the sector again to another file and compare both files. * attach the disk to your 12 system, GPT should become corrupted. Save the last sector and compare with previous file. You can look at the hexdump of this file, and probably it should be obviously what is extraneous in the data. To save the last sector you need to know its number, it can be found by this command: # diskinfo da0 | awk '{print $4-1}' Then use dd to save it: # dd if=3D/dev/da0 of=3D./sector skip=3D`diskinfo da0 | awk '{print $4-1= }'` # hexdump -C ./sector You should see something like this: 00000000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...| 00000010 d7 b2 b7 bc 00 00 00 00 af 32 cf 1d 00 00 00 00 |.........2......| 00000020 01 00 00 00 00 00 00 00 28 00 00 00 00 00 00 00 |........(.......| 00000030 87 32 cf 1d 00 00 00 00 a0 4a 4a e0 b0 0a e7 11 |.2.......JJ.....| 00000040 ba c4 54 ee 75 ad 8c c7 8f 32 cf 1d 00 00 00 00 |..T.u....2......| 00000050 80 00 00 00 80 00 00 00 22 88 eb 6d 00 00 00 00 |........"..m....| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 The dump of correct GPT header should not have more lines. --=20 WBR, Andrey V. Elsukov --Ae5n7VGeqMqm1QfpHnv57KHURQkTRC7A1-- --JRqLa4A52BwdoRQFOiFIR4h4qtvpdKrTE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlje2gcACgkQAcXqBBDI oXrv5QgAqb8MKJqmbZxUFMRMW9MVytMLgk2Eddy9RYxtswgTd5uXe1+1R3beOD+B B/SwRfrvdtFuLG6mMH6tWS7yQOeoWOzIfay95hHD3u2M7xfd11t4BCjVSMCSgH+p oI2TsPo9Mz+DWHDX8lZ82do8mx4DZv3eNF0SYwMMzCjBiU/vMVGIFqkbCxBQGA6h pEvJNZfXgyY02scbrBBbzF/EQmUYwtCmr/7eAM/WhGsSxauC2m9LrC0cllwq5/ED z/fFY20dn2DhfTvv6z8BefwaNch1gul/DGOvzhUliFZXXqaf+1YyU1ycOV2l7X9v CRO8WDGkw7b8aKHIMh9UfI0YF8XL2Q== =QG9o -----END PGP SIGNATURE----- --JRqLa4A52BwdoRQFOiFIR4h4qtvpdKrTE--