From owner-freebsd-questions@freebsd.org Wed Sep 28 18:35:10 2016 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 AE73DBEC787 for ; Wed, 28 Sep 2016 18:35:10 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 29707647 for ; Wed, 28 Sep 2016 18:35:09 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id u8SIYwwv029901; Thu, 29 Sep 2016 04:34:59 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 29 Sep 2016 04:34:58 +1000 (EST) From: Ian Smith To: David Christensen cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD-10.3-RELEASE-i386-memstick.img installer changes contents of USB flash drive In-Reply-To: Message-ID: <20160929014801.W6806@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Wed, 28 Sep 2016 18:35:10 -0000 In freebsd-questions Digest, Vol 643, Issue 3, Message: 17 On Tue, 27 Sep 2016 14:19:39 -0700 David Christensen wrote: > On 09/27/2016 08:12 AM, Ian Smith wrote: > > Just checking .. did you only access the stick by reading with dd? > > Correct. OK. > > Where? > > The last block: > > # ll > /mnt/i3000d/data/dpchrist/iso/freebsd/10.3/FreeBSD-10.3-RELEASE-i386-memstick.img > > -rw-r--r-- 1 dpchrist dpchrist 691669504 2016/09/25 11:25:37 > /mnt/i3000d/data/dpchrist/iso/freebsd/10.3/FreeBSD-10.3-RELEASE-i386-memstick.img > > # cmp -l > /mnt/i3000d/data/dpchrist/iso/freebsd/10.3/FreeBSD-10.3-RELEASE-i386-memstick.img > /dev/sdc > 691669010 351 235 << ~18 bytes into the last 512-byte block > 691669011 117 252 > 691669012 2 351 > 691669081 121 0 > 691669082 235 0 > 691669083 252 0 > 691669084 351 0 > 691669085 0 301 > 691669086 0 203 > 691669087 0 127 > 691669088 0 137 > 691669089 0 337 > 691669090 0 24 [..] > 691669495 0 227 > 691669497 0 22 > 691669498 0 163 > 691669499 0 362 > 691669500 0 372 > 691669501 0 221 > 691669502 0 230 > 691669503 0 122 > 691669504 0 256 > cmp: EOF on > /mnt/i3000d/data/dpchrist/iso/freebsd/10.3/FreeBSD-10.3-RELEASE-i386-memstick.img Right, so most of the last sector was updated. I'm no good at octal .. We discerned recently that for 10.3, i386 memstick is GPT/EFI and amd64 is still MBR/BSD. Since only the last sector differs, perhaps something has updated the secondary GPT during the installation, assuming that a GPT image should already include one - or at least, the space for one? Possibly this doesn't matter at all, but it does seem 'untidy' at best. I wonder if a hardware-write-protected GPT memstick would have issues? cheers, Ian