From owner-freebsd-current@FreeBSD.ORG Fri Jun 7 21:24:49 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 43E42513 for ; Fri, 7 Jun 2013 21:24:49 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 076FB167B for ; Fri, 7 Jun 2013 21:24:48 +0000 (UTC) Received: from mail.bitfrost.no (mail.bitfrost.no [46.29.221.36]) by mta.bitpro.no (Postfix) with ESMTP id E6CBD7A1B9; Fri, 7 Jun 2013 23:24:44 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at bitfrost.no Received: from laptop015.hselasky.homeunix.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hanspetter) by mail.bitfrost.no (Postfix) with ESMTPSA id 2758F2066A; Fri, 7 Jun 2013 23:24:42 +0200 (CEST) Message-ID: <51B24FEE.1090607@bitfrost.no> Date: Fri, 07 Jun 2013 23:26:06 +0200 From: Hans Petter Selasky Organization: Bitfrost A/S MIME-Version: 1.0 To: Jimmy Subject: Re: 10-CURRENT i386 memstick snapshots broken? References: <20130607205129.GA1103@jmobile.jimmy.net> In-Reply-To: <20130607205129.GA1103@jmobile.jimmy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:24:49 -0000 On 06/07/13 22:51, Jimmy wrote: > Greetings - > > 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. > > 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=xxx-memstick bs=512 count=1 | 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. > > Has anyone else tried the i386 memstick and having the same problem? > > Jimmy Hi, The memstick images does not contain an MBR. That's why some bioses won't boot them. You can fix this by using: fdisk -BI /dev/daX dd if=xxx.img of=/dev/daXs1 count=65536 --HPS