From owner-freebsd-questions@FreeBSD.ORG Mon Mar 31 18:20:51 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4152CCB7; Mon, 31 Mar 2014 18:20:51 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01B64200; Mon, 31 Mar 2014 18:20:50 +0000 (UTC) Received: by mail-ig0-f181.google.com with SMTP id h18so3825929igc.14 for ; Mon, 31 Mar 2014 11:20:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=caiHPSC14gCtqnE45tRKYm/MV69J+IM06fMsbOmtIGw=; b=eih5+bRJtSIovmnaLp4XMVxXED1m9xW/bCRpmd2CAFWgz9PonpW9xc1IguNMUw63VI t90BwwwyXN96xZh+WIKv1Ytxxgd6heLohO4apt+JBm9mMToLGveyq5PUBgl7TXuIiViV sh/oWh8IQnpvbTEyx2e+67G6YvDHHpCJnWoowlCEQP/7eukS8HQbq/9H8NMG7BtvoGu/ e6ReX4wpiKi/nOD0PZLRH8Yec0SySFIvkDLsLqGT8qDrYZrJfq8k/ijvEAKdLZPWrSQv OoZLQRm03iak1SuwQd1IgJj2+HTRS51Epjq03bBoSdi9KISKptX9Xj90inKU+9nTpicx 5h5A== MIME-Version: 1.0 X-Received: by 10.42.43.136 with SMTP id x8mr5212793ice.85.1396290049647; Mon, 31 Mar 2014 11:20:49 -0700 (PDT) Sender: vrwmiller@gmail.com Received: by 10.64.235.212 with HTTP; Mon, 31 Mar 2014 11:20:49 -0700 (PDT) In-Reply-To: References: <024701cf4aa7$f68be1b0$e3a3a510$@FreeBSD.org> <066f01cf4cff$178e0ab0$46aa2010$@FreeBSD.org> Date: Mon, 31 Mar 2014 14:20:49 -0400 X-Google-Sender-Auth: JBtVtfg5g1IC4fwcRqSoKPLtaQ0 Message-ID: Subject: Re: FreeBSD 10 custom bootonly ISO error From: Rick Miller To: Devin Teske Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2014 18:20:51 -0000 Fixed, see thread below... On Mon, Mar 31, 2014 at 1:22 PM, Rick Miller wrote: > > On Mon, Mar 31, 2014 at 12:34 PM, wrote: > >> >> >> > -----Original Message----- >> > From: Rick Miller [mailto:vmiller@hostileadmin.com] >> > Sent: Monday, March 31, 2014 7:33 AM >> > To: Devin Teske >> > Cc: FreeBSD Questions >> > Subject: Re: FreeBSD 10 custom bootonly ISO error >> > >> > On Fri, Mar 28, 2014 at 1:05 PM, wrote: >> > >> > > >> > > > Hi all, >> > > > >> > > > I will customize the FreeBSD 10 bootonly ISO to perform a >> > > non-interactive, >> > > > automated OS installation. The initial ISO was built via release.sh >> > > > and >> > > was >> > > > successfully tested for boot functionality prior to touching >> > > > ${CHROOTDIR}/usr/obj/usr/src/release/bootonly/etc/installerconfig >> > > > and running mkisofs on bootonly/ generating a new bootonly ISO. >> > > > >> > > > NOTE: mkisofs command used: mkisofs -R -no-emul-boot -b boot/cdboot >> > > > -o bootonly.iso bootonly >> > > > >> > > > Booting the new ISO via a vmware 5.x VM resulted in an error >> > > > mounting the filesystem[1] (see image in reference [1]). Manually >> > > > entering the "mount from" here[2] (cd9660:/dev/cd0) resulted in the >> > > > system continuing to boot into bsdinstall as expected. >> > > > >> > > > The error appears to suggest using /dev/acd0, despite the the first >> > > > line >> > > in the >> > > > output of bootonly_iso_error.png suggesting the CD-ROM device is >> > > > actually /dev/cd0. I'm inclined to believe I missed a step normally >> > > > performed >> > > during >> > > > execution of release.sh (such as editing >> > > > bootonly/boot/defaults/loader.conf), but have been unable to >> > > > ascertain what. Any feedback or clues would be greatly appreciated. >> > > > >> > > > [1] http://www.hostileadmin.com/images/bootonly_iso_error.png >> > > > [2] http://www.hostileadmin.com/images/bootonly_iso_cdboot.png >> > > > >> > > >> > > You didn't give the ISO a label. It actually doesn't look for cd0 nor >> > > acd0 but FREEBSD_INSTALL label which ends up in /dev/iso9660/ >> > > >> > >> > I regenerated the ISO using "-V FREEBSD_INSTALL" and "-volset >> > FREEBSD_INSTALL", neither of which produced a result beyond the original >> > error. Thoughts? >> > >> >> My bad, it appears to be camel-case "FreeBSD_Install". See lines 205-212 >> of >> >> http://svnweb.freebsd.org/base/head/release/Makefile?revision=262505&view=ma >> rkup >> >> > > I assumed caps was the correct syntax based on something found in the > archives that suggests this[1], but using "FreeBSD_Install" failed as well. > > [1] > http://lists.freebsd.org/pipermail/freebsd-amd64/2013-April/015251.html > I chose to generate the iso the same way it is done in release/Makefile as opposed to running mkisofs on it and the resulting ISO booted as expected. Thanks for the help, Devin. -- Take care Rick Miller