From owner-freebsd-current@FreeBSD.ORG Fri Jun 7 21:23:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 029AD292; Fri, 7 Jun 2013 21:23:03 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with ESMTP id D729D1664; Fri, 7 Jun 2013 21:23:02 +0000 (UTC) Received: from glenbarber.us (static-108-16-252-210.phlapa.fios.verizon.net [108.16.252.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 43AB423F848; Fri, 7 Jun 2013 17:22:58 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us 43AB423F848 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 7 Jun 2013 17:22:56 -0400 From: Glen Barber To: Jimmy Subject: Re: 10-CURRENT i386 memstick snapshots broken? Message-ID: <20130607212256.GG38117@glenbarber.us> References: <20130607205129.GA1103@jmobile.jimmy.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7lMq7vMTJT4tNk0a" Content-Disposition: inline In-Reply-To: <20130607205129.GA1103@jmobile.jimmy.net> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 07 Jun 2013 21:23:03 -0000 --7lMq7vMTJT4tNk0a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 07, 2013 at 03:51:29PM -0500, Jimmy wrote: > Greetings - >=20 > I had originally started playing with the 10-CURRENT amd64 release > a couple of months ago (no complaints here - keep up the good work!) > and had used the memstick snapshot to set things up back then with > no problems. >=20 > Now I'd like to wipe everything and switch to the i386 version, but > the memstick images (all of the last 4 or 5) seem to be broken. > My machine sees that the USB stick is there, but won't boot off of > it at all. When I do 'fdisk' on /dev/da0 with the i386 stuff loaded, > I get a invalid partition error, so on a hunch I decided to take a > closer look at the memstick images using > dd if=3Dxxx-memstick bs=3D512 count=3D1 | hd > The amd64 images look like what I would expect: some bootblock code > with a partition table at the end and the "a5" type marker. The i386 > image, however, is ALL '00'. It would appear the whatever puts those > memstick images together (src/release/i386/make-memstick.sh, perhaps?) > is failing for some reason. >=20 > Has anyone else tried the i386 memstick and having the same problem? >=20 Hmm. Thanks for the report. I'll take a look at the logs for i386, but they are generated the same way as the amd64, so in theory should not have any noticable difference. Glen --7lMq7vMTJT4tNk0a Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRsk8wAAoJEFJPDDeguUajWToH/Ap5W2isZsD5u5syVF1OkI5+ TYfUdRIvbPWiF2taXglvxUkpa1XEAtsT28vchb7AQQQBohJoVaWtTGnCvNuvIAfm ZsxcSH3EclajLXprNC/lIiLy9nja8tBzoMvTHc/Mf0tDlddXkOF31GepNMYofvu2 ppuzN0lexYIap+0l22xFr6S7+bMD/UGabDVSOWJMHsfw+ZYcrL9aNLZOBT8+aMmt N3fXzbuEwefUqnsmjemFtBPwpVnhF3PD0CBITdSRH07oK7XcV2LpfpdR/JBQwdFf UUBaImS1OE1H8d3GR9C2PHQ125o93ZjnckIDd+MTXc0IYEQ0DfdEhPxZvwmMFts= =V5cp -----END PGP SIGNATURE----- --7lMq7vMTJT4tNk0a--